Related
...someone calls while you happen to be flashing your rom, radio or otherwise? Will it brick the phone?
I finally bit the bullet and managed to unlock and flash a new rom into my T-Mobile MDA last night.
Just a few minutes ago, I was about to upgrade my radio rom and right before I clicked to start the process, I got a phone call.
Now, I realize I may be lucky as hell because I have a feeling the phone could've been bricked.
I don't recall ever seeing any warnings to actually turn off the phone function while doing any rom updates, but I guess this should've been common sense in my part.
Anyway, like I said, I'm curious, anyone know what actually happens?
therocketeer said:
...someone calls while you happen to be flashing your rom, radio or otherwise? Will it brick the phone?
I finally bit the bullet and managed to unlock and flash a new rom into my T-Mobile MDA last night.
Just a few minutes ago, I was about to upgrade my radio rom and right before I clicked to start the process, I got a phone call.
Now, I realize I may be lucky as hell because I have a feeling the phone could've been bricked.
I don't recall ever seeing any warnings to actually turn off the phone function while doing any rom updates, but I guess this should've been common sense in my part.
Anyway, like I said, I'm curious, anyone know what actually happens?
Click to expand...
Click to collapse
as far as i know i don't think anything happens. just ignore the call. when booting the room the rom updater tool will reboot the phone regardless if the phone is ringing or not. someone correct me if im wrong.
therocketeer said:
...someone calls while you happen to be flashing your rom, radio or otherwise? Will it brick the phone?
Click to expand...
Click to collapse
Once your phone screen goes black, then I believe all functions, phone/pda ceases to work until it boots back up with the new ROM.
i dont think the phone would even know it has an incoming call, since all the software is basically in the process of being overwritten with the newer one...
The phone will go into the bootloader no software will be loaded so you wont have to worry about phone calls, text messages, etc. there is no interface during flashing, just a progress bar.
oh
Ok thanks guys. That's good to know I don't have to worry about it. It was pretty funny though since I didn't know what would've happened, my heart almost skipped a beat thinking my phone almost got bricked by a phone call.
Thanks again!
I just received my galaxy note n7000 back from Samsung service centre after 2 months wait.
However, I noticed the phone speaker does not work somehow. Yesterday, I was able to call and hear notification sounds for a while and then I lost all the sounds from the phone after few hours later. I decided to talk to samsung tech team but when I looked my phone again this morning, it worked perfectly. Everything worked again. However, now I don't hear anything from the phone again. I have no idea what is going on since it worked this morning. I wanted to ask you guys first since I seriously don't want to wait another 2 months to use my phone and I believe it might be related to software bug since the sound worked again. Is there any known issue with that?
if u think it's sw related then flash a stock rom from ur region thru pc Odin.
it might be the volume bug ringer issue, try to simulate by increasing the volume under settings >sounds.. notifications, systems, media, ringtones and etc...
use your phone as you would use it and check back those settings again if they've been lowered or decreased by one notch. If you do notice that, then definitely it's a bug on the stock ICS firmware.
Same Problem
I am having the same problem. I'm pretty sure it's a hardware problem, as I've tried changing all kinds of settings, turning the device completely off and back on, etc. And none of it makes any difference. It just doesn't work at all sometimes, and works just fine other times. I've even had it stop working in the middle of playing a sound.
Anyone know anything about this, or if there's any fix for it? I guess I'm going to try to get my device replaced, as it is still under warranty. I'm just worried that everything's going to work fine when I go to get it replaced, only to stop working once I get home.
Hello!
Wifi and Bluetooth aren't working anymore When you try turning them on, them just turn off immediately. It has been going on after KitKat 4.4.3 update.
It's the same situation this member described in this thread: >>>>http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-bluetooth-issues-t2808419<<<<
He also uploaded a video about this issue: >>>>youtube . com / watch? v = girqFv6eWnQ<<<<
I also have been reading this threads:
>>>>http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-isnt-t2760479<<<<
>>>>http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308<<<<
and the solution for this would be replace the WCNSS_qcom_wlan_nv.bin in the Persist folder. As my phone is not rooted, it seens impossible I had accidently deleted this file, right? Anyway, the Persist folder of my phone is empty. It's because my phone is not rooted so it doesn't show the files inside the folder? At the wlan/prima, there are the following files:
WCNSS_cfg.dat
WCNSS_qcom_cfg.ini
WCNSS_qcom_wlan_nv.bin (that's the file, right?)
WCNSS_qcom_wlan_nv_calibration.bin
WCNSS_qcom_wlan_nv_regulatory.bin
Is there some possible solution or I really need to send my phone to technical support?
I'm sorry about my English and my poor knowlegde. Thank's a lot!
rafaelrossignoli said:
Hello!
Wifi and Bluetooth aren't working anymore When you try turning them on, them just turn off immediately. It has been going on after KitKat 4.4.3 update.
It's the same situation this member described in this thread: >>>>http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-bluetooth-issues-t2808419<<<<
He also uploaded a video about this issue: >>>>youtube . com / watch? v = girqFv6eWnQ<<<<
I also have been reading this threads:
>>>>http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-isnt-t2760479<<<<
>>>>http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308<<<<
and the solution for this would be replace the WCNSS_qcom_wlan_nv.bin in the Persist folder. As my phone is not rooted, it seens impossible I had accidently deleted this file, right? Anyway, the Persist folder of my phone is empty. It's because my phone is not rooted so it doesn't show the files inside the folder? At the wlan/prima, there are the following files:
WCNSS_cfg.dat
WCNSS_qcom_cfg.ini
WCNSS_qcom_wlan_nv.bin (that's the file, right?)
WCNSS_qcom_wlan_nv_calibration.bin
WCNSS_qcom_wlan_nv_regulatory.bin
Is there some possible solution or I really need to send my phone to technical support?
I'm sorry about my English and my poor knowlegde. Thank's a lot!
Click to expand...
Click to collapse
There is no way to prove that persist is vacant as you are unrooted. It is most likely a coinsident hardware failure. But still possible.
Go warranty replacement. Rsd restore is no help as persist is not in the XML.
aviwdoowks said:
There is no way to prove that persist is vacant as you are unrooted. It is most likely a coinsident hardware failure. But still possible.
Go warranty replacement. Rsd restore is no help as persist is not in the XML.
Click to expand...
Click to collapse
For first, thank you for your concern.
I see. It's a poor situation we have been seeing with others Moto X owners, especially after 4.4.3 update. Considering it's not a hardware issue and 4.4.4 update release (my phone is still in 4.4.3), is the 4.4.4 update worth it? I have been reading about increasing battery consumption after 4.4.4 update. I also have read about restoring the stock rom could be a worth try, even if your phone has never been rooted. What you say?
rafaelrossignoli said:
For first, thank you for your concern.
I see. It's a poor situation we have been seeing with others Moto X owners, especially after 4.4.3 update. Considering it's not a hardware issue and 4.4.4 update release (my phone is still in 4.4.3), is the 4.4.4 update worth it? I have been reading about increasing battery consumption after 4.4.4 update. I also have read about restoring the stock rom could be a worth try, even if your phone has never been rooted. What you say?
Click to expand...
Click to collapse
I have a Maxx now on 444, not rooted & 444 is fine. There is much feedback on x 444 around.
aviwdoowks said:
I have a Maxx now on 444, not rooted & 444 is fine. There is much feedback on x 444 around.
Click to expand...
Click to collapse
So I will try to update it on 4.4.4. A last question I forgot asking: my 3/4G is working fine. 3/4G has nothing to do with wifi/bluetooth hardware/software, right?
rafaelrossignoli said:
So I will try to update it on 4.4.4. A last question I forgot asking: my 3/4G is working fine. 3/4G has nothing to do with wifi/bluetooth hardware/software, right?
Click to expand...
Click to collapse
Correct.
I've sent my phone warranty. I'm a previous contact they told me it's probably a hardware issue. The battery comsumption has increased a lot and the explanation is that phone is constantly searching for wifi/bluetooth. Is it possible even with hardware failure?
When I get my phone back tell you what was it's problem and the possible solution.
Wifi and bluetooth had started working from nothing. Then, it stopped again. And it went this way several times since. Now, it's working properly, but it may stop anytime. Could it still be a hardware issue? I just have updated 4.4.4 yesterday. In one of the situations, I found the message "supplicant status: scanning".
rafaelrossignoli said:
Wifi and bluetooth had started working from nothing. Then, it stopped again. And it went this way several times since. Now, it's working properly, but it may stop anytime. Could it still be a hardware issue? I just have updated 4.4.4 yesterday. In one of the situations, I found the message "supplicant status: scanning".
Click to expand...
Click to collapse
Yes. based on the information you have provided, and my personal experience, I would suspect a hardware failure.
samwathegreat said:
Yes. based on the information you have provided, and my personal experience, I would suspect a hardware failure.
Click to expand...
Click to collapse
Well, wifi and bluetooth aren't working anymore since my last post. There's a big battery drain - something like 60% of battery life in 3 hours with phone - supposedly - in sleep mode, even when it is in airplane mode. It seems the system tries to find wifi and bluetooth. When I see my battery status, Android OS and Android System processes are draining more battery life than screen itself. Could it be a hardware failure even if wifi and bluetooth get back working sometimes?
I think I'll buy a lower cost android phone if I decide sending my Moto X warranty. It's complicated staying without a smartphone during 20~30 days.
I appreciate you all for the help and considerations.
Update: sending my Moto x warranty. Tell you what was wrong when I get it back
crappy wifi
rafaelrossignoli said:
Update: sending my Moto x warranty. Tell you what was wrong when I get it back
Click to expand...
Click to collapse
Have you managed to get an update? I think I am having the same exact problems.
Not a developer device so can't unlock the bootloader
Not rooted. \persist\ is empty if that would make any difference at all.
Surprisingly once when I restarted the phone in bptools menu options on the boot menu, the phone came up fine and I was able to turn on my wifi and bluetooth. After about 10 minutes, the phone restarted on it's own and ever since they won't turn on.
Did a full wipe, FDR and also wiped cache but still the same now. Booting using BPTools menu option doesn't help any more.
For the last couple weeks, my phone is just guzzling data on 4G. Having a wifi would help. Please don't suggest me to do a warranty repair That is what I might end up doing in about two weeks. The unlocked device was bought in India but I am now abroad.
Using XT1052 running Kitkat 4.4.4 - AsiaRetail.
mutukrp said:
Have you managed to get an update? I think I am having the same exact problems.
Not a developer device so can't unlock the bootloader
Not rooted. \persist\ is empty if that would make any difference at all.
Surprisingly once when I restarted the phone in bptools menu options on the boot menu, the phone came up fine and I was able to turn on my wifi and bluetooth. After about 10 minutes, the phone restarted on it's own and ever since they won't turn on.
Did a full wipe, FDR and also wiped cache but still the same now. Booting using BPTools menu option doesn't help any more.
For the last couple weeks, my phone is just guzzling data on 4G. Having a wifi would help. Please don't suggest me to do a warranty repair That is what I might end up doing in about two weeks. The unlocked device was bought in India but I am now abroad.
Using XT1052 running Kitkat 4.4.4 - AsiaRetail.
Click to expand...
Click to collapse
For first, thank you for reminding me about this thread. I bring bad news for you, unfortunately. It's 99% a hardware failure. In my case, it really was one. After 25 days, my phone was back from warranty with a new wifi/bluetooth hardware.
My phone was behaving the same way as yours. Sometimes the wifi was back working for a while, then my phone restarted and wifi was unavailable again. So, i recommend you send your phone warranty as soon as possible. Good luck!
rafaelrossignoli said:
So, i recommend you send your phone warranty as soon as possible. Good luck!
Click to expand...
Click to collapse
Well, I don't think I really have a choice here. I would be able to give my device for service only in about another 2 weeks so I have to live with 4G! I'll let you know how it goes. And thanks for the update...
wifi and bluetooth not turning On FIX
Hello everybody.i use a moto x (xt1052) 4.4.4 kitkat not rooted.
A week ago started having problems with wifi communication not turning on and a couple of days later bluetooth couldnt locate any connections
I fixed these problems by switching to ART Runtime from the developer settings.this will reboot your phone and starts upgrading your apps .after that wifi and bluetooth work fine .(for now..)
I am also wondering if anyone has any random reboots or its just my pocket..
Hope it helps for you too.
Cheers,Stelios
Updated: WiFi and Bluetooth stopped working again.leaning more on software issue than hardware.
are.petrakis said:
I fixed these problems by switching to ART Runtime from the developer settings.this will reboot your phone and starts upgrading your apps .after that wifi and bluetooth work fine .(for now..)
Updated: WiFi and Bluetooth stopped working again.leaning more on software issue than hardware.
Click to expand...
Click to collapse
Nope, that didn't help me at all. I think at least my issue is hardware related. Giving the phone for warranty repair on Thursday, let's see what happens.
Update
Been to the service center a week ago. Apparently the moment I explained my issue, they said it is an hardware issue and so the board needs a replacement. Got my phone back and it has been a week with no issues. Fingers crossed...
I've had it since Saturday and so far its done it 3 times.
Once yesterday just when I was trying to open the phone with the fingerprint sensor and twice now today when trying to do something with the phone connected to Bluetooth.
This morning I was trying to set up the connection to my in car TomTom Toyota 2 unit for the first time. Got part way through the process then it failed then when i tried again the phone rebooted then it worked.
This afternoon I turned on my Bluetooth connected to the car but it wouldn't do anything then the phone froze and rebooted but then it all worked fine.
I'm not giving up yet but its making me a bit nervous having these issues so soon (better now than later i guess). If it happens more this week ill take it back and might see about a different phone.
Just curious if anyone else has had similar?
This Bluetooth device worked fine previously with my Nexus 5X also on Oreo so its fine software compatibility wise.
Oblox said:
Just curious if anyone else has had similar?
Click to expand...
Click to collapse
I haven't, and I use BT in the car everyday.
Thanks. I'll see if it happens again this week and take mine back if so.
No, I haven't had a single reboot in the 6 days that I own the device.
Oblox said:
I've had it since Saturday and so far its done it 3 times.
Once yesterday just when I was trying to open the phone with the fingerprint sensor and twice now today when trying to do something with the phone connected to Bluetooth.
This morning I was trying to set up the connection to my in car TomTom Toyota 2 unit for the first time. Got part way through the process then it failed then when i tried again the phone rebooted then it worked.
This afternoon I turned on my Bluetooth connected to the car but it wouldn't do anything then the phone froze and rebooted but then it all worked fine.
I'm not giving up yet but its making me a bit nervous having these issues so soon (better now than later i guess). If it happens more this week ill take it back and might see about a different phone.
Just curious if anyone else has had similar?
This Bluetooth device worked fine previously with my Nexus 5X also on Oreo so its fine software compatibility wise.
Click to expand...
Click to collapse
Have you tried performing a factory reset? It might fix your problem. If it persists, then you can send it back for a replacement.
Rebooted again today just in the camera.
Not tried a factory reset yet, will take it into store today and see what they say is best to do. Don't mind doing a reset but then its waiting again to see if it does it again after which isn't something I can easily replicate.
If i can get a new unit id prefer that so i can see if its just my current one with an issue, even with the pain of having to buy a new screen protector.
Lazaros_K said:
Have you tried performing a factory reset? It might fix your problem. If it persists, then you can send it back for a replacement.
Click to expand...
Click to collapse
If the factory reset doesn't work, install the Sony Companion software and run a software repair on it. That may fix the issue. Mine hasn't restarted at all in the 24 hours I've had it, even after using Wifi, Bluetooth, installing lots of apps, using 3G and 4G... However, I installed Newpipe via F-Doid and it crashed at least 4 times on me when I left the video I was watching and came back to it.
No reboots. Two days of heavy use.
I factory reset it soon as I received it and firware update poped up.
Oblox said:
Not tried a factory reset yet, will take it into store today and see what they say is best to do. Don't mind doing a reset but then its waiting again to see if it does it again after which isn't something I can easily replicate.
Click to expand...
Click to collapse
No reboot, have had phone for over a week now.
What did the store recommend you do? Here, they always suggest you factory reset first, same with going to the service center, they actually do that first thing when you send in for repairs.
What did you eventually do? Did it solve your problem?
mhaha said:
No reboot, have had phone for over a week now.
What did the store recommend you do? Here, they always suggest you factory reset first, same with going to the service center, they actually do that first thing when you send in for repairs.
What did you eventually do? Did it solve your problem?
Click to expand...
Click to collapse
I took it into a store the other day and they had no stock so i'm taking it to a different one today. The store i went to said it would be no problem though as id not had it long. Its been rebooting still a few times just when sitting in my pocket doing nothing, ive had the must enter pin after reboot message.
Well on the way to store speaking to my wife (also with XZ1 compact) her phone froze mid call and rebooted. When she rang back she said she was showing a software update. Checked mine when parked and i had it too.
Sony rep happened to be in store today so told him the issue, he had one himself and hasn't experienced or heard of this but said to do a repair with xperia companion to clean flash the new firmware on both our phones. If still having issues then theres nothing more we could do ourselves and bring back to store to swap.
I have another week in which i can change phone or another 3 weeks to swap for a new XZ1 compact.
Will do repairs tonight and hope the problem goes away.
Repaired friday evening, phone rebooted randomly again after freezing sunday. Taking in today to swap for a new unit.
If any similar problems this week with the new one ill ask to swap to a different phone entirely.
Probably need a software update. Mine is running fine on 47.1.A.2.324
Sent from my G8441 using Tapatalk
No i updated that on friday before repairing and the repair had that version too and it still rebooted sunday and today.
Me and my wife got a new unit now so will see how these ones go.
got my first reboot today after plugging the headphone... weird...
profyler said:
got my first reboot today after plugging the headphone... weird...
Click to expand...
Click to collapse
Not good if others are getting this too, lets hope it was a one off for you.
So far just setup and listened to music on my new phone and all is good but there's no pattern to what causes the reboot so will see how the next few days go.
My XZ1 Compact also has the reboot-issue...
Mine has just done the fourth reboot in just a little more than one week. In different situations, with bluetooth in use and without. Once when I tried to call someone, once when I was searching for wifi networks and the other two times in pretty normal "just using it" situations.
As not everyone is having those issues, I think it is some hardware defect and I need to get the phone replaced, right?
Harry
flyhigh79 said:
Mine has just done the fourth reboot in just a little more than one week. In different situations, with bluetooth in use and without. Once when I tried to call someone, once when I was searching for wifi networks and the other two times in pretty normal "just using it" situations.
As not everyone is having those issues, I think it is some hardware defect and I need to get the phone replaced, right?
Harry
Click to expand...
Click to collapse
Difficult to tell. A hard reset might help but it could also be a problem with Android 8 on xz1 that wasnt very well optimized..
Id get the handset replaced, 'repairing' didn't do anything for my issue. Only time will tell if my new handset has the same issues and same for you.
Well this morning I got in the car to go to work and went to turn on bluetooth. Tried OK google no response at all, went to manually unlock and it sat on the lock screen my finger prints not working and wouldnt swipe up for PIN entry. Mic and camera toggle reacted to swipes but didnt do anything. Then it rebooted.
Bye bye Xperia XZ1 Compact, the potential was there but rebooting and dodgy camera is too much to hope for a fix for.
Looking for help on this one. Every 3-5 days my Ultra gets into a state where no voice can be heard by either myself or the person on the other phone when a call is made or received, but I can hear the ring tone if I'm calling prior to the person answering, and my phone rings as normal if someone calls me. But when answering the call it's just silence on both sides. A reboot fixes this only for it to happen again 3-5 days later, requiring another reboot.
At first I assumed it was a corruption of the rom I had installed, so I flashed back to my stock image with Odin, including a fresh VOD CSC install. Unfortunately, it's still happening after this. Speaking as an engineer, it's unusual but not unheard of for a device to have a hardware issue of this type and it be rectified each and every time with a reboot, that would normally point to a software/firmware error of some sort. However, the fact it's continuing to happen after a completely fresh re-flash of stock Android suggests my worst fears that it is hardware. I could try some things, like not installing Magisk or even re-locking my bootloader, but I don't believe either would be a factor. I only used Magisk for rooting and don't install additional modules. I've also ruled out the sim card or sim slots by swapping to an e-sim, only for it to still happen.
Anyway, any suggestions would be welcome, especially if you have suffered something similar. There is an easy fix, which is to schedule a reboot every morning at around 3am, but I'd sooner not have to do this before working out what the underlying cause is.
I don't have a solution for you but I just wanted to share that I am having the same issue. But I'm not using Magisk and not unlocked, or rooted. The only thing I did was flash stock Samsung and disable some bloat.
I was having the issue the other night (for the second time) when calling my carrier (AT&T) about an order. I just assumed it was them at first. I disabled wifi calling (after them not hearing me several times) then tried again and it worked.
Were you using wifi calling at the time? I haven't been able to reproduce the issue yet so I don't know if disabling wifi calling had anything to do with it working.
Just to clarify, you say you're using Magisk but you're not unlocked or rooted? That isn't possible, but perhaps you just worded it wrong and you meant you're not using Magisk.
Funny you should mention Wifi-Calling, when it happened a few weeks back I force closed Wifi calling in an attempt to track down any potential services that might be causing the problem. And when I did that the calling started working again without a reboot. I thought I'd tracked it down and thought I'd test it again once it happened again a few days later, I would then freeze wifi-calling (something I never use) which would hopefully stop it ever re-occurring. However, the second time I force stopped wifi-calling it didn't fix the issue.
Beefheart said:
Just to clarify, you say you're using Magisk but you're not unlocked or rooted? That isn't possible, but perhaps you just worded it wrong and you meant you're not using Magisk.
Funny you should mention Wifi-Calling, when it happened a few weeks back I force closed Wifi calling in an attempt to track down any potential services that might be causing the problem. And when I did that the calling started working again without a reboot. I thought I'd tracked it down and thought I'd test it again once it happened again a few days later, I would then freeze wifi-calling (something I never use) which would hopefully stop it ever re-occurring. However, the second time I force stopped wifi-calling it didn't fix the issue.
Click to expand...
Click to collapse
I missed a word when I first replied. I added "not" to Magisk but you must have seen it before I fixed it.
I've had many work meetings (on phone) since then and haven't had it pop up. I haven't changed anything and even have wifi calling back on, so I'm at a loss.
OK, traced this to possibly be linked to the attached logcat. Any suggestions?
Also, contrary to my claim in the opening post, the dial tone can only be heard sometimes.
An additional oddity, whilst the fault is occurring (prior to a reboot), voice calls on WhatsApp work fine.
Perhaps a form of modem fault?
I give up on this. I flashed the stock VOD rom in Odin and relocked the bootloader to take it as close to stock as possible (minus the knox flag being tripped which is unavoidable at this point) and it still showed the issue after a couple of days. I've also disabled Bluetooth at a service level to no avail as I thought it might be a glitch with that.
It's clearly a hardware issue that will only be resolved with a logic board replacement. Which currently aren't available.
One good thing is that a full reboot isn't required to fix it, a soft reboot seems to do it. So I've got a link to do that on my home page, only takes 10-15 seconds.
Beefheart said:
OK, traced this to possibly be linked to the attached logcat. Any suggestions?
Also, contrary to my claim in the opening post, the dial tone can only be heard sometimes.
Click to expand...
Click to collapse
Hi, sorry to re-open this old topic. My S21 has the same problem from the beginning, but I have the stock rom. Did you get this log using *#9900# tool? Which log level did you use? Which file is the attached one? BTW, I'm almost sure that it's an hardware failure, did you solve it? Thanks
nrg84 said:
Hi, sorry to re-open this old topic. My S21 has the same problem from the beginning, but I have the stock rom. Did you get this log using *#9900# tool? Which log level did you use? Which file is the attached one? BTW, I'm almost sure that it's an hardware failure, did you solve it? Thanks
Click to expand...
Click to collapse
I'm afraid not, I ended up selling it as parts or repair a few weeks after that post.
Beefheart said:
I'm afraid not, I ended up selling it as parts or repair a few weeks after that post.
Click to expand...
Click to collapse
Thanks anyway, I will try to bring mine to the repair center.