Database Develop

[Q] Moto X (NOT ROOTED) - Wifi and Bluetooth problems

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...

[Q] nexus 6 after new 5.1.1 update BIG PROBLEM(Keeps turning off

Hi , ive done all i can before coming here for help but this is my last resort as im stumped. About a month ago i updated my phone to the latest Android version on my Nexus 6. Literally straight after the update my phone began to play up. It started turning itself off at random times , not when i did a specific thing it could be anything and at any time. Spoke to Motorola and they were no use , so cleared my phone did a reset and still the same occurrence, as it was still on the newest version. But what i found was when the phone was plugged into the mains it didn't go off at all, but then again this problem happened right after the update. SO the next thing i have done is custom ROM but again the device will turn off randomly .I really need help as ive only had this phone since January and ive not been able to use it.
Thanks in advance

Sounds like battery defect. Has same issue on my n4 with regards to being ok when plugged in
Sent from my Nexus 6 using Tapatalk

benthebratt said:
Hi , ive done all i can before coming here for help but this is my last resort as im stumped. About a month ago i updated my phone to the latest Android version on my Nexus 6. Literally straight after the update my phone began to play up. It started turning itself off at random times , not when i did a specific thing it could be anything and at any time. Spoke to Motorola and they were no use , so cleared my phone did a reset and still the same occurrence, as it was still on the newest version. But what i found was when the phone was plugged into the mains it didn't go off at all, but then again this problem happened right after the update. SO the next thing i have done is custom ROM but again the device will turn off randomly .I really need help as ive only had this phone since January and ive not been able to use it.
Thanks in advance
Click to expand...
Click to collapse
Yes, absolutely sounds like the battery issue that is somewhat common. Best to RMA at this point because the next step is that the battery starts to expand.
You can, in the meantime, boot into bootloader, and select bootloader logs. Press power to select and then reboot. This clears and calibrates the battery stats. Most likely, the issue will return.

Evolution_Tech said:
Yes, absolutely sounds like the battery issue that is somewhat common. Best to RMA at this point because the next step is that the battery starts to expand.
You can, in the meantime, boot into bootloader, and select bootloader logs. Press power to select and then reboot. This clears and calibrates the battery stats. Most likely, the issue will return.
Click to expand...
Click to collapse
Thanks for the reply, what does RMA mean ? ive done that calibrating but didnt turn on . Also i spoke to Motorola and they said as i have a cracked screen they will have to replace that before reparining costing £120

benthebratt said:
Thanks for the reply, what does RMA mean ? ive done that calibrating but didnt turn on . Also i spoke to Motorola and they said as i have a cracked screen they will have to replace that before reparining costing £120
Click to expand...
Click to collapse
Return merchandise authorization.

Lollipop causing phone to turn off

Idk what's the problem with Samsung phones and updates. I had the same problem with my Note 3 when KitKat got released, I had to get a replacement phone. Lucky for me the replacements Note 3 didn't have the update on it. However I wasn't so lucky with the Note 4.
I accidently hit the update on my notifications when I was half sleep.
Anyways.
Every since Lollipop been installed on my Note 4, it has been a nightmare from hell.
When I installed it on my original Note 4, I kept having my keyboard become unresponsive. Force close on multiple apps (stock Web, camera, calender, and more).
I called T-Mobile to see if they could send me a replacement. They "tried" to fix it, saying that I should do a factory reset and clear cache , which I already tried before I called numerous times.
Finally they said they said they were going to send me out a replacement phone.
I also asked if anyone have been complaining about Lollipop they said no, they were totally oblivious to Lollipop having any kinks (as always ). It's crazy they said that because I have read over 100 post bashing the new update.
I received the Note 4. I turned the phone on and Lollipop was already installed. I called T-Mobile and asked why was Lollipop installed on my replacement, they informed me that they are sending out the phones with Lollipop, and assured there would be no problems with it.
With in the first hour, my phone would turn off and not turn back on. I knew there was nothing wrong with the battery because it was on 90% and it worked flawless with another phone. So I drained all the electricity out the phone and put the battery back in. That worked, but it did over 20 times within that day. I called T-Mobile again , they told me I would have to go to a store and see if they could diagnosis the phone.
The next day I went to the store, everything came back clear on the diagnosis, but they could see it turn off randomly.
I called customer care and explained the situation and told them I need a replacement.
Now I am waiting on a replacement. If this one don't work, I think I will have to get on whole different phone. I'm on the verge of getting a flip phone because I know that I don't want to have an iPhone.
Anyone having these issues with the update Lollipop?

I've never heard about an update getting positive reviews from users, most get bashed.
Fortunately I don't have those issues, nor have I had any with updates. Have you tried to odin the stock firmware? That's all I can really think of.

MajorTom_ said:
I've never heard about an update getting positive reviews from users, most get bashed.
Fortunately I don't have those issues, nor have I had any with updates. Have you tried to odin the stock firmware? That's all I can really think of.
Click to expand...
Click to collapse
It seems like I tried everything. I haven't tried that though. I will try that today, if my phone ever boots up.

W0man09 said:
It seems like I tried everything. I haven't tried that though. I will try that today, if my phone ever boots up.
Click to expand...
Click to collapse
As long as you can get it into download mode something may be possible.

Odin to stock lollipop, factory reset / data wipe.
Additionally, I would consider a custom rom.
..........
If you really like kitkat better you could also Odin to stock kitkat, factory reset / data wipe.

MajorTom_ said:
As long as you can get it into download mode something may be possible.
Click to expand...
Click to collapse
Lol thanks for the help. I can't even get it to turn on, to get it in download mode. ??
. Now I'm just waiting on T-Mobile to send the replacement.

6.0.1 Changes for LG G Watch R

So my watch updated last night, and now I am trying to figure out all the changes.
I see that we have new gestures. I don't really use them, so Meh.
I also see that my battery projection jumped from 50 hours to 3 days, so that I freaking awesome if it pans out.
Anyone see anything else?
-Chris

cdaly1970 said:
So my watch updated last night, and now I am trying to figure out all the changes.
I see that we have new gestures. I don't really use them, so Meh.
I also see that my battery projection jumped from 50 hours to 3 days, so that I freaking awesome if it pans out.
Anyone see anything else?
-Chris
Click to expand...
Click to collapse
No more reboot watch.. Have to turn it off and on again.

matejilic said:
No more reboot watch.. Have to turn it off and on again.
Click to expand...
Click to collapse
Yeah I noticed that. Find this odd as to why they removed that

Hawke84 said:
Yeah I noticed that. Find this odd as to why they removed that
Click to expand...
Click to collapse
I think Google's reason was: "Why? Because F**k you, thats why!" It also baffles me that they still haven't incorporated custom canned responses to declined phone calls; you are stuck with the default ones even though you set up custom ones on the phone - the reason was probaby the same as the reboot omisson.

matejilic said:
I think Google's reason was: "Why? Because F**k you, thats why!" It also baffles me that they still haven't incorporated custom canned responses to declined phone calls; you are stuck with the default ones even though you set up custom ones on the phone - the reason was probaby the same as the reboot omisson.
Click to expand...
Click to collapse
but how to make a factory reset now? there is no item in menu.

Hawke84 said:
Yeah I noticed that. Find this odd as to why they removed that
Click to expand...
Click to collapse
Just hold down the button until it buzzes and reboots. Hardware reboot.

shobull.eu said:
but how to make a factory reset now? there is no item in menu.
Click to expand...
Click to collapse
Have you tried 'Unpair with phone'? To me that sounds like it would do a factory reset since an unpaired watch is basically useless.

Big change
Hi all,
Also got marshmallow, and biggest change for me is that it won't pair with phone. It comes up alright, and after accepting the Bluetooth code the phone wear app says "couldn't connect with ...". I tried factory resets (via unpair phone setting item), fresh install of wear phone app, and what not - still no luck.
Will try to downgrade and see if that helps.
Yours,
Christian

Hawkeye3 said:
Have you tried 'Unpair with phone'? To me that sounds like it would do a factory reset since an unpaired watch is basically useless.
Click to expand...
Click to collapse
From what I understand factory reset is "Unpair with phone" now, as when you select it asks: "are you sure you want to unpair and factory reset watch.
Interesting thing, is the new Reminders app, doesn't seem to work it asks to update android wear on phone when I open it, but nothing happens.

cholm said:
Hi all,
Also got marshmallow, and biggest change for me is that it won't pair with phone. It comes up alright, and after accepting the Bluetooth code the phone wear app says "couldn't connect with ...". I tried factory resets (via unpair phone setting item), fresh install of wear phone app, and what not - still no luck.
Will try to downgrade and see if that helps.
Yours,
Christian
Click to expand...
Click to collapse
I replied to you in the other thread but will post here as it may be useful to others..
I have the same issue. After OTA , i factory resetted and now it will not pair. I get "failed to pair...." I have tried multiple resets and cleared the data on the android wear app but no joy. I have gone back to 5.1.1 using the first post of the factory image thread. I was able to flash boot.img and system.img but recovery.img failed due to a partition error. Now everything is working again. Paired and synced on first attempt.

Downngrade wakes up watch
Hi there,
mhacin said:
I replied to you in the other thread but will post here as it may be useful to others..
...
I have gone back to 5.1.1 using the first post of the factory image thread. I was able to flash boot.img and system.img but recovery.img failed due to a partition error. Now everything is working again. Paired and synced on first attempt.
Click to expand...
Click to collapse
I also went back to 5.1.1 and things now work again - recovery flash also worked.
Seems the problem is really on the phone end. I have a Nexus 4 with "Fake stock" ROM (marshmellow). I could get the watch to pair with my Nexus 7 running stock 6.0..1 and that paired just fine. I also see other problems with the same Nexus 4 ROM with other bluetooth devices - e.g., my Jabra Tag II bluetooth audio RX/TX. I've posted on the ROM bug report forum.

My watch gives an error about a muted microfone although the mike is enabled everywhere in the settings where possible.
" Microfone disabled, waiting for injected audio."
Any suggestions?
Edit: Also the screen goes off after some time although I haven't enabled it anywhere?
Maybe I'll just reset it...

The biggest change for me - now we have native vibration when the watch disconnects (on connects) ... it was about f'in time ...

cholm said:
I have a Nexus 4 with "Fake stock" ROM (marshmellow).
Click to expand...
Click to collapse
I also have nexus 4 running Chroma MM. I will wait for OTA again and this time I wont factory reset to see how it goes

Manually updated mine to 6.0.1 using adb and now my iPhone (9.3 beta3 and latest android wear app) constantly looses connection. Have to pair as new device, restarting phone and/ or watch won't help.
Does anybody experience the same?
Might have to go back to 5.1.1 ...
Gesendet von iPhone mit Tapatalk

Hmm, well thats a disappointing. The removal of the reboot and reset is moronic and the new gestures are useless.
For the most part I cant get them to work, and even if I could why would I want to look like I was a nutter because I was randomly flapping my arm around trying (usually unsuccessfully) to control my damn watch?

delete me

mhacin said:
I replied to you in the other thread but will post here as it may be useful to others..
I have the same issue. After OTA , i factory resetted and now it will not pair. I get "failed to pair...." I have tried multiple resets and cleared the data on the android wear app but no joy. I have gone back to 5.1.1 using the first post of the factory image thread. I was able to flash boot.img and system.img but recovery.img failed due to a partition error. Now everything is working again. Paired and synced on first attempt.
Click to expand...
Click to collapse
Which 5.1.1 is better?

SharpSA said:
Which 5.1.1 is better?
Click to expand...
Click to collapse
I used the one at the top of the list. I don't know what the differences are between 5.1.1 versions

Verizon Auto-Updating Turbos to .49?

Something really strange happened to my father's Turbo. He got it brand new from Verizon about a month ago and I sat down and updated up to .44. I told him that if another update comes in, do not touch it because I was going to unlock it with Sunshine and root it. I don't allow him to do updates on anything, I do it for him when I know the bugs won't screw anything up and flash it myself.
I was ready to unlock the phone and when I looked About Phone, I saw it was on .49. So I checked a little more and found the exact date and time it updated (July 23rd, 7:23PM). The date and time coincided with his being in the hospital and I had possession of the phone. The phone was sitting in my room (there's no one else around to mess with things), undisturbed for a week. I never saw the .49 update show up before I left it alone--and I checked it to make sure he didn't accidentally update it, just in case. I know on my Turbo, it was annoying as all get out and I dealt with the nag screens for a week or so until I could buy the Sunshine app.
Is it possible Verizon is now forcing the .49 update? I know there's no way possible that either, I or my father, allowed this update to happen.

pearlheartgtr said:
Is it possible Verizon is now forcing the .49 update? I know there's no way possible that either, I or my father, allowed this update to happen.
Click to expand...
Click to collapse
Others have claimed that with some people being very skeptical. I would not put it past Verizon. Is it possible if you totally ignored the nag screens Verizon takes that as a yes?

Thing is, the update and nags never showed up in the first place for it to be accepted or ignored. It just happened.

My phone auto-updated while I was sleeping one night. I was thinking of unlocking the bootloader. Oh well.

lastnight that's update come to my turbo,.luckily that's happen when the phone on my hand,so i'm disconeted a mobile data ..
but now i'm stuck on no mobile data or wifi cause i'm afraid when i'm turn it on,the updates get installed

mt021322 said:
lastnight that's update come to my turbo,.luckily that's happen when the phone on my hand,so i'm disconnected a mobile data ..
but now i'm stuck on no mobile data or wifi cause i'm afraid when i'm turn it on,the updates get installed
Click to expand...
Click to collapse
(Wow, that's quite a cracked screen!)
Can you boot into recovery and clear cache? Would that clear the downloaded update files from the phone?
Of course, first chance -- after you stop the SUTL-49 update -- you get go ahead and unlock the bootloader already! Then you don't have to worry about it anymore.

(Wow, that's quite a cracked screen!)
Can you boot into recovery and clear cache? Would that clear the downloaded update files from the phone?
Of course, first chance -- after you stop the SUTL-49 update -- you get go ahead and unlock the bootloader already! Then you don't have to worry about it anymore.[/QUOTE]
yups,,for a first time the progress still there,,but after I'm trying to root a phone using vroot (via pc) and kingroot,specially by vroot cause this process makes turbo reboot a couple time (with a failed result :silly,.now on the second time on wipe cache,the progress is gone ( it's a temporary right?it's will coming again on a mysterius time :silly i'm use Gsm/Edge for a connectivity to make a slow downloading update progress when is coming back
.
a money problems for this time to buy that license

I, too, would probably resist unlocking that particular device, since the screen is so cracked up... if you replace the phone, you'd have to get another Sunshine license for the new device.
Anyway, back to the original point, I recall on my old GalaxyS3, VZ was pushing an update that only allowed you to postpone it for some specific amount of time and/or it had a timer for the "we're going to start installing" popup, after which it would force-install. Based on that, I wouldn't be surprised to hear VZ is forcing updates, especially on an unattended phone...

There may be hope...
http://forum.xda-developers.com/droid-turbo/general/sunshine-bootloader-unlock-su4tl-49-t3445523

while collecting a money,i'm try freezing updater using adguard.apk (non root) and the result for a last two days,the update progress is gone (I don't know if that's a result from a adguard method)..

The old user of my phone said that. The .49 update was made automatically, with no Yes/No options, just updated.

I think it might be that if you don't interact with the prompt it will update your phone after a certain amount of time. When the update first rolled out I would always postpone it, telling it to remind me at 12AM cause that's when I usually go to bed. However one day, after setting it to remind me at 12, I fell asleep earlier and didn't see the prompt. The next morning, surprise, surprise, it was updated to .49.

Good news!
Sunshine will now unlock bootloader on Verizon SUTL-49 on the Droid Turbo XT1254:
http://forum.xda-developers.com/showpost.php?p=68384014&postcount=21
jcase said:
We just released it, 3.4.6 will unlock SunShine
Sometimes stars align and a bug becomes apparent, one that we can use.
Click to expand...
Click to collapse

ChazzMatt said:
Good news!
Sunshine will now unlock bootloader on Verizon SUTL-49 on the Droid Turbo XT1254:
http://forum.xda-developers.com/showpost.php?p=68384014&postcount=21
Click to expand...
Click to collapse
It is a great news for a lot of people.
Good work by Sunshine team.

In the future with any phone. If you see a update is about to happen, plug your phone to your computer, go to root of storage, and delete the download.. Hell I do this all the time... You can't miss it, it will be the only white looking item there..