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?
Related
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
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
Hello there. I'm new and I have a problem upgrading to 5.0 from kitkat. I barely know anything about cellphones and my friend was helping me out before this happened.
So the background story was this:
My cellphone (Moto G LTE XT1040) was not showing the push notifications so after digging, I looked for some solutions that required a rooted cellphone, so I did it.
I unlocked the bootloader and installed a custom recovery (TWRP), then I installed SuperSU to make the cellphone root and tinkered around with the solutions to the push notifications issue, and left the cellphone untouched after.
Just this week, I recieved the upgrade to android 5.1 and before installing it I unrooted the cellphone, uninstalled SuperSu, flashed it with stock recovery and then a factory reset it. That should clean everything, but it turns out that after 2 failed tries, It doesnt install the upgrade. The cellphone shuts down and it shows that it tries to install the upgrade but the bar fills up until around 15% and a quick error message displays and it restarts normally.
Should I just install the stock rom (the 500 mb file) so all functions and settings go back to true default?
Thanks beforehand and sorry for the bad english
Hi everyone! I'm new here.
I tried to downgrade my XT1040 using fastboot from 5.1, but when the phone restarted, Lollipop was still there. The phone was formatted and with no network signal and Wi-Fi capabilities :crying: . The phone enters in a loop of restarting that doesn't stops until I manually turn it off.
I've tried to install stock ROMs via fastboot and via TWRP, but the problem persist. The bootloader is unlocked.
I'm looking for a solution as I haven´t found anything useful on the internet...
PLEASE HELP!!!
You can NOT downgrade via fastboot to a version with lower BL (e.g. KitKat), and even if you manage to do that, chances are you will receive an OTA update that pushes you into an unrecoverable brick state.
For now, since your device can still power on, I believe flashing stock and wiping data afterwards should be suffice to get it back on track.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
Finally, I found a stock ROM for my region (Latin America) so I installed it via fastboot with mfastboot and adb. It seems that the loose of WiFi and network capabilities it's a common issue on devices running an incompatible version of Android.
Thanks! (close topic)
Hello guys! After experiencing all custom ROMS including Xiaomi.EU, figured out that every single one has some small inconvenience for me and planning to return to stock, eventually using only Magisk and potentially a custom Kernel.
Managed to install every single version of Global Developer ROM, everything works well except the FaceUnlock that was gone, (the phone remained stucked in China region) and I am not able to access the fingerprint section, after few tries it brings me an error message.
Tried also using MIFlash , but the Fastboot ROM writting took 3 sec to write and stopped as successfully, then nothing but bootlooping.
Currently is the phone is functional, but as mentioned before not able to setup new fingerprints (using cache and data from old recovery and those work) neither Face Unlock.
Tried to Google any kind of solution, but unfortunately nothing worked.
Any suggestion is appreciated.
I see that nobody is interested to support, so I continuously researched and figured out that doing a full wipe and following these steps from this post will solve my problem:
https://forum.xda-developers.com/mi-8/help/chinese-mi8-to-global-instructions-t3839665
From I don't know which reason I was blocked on China region without the possibility to changing it.