Turbo WiFi not working - Verizon Motorola Droid Turbo Q&A, Help & Troublesh

When I rooted my Droid Turbo the wifi stopped working.
I try to turn the WiFi on and it immediately goes back off.
How do I get it running again?
XT1254
It is running version 5.1 with 23.21.44.quark_verizon.verizon.en.US vzw
Build number SU4TL-44
I have flashed the 44 again with no luck.
Any help would be appreciated.
Thanks
LD

Try re-flashing the radio for .44.
You can even try flashing the .49 radio.
There's both ADB and TWRP-flashable versions here:
[Droid Turbo XT1254] Bootloader & Radio Packages (+Unlocked warning removal)
http://forum.xda-developers.com/droid-turbo/development/droid-turbo-xt1254-bootloader-radio-t3259327

Still no worky
Thanks,
I re-flashed and still no worky.
Any other suggestions?

durtschi said:
Thanks,
I re-flashed and still no worky.
Any other suggestions?
Click to expand...
Click to collapse
Maybe flash the full .49 (Lollipop) firmware, maybe flash the 6.0.1 OTA update? Since your bootloader is unlocked you are safe. We have those here available in this forum. Here's the 6.0.1 OTA update:
[OTA] Official Marshmallow build MCG24.251-5
http://forum.xda-developers.com/dro...ota-official-marshmallow-build-mcg24-t3512813
(Do NOT attempt to install that if you have an encryption turned on.)
If those don't work, then it's something hardware related, I would presume. Just unlocking bootloader and "rooting" shouldn't affect anyone's wi-fi capability.
________
Is there SOMETHING ELSE you have installed that might affect Wi-Fi? Some battery save app would turn off and turn on Wi-Fi at different times? Something xPosed module like Smart Network? Some app or setting that is supposed to recognize a GPS location and do a certain action, like connect/disconnect Bluetooth? (But such apps can also control Wi-Fi.) One such app is Tasker, but there are plenty of others. Some people even have a couple of apps like that doing similar tasks and it's easy to have conflicts or just simple human error.
One time I configured my wife's volume control app to turn to "normal" volume at 8am and go silent at 8:30pm. Unfortunately, I accidentally chose 8:30am. (I swear I didn't, but there it was.) For two days, she had totally silent phone except for 30 minutes! And I'm the tech guy in the family.

Related

[Q] T-Mo US possible damaged radio or partition corruption; Baseband: Unknown

I was trying to post my post, but it was flagged and blocked by the system, probably because I kept previewing it, so until I can post it, I'm going to be really brief about the latest news on my problem.
I have a T-Mo US HTC One that's now S-Offed, running CWM recovery, and running 4.19.531.10 firmware+radio. It's running Android Revolution HD 91.1, and the first error from before I did any of this was "Failed to powerup external modem!" The phone would randomly reboot and such. Now, it's running normally except for the fact that I can't get the phone part of it to work. I also don't think I can warranty it because I already opened it up because I managed to break the back and also changed the frame color, screen, and camera. In the settings, Baseband read as "Unknown." I'm hoping you guys here can help me fix my problem as I hope it's software related, but think it might be hardware related.
Is there any hope for this? At one point, running the ElementalX kernel and the Android Revolution HD ROM with it still S-On and running latest Radio from 7.18.531.2, if I wiped dalvik cache and kept power saver off, the radio would start and it would work fine until I turned power saver on (even if the turn mobile network off part was off).
aruaour said:
I was trying to post my post, but it was flagged and blocked by the system, probably because I kept previewing it, so until I can post it, I'm going to be really brief about the latest news on my problem.
I have a T-Mo US HTC One that's now S-Offed, running CWM recovery, and running 4.19.531.10 firmware+radio. It's running Android Revolution HD 91.1, and the first error from before I did any of this was "Failed to powerup external modem!" The phone would randomly reboot and such. Now, it's running normally except for the fact that I can't get the phone part of it to work. I also don't think I can warranty it because I already opened it up because I managed to break the back and also changed the frame color, screen, and camera. In the settings, Baseband read as "Unknown." I'm hoping you guys here can help me fix my problem as I hope it's software related, but think it might be hardware related.
Is there any hope for this? At one point, running the ElementalX kernel and the Android Revolution HD ROM with it still S-On and running latest Radio from 7.18.531.2, if I wiped dalvik cache and kept power saver off, the radio would start and it would work fine until I turned power saver off (even if the turn mobile network off part was off).
Click to expand...
Click to collapse
seems like you went to a lot of trouble for a $100 phone
you can find a decent replacement on eBay cheap
Meanwhile you can update your firmware to the latest it will match the rom that way
I'm a little reluctant to change anything now. I just finished flashing the ElementalX kernel and did a dalvik-cache wipe and the phone service is working again. Assuming it's just like before, power saver should cause it to fail again.
I'm busy now, so I'll do a nandroid backup when I can later and try the RUU for the firmware again. The RUU kept failing on me before and htc_fastboot.exe would crash. I don't know how to decrypt the rom zip to manually flash it.
Edit: Any idea why using the ElementalX Kernel and wiping Dalvik-Cache makes the radio work again? It seems relatively stable right now (Powersaver off, it's not very stable with it on).

N4 unable to connect to network..Help please!

Hey everyone, so I just recently upgraded my Note 4 from KK to LP, but during the process, I had to flash the Baseband and modem before I flashed the LP ROM. I then flashed the ROM after I did that, and ended up with no network... I'm still able to make calls ONLY when I'm connected and close enough to the WiFi, texting is still fine I believe. So then I tried going through the process of downgrading to see if that would relieve the problem of my network issue, but it still isn't even working. Even after doing the process in reverse, flashing the baseband and modem before flashing my ROM.
I'd like to add that I did take apart my phone because my screen needed replacing, so I took apart my phone to see if I made my signal cables loose, they were, but then I popped them back in again, turned on my phone to see if that was the issue, and it still doesn't work, as well as my hardware back button doesn't work anymore so I have been using a nav bar to access my multi-window app.
I have tried flipping my signal cables, going from LP to KK, KK to LP, and reinstalling the firmware...
Edit: Whenever I factory reset in the stock recovery, I get an " Error:failed to mount /preload (no such file or directory)
Have you odin'd to stock lollipop?
You need to Odin stock firmware from Samsung, this will fix what you borked.
Then you can try again.
Pp.
Android_Monsters said:
Have you odin'd to stock lollipop?
Click to expand...
Click to collapse
Yes
PanchoPlanet said:
You need to Odin stock firmware from Samsung, this will fix what you borked.
Then you can try again.
Pp.
Click to expand...
Click to collapse
I've tried 2 fresh downloads of the stock firmware and it hasn't worked, but I will just download the file straight from Samsung this time to see if that could fix the problem. My new signal antennas I ordered from ebay are on the way and should arrive tomorrow. I'll then try that if this troubleshoot doesn't work because I don't have any 4gLte network at all, and it only pops up randomly and at certain areas I drive. I'm constantly moving and I could never have a stable connection, no calls, no text messages till I'm connected to the wifi:crying:
Edit #2: So I have installed new signal cables, and still not getting any 4G/LTE Network. I have constantly checked on my wires to see if it does anything to the network, but it doesn't. Still able to make calls on Wi-Fi only ): And I have used Odin to try and revert back to stock fully and no luck..

Random Reboots [Stock 6.0]

Hello,
My brain is collapsing about this reboots, I have stock android 6.0 on my XT092 device.
Wipe cache + reset doesn't resolve anything. Wipe backup data and unmark auto-restore apps on google auto-backup. After wipe cache/reset I put on this device "configure as a new phone" , then I unmark auto-restore on settings then I install my apps (whatsapp dropbox, cant install more without problem solved..), what I can do more or what im doing wrong?
Thank you all :good:
Try to collect log from device and publish it here, we'll read and think
summer.cat said:
Try to collect log from device and publish it here, we'll read and think
Click to expand...
Click to collapse
How can I collect my log? USB debug?
Nobody else have random reboots with marshmallow, i'm the only one? Didn't see nobody complaing :crying:
tpati said:
How can I collect my log? USB debug?
Nobody else have random reboots with marshmallow, i'm the only one? Didn't see nobody complaing :crying:
Click to expand...
Click to collapse
Mental note, this reboots only happens when i'm not touching in the phone (standby). If I'm using it or charge he never reboots! I can't leave this phone awake during night
Hello guys
I have stock android 6.0 [24.11.18.victara_reteu.reteuall.en.Eu retfr] on my Motorola Moto X 2014 [XT1092] after OTA update to android 6.0 I have always random reboot's on it. I search for all internet about a possible fix and I think I tried almost everything but I have hope can solve this problem.. Put on Moto X 2014 forum too but is a old device without much visibility!
I have try to hard resed and wipe caches (don't know how many times I did it, probably 100 with various configurations). Last time I do it I just reset/wipe and initiate the phone without sim-card and internet (always skip) after that I put the sim-card without 4G and WiFi and didn't install or update any type off app (Google's backup is disable and I clean everything I could about old's data) and the phone always reboots (think we never could stay 24h on without a single reboot, this is so frustrating).
Hardware phone problem? System operating problem (is stock and didn't see nobody like me)?
Any one have suggestions what I could do more or someone have this problem with your stock device?
Thank you for the time dispend reading this :good:
tpati said:
Hello guys
I have stock android 6.0 [24.11.18.victara_reteu.reteuall.en.Eu retfr] on my Motorola Moto X 2014 [XT1092] after OTA update to android 6.0 I have always random reboot's on it. I search for all internet about a possible fix and I think I tried almost everything but I have hope can solve this problem.. Put on Moto X 2014 forum too but is a old device without much visibility!
I have try to hard resed and wipe caches (don't know how many times I did it, probably 100 with various configurations). Last time I do it I just reset/wipe and initiate the phone without sim-card and internet (always skip) after that I put the sim-card without 4G and WiFi and didn't install or update any type off app (Google's backup is disable and I clean everything I could about old's data) and the phone always reboots (think we never could stay 24h on without a single reboot, this is so frustrating).
Hardware phone problem? System operating problem (is stock and didn't see nobody like me)?
Any one have suggestions what I could do more or someone have this problem with your stock device?
Thank you for the time dispend reading this :good:
Click to expand...
Click to collapse
Stop spamming the forums, already answered you in one of your other posts.
Sent from my XT1095 using Tapatalk
I had about the same problem (happened maybe 5 times) on my xt1096 while I had 5.1 verizon stock.
Since I installed the stock xt1095 6.0 marshmallow (about a month), I didn't have that problem again.
Maybe you should try that too? Just a suggestion.
AGISCI said:
Stop spamming the forums, already answered you in one of your other posts.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Sorry, I collect the log but I have my data on it.. I will colect it with full reset/wipe and any update!
I search about all forums I could but didn't find anyone with same error, I copy the text about 3 or 4 topics to have more visibility because this phone is making old (but I love it)..
OrenGazala said:
I had about the same problem (happened maybe 5 times) on my xt1096 while I had 5.1 verizon stock.
Since I installed the stock xt1095 6.0 marshmallow (about a month), I didn't have that problem again.
Maybe you should try that too? Just a suggestion.
Click to expand...
Click to collapse
When I bought this phone (2 months ago) he have 4.4.4, I think he update to 5.0 or 5.0.1 and after that updated to 5.1 (he stays about 2 weeks in 5.1) after that he receive 6.0 (problem apears)..
I think I couldn't downgrade the 6.0 to 5.1 (without touch on root's etc etc) right? Could I reinstall 6.0 in boot menu with all stock and no-rooted?
tpati said:
When I bought this phone (2 months ago) he have 4.4.4, I think he update to 5.0 or 5.0.1 and after that updated to 5.1 (he stays about 2 weeks in 5.1) after that he receive 6.0 (problem apears)..
I think I couldn't downgrade the 6.0 to 5.1 (without touch on root's etc etc) right? Could I reinstall 6.0 in boot menu with all stock and no-rooted?
Click to expand...
Click to collapse
You have to have root and unlock bootloader to change roms as far as I know.
I too am experiencing this issue since day one with a XT1092. It happend across several ROMs, including stock. Like previously stated, it happens only when the phone is not connected to a charger and in standby, seemingly randomly.
I suspect the radio to be the issue, since it is the same regardless what ROM one uses. Maybe certain frequencies (I am constantly connected to LTE; mostly Band 20, 800 MHz) or something similar could be the cause. That would explain why it is such a rare issue and so hard to reproduce. Or maybe it is simply a hardware malfunction, I guess I'll never know.
Edit: Got a soft reboot without a SIM card in the phone. Usually it's a hard reboot, but this time it was "only" a quick soft reboot.

[HELP] Dying Moto X (XT1058), trying to save it, any help appreciated

Hello,
So my Moto X (1st gen, 2013, XT1058) used to work fine on KitKat but after it auto-updated to Lollipop it started messing up more and more every day. The phone is fully stock and locked. Here's a brief list of problems:
random freezes and crashes of apps and the OS itself
random screen freezes (doesn't respond to touches) or completely blank screen apart from the notification bar, often times nothing help but a reboot
random reboots, "optimizing apps" every so often on boot, especially when on charger
flaky and unreliable WiFi, not connecting when it should or disconnecting at random including when screen goes off (despite having "always on" selected)
GPS would sometimes have difficulty acquiring lock and would lose lock randomly (worked just fine before)
I'm not quite sure what to do at this point. It's the AT&T variant which means the bootloader is not unlockable. It is also updated to the latest OTA (build LPAS23.12-21.7-1) which means no rooting method works, or at least I haven't been able to find any. So I can't get even a temproot. I tried everything I could find, nothing worked and I'm running out of options. I love this phone and I'd like to get it back to working order. I'm wholeheartedly hoping someone here will have some good advice or some resource I haven't tried.
Here's what I tried so far:
multiple factory resets, both from system settings and through recovery
didn't help, works for a while but all the issues reappear soon after
rooting with KingRoot
failed, rooting method not available
rooting using this method
failed (not surprising, it does mention it doesn't work on OTA)
unlocking BL via Moto's official unlock service
device not supported
installing moforoot
failed, mofoverify just quits silently and the phone shows a message about some missing fastboot var
unlocking BL using Sunshine
says the device should be supported but then fails acquiring temproot, the phone just reboots
reflashing stock KitKat from here (file: ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF.xml.zip) via fastboot
failed, OS/BL downgrade not allowed
reflashing stock Lollipop from here (file: ATT_XT1058_5.1.0_LPAS23.12-21.7-1_cid1_CFC.xml.zip) via fastboot
partial success, managed to flash a few parts, however it fails on all relevant partitions (gpt, boot, system), reports "downgrade not allowed" just like with KitKat which is surprising, this version/build should be exactly the same as what's currently on the phone
wiping userdata and cache via fastboot
didn't help
I might have tried some other things/methods too, this is just what I could remember right now.
Again, I'd very much appreciate if someone could help me revive this phone. I enjoyed using it while it was working well and I'd like to get it back to that state. Any help is very much appreciated.
Cheers!
I'm having exactly the same issues on my wife's moto x. The only thing I've been able to do for a temporary fix is to enter stock recovery and clear cache. Is there really no root/custom rom method for this device?

G7 Plus Android 10 Bluetooth issue

Hi all
I have re-posted this to the G7 plus forum, I mistakenly posted it in the G7 forum previously.
I have a Motorola G7 Plus XT1965-3 RETGB, after being pestererd by the update to android 10 mesage for several weeks, I finally agreed, since then, the phone fails to work with my in car head unit bluetooth connection.
It pairs, and will stream music from the phone through bluetooth to the head unit, just will not work as a hands free phone.
The head unint is a Kenwood DNX4230DAB, it shows the device connected as A2DP, but the phone (HFP) just shows connecting forever, before the update to Android 10, it worked flawlessly.
I've tried doing a full device reset, didn't help, and following various things posted on forums on the web, again no luck, the phone is unrooted, and the bootloader is locked, it is essentially as was when purchased other than the Android 10 OTA update.
Can anyone tell me is it poossible to roll back the Andoroid 10 update, I should never have done it in fairness, i've been bitten many times before with updates breaking stuff.
If anyone has any suggestions as to how to get the handsfree calling working again, or can offer a easy to follow guide on how to roll back to Android 9, I would be super grateful, I need to get the device working as a handsfree phone before I go back to work this week if at all possible.
Hoping someone can help.
I have an similar issue. On LOS17 the phone app works well with bluetooth but all the other voip apps like zoiper, bria or groundwire dont. the audio over bt is one way only
Regarding your issue: I afraid an OTA downgrade is not possible. However with fastboot you should be able to flash every stock you want as long as it is stock
Unfortunately, I tried to flash the stock Android 9 retgb rom, now the phone is a brick!
I wasn't aware that you need to unlock the bootloader before you flash the rom, so now it will no longer start
k4tfish said:
I have an similar issue. On LOS17 the phone app works well with bluetooth but all the other voip apps like zoiper, bria or groundwire dont. the audio over bt is one way only
Regarding your issue: I afraid an OTA downgrade is not possible. However with fastboot you should be able to flash every stock you want as long as it is stock
Click to expand...
Click to collapse
You only need to unlock the bootloader when you are downgrading or switching to another version, like from retus to retbra, saying this, you phone turns on? does it do anything? maybe you just need to flash the rom again, you can go here: https://mirrors.lolinet.com/firmware/moto/lake/ and find the firmware for your phone, you may have to flash it manually, i have tried to flash the firmware for my phone with RSD Lite but it says that its not in bootloader, if you are flashing the same build that you had or a higher build you dont need to have an unlocked bootloader, just check the dates and the build numbers to make sure that its the same you had or a higher one, just search how to manually flash it, if its really bricked, that it will not boot into bootloader, you can use blankflash to save it, just search on the forum

Categories

Resources