Related
Wondering if anybody else is having this problem? If I install a custom rom like cm11 unofficial I just get stuck on the boot animation. It happens on any custom rom I installed and I followed all instructions. Any ideas? Running 1034 16gb on kit kat.
imprzwv said:
Wondering if anybody else is having this problem? If I install a custom rom like cm11 unofficial I just get stuck on the boot animation. It happens on any custom rom I installed and I followed all instructions. Any ideas? Running 1034 16gb on kit kat.
Click to expand...
Click to collapse
Make sure your bootloader is unlocked and your device is rooted. In addition your recovery must be installed correctly.
eddvys said:
Make sure your bootloader is unlocked and your device is rooted. In addition your recovery must be installed correctly.
Click to expand...
Click to collapse
i have the same problem on my xt1032 unlocked and rooted.
how i know if my recovery is installed correctly?
(i can only flash stock rom)
yoyococo said:
i have the same problem on my xt1032 unlocked and rooted.
how i know if my recovery is installed correctly?
(i can only flash stock rom)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2563599 Flash CWM in fastboot
Push ROM files to your /sdcard/
Install using your recovery xxx.zip
Instruction are there just follow them right.
I had this problem yesterday. Here is how I fixed it:
Install stock firmware. I installed a 4.4 one. http://forum.xda-developers.com/showthread.php?t=2542219
Then rooted using superboot
Finally, I installed TWRP
It took like three tries to get superboot and twrp to work properly. That's how I fixed it. Goodluck
Sent from my XT1032 using Tapatalk
Worked great thank you
x-Wooboost-x said:
I had this problem yesterday. Here is how I fixed it:
Install stock firmware. I installed a 4.4 one. http://forum.xda-developers.com/showthread.php?t=2542219
Then rooted using superboot
Finally, I installed TWRP
It took like three tries to get superboot and twrp to work properly. That's how I fixed it. Goodluck
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Works great now on my XT 1034.
x-Wooboost-x said:
I had this problem yesterday. Here is how I fixed it:
Install stock firmware. I installed a 4.4 one. http://forum.xda-developers.com/showthread.php?t=2542219
Then rooted using superboot
Finally, I installed TWRP
It took like three tries to get superboot and twrp to work properly. That's how I fixed it. Goodluck
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Had the same problem with a xt1032 retail.DE version, but didn't work.
I flashed the US umts4.4.2 version, was able to install root using superboot (at 2nd of 3rd try) and installed TWRP. Tried to Cm11 and gapps installed good, but still got stuck on bootanimation.
Losing faith here.
well this just happened on my phone again. the way I fixed it last time isn't working now I have no idea what to do
Why is no one helping with this issue. Ive experienced this a lot and I always have to restore it stock. I have never been able to install a custom ROM no matter how many times I root.
Sent from my XT1034 using xda app-developers app
I have this issues also on 4.4 us global rom. Rooted and recovery cwm
Sent from my XT1032 using Tapatalk
There are two ways to get this fixed:
Fix permissions through TWPR recovery (not available on CWM recovery);
Restore to stock firmware (you can find 4.4.2 firmware here: http://forum.xda-developers.com/showpost.php?p=49861244&postcount=101), flash CWM recovery (or TWRP) and flash CM11 again. This worked for me.
Let me know!
Can anyone confirm these methods? (at least the first one)
Done the 2nd multiple times, same result.
i have same problem , and don't know what to do ?
i flashed 3 different ROMs all stuck on bootanimation .
I'm curious. Did this happen the first time you flashed a rom? When I bought my Moto G (tesco version) it had 4.3 on it, I upgraded to 4.4 via OTA. Unlocked the bootloader, flashed CWM for 4.4 kernel, made backup and flashed various CM builds, booted with no problems.
Now I restored to backup, because of the non-working GPS.
It stucks on CM (the flashed rom) boot screen or the bootloader warning screen?
BBOXPT said:
Can anyone confirm these methods? (at least the first one)
Done the 2nd multiple times, same result.
Click to expand...
Click to collapse
After trying the second one 3 times, I used the TWRP/Fix Permissions method and successfully flashed CM11.
kellerman40 said:
I'm curious. Did this happen the first time you flashed a rom? When I bought my Moto G (tesco version) it had 4.3 on it, I upgraded to 4.4 via OTA. Unlocked the bootloader, flashed CWM for 4.4 kernel, made backup and flashed various CM builds, booted with no problems.
Now I restored to backup, because of the non-working GPS.
It stucks on CM (the flashed rom) boot screen or the bootloader warning screen?
Click to expand...
Click to collapse
I got CM 11 to boot the first time on a dirty flash, but forgot to flash gapps, so got a load of FCs when it loaded up. Since then, any sort of flash, clean or dirty gives me a bootloop.
Even directly flashing boot.img via fastboot doesn't fix it. Reinstalling the stock firmware and starting from scratch doesn't do it either.
Hi everyone!
I'm the owner of a Moto G 8GB retail.DE xt1032. And i can't install custom Roms.
The phone shipped with good ol' 4.3, and then I flashed the retail.DE 4.4.2 OTA as soon as it came out. But I got tired so I, unlocked bootloader, installed CWM and installed a custom ROM (at the time, CM11, wich I loved).
Then I tried to change the bootanimation (I know, such a lame thing to do) and i wasn't able to boot a custom ROM anymore, even stock based (infusion).
I tried every rom available (cm11, PA, Carbon, AOSP/CodeAurora, Nexus G), and it ALWAYS hangs on bootanimation forever.
If I remember correctly, I had to downgrade to 4.3 Bootloader at that time to install CMW, but since I've had this problem I already reverted to Retail.DE Stock and upgraded via OTA to stock 4.4.2 (so bootloader should have been upgraded to 4.4 too...?).
I still have the 4.3 bootloader .img file on my computer, so should I flash it and try again?
Same here man. We need help!
Sent from my XT1032 using Tapatalk
The latest version of CWM supports 4.4 bootloader.
I was having similar problem, and returning back to full stock and redoing everything solved the problem. As you are already back to stock, I suggest you give it another shot. Good luck...
suhridkhan said:
The latest version of CWM supports 4.4 bootloader.
I was having similar problem, and returning back to full stock and redoing everything solved the problem. As you are already back to stock, I suggest you give it another shot. Good luck...
Click to expand...
Click to collapse
I followed this mans suggestion and it worked for me. I was stuck on nexus g.
I've done it yesterday at least 2 times, with the same result.
I'm really confused, because it shows no error while installing the rom, and it even shows the rom specific bootanimation (which means files were actually copied to /system).
EDIT: just did the whole process again. Return to stock 4.3, update to 4.4.2 via OTA, flash CWM, flash rom (in this case Infusion 4.4.2 Beta (stock 4.4.2 based)) and here i am, stuck @ bootanimation for solid 10minutes.
BBOXPT said:
I've done it yesterday at least 2 times, with the same result.
I'm really confused, because it shows no error while installing the rom, and it even shows the rom specific bootanimation (which means files were actually copied to /system).
Click to expand...
Click to collapse
That's very strange. How did you return to stock? This method worked for me...
http://forum.xda-developers.com/showthread.php?t=2542219 (Note that, you will lose all your data, make a backup on PC)
if i try to flash stock using the downloaded firmware without changing a thing, i end up getting this error message in fastboot:
https://dl.dropboxusercontent.com/u/8675405/Untitled.jpg
what I usually do is delete a few lines in the flashall.bat file:
CALL :fastboot_flash partition gpt.bin
IF %errorlevel% NEQ 0 EXIT /b 1
Click to expand...
Click to collapse
as stated here: http://forum.xda-developers.com/showthread.php?t=2542219 OP point 3a) regarding downgrading.
i installed cm 11 unofficial from this thread http://forum.xda-developers.com/showthread.php?t=2608377 but when i turn my moto g on it gets stuck in the cyanogenmod loading screen if anyone can help it will be great
You didn't want to post your issue in that thread?
I'm having same problem.. Also same problem for bam ROM
Sent from my XT1032 using xda app-developers app
managed to get out of the CM11 bootloop after applied Fix Permissions (or something similar) in TW's Custom Recovery.
Seems that only TW recovery can fix this through a permissions fix.
Got the same problem last night and the only thing to do to get it works was to re-flash the stock firmware, flash the recovery and reinstall the CM build. Latest build seems to be pretty good.
Simply wiping the cache before and after flash worked for me.
Sent from my XT1032 using Tapatalk
imxdot said:
Simply wiping the cache before and after flash worked for me.
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Not for me, sadly.
I've also tried to re-flash the rom through the recovery but the only fix that worked for me was to flash the stock firmware and then install the CM via recovery.
Same here, had difficulties getting Cyanogen to boot.
What I did is :
- roll back to stock 4.3 : http://forum.xda-developers.com/showthread.php?t=2546251 (yes, you can roll back, read the end of the post)
- allow OTA update to 4.4.2
- install CWM
- in CWM : format /system, /data and /cache, install cyanogen from ZIP, wipe dalvik cache
Mysteriously it worked like a charm after many unsuccessful tries and a softbrick ^^
Btw, no need to root the stock ROM to install CWM or a custom ROM, just skip this step
Do you have the XT1032 version?
xavier66 said:
Same here, had difficulties getting Cyanogen to boot.
What I did is :
- roll back to stock 4.3 : http://forum.xda-developers.com/showthread.php?t=2546251 (yes, you can roll back, read the end of the post)
- allow OTA update to 4.4.2
- install CWM
- in CWM : format /system, /data and /cache, install cyanogen from ZIP, wipe dalvik cache
Mysteriously it worked like a charm after many unsuccessful tries and a softbrick ^^
Btw, no need to root the stock ROM to install CWM or a custom ROM, just skip this step
Click to expand...
Click to collapse
I´m tired of the mess made it because of the three different Moto G versions, i'm waiting for official Recovery from CWM, maybe 3 months it's to early but I wanna try this method. (I hope to don´t hardbrick haha)
I was having the same problem with every rom i tried. After going back complete stock with Alonsoch's tool in the original Dev thread, I was then able to get past the boot on any rom
Sent from my XT1034 using Tapatalk
stuck in loop after installation
Hi everyone
I have tried to install cyanogen mode date : 23, 22 nightly roms on my moto g xt1033 KK vesion using twrp as well as cyanomod recoveries but after installation my phone stuck on boot window. I waited for 20 min but nothing happens. I read throgh so many posts and orignal rom thread and found that its supporting 4.3 and 4.4 both versions and I want to test it with only 4.4. (Dont want to downgread).. Any solution?
I am newbee and want to take part in rom devlopment as tester. Sorry if i asked somethin silly or may be twice.
sandeepg9 said:
Hi everyone
I have tried to install cyanogen mode date : 23, 22 nightly roms on my moto g xt1033 KK vesion using twrp as well as cyanomod recoveries but after installation my phone stuck on boot window. I waited for 20 min but nothing happens. I read throgh so many posts and orignal rom thread and found that its supporting 4.3 and 4.4 both versions and I want to test it with only 4.4. (Dont want to downgread).. Any solution?
I am newbee and want to take part in rom devlopment as tester. Sorry if i asked somethin silly or may be twice.
Click to expand...
Click to collapse
please use the thread for the ROM you have issues with.
thread closed
Hi, I'm new to flashing roms and after installing CWM 6.0.4.7 on my xt1032 and rooting whenever i try to flash a rom it gets stuck in the boot animation. I have tried CM 11 Carbon rom and paranoid android. I don't know if I'm using the wrong GAPPS or what. Please help.
Gapps are not the problem:the same thing was happening to me. The real problem is the bootloader: if you are on kitkat, you have to revert to stock jelly bean (4.3), install custom recovery (for JB), root and flash the custom rom you desire. That's the only way that worked for me.
Sent from my falcon using xda app-developers app
skorpionvenom said:
Gapps are not the problem:the same thing was happening to me. The real problem is the bootloader: if you are on kitkat, you have to revert to stock jelly bean (4.3), install custom recovery (for JB), root and flash the custom rom you desire. That's the only way that worked for me.
Sent from my falcon using xda app-developers app
Click to expand...
Click to collapse
Ok thanks, I will try that when i have some free time. And how do you revert back to 4.3
never mind i found a post on how to testing now
Brick?
skorpionvenom said:
Gapps are not the problem:the same thing was happening to me. The real problem is the bootloader: if you are on kitkat, you have to revert to stock jelly bean (4.3), install custom recovery (for JB), root and flash the custom rom you desire. That's the only way that worked for me.
Sent from my falcon using xda app-developers app
Click to expand...
Click to collapse
I tried o revert to 4.3 but when flashing boot.img it said hab check failed for boot and now when i try to boot up it goes to the unlock booloader warning turns off and repeats. I can get back to fastboot but when i try to enter recovery it shows a broken android lying sideways. I think i bricked my phone. I really need help
Go back to Stock and start from Scratch.
As long as you can enter fastboot you should be fine.
I too have suffered with this problem, today i have done as above said, reflashed 4,3 but when i onstalled the cwm 4.3 version i still suffered the same problem, so i tried the cwm4.4 and hey presto, i now have cm11 on my phone, yee haaa
A Wild Willis said:
I tried o revert to 4.3 but when flashing boot.img it said hab check failed for boot and now when i try to boot up it goes to the unlock booloader warning turns off and repeats. I can get back to fastboot but when i try to enter recovery it shows a broken android lying sideways. I think i bricked my phone. I really need help
Click to expand...
Click to collapse
Try this,when you get to the broken android follow the instructions in the link below for "external reset" this will reset your phone.
https://motorola-global-portal.cust..._detail/a_id/97329/p/30,6720,9050/action/auth
if that fails just flash a stock 4.4 image with fastboot using one of the guides.
Worked
quizmaniac said:
Try this,when you get to the broken android follow the instructions in the link below for "external reset" this will reset your phone.
https://motorola-global-portal.cust..._detail/a_id/97329/p/30,6720,9050/action/auth
if that fails just flash a stock 4.4 image with fastboot using one of the guides.
Click to expand...
Click to collapse
Yes thank you so much I'm back on 4.4.2 You guys are great
hello everyone
I have a question about PaulOBrien superboot root method (look in modaco forum the moto g root method 1).
I have a 16GB Moto G and updated to Kitkat via OTA.
yesterday I used the method 1 (superboot) on windows 7, to root my phone, and run it for the first time and ended on a black screen with green bars (supposedly normal). I power off the phone and turned on and load kitkat normally and noted that the phone was not rooted.
y tried the method for a second time and have the same results (ended on a black screen with green bars), but when kirkat launched, on the initial screen i saw a message "System UIDs Inconsistent. UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable." and the system didn't respond.
I performed a factory reset via stock recobey and kitkat showed the same message but let me in the "i´m feeling lucky button" worked this time. there I noticed that my device was now rooted but non app was able to access the internal memory due to some r/w permissions as I think, because when I try to copy files to the phone via USB cable, I get have the same denial, even whit ADB push i get the same message of permissions denial.
I need a way to solve this because in this actual stage the phone works but the apps have like no access to the memory making them unusable,
for example i cannot take a picture, or download a file, for some reason all google apps not work or force close every time.
I need a way to upload a .img file to the phone in order to perform a recobery or to make a fresh install via fastboot, donn't know how to make the phone let me wrhite files on it. :crying:
(note: sorry for my bad English)
A Wild Willis said:
I tried o revert to 4.3 but when flashing boot.img it said hab check failed for boot and now when i try to boot up it goes to the unlock booloader warning turns off and repeats. I can get back to fastboot but when i try to enter recovery it shows a broken android lying sideways. I think i bricked my phone. I really need help
Click to expand...
Click to collapse
As long as you can enter the bootloader you haven't bricked anything!!! so don't you worry!
I have two questions: when did you download the stock rom, did you check the MD5 ??? Are you sure that it wasn't a bad download ?
Additionally: are you sure that you have downloaded the appropriate ROM? Did you try to flash any other ROM?
will8578 said:
I too have suffered with this problem, today i have done as above said, reflashed 4,3 but when i onstalled the cwm 4.3 version i still suffered the same problem, so i tried the cwm4.4 and hey presto, i now have cm11 on my phone, yee haaa
Click to expand...
Click to collapse
i'm having troubles too...
tried to install custom roms (c-rom and liquid rom), coming from 4.4 (unlocked and rooted) stock but it stays at the bootanimation.
flashed a stock 4.3, rooted installed, tried 2 recoveries (cwm and twrp), tried c-rom once more...
same problem :crying:
i've run out of options, so have to flash a stock 4.4 again, unless someone gives me thé idea what i can do to make it work.
xt1032
dreezz said:
i'm having troubles too...
tried to install custom roms (c-rom and liquid rom), coming from 4.4 (unlocked and rooted) stock but it stays at the bootanimation.
flashed a stock 4.3, rooted installed, tried 2 recoveries (cwm and twrp), tried c-rom once more...
same problem :crying:
i've run out of options, so have to flash a stock 4.4 again, unless someone gives me thé idea what i can do to make it work.
xt1032
Click to expand...
Click to collapse
I am having the same issue. I got this xt1032 after it was OTA upgraded to Lollipop 5.0.2 and I downgraded it to KitKat 4.4.4 Stock. Now I'm also getting stuck on the boot animations on every Custom ROM I try to flash on it.
Does anyone know if having the bootloader upgraded due to the Lollipop update has anything to do with this? mine is at Ver. 41.18.
EDIT: I was finally able to flash after Formatting Data from Recovery. Keep in mind this will basically delete everything from the internal storage and you need to put everything back there manually. Always make sure you backup your info/apps/music/fotos before Formatting Data.
I've been flashing ROMs, recoveries etc for years on every android device I've had, from Samsung to nexus, HTC. Everything. This is my first Motorola and I'm having a lot of problems.
Unlocked the boot loader, flashed TWRP but wouldn't backup my stock ROM so put on Pholz recovery and it wouldn't backup either.
Tried to install C-Rom after the usual wipes and just sticks at boot screen. Tried Tweakone ROM I think its called and same problem.
Any ideas? I have the XT1032
I know about restoring to factory but what I'm asking is, is there anything specific I'm doing wrong? I'm quite an experienced flasher. Research is showing me how to recover the phone but what's gonna stop it happening again
Sent from my Nexus 5 using Tapatalk
A lot of users report issues not being able to flash rom's on 4.4.2 kitkat.
A fix is to downgrade to 4.3, then flash roms.
I dont know why. I bought my device upgraded to 4.4.2 already, and i can flash roms with no issues.
Search the forum for the topic and you will find the info you need.
Roshi69 said:
I've been flashing ROMs, recoveries etc for years on every android device I've had, from Samsung to nexus, HTC. Everything. This is my first Motorola and I'm having a lot of problems.
Unlocked the boot loader, flashed TWRP but wouldn't backup my stock ROM so put on Pholz recovery and it wouldn't backup either.
Tried to install C-Rom after the usual wipes and just sticks at boot screen. Tried Tweakone ROM I think its called and same problem.
Any ideas? I have the XT1032
I know about restoring to factory but what I'm asking is, is there anything specific I'm doing wrong? I'm quite an experienced flasher. Research is showing me how to recover the phone but what's gonna stop it happening again
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It wont backup saying what error?
Twrp just said 'failed' in red writing after the data backup I think. And philz touch said something along the lines of Not being able to write a file into the \clockworkmod folder.
I bought the device with 4.4.2 on it and followed the guides after reading up about the problems etc but TWRP 2.7.0.0 had a lot of reports that everything was working on it so went ahead with it
Sent from my Nexus 5 using Tapatalk
Ya that's strange because philz works great for me. Do you have a USB otg to try an external backup?
Sent from my XT1032 using Tapatalk
I got the phone booted again by following a guide and flashing a stock rom.
Installed Philz recovery again and still getting the backup error. it says: E: Error while backing up boot image!
So understandably i am now scared to flash another rom in case i get a boot loop again.
*update* Strangely i flashed TWRP via CWM, rebooted into TWRP 2.7.0.0 and performed a backup successfully.
Roshi69 said:
I got the phone booted again by following a guide and flashing a stock rom.
Installed Philz recovery again and still getting the backup error. it says: E: Error while backing up boot image!
So understandably i am now scared to flash another rom in case i get a boot loop again.
*update* Strangely i flashed TWRP via CWM, rebooted into TWRP 2.7.0.0 and performed a backup successfully.
Click to expand...
Click to collapse
Why dont you use Clockwork mod recovery for flashing Rom. I have flashed 10 Roms with that and all are backed up with out any problems. TWRP has no official support for moto g, and instead of all that why don't you try Cyanogenmod ?
(sorry if my english is not perfect)
Hello,
I have exactly the same problem with my XT1032.
Bootloader unlocked, CWM (6.0.4.7) successfully installed and backup done with no issues.
But custom roms won't load...
CM11 is stuck at "bootloader unlocked warning screen" and SlimKat is stuck at slimkat logo.
I never had such problems on my Nexus..
Please help me, I don't know what's going on
TheSkweed said:
I have exactly the same problem with my XT1032.
Bootloader unlocked, CWM (6.0.4.7) successfully installed and backup done with no issues.
But custom roms won't load...
CM11 is stuck at "bootloader unlocked warning screen" and SlimKat is stuck at slimkat logo.
Click to expand...
Click to collapse
Same here. It may be possible to downgrade to 4.3 (see here), but would it then be possible to flash a 4.4.2-based custom ROM ? I'm not sure.
Heres the steps I took.
*******Before device was stuck at bootloop*******
1. Bought phone (XT1032)
2. unlocked boot loader
3. Rooted
4. Flashed Philz Recovery (wouldn't backup rom)
5. Flashed TWRP and CWM with same issue.
6. Flashed 2 ROMs to try it (TweakyOne + C-Rom, Both wouldn't boot. and tried on all recoveries.
********Steps after being stuck at bootloop*******
1. Followed this amazing guide here (https://www.youtube.com/watch?v=laU6NQ0LxR0)
2. Set up the stock ROM again
3. Flashed TWRP 2.7.0.0 via Fastboot
4. Backup worked successfully
5. installed CM11 and setup successfully
6. installed Lego rom just to assure myself (currently running this ROM)
I know this is no solution at all but just wanted to share my steps to see what maybe fixed my phone. possibly the stock 4.2.2 rom I flashed was the solution. Maybe the original factory ROM that came on the phone was the issue?