Hi all,
Let me start off by saying hello. I just joined these forums, and sadly I already have to bother you with an issue. Hopefully you can help me.
Recently, I decided to unlock the bootloader of my Moto G 2014 and install CM12.1. Sadly, Cyanogenmod stopped working after I installed Google Apps (from OpenGApps).
I then installed stock Marshmallow, using this tutorial. It got stuck on the boot animation.
Finally, I installed the stock Lollipop 5.0.2 firmware (the version I came from). It works now, but everytime I power the device up, it boots straight into TWRP. I can boot it normally using the bootloader, though. Also, when I try to lock the bootloader again, it won't boot at all (probably because I have TWRP on it).
This isn't an issue for me, but I upgraded to a Nexus 5X yesterday, and I'm giving my Moto G to my little sister, who is currently using a Nokia Lumia 635. I want the device to function as it should before I give it to her. Therefore, I'd like to do a complete wipe of my phone, and install the stock firmware, just like it was before I unlocked the bootloader. I could use some help with it.
My main concern is the fact that it boots into TWRP. Is there any way to fix this? Can I install the normal recovery mode again?
As for the firmware I was using, it was Android 5.0.2:
System version: 22.21.28.titan_retaildsds.retaildsdsall.en.03
Kernel version: 3.4.42-g48d3b85
Build number: LXB22.46-28
I can provide additional info, as I do have the stock ROM installed atm.
Thanks in advance!
P.S. I do also have SuperSU installed on the phone, but it says there is 'no SU binary installed'. It seems something went wrong there as well. Not too bothered by it, as I don't want it rooted, but I figured it was worth mentioning.
Related
hello, i have locked moto and wonder do i need 4.2.2 root to install this rom or 4.4 cause i get bootloop after installing the rom.
Are you currently running jellybean? Sounds like you are not running the KitKat kernel.
Sent from my XT1060 using Tapatalk
Same Bootloop
Hey Nitro,
Moto X VZW Dev.Ed.
Unlocked BL
TWRP 2.6.3.1
Stock rom 4.4.2
SuperSU
Rom Toolbox Pro for my needs
Had Eclipse installed and was running great. Screen started to flash between operations and loading apps. Thought it was just a misbehaving app, deleted everything I installed and it kept happening. Reinstalled the Eclipse ROM, no-joy. So I brought the phone back to complete stock. I was running on stock for about a week, the OTA came for 4.4.2 and I took it.
Flashed TWRP and installed SU again. When I go to install Eclipse 3.3.2 it shows that everything is loading correctly (love the "mounting your system like a horse"). When it restarts itself it gets stuck in a bootloop with just the Eclipse image. I've left the phone alone for a half hour at a time and it never completes (at 45 minutes on the latest install attempt). Downloaded from the primary and mirror and tried those, same issue, tried it dirty at first, then wiped the dalvik/cache. I've read the main ROM thread - nothing that I could find where someone got stuck in a bootloop like this. Just wanted to pick your brain and see what you thought.
^^^It's long, my bad. I just wanted to make sure you had every detail possible.
Really appreciate it, it's a great ROM when I don't jack things up.
d33pblue said:
Hey Nitro,
Moto X VZW Dev.Ed.
Unlocked BL
TWRP 2.6.3.1
Stock rom 4.4.2
SuperSU
Rom Toolbox Pro for my needs
Had Eclipse installed and was running great. Screen started to flash between operations and loading apps. Thought it was just a misbehaving app, deleted everything I installed and it kept happening. Reinstalled the Eclipse ROM, no-joy. So I brought the phone back to complete stock. I was running on stock for about a week, the OTA came for 4.4.2 and I took it.
Flashed TWRP and installed SU again. When I go to install Eclipse 3.3.2 it shows that everything is loading correctly (love the "mounting your system like a horse"). When it restarts itself it gets stuck in a bootloop with just the Eclipse image. I've left the phone alone for a half hour at a time and it never completes (at 45 minutes on the latest install attempt). Downloaded from the primary and mirror and tried those, same issue, tried it dirty at first, then wiped the dalvik/cache. I've read the main ROM thread - nothing that I could find where someone got stuck in a bootloop like this. Just wanted to pick your brain and see what you thought.
^^^It's long, my bad. I just wanted to make sure you had every detail possible.
Really appreciate it, it's a great ROM when I don't jack things up.
Click to expand...
Click to collapse
Did you do a factory reset wipe? Also, are you running the 4.4.2 kernel?
Sent from my HTC6525LVW using Tapatalk
Info
nitroglycerine33 said:
Did you do a factory reset wipe? Also, are you running the 4.4.2 kernel?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I did not do a factory reset wipe the first time. I did the second time. Same situation.
The kernel I'm using is:
3.4.42-g3385454
- Jan 23 17:09
System Version:
164.55.2.ghost_verizon.Verizon.en.US
Build #:
KXA20.16-1.25.2
I appreciate you taking the time out to look at this, thank you.
Hi,
I have moto g 2014 dual sim. today I tried to reflash the os but got "Failed to validate system image" upon reboot. So I unlocked the bootloader and again reflashed the os but got bootloop.. Please tell me how to boot my moto G 2014?
Read the instructions and flash it correctly with the correct firmware. Also post your question in the correct section.
If you have winrar or 7zip you can extract the firmware and take the "boot.img" file and flash it separate from the other firmware and it should work. That's how I do mine.
Sent from my Moto G using XDA Premium 4 mobile app
Sorry for posting in different section, but I need help
eksasol said:
Read the instructions and flash it correctly with the correct firmware. Also post your question in the correct section.
Click to expand...
Click to collapse
Let me tell you the series of events that led me to have bricked Moto G 2014:
1. I had X1068 Moto G 2-14
2. Wanted to reflash firmware and followed the steps provided in 4.2 section here http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
3. I got "Failed to Validate System Image" when I tried to reboot.
4. I was advised to unlock bootloader and reflash firmware. I did the same but got bootloop when I tried to reboot.
5. Now when I power on the phone, bootloader unlocked warning message comes and the screen blinks with the same message..
Please help Bro..
Who ever told you to unlock bootloader to flash firmware is giving bad advice. It is not required to unlock the bootloader to flash the factory firmware.
Make sure you're using the driver from here: http://www.mymotocast.com/download/MDM?platform=windows
(If you have other Android ADB drivers installed, uninstall them first, before installing this one.)
Make sure you are using mfastboot.exe, not the regular fastboot.exe.
Make sure your downloaded firmware is not corrupt and you got the correct version of the firmware for your device, there are different ones.
Download the firmware from here: http://sbf.droid-developers.org/phone.php?device=36
I believe your file is "Blur_Version.21.11.14.titan_retaildsds.retaildsdsall.en.03", but check on it.
After you reflash, make sure you boot into recovery mode and do a factory wipe.
The firmware for this phone is split into 3 files, so make sure you flash all three of them.
Issue Resolved
DillonFixDroids said:
If you have winrar or 7zip you can extract the firmware and take the "boot.img" file and flash it separate from the other firmware and it should work. That's how I do mine.
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks bro.. It was my mistake not to flash all files in the firmware folder.. apart from three system files (0,1,2), we also need to flash fourth system file (3) in the firmware folder... Thanks again bro...
MotoG 2nd Gen
Folks, I got a MotoG 2nd Gen (XT1068) I'm trying to root it but not successful. The main reason for rooting is that I want to record all my calls. Any solution?
Thanks,
Raj.
4dglobal said:
Folks, I got a MotoG 2nd Gen (XT1068) I'm trying to root it but not successful. The main reason for rooting is that I want to record all my calls. Any solution?
Thanks,
Raj.
Click to expand...
Click to collapse
Please be more presice, have you unlocked bootloader, before trying to flash the recovery?
Greetings from Venezuela. Just recently, I bought a new Moto G since my old S3 got severly damaged which made it unrepairable. I loved the reviews about de Moto G, but sadly since I got it I've had no luck with it.
While being connected to a WiFi connection, just looking around the celphone's settings, the phone required a system update straight off the bat. I had noticed before the update that the phone was instantly rebooting once the inactivity timer went off locking itself. Obviously after some time I did notice it by locking the phone manually (pressing the power button). I'm not that geeky or experienced in the Android field, but by doing some research on the web I've read some stuff that makes me not lose all hope on the phone, making me want to fix it.
I've tried factory resets, recoverys and nothing has worked. It has made me really frustrated not being able to fix the issue. All I've really done refering to flashing is unlocking bootloader, but still without flashing anything yet to make sure what I'm doing is the right thing to do.
Specs
Android version: 5.0.2
Baseband version: MSM8626BP_1032.3112.97.00R
RETUSA_AWS_CUST
Kernel version: 3.4.42-gf18cb80
System version: 22.46.12.titan_retuaws.retuaws.en.US retus
Need help with this, and I'll be eternally grateful with anyone that can help me.
P.S: new to the forums. In any case that I'm missing something, let me know.
joserodriguezv said:
Greetings from Venezuela. Just recently, I bought a new Moto G since my old S3 got severly damaged which made it unrepairable. I loved the reviews about de Moto G, but sadly since I got it I've had no luck with it.
While being connected to a WiFi connection, just looking around the celphone's settings, the phone required a system update straight off the bat. I had noticed before the update that the phone was instantly rebooting once the inactivity timer went off locking itself. Obviously after some time I did notice it by locking the phone manually (pressing the power button). I'm not that geeky or experienced in the Android field, but by doing some research on the web I've read some stuff that makes me not lose all hope on the phone, making me want to fix it.
I've tried factory resets, recoverys and nothing has worked. It has made me really frustrated not being able to fix the issue. All I've really done refering to flashing is unlocking bootloader, but still without flashing anything yet to make sure what I'm doing is the right thing to do.
Specs
Android version: 5.0.2
Baseband version: MSM8626BP_1032.3112.97.00R
RETUSA_AWS_CUST
Kernel version: 3.4.42-gf18cb80
System version: 22.46.12.titan_retuaws.retuaws.en.US retus
Need help with this, and I'll be eternally grateful with anyone that can help me.
P.S: new to the forums. In any case that I'm missing something, let me know.
Click to expand...
Click to collapse
SEE POST#3 USA AWS CARRIERS for latest update - READ INSTRUCTIONS
reefuge said:
SEE POST#3 USA AWS CARRIERS for latest update - READ INSTRUCTIONS
Click to expand...
Click to collapse
I followed the inscrutions, successfully flashing stock rom. But the bug is still there since the phone keeps rebooting once the screen is locked. Still need to know if there's any fix. Thanks for the help!
A New Problem
I recently got an ~138mb OTA update, tried to install it, after downloading it, but it failed at default recovery installer, rebooting with an error message saying "Update installation unsuccessful". Hence, I tried it with a custom recovery TWRP installed in my mobile, with TWRP manager app for android (with my phone rooted obviously) So after downloading update, on giving install, it goes to TWRP recovery main menu, from there I dont know how to install the downloaded update, or where it is available to browse to... Being unsure, I rebooted it to normal boot up, but no matter what I do now, the phone after turning on in the home screen, automatically powers down(switching off) to TWRP recovery main menu, I am stuck here please help me, someone.
I dont wanna lose all my data!! Give me a suitable solution
Goutham_SRIRAM said:
I recently got an ~138mb OTA update, tried to install it, after downloading it, but it failed at default recovery installer, rebooting with an error message saying "Update installation unsuccessful". Hence, I tried it with a custom recovery TWRP installed in my mobile, with TWRP manager app for android (with my phone rooted obviously) So after downloading update, on giving install, it goes to TWRP recovery main menu, from there I dont know how to install the downloaded update, or where it is available to browse to... Being unsure, I rebooted it to normal boot up, but no matter what I do now, the phone after turning on in the home screen, automatically powers down(switching off) to TWRP recovery main menu, I am stuck here please help me, someone.
I dont wanna lose all my data!! Give me a suitable solution
Click to expand...
Click to collapse
ota can only be installed to non rooted stock roms with stock recovery
tbh you need to minimum factory reset
but I believe you will need to install stock rom from scratch
---------- Post added at 06:54 PM ---------- Previous post was at 06:52 PM ----------
joserodriguezv said:
I followed the inscrutions, successfully flashing stock rom. But the bug is still there since the phone keeps rebooting once the screen is locked. Still need to know if there's any fix. Thanks for the help!
Click to expand...
Click to collapse
Never had or seen this all I can suggest is a factory reset twice and a few reboots to see if settles down
Guys i need help! I have the european Dual Sim Moto 2nd gen, locked bootloader and i tried to install Android Marshmallow via the indian zip (soak test) that i found in XDA. After installing the update via internal storage, it got stuck in optimizing 157 apps/158, it bootlooped and now it stucked it 1/1 optmizing ... What can i do???
Please, anything.
PRIMARY QUESTION: I cannot seem to install any "ghost" KitKat or Lollipop ROM on my XT1058. Can anyone please help shed some light on this? I've spent around a combined 12+ hours searching, researching, and tinkering trying to figure this out, but no success. I typically receive a "com.android.systemui" error message or "Unfortunately, System UI has stopped" message. After I acknowledge the message, it pops up again in a second or two. I have to force a shutdown of the phone and recover via TWRP. I've detailed my history and attempts below.
On the CM website, it says something about how "ghost" is a unified OS for every Moto X, except AT&T, since it's not unlockable. With Sunshine, shouldn't I be able to install the "ghost" ROM? Or does it not matter? I hope this isn't a case of, "even though you have an unlocked bootloader, the 'ghost' ROM isn't intended for your version of the phone." If that's true, it looks like all development on the XT1058 has pretty much stopped.
Many thanks, XDA Community, for helping me understand all this!
Secondary Questions:
I recently tried using the feature, "fixing permission" in TWRP thinking it might help with the "ghost" installations. I started getting bootloops when trying to restore to previous ROMs. The only restore that worked was my true original stock backup; the other restore attempts on SlimKat and other stock instances failed. That worries me. While I have successfully restored my phone, does anyone know if I may have screwed up my phone for the long-term?
(Answered by KidJoe; thank you!) Since I unlocked my bootloader at 4.2.2, can I freely upgrade and downgrade stock OSs? i.e., Can I install AT&T's stock 4.4.4 and then downgrade to 4.4.2?
(Answered by KidJoe; thank you!) Why do so many people seem to care to downgrade their stock OS? While I'm sure some may not be happy with some changes that come with upgrades, what could possibly be so "upsetting" that people need to downgrade?
HISTORY
Phone: AT&T Moto X XT1058, non-developer edition
Android: 4.2.2 | No attempt has been made to upgrade the OS beyond 4.2.2
Used Sunshine to unlock the bootloader while still on 4.2.2
Recovery: Installed TWRP v2.8.1.0, and I use TWRP to backup and install old and new ROMs (I think it's version 2.8.3... I never downloaded a version 2.8.1, but that's what the screen says. I'm wondering if the authors just forgot to update the version number in the program.)
Successful ROM installs:
SlimKat build 7 Official, msm8960dt
Cyanogenmod 11 Snapshot M5 msm8960dt (2014-04-05)
Failed ROM installs:
Cyanogenmod 11 Snapshot M12 ghost (2014-11-15)
Cyanogenmod 11 Nightly ghost (2014-12-19)
LiquidSmooth KitKat v3.2 Nightly ghost (2014-10-31)
LiquidSmooth Lollipop v4.0 Nightly ghost (2014-12-20)
Other Notes:
GApps were always installed when available. I also tried not installing them.
cxwong1 said:
Many thanks, XDA Community, for helping me understand all this!
Secondary Questions:
Since I unlocked my bootloader at 4.2.2, can I freely upgrade and downgrade stock OSs? i.e., Can I install AT&T's stock 4.4.4 and then downgrade to 4.4.2?
Why do so many people seem to care to downgrade their stock OS? While I'm sure some may not be happy with some changes that come with upgrades, what could possibly be so "upsetting" that people need to downgrade?
Click to expand...
Click to collapse
I will answer these two....
1. NO you can not. Once you have 4.4.2, 4.4.3 or 4.4.4 on your phone, do NOT attempt to downgrade, even if you have an unlocked bootloader... For more details see what I typed here -> http://forum.xda-developers.com/moto-x/general/4-4-4-downgrade-possibility-t2971847/post57563419 along with the other discussions in that SHORT thread.
2. The older root and write protection disable processes for a Moto X with a locked bootloader (like ATT and Verizon) rely on taking advantage of vulnerabilities in the 4.2.2 w/Camera update rom version, or the 4.4 rom. These processes walk you through downgrading your ROM to 4.2.2 w/Camera update and following a set of steps to upgrade which will keep root and disable write protection. NOTE: It was safe to downgrade from 4.4. to 4.2.2 w/Camera update when following the SlapMyMoto/MotoWpNoMo processes. But that was the only time it was safe!!!!
KidJoe, thank you much!
Does anyone else have any idea about my "systemui" issue?
cxwong1 said:
KidJoe, thank you much!
Does anyone else have any idea about my "systemui" issue?
Click to expand...
Click to collapse
Just got a Moto X 1st gen replacement from Motorola and getting same problem after unlocking/rooting. Have you found a fix for this? Or does anyone know how to fix? Spent all day working on this and its driving me nuts.
syckman said:
Just got a Moto X 1st gen replacement from Motorola and getting same problem after unlocking/rooting. Have you found a fix for this? Or does anyone know how to fix? Spent all day working on this and its driving me nuts.
Click to expand...
Click to collapse
Hey! Nope, I haven't found the answer, unfortunately. I haven't really tried to upgrade my OS since.
cxwong1 said:
PRIMARY QUESTION: I cannot seem to install any "ghost" KitKat or Lollipop ROM on my XT1058. Can anyone please help shed some light on this?
Click to expand...
Click to collapse
I bit the bullet yesterday and paid for the Sunshine bootloader unlock. After replacing the stock bootloader with TWRP and making a backup, I started looking into putting CyanogenMod onto it, as I had just updated a Galaxy Tab 2 7.0 to KitKat (via CyanogenMod 11) last week and it wasn't right that my phone had an older Android build than my tablet. I ran into conflicting information here and elsewhere, but the bottom line:
I have CyanogenMod 11 running on my AT&T Moto X.
More specifically, it's this zipball (remove spaces in next line to bypass the forum's lame link blocking):
https :// download.cyanogenmod.org / get / jenkins / 90775 / cm-11-20141115-SNAPSHOT-M12-ghost.zip
I also tried the latest 12.1 nightly, but while it appears to boot up, it reboots almost as soon as you try to set it up.
One thing that seems to help: before loading any ROM (whether stock, CyanogenMod, or whatever), wipe the flash. I have the ROM and Google Apps files on a flashstick that gets connected through an OTG cable, so I just tell TWRP to wipe everything but OTG storage, restore the ROM, let it boot up, then go back to TWRP to install the Google apps.
(Good thing I had the stock ROM backed up...had to revert to it this morning to back up aCar and Stocard data so I could bring them into CM.)
Starting configuration for my phone: AT&T XT1058, stock 4.4 firmware, rooted with the usual means for doing so, bootloader locked until Sunshine worked its magic.
Hey guys, i just got a Moto X Sprint XT1056, i got it from someone, it has been rooted, running on android 4.4.2
My moto x has an front facing camera issue, which the button to switch between the camera disappeared. So, i just try to take the OTA. After finishing download the OTA, i installed it anyway, then it got bootloop, power off every 10 seconds
Then i go to TWRP to factory reset the phone, but ACCIDENTIALLY, i also wipe the system. Then when i want to reboot the phone, it said "NO ROM installed"
I download Nexus Experience rom for moto X, then, i pushed it into internal storage using adb. But when i flashed it, it said failed! NO MD5 file found
What should i do?
Is the bootloader unlocked?
Flash the stock firmware again. Same Android version that was on it or higher. NOT a lower version. If the Ota did flash, then you need to flash that version. Best to anyway really, to be safe.
See the complete moto X guide in the general section, the returning to stock portion of the guide.
?
Hi, first off I want to introduce myself since I have been lurking in the forums for some time now but never posted anything. (I am not a developer).
My name is Nicolas, and currently I own a Moto X 2014. (XT1097)
I bought it recently, with lollipop out of the box, and updated via OTA to MM, since I wanted to check what was available to flash I unlocked the bootloader and flashed TWRP to then get root.
All up to this point it was all normal. I proceed to flash CyanPop 4.8 via TWRP, again all normal.
The problem begun when i wanted to flash a MM Stock ROM back, flashed via TWRP and as soon I hit reboot it gets stuck in the M logo with the white backgroud and bootloops there.
I reflashed Stock ROM XT1097, still bootloops, flashed Stock ROM Lite XT1097, still bootloops, flashed Stock rom XT1095, bootloops.
I ended up returning to CyanPop 4.8, (btw, I say its a hybrid in the title because as soon I installed CyanPop, the setup screen told me it was a XT1095)
and cant get out.
I know its kind of messy, but if anyone could bring light to what is going on, I would be extremely grateful, or if anyone knows what to search for to point me in the right direction, also i would be extremely grateful.
Anyway, thanks for all the work you guys do, and for this awesome forum :good::good::good::fingers-crossed: