[Q] Wifi and Bluetooth not turning on - Moto X Q&A

I'm trying to sell my moto x so I factory reset it but when it tries to make you type something in it didn't give you the option to use a keyboard, it only let you use voice typing. So I tried flashing some factory firmware from here after removing the line in the xml file that prevents them from flashing.
ATT 4.4.2 flashed fine and then now Wifi and bluetooth won't turn on.
ATT 4.2.2 and ATT 4.4 won't flash. Fastboot screen on the phone says "downgraded security version" so it refuses to flash those.
I never had any custom ROM's on here. It was rooted previously but HO LEE S**T it was the most convoluted process ever and I'm never doing that again. What do I do? Has anyone else had this problem?

okay somehow it got fixed.
I tried flashing 4.4 using this guide, the manual way. It kept throwing "FAILED <remote failure>" for half the stuff but i just kept going :silly: and at the end it rebooted and wifi was working. Despite trying to flash 4.4, it still has 4.4.2 on it...
really makes me appreciate how easy everything is with Nexus 5

Related

[Q] Verizon service shuts down on CM9

I have an SCH-i800 that I have CM9 (p1c 9.1.0) installed on. I have been using it for several weeks with no problem. Since I am planning on going on a trip, I decided to active pre-paid Verizon service for the tablet. At first, I attempted to activate the device. It went through the phone call but after a minute, it just sat at activating. That is when I noticed that the radio state in the status bar had an X on it. I rebooted the tablet to try again and got "com.android.phone has topped unexpectedly". I re-flashed CM9 (at the time I was using 9.0.0) and it worked again. Activation was not necessary. After a day, the error came up again and radio state went to off with an X. I tried 9.1.0, same problem after a day. I even tried a nightly CM10, same problem. Reboots, cache wipes, permission fixes do not make it work. The error persists until a re-flash of CM. I see on the Support Downloads for the Verizon Tablet, there are two modem files. My baseband version is currently S:I800.0.3V.EI04. I have attempted to "flash" these both via Odin (which failed after a couple minutes) and ZIP (which looked like it worked) to the EC02 on the site, but my baseband doesn't seem to change.
So my first question is, is there a how-to on flashing as I have searched high and low on one for the Verizon Tab specifically, and have yet to find one. Is there a ZIP file that is specifically meant for the i800? I am almost certain this is my problem and that a downgrade (this tablet when stock was updated to the latest Verizon image).
My second question is, has anyone else experienced this? Is there someone that is using a CM9 Verizon tab with EI04 baseband and not have this problem?
Is there a way I can track down what crashed the program? I have tried logcat, but it doesn't appear to give me much detail other than to tell me that it stopped.
And if you ask, no I did not use the Verizon service with this tablet before putting CM9 on it, so I wouldn't know if it worked before.
Any input that someone could provide would be useful. Thanks!

[Q] Various Issues - Tried different ROMs but issues remain

Hi guys,
this is gonna be a long story, but I'm at end of my wits.
So my phone (HTC One M7_UL Vodafone DE) got water damaged (it was submerged in water for at least a minute). I tested it again last weekend and it seemed to work in terms of hardware. I managed to test the speakers, the charge jack, the headphones jack, wifi, gsm, both cameras, etc. it all seems to work fine, and it's not about that anyways. I kept getting a "com.htc.htcdialer" issue, saying the process had unexpectedly crashed and then a few minutes later the phone would reboot. I tried finding out what this error was and how to fix it but I couldnt find anything. Also its weird that I got a software error.
So I unlocked the bootloader (via htcdev.com), flashed the latest recovery (I tried both cwm and twrp), which was also fine. I managed to install the latest Android Revolutions HD (53.0) and thats where the problems started again: I would get to the lock screen but as soon as I would swipe up to unlock it I would the white screen with the HTC letters on it. I tried wiiping all the cache and partitions i could find and reinstalled that rom, but the problem remained the same. Tried a different recovery (twrp) repeated all the steps and still no more luck than before.
So I decided to give a different rom a try and just flashed the latest stable cyanogenmod rom on it, and that boots fine, but eventually without error message reboots as well.
Then I tried flashing the latest viper rom, but there I have the same issue as at the beginning, that I get as far as the lock screen and then it just wont let me unlock it.
And that's where Im at the end of my wits. I cant imagine its a hardware related issue, but i might be wrong.
Ideally I would love to get my hands on a nandroid backup to restore the phone to stock, a stock rom ruu, but I cant find any of those either.
I'd really appreciate your help.
Let me know if you need specific details of installations, versions, decide numbers, etc

[Q] 24A to 26A Update Failure

Every day I get a notification to update from 24A to 26A and it fails every time. with the error code: 0x1111004. Stock (never been rooted). Do you guys have any idea what I should do? After MKBHD released his Android L overview, It makes me really want to try it one my phone or something to maybe get a bit better battery life. Or should I just call verizon and see if they can help me out because when I plug it into the computer, it doesn't say an update is available but I get the notification to update at least once a day.
Since you are not rooted, there aren't many workaround options.
I can save you some time on the phone with Verizon and tell you what they will say: Do a factory reset and try again.
Factory reset

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

[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?

Categories

Resources