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:
Related
Hi folks,
Looking for a little help here.
I have been following Omar-Avelar's rom and updating it as and when new versions are released, and prior to the conflict arising when Omar changed the kernal, I had been using Arman68's AIO. Today I perhaps foolishly updated to Omar's April 19th update along with Arman's AIO V5. This combination wouldn't boot...no big issue, just reinstall Omar's rom as a stand alone. However, this just gets in a perpetual bootloop off>fugly unlocked bootloader warning>motorola logo>intel logo>off ad infinitum.
I then tried to flash 91.2.26001 Orange Gb and 91.2.26001 EU...but they don't get past the little android guy in the flash process...he just falls over and the process quits.
I can access CWM Recovery just fine, but I don't seem to be able to flash a working rom from there.
Following this, I installed RSDLite, hoping to effect a fix from there...but because the phone is cycling, windows doesn't pick it up.
Any solutions, gratefully received
Coxie
Coxie said:
Hi folks,
Looking for a little help here.
I have been following Omar-Avelar's rom and updating it as and when new versions are released, and prior to the conflict arising when Omar changed the kernal, I had been using Arman68's AIO. Today I perhaps foolishly updated to Omar's April 19th update along with Arman's AIO V5. This combination wouldn't boot...no big issue, just reinstall Omar's rom as a stand alone. However, this just gets in a perpetual bootloop off>fugly unlocked bootloader warning>motorola logo>intel logo>off ad infinitum.
I then tried to flash 91.2.26001 Orange Gb and 91.2.26001 EU...but they don't get past the little android guy in the flash process...he just falls over and the process quits.
I can access CWM Recovery just fine, but I don't seem to be able to flash a working rom from there.
Following this, I installed RSDLite, hoping to effect a fix from there...but because the phone is cycling, windows doesn't pick it up.
Any solutions, gratefully received
Coxie
Click to expand...
Click to collapse
If you can enter fastboot mod, just download sbf form http:?/sbf.droid-developers.org/smi/list.php (sorry for the link...) and RSDlite 6.1.4,
Make sure you have drivers installed, enter to fastboot mod, wait untill phone is detected, choose your sbf and let RSD do his job.
Enter in the CWM and try to make a full wipe.
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.
Hi, I tried searching for this here (I remember reading something about the bootloop problem) but can't seem to find the thread, so any help will be greatly appreciated.
I have successfully rooted my Z3c using this guide all the way to the very end, however I noticed that the wifi wasn't working. I figured it was simply because I hadn't flashed the 23.1.A.0.690 firmware yet, but once I did, my phone is stuck in a bootloop; the sony logo appears and the phone resets over and over. I'm still able to go into fastboot but my question is, how can I put a stop to the boot loop? should I flash the newest FW (D5803_23.1.A.1.28_Customized_US.ftf), go back to the one the phone was shipped with (D5803_23.1.A.0.726_Customized_US.ftf), or reflash the root exploit one (D5803_23.0.1.A.5.77_US.ftf)>
UPDATE: I flashed D5803_23.0.1.A.5.77_US.ftf and the phone booted up without a hitch and kept rooted.
cowboyv said:
Hi, I tried searching for this here (I remember reading something about the bootloop problem) but can't seem to find the thread, so any help will be greatly appreciated.
I have successfully rooted my Z3c using this guide all the way to the very end, however I noticed that the wifi wasn't working. I figured it was simply because I hadn't flashed the 23.1.A.0.690 firmware yet, but once I did, my phone is stuck in a bootloop; the sony logo appears and the phone resets over and over. I'm still able to go into fastboot but my question is, how can I put a stop to the boot loop? should I flash the newest FW (D5803_23.1.A.1.28_Customized_US.ftf), go back to the one the phone was shipped with (D5803_23.1.A.0.726_Customized_US.ftf), or reflash the root exploit one (D5803_23.0.1.A.5.77_US.ftf)>
UPDATE: I flashed D5803_23.0.1.A.5.77_US.ftf and the phone booted up without a hitch and kept rooted.
Click to expand...
Click to collapse
Bootloops on Android devices can be caused by multiple factors. I suggest Flashing the .93 Kitkat firmware from there Root and if I am not mistaken there are flashable ( .zip) Pre-Rooted Roms which are Lollipop found in the Android Development Section of this Area.
Just make sure to flash the FW corresponding to your Model Number either D5803/833
If you prefer the harder way you can always use Flashtool to flash the Stock 4.4 FTF it came with and upgrade from there.
Revontheus said:
Bootloops on Android devices can be caused by multiple factors. I suggest Flashing the .93 Kitkat firmware from there Root and if I am not mistaken there are flashable ( .zip) Pre-Rooted Roms which are Lollipop found in the Android Development Section of this Area.
Just make sure to flash the FW corresponding to your Model Number either D5803/833
If you prefer the harder way you can always use Flashtool to flash the Stock 4.4 FTF it came with and upgrade from there.
Click to expand...
Click to collapse
Yeah, what I did was reflash the .77 FW without wiping system, and then, from there I flashed this 5.02 image, however now I am encountering a different problem: a persisting notification stating that I need to update google play services, even when I'm using the 7.5.73 version for 036. Has any one else encountered this problem? Is there a solution to this?
cowboyv said:
Yeah, what I did was reflash the .77 FW without wiping system, and then, from there I flashed this 5.02 image, however now I am encountering a different problem: a persisting notification stating that I need to update google play services, even when I'm using the 7.5.73 version for 036. Has any one else encountered this problem? Is there a solution to this?
Click to expand...
Click to collapse
You can always download GAPPS manually, and flash it via Recovery if you think the Google Play Services that comes with your FW is bugged
I just realized I posted in the wrong phone section. Can someone move this over to the G2? Sorry
Hi all, after updating my lollipop moto g2 today, 3/3/2016 my moto G2 has been stuck on the no command screen (dead android with red exclamation mark). This update was all stock, the bootloader was not unlocked and everything was untouched. I tried going to recovery, clearing and wiping cache and even factory reset and everything in the recovery option but still end up with the no command screen and constant rebooting.
I called Motorola and they told me that I have to send in my phone for "repair" and the update clearly bricked my phone and I'd have to pay for the repair which I don't think is fair
Is there anyone with a fix?
Thanks
I think they should recall this update until they can get it fixed and usable! This is beyond a joke
@Gary +1 Really, what a disaster. Does not inspire confidence in the entire Android enterprise/ecosystem.
bro if you are able to boot the phone into the bootloader mode then you can easily fix it
by flashing stock 6.0 firmware on your device take a look
How To Flash 6.0 Official Marshmallow On Motorola Moto G2:-https://youtu.be/dWMsgX1emN4
mandar91 said:
bro if you are able to boot the phone into the bootloader mode then you can easily fix it
by flashing stock 6.0 firmware on your device take a look
How To Flash 6.0 Official Marshmallow On Motorola Moto G2:-https://youtu.be/dWMsgX1emN4
Click to expand...
Click to collapse
Thanks for the reply, I will give it a try
Guys I need help please. So I have a moto g2014 ( XT1068 ) (non gplay version) and I tried installing a Custom ROM (I don't quite remember the name of the ROM). My phone was rooted and I had TWRP recovery. But when I tried to install the ROM I first click on "wipe system" so my stock ROM was no logern existing. When I flashed the Custom ROM everything was allright but there was a signal bug that when I hit "ok" it appears again, fed up with that I decided to wipe that ROM from my phone but I forgot that I have no backup of my stock ROM. Tried installikg KK (the phone came with that SO but I updated to Lollipop as soon as I could) and then the TWRP stopped working (and it seems to have dissapeared becausd I get the "recovery fail" at the bootloader screen when trying to enter recovery mode). Now I'm stuck in the Moto loading screen and nothing else happens. Help guys, please!!! (bootloader is ulocked btw) ???
---------- Post added at 07:05 PM ---------- Previous post was at 07:01 PM ----------
mandar91 said:
bro if you are able to boot the phone into the bootloader mode then you can easily fix it
by flashing stock 6.0 firmware on your device take a look
How To Flash 6.0 Official Marshmallow On Motorola Moto G2:-https://youtu.be/dWMsgX1emN4
Click to expand...
Click to collapse
I will try to do this, I hope it works because since I wiped the stock S.O nothing works on my moto ???
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.