Hi all
After finding CM11 wouldn't install on my moto g running 4.4.2 GPE, (Well, it would, but it said about "Encryption failure") I tried to return to retail GB 4.3 to upgrade to retail GB 4.4.2. However, the phone won't boot and TWRP reports no OS installed, as well as not mounting system, cache, data etc..
Any ideas? Tried sideloading a zip but to no avail, and I really need help
Thanks in advance
Can you access the recovery? (When it's off switch it on while holding the volume down button for 3 seconds)
Sent from my Moto G using Tapatalk
Yep, get into fastboot and recovery just fine. Got no OS, and not recognised by adb, so I'm at a loss. Tried the restoring stock firmware guide multiple times, but still nothing. Now sits in either bootloop or recovery
Try with stock 4.4.2 ROM instead.
Trying the stock GPE 4.4.2 images, and if it works, I'm certainly leaving it alone. Things were so much easier when I had a ZTE Skate....
Use the mototool to flash gpe firmware. Worked for me every time ..I have the same issue with encryption error
The moto tool is located in the original android development section for the moto g.
That's how I saved my phone.
Sent from my XT1032 using XDA Premium HD app
Wow, it's alive!!!
Needed to flash twice, but it lives! How I didn't try the tool before is beyond me, but I've used it and now we have a boot animation at least
Thanks to one and all for their help
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.
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.
Hey guys,
I have followed many tutorials (video and text) on how to flash ROMs on the Moto G, but to no avail.
I followed all the steps correctly, and my Moto G is stuck in a boot loop after 10 minutes. This happens every time I want to flash a ROM, and it has happened with many different ROMs, what am I doing wrong?
I have wiped all the wipey stuff and whatnot, I just don't know why it isn't working!
This is my first post, so please call me out if i missed any details I need to write down
Custom ROMs I have tried:
CyanogenMOD (Nightly)
Paranoid Android (unoffical)
C-Rom
Any help at all is much appreciated
Regards,
barky02
barky02 said:
Hey guys,
I have followed many tutorials (video and text) on how to flash ROMs on the Moto G, but to no avail.
I followed all the steps correctly, and my Moto G is stuck in a boot loop after 10 minutes. This happens every time I want to flash a ROM, and it has happened with many different ROMs, what am I doing wrong?
I have wiped all the wipey stuff and whatnot, I just don't know why it isn't working!
This is my first post, so please call me out if i missed any details I need to write down
Custom ROMs I have tried:
CyanogenMOD (Nightly)
Paranoid Android (unoffical)
C-Rom
Any help at all is much appreciated
Regards,
barky02
Click to expand...
Click to collapse
Happened to me at first too, when i had 4.4.2 stock in my Moto G, CM11 gets stuck in the bootanimation forever, what i did is downgrade to 4.3 (including the recovery) and then installed CM11.
Z-WolF said:
Happened to me at first too, when i had 4.4.2 stock in my Moto G, CM11 gets stuck in the bootanimation forever, what i did is downgrade to 4.3 (including the recovery) and then installed CM11.
Click to expand...
Click to collapse
Thanks a lot so how do I downgrade? and where can I find the 4.3 CWM recovery?
Edit: also, isnt 4.3 the upgrade? or is that a typo
barky02 said:
Thanks a lot so how do I downgrade? and where can I find the 4.3 CWM recovery?
Edit: also, isnt 4.3 the upgrade? or is that a typo
Click to expand...
Click to collapse
What i meant was that you need to flash the 4.3 stock recovery, along the 4.3 rom. those files normally come together.
Then you flash the custom recovery of your choice (i used CWM 6.0.4.7 touch) and CM11.
Look Here
4.3 = Jelly Bean Android
4.4 = KitKat Android
alezardstar said:
Dude, I completely understand you but I want to be very sure about what I will do foot try another time.
I back to 4.3 image downloading it here ( http://sbf.droid-developers.org/phone.php?device=14) and it already has the 4.3 recovery inside or I must to download it (from where?). Can you share the thread where you found the CWM recovery, please? Just to do it identical as you.
Thanks in advance.
Click to expand...
Click to collapse
let me see...
the guide to downgrade to 4.3 is this one
the guide to install CMW and CM11 is in cyanogenmod's wiki, you can find it here
as far as i know every (or at least most) stock ROM zip or tar file out there comes with a "recovery.img"
Yup downgrade to 4.3 needed then you'll have no problems
Sent from my Moto G using xda app-developers app
Happened to me as well (mine was rooted too), I followed the exact same steps Z-Wolf mentioned after searching and this seems to be a common problem.
I bought my device already upgraded to 4.4.2. I was able to install c-rom with no issue. I'm using tweaky ROM right now.
I'm curious as to why some devices need to downgrade and some don't?
Sent from my XT1032 using Tapatalk
What I did was installing cm11 from GPE and then wipe all cache and wipe system data or something like that (it deletes everything un your infernal sd), it worked for me after having bootloop with every ROM I tried. Ask the guys for those wipes ( I think it was format system/data but I don't remember very well).
ATRIXXIRTA said:
I bought my device already upgraded to 4.4.2. I was able to install c-rom with no issue. I'm using tweaky ROM right now.
I'm curious as to why some devices need to downgrade and some don't?
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
How did you do that man? I tried almost every found on this forum and I wasn't abble to get this done, always the same problem with encrypted partition comes up
---------- Post added at 02:00 PM ---------- Previous post was at 01:58 PM ----------
Z-WolF said:
Happened to me at first too, when i had 4.4.2 stock in my Moto G, CM11 gets stuck in the bootanimation forever, what i did is downgrade to 4.3 (including the recovery) and then installed CM11.
Click to expand...
Click to collapse
Did you get the downgrade version from here, which one did you use? I tried several and without success. I have a Moto G GPE
I will share my history with my phone since it can be useful for someone... Well I got the phone about a month ago, since i ordered from amazon, there's no way im going to return it for garanty if it broke, flashed cwm and rooted the same night, but when i was going to flash cm, l encountered a bootloop, since i didn't make a backup... i was at lost, my computer doesn't detect the phone in cwm, so I was with bootloop and not able to flash anything... Tried fastboot... Yes! so I downloaded stock and flashed away in fastboot, then i tried again with cm11, and this time it booted fine! I guess something prevented us to flash anything directly over stock, dunno what
I was stuck on boot loop for the past 24h, trying to flash a Lego ROM.
After a few factory resets and stock ROM flashes, I came across the solution of downgrading from KitKat 4.4.2 to Jelly Bean 4.3, then flash Lego again, and now all is well and good !
Here's the guide : http://forum.xda-developers.com/showthread.php?t=2542219
Flash Radios and New Kernel.
1031_Boost_US_CDMA_390.81.01P.zip
https://www.androidfilehost.com/?fid=23681161096070097
1031_Boost_US_CDMA_Kernel_3.4.42-gb89c9dd.zip
https://www.androidfilehost.com/?fid=23681161096070111
in my case I was flashing a Falcon, Boost Moto G, keep getting bootloops.
This is the first time in years I have ever had to sideload the Kernal and Radio, but non the less it stopped my bootloop.
Now if I get the error 16 voice mail message taken care of and input my MSL......
https://www.androidfilehost.com/?fid=23681161096070097
So, It seems ive effed up my Boost Moto G (on Page plus). Was fine on one VZW 4.4.4 ota .... then tried custom rom that i didnt like. Tried re flashing the old Verizon rom 4.4.2, and get constant reboots after about 30 secs and no Mobile or Wifi signal... Any help would be great.
Also, Ive treid reflashing the original boost roms, and they do the same thing.
Thanks!
hemanolio said:
So, It seems ive effed up my Boost Moto G (on Page plus). Was fine on one VZW 4.4.4 ota .... then tried custom rom that i didnt like. Tried re flashing the old Verizon rom 4.4.2, and get constant reboots after about 30 secs and no Mobile or Wifi signal... Any help would be great.
Also, Ive treid reflashing the original boost roms, and they do the same thing.
Thanks!
Click to expand...
Click to collapse
How did you flash the stock Verizon (and Boost) 4.4.2 ROMs? Using what method/commands? Did you get any errors?
Fixed it!! I did exactly as randomchaos26 suggested here: http://forum.xda-developers.com/moto-g/help/captured-verizon-g-4-4-4-update-t2824885
I reflashed the vzw 4.4.2 and the foloowed his directions:
quote: Save the update zip ( http://goo.gl/Vuw0P9 ) and the cwm flashable supersu zip to your phone.
Boot into cwm recovery and do a backup (assuming you have space on /media/data for a backup.)
Reboot to bootloader.
Restore *just* your system partition to stock with fastboot (using: CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip)
Boot into cwm again, apply the update zip, then immediately apply the supersu zip.
Boot up normally and let it do its update stuff, then go into titanium backup and kill off any of the verizon bloatware that you don't want.