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, 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?
I just recently got the newest update. I downloaded all 99mb of it, plugged in my charger and it rebooted to update my phone. But when it turned on again my phone hasn't been updated, it's still 4.4.2. Checking for updates doesn't work at all.
Anyone have a clue where the download is stored so I can just try to manually flash it?
Stock ROM & Kernel 4.4.2
Rooted
CWM Touch recovery
Sent from my Nexus 5
JustinBieber said:
I just recently got the newest update. I downloaded all 99mb of it, plugged in my charger and it rebooted to update my phone. But when it turned on again my phone hasn't been updated, it's still 4.4.2. Checking for updates doesn't work at all.
Anyone have a clue where the download is stored so I can just try to manually flash it?
Stock ROM & Kernel 4.4.2
Rooted
CWM Touch recovery
Sent from my Nexus 5
Click to expand...
Click to collapse
I read somewhere that the script will abort if your device is rooted. Not sure if this applies to you.
robbham78 said:
I read somewhere that the script will abort if your device is rooted. Not sure if this applies to you.
Click to expand...
Click to collapse
Incorrect. Root has nothing to do with it. You will lose root after updating, but it's as simple as flashing SuperSU in your custom recovery to get it back. The reason it's failing is because you have a custom recovery, and are trying to apply the OTA from within Android. If you do that, you have to have stock recovery. If you are stock, just with root, you can flash the OTA.zip using your CWM recovery. The OTA.zip can be found in the /cache directory. I believe it reverts your custom recovery back to stock recovery, but getting it back is as easy as fastboot flashing it.
charesa39 said:
Incorrect. Root has nothing to do with it. You will lose root after updating, but it's as simple as flashing SuperSU in your custom recovery to get it back. The reason it's failing is because you have a custom recovery, and are trying to apply the OTA from within Android. If you do that, you have to have stock recovery. If you are stock, just with root, you can flash the OTA.zip using your CWM recovery. The OTA.zip can be found in the /cache directory. I believe it reverts your custom recovery back to stock recovery, but getting it back is as easy as fastboot flashing it.
Click to expand...
Click to collapse
Thanks guys, I didn't know everything had to be stock! plus I found out that xposed will also break the ota
There's an OTA help desk sticky thread in general that tells you everything you need to know
Sent from my Nexus 5 using Tapatalk
Ran into a problem yesterday (I'm not sure exactly what), but my phone was hanging on the HTC One loading screen. I used my TWRP 2.4 to factory reset. I am unlocked and can get into bootloader fine but cannot flash anything (I am using the HTC One S All-in-one kit by Hasoon2000). The reason I am trying to do this is I want to reinstall to the latest OTA update which I believe was 4.1. (3.14.531.17), but when I try to update it takes me first to the TWRP, and when I try to install it from there it fails.
Help would be greatly appreciated, and seeing as this is my first post, I apologize in advance if I'm posting in the wrong place or something.
I'd start installing the latest TWRP version, which should be the 2.8.x.x. Other than that, I don't know...
Fiabeschi said:
I'd start installing the latest TWRP version, which should be the 2.8.x.x. Other than that, I don't know...
Click to expand...
Click to collapse
I was able to get 2.8.1.0 installed through TWRP Manager from the play store, still can't upgrade the stock rom though.
For reference, I was able to get the stock recovery installed using Flashify from the Play Store. The OTA went smoothly after that.