Database Info

[Q] xt926 CM10.2 Stuck on Boot Logo After 1st Reboot

xt926 with unlocked bootloader and can run 10.1 nightly from get.cm with no problem. However, when I install a 10.2 nightly - whether from get.cm, epinter, dhacker or skrilaz - even though the initial boot comes up clean, rebooting after the initial boot gets stuck on the boot logo.
I have tried different recovery images - cwm, twrp, oudhs - and different versions of each.
I have tried clean installs, full formats and dirty upgrades from 10.1.
I have tried multiple force boots from this state (power+vol up).
I have tried with and without the updated gapps and UPDATE-SuperSU-v1.51.zip.
Restoring from backup does not get past this hang. The only way out is to revert to stock (I use mattlegroff's DROID_RAZR_HD_Utility_1.21).
Does anyone have any idea how I might get past this or even get a log?

Only thing that fixed this for me was to flash back to stock 4.1.2, flash newest CWM touch recovery, then flash newest nightly, Gapps, and SU. Then, a popup comes up saying something about the ROM wants to flash your boot image, and asks if you'd like to fix this. I answered YES (fix) and been working since.

Any chance you could link where you got your recovery and SU?
Much appreciated.

Same issue here...
I've also tried everything listed above. I've done everything i can possibly think of to get cm 10.2 on my xt926. For some reason my phone just isn't making it after the first reboot. I've searched and found similar issues but none of the troubleshooting has been working for me. I hope to find a way around this. I need that 10.2!

Same issue here. Not just CM, every 4.3 based ROM I've tried has either failed to boot or failed to boot more than once (more often than not, they won't boot at all).
I've been at this for hours, but I've had no success so far. I'll let you know if I come up with anything.
EDIT:
Here's my setup:
After every try, I flash back to stock 4.1.2 with VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml. I've edited it so it doesn't flash the stock recovery and so it flashes a modified logo that doesn't show the bootloader warning. Partway through, I booted up and updated to the latest OTA, so I had to comment out the tz.mdm files as well. I was using TWRP 2.2.2.1, but I updated to 2.6.0.0 earlier.

GeorgeHahn said:
Same issue here. Not just CM, every 4.3 based ROM I've tried has either failed to boot or failed to boot more than once (more often than not, they won't boot at all).
I've been at this for hours, but I've had no success so far. I'll let you know if I come up with anything.
EDIT:
Here's my setup:
After every try, I flash back to stock 4.1.2 with VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml. I've edited it so it doesn't flash the stock recovery and so it flashes a modified logo that doesn't show the bootloader warning. Partway through, I booted up and updated to the latest OTA, so I had to comment out the tz.mdm files as well. I was using TWRP 2.2.2.1, but I updated to 2.6.0.0 earlier.
Click to expand...
Click to collapse
one of 2 things should fix this problem,
use cwm 6.0.3.5 from here or
go to recovery/mounts and storage and format the data-media line (i know it says sd card but its internal, do not format the external ed card line or you will loose data on it)
also i updated matts utiliity to the latest ota, so you dont have to take the ota just to get the baseband. its in the dev forum. i will be updating it to a newer version if you wait until later, with the newest recoveries.
edit, btw 2.6.0.0 is not the latest twrp although i recommend using cwm as some have had issues with twrp including me.

First off, the latest TWRP seems to have fixed the problems (for me, anyway). Second, you'll need to use the most up-to-date GAPPs when you flash. Also, a lot of people have noted that mounting sytem prior to doing their wipes has solved the reboot issues.

Thanks a ton for the help. Flashed latest CWM and bumped up to 4.4 and everything's working fine. I appreciate the help!

[Q] Unable to use Custom Roms

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.

problem flashing roms on moto g xt1032

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.

[Q] [Custom ROMs] Stuck in Bootloop after many attempts

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

Custom ROM Issue... Stuck Booting...

Hey androids, I submitted this question as a reply to the guide thread already earlier... just thought it might get noticed in this forum alittle quicker... any help would be appreciated
I'm working on a recalled tablet that I rooted to keep using, and up until recently the ROM i had installed on it worked famously (bliss pop with android 5.1.1). Now, I was having some issues with it and thought "Well, i'll try out a different rom!"
So, I already had root (obviously) and I had already successfully installed a rom to this tablet... Using TWRP (both the 2.8.x.x I used previously and the newest one available for the shield) I have backed up, wiped, and flashed the images to 3 different roms + gapps for the appropriate versions...
first, I was going an issue with it mounting the \data partition so it wouldn't flash anything... then I repaired and rewiped the partitions, and got (what appeared to me in the logs) a clean and successful install of the roms. Each time I successfully flashed a ROM and GAPPs zips I would go to boot the ROM and my table would sit on the "NVIDIA" boot screen forever, never advancing to boot the ROMs.
I was worried that I had made a mistake and bricked the thing (though, it's been on borrowed time anyways being a recalled tablet). But I was able to force shutdown the tablet and reboot it into TWRP for another try. Each time I cleared the previous flash, wiped the cache and system partitions, and would get another clean install... but each time, it would get stuck on that same boot screen....
Anyone have any suggestions? thoughts? ideas? fixes? answers?.... anything? lol
Thanks folks!

Assuming you are trying to flash MM custom roms: You need the MM bootloader.

edisso10018 said:
Assuming you are trying to flash MM custom roms: You need the MM bootloader.
Click to expand...
Click to collapse
Is the newest TWRP *not* a MM bootloader?

TWRP is a recovery. A bootloader is a bootloader.

This is covered in every rom thread that updated from L to M.

lafester said:
This is covered in every rom thread that updated from L to M.
Click to expand...
Click to collapse
I'll re-look, the guides i've read have only covered flashing TWRP, then using them to flash the ROM and GAPPs... Which is what I did the first time I rooted it and put on a custom ROM... though maybe I didn't delete the original bootloader the first time and did so accidentally this time?

Thanks for the heads up though people, we'll see if I can straighten it out now that I know what I'm looking for

edisso10018 said:
Assuming you are trying to flash MM custom roms: You need the MM bootloader.
Click to expand...
Click to collapse
Ok, so I've downloaded the shield recovery zip, flashed the boot.img to the boot... nothing, then I read on one of the guides here that the "blob.img" is the bootloader... but the zip has a blob, without the .img
So I then attempted to add .img, and flash it to "boot" in TWRP, and there was an error, saying the file is too large...
do you (or someone else) know where to find a guide on where to find/how to flash a MM bootloader?
thanks

Ok, so I found guide with links to the latest firmware update; I flashed it, rebooted, and now I've gotta past the "Nvidia" boot screen into the Bliss boot screen... It's been here for a couple minutes now, gonna give it alittle bit and then try to install the other ROM I had tried.

MilesD37 said:
Ok, so I found guide with links to the latest firmware update; I flashed it, rebooted, and now I've gotta past the "Nvidia" boot screen into the Bliss boot screen... It's been here for a couple minutes now, gonna give it alittle bit and then try to install the other ROM I had tried.
Click to expand...
Click to collapse
Im stuk with the same probem, can you sendme the Link to the gide please