Database Info

Moto G Won't boot anymore.

Hello Guys,
after a week using Paranoid Android my moto g xt1032 acted weird, so I reinstalled stock using fastboot.
I am pretty familiar with the use of fastboot and flashing and so on (Guess I've flashed, and fixed over 20 different phones)
But now I've come to the point I can't even fix my own phone.
What does it do?
Well, when I start my phone, it will only show the "warning bootloader unlocked" message, and just restarts and does the same.
Sometimes it even gives a blue screen > restarts.
I can boot into fastboot mode, I tried to flash a RETAIL UK 4.4.2 And RETAIL UK 4.3 stock firmware, even though I am from The Netherlands,
but UK or German roms are the closed to mine, and as far as my knowledge goes, EU firmware are usually the same.
I managed to go into stock recovery, but when I flash philz or twrp, it just stays at the "warning bootloader unlocked" screen.

Going to try XT1032_RETAIL-EU_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml.zip right now.

same result.

bump

bump

Try this - http://forum.xda-developers.com/moto-g/help/guide-recover-xt1032-gpe-4-4-4-t2824377
While my situation below may not be yours, at least this may get you back to a stable and functional device. I hope it helps. And as you are aware this will COMPLETELY wipe your phone. If you can, backup any pictures or files you want to keep before doing this.
My situation was like many others that had flashed a 4.4.4 GPE or custom ROM and ended up with a mini wifi tablet as the radio was off (as stated by dialing 8#8#4626#*#*). I have gone two days with no cell signal due to this. Trying to flash a stock image (http://sbf.droid-developers.org/phone.php?device=14) resulted in boot loops. I believe that is what everyone else is calling it. I never saw the loop as it stayed on the initial logo screen before the animation begins. Maybe it is looping fast and just showing the same screen again instead of it simply not changing. Oh well. I'm fixed now but on EU ROM. Now I'm attempting to install Blur_Version.174.44.1.falcon_umts.Retail.en.US. The EU ROM currently installed is 176.44.1, and while it works I simply want to be stock US version for now. I mention this because there is also a 174.44.4 US ROM on SBF-DROID-DEV. I tried that one (among many others) when trying to revive my phone. None of the stock images worked and I'm currently not happy with any of the custom ROMs. Stock or rooted stock will be good for me. On a tangent but I have a XT1032 purchased from AIO Wireless (now Criket but still part of ATT). Well AIO tweaked Motorola's ROM to disable tethering. I actually use Red Pocket for service (another ATT MVNO) and only bought from AIO becausse they had a sweet deal. Wasn't so sweet after I found I could not tether and after 6 months found a way to unlock bootloader, which cost another $25. In short it spent just as much money and had much frustration that could have been avoided if I had purchased directly from Motorola and got a FULLY stock and unlockable device.
---------- Post added at 11:51 PM ---------- Previous post was at 11:42 PM ----------
Pass this along also to anyone looking: theroot.ninja worked for me to unlock the bootloader (I've not posted enough to XDA so posting true URL is disabled. Google "sunshine bootloader unlock"). I found a vague reference on XDA somewhere but don't recall thread. Basically, certain carriers (like ATT and its MVNOs) have agreement with Motorola to restrict bootloader unlocking on devices they resell. Like I said, cost me $25, but it worked and I've wasted more $$ on less.

My bootloader is unlocked, I can't get into recovery, only fastboot.
and it stays at the "warning bootloader unlocked screen" aka logo screen, and it restarts so now and then.
When I start it up for the first time, the screen turns blue right away, and restarts, after a couple of restarts, it stays stuck on the logo screen :S
I tried lots of stock firmware, but none of them worked, I wonder if it's a hardware fault, but I reassembled everything, without success.

http://sbf.droid-developers.org no longer has the latest firmware images. You need to read through this thread instead:
http://forum.xda-developers.com/showthread.php?t=2546251​
4.4.4 Recovery flashable Stock Motorola zips available here:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688​
Regarding fastboot and the 4.4.4 firmware image - you are obviously not doing all the necessary commands. Please state the commands you have used. Since you have updated your bootloader, ensure you are actually attempting to flash a 4.4.4 image, as a 4.4.2 image will result in an error.

lost101 said:
http://sbf.droid-developers.org no longer has the latest firmware images. You need to read through this thread instead:
http://forum.xda-developers.com/showthread.php?t=2546251​
4.4.4 Recovery flashable Stock Motorola zips available here:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688​
Regarding fastboot and the 4.4.4 firmware image - you are obviously not doing all the necessary commands. Please state the commands you have used. Since you have updated your bootloader, ensure you are actually attempting to flash a 4.4.4 image, as a 4.4.2 image will result in an error.
Click to expand...
Click to collapse
I am pretty sure I am using 4.4.4
I used these commands:
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache

I suggest you add the follow command which will entirely wipe any remaining files your phone.
mfastboot erase userdata​

lost101 said:
I suggest you add the follow command which will entirely wipe any remaining files your phone.
mfastboot erase userdata​
Click to expand...
Click to collapse
Tried it, no change.

Jur13n said:
Tried it, no change.
Click to expand...
Click to collapse
The system flashing commands are wrong. They should be:
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
See if that fixes it for you.

meekrawb said:
The system flashing commands are wrong. They should be:
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
See if that fixes it for you.
Click to expand...
Click to collapse
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
To be exactly, I know what I am doing

Jur13n said:
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
To be exactly, I know what I am doing
Click to expand...
Click to collapse
Okay. Good luck!

Jur13n - did you try http://forum.xda-developers.com/mot...-gpe-4-4-4-t2824377/post55768571#post55768571. Once back to 'base' you can update to 4.4.4 OTA or flash another ROM. And if you get stuck again, re-run this process. Three downloads, a few scripts to run; double-click easy.
Good luck.

e.martin.howell said:
Jur13n - did you try http://forum.xda-developers.com/mot...-gpe-4-4-4-t2824377/post55768571#post55768571. Once back to 'base' you can update to 4.4.4 OTA or flash another ROM. And if you get stuck again, re-run this process. Three downloads, a few scripts to run; double-click easy.
Good luck.
Click to expand...
Click to collapse
http://sbf.droid-developers.org/phone.php?device=14 is offline atm, I'll try it.
What do you mean with three downloads o.o?
I only see him saying Blur_Version.174.44.1.falcon_umts.Retail.en.US

Your issue could be due to older images. Here is the EU Retail 4.4.4 image. It doesn't matter where you are in the world, it will work fine.
http://forum.xda-developers.com/showpost.php?p=54757500&postcount=348​

lost101 said:
Your issue could be due to older images. Here is the EU Retail 4.4.4 image. It doesn't matter where you are in the world, it will work fine.
http://forum.xda-developers.com/showpost.php?p=54757500&postcount=348​
Click to expand...
Click to collapse
Tried it, didn't work.
Going to try the Blur_Version.174.44.1.falcon_umts.Retail.en.US one right now.

-- edit --
no result, also tried to convert it to gpe, no result either.
I guess it's a hardware problem somehow (maybe reading the harddisk fails?)

If you still have the box that the phone came in look at it and it will tell you which Moto G you have.

DROID MAXX stuck at Motorola screen/fastboot "Boot up failed"

Huy guys, very strange issue on my XT1080M.
I stopped using this phone a couple of months ago when I got my Moto X and then work provided me with a different device. The phone went dead at some point, and now, even after plugging it in and letting it charge, it will NOT boot up. It will not progress past the Motorola screen. The screen comes on, it vibrates, and then it gets stuck. The Moto logo is the same color every single time (purple) instead of changing.. thought that was interesting.
The phone had a pending software update that I never took, and I wonder if something prompted it to actually start the update instead. Either way, I downloaded the 4.4.4 fxz files and flashed it in RSDLite. The flashing went through successfully, but it still will not boot. Fastboot is accessible, but if you pick "Recovery", it shows the Moto logo, then comes back to the Fastboot screen and says "Boot up failed".
I re-downloaded and reflashed the files thinking maybe something is corrupt, but it still won't boot.
I really hate to lose this phone as it'd be really great to have as a backup, but I'm really out of any ideas. Bootloader is locked. Device was originally rooted and "security unlocked" with rockmymoto and whatever the security off program was (it's been a while..)
Any ideas at all?

digitaloutsider said:
Huy guys, very strange issue on my XT1080M.
I stopped using this phone a couple of months ago when I got my Moto X and then work provided me with a different device. The phone went dead at some point, and now, even after plugging it in and letting it charge, it will NOT boot up. It will not progress past the Motorola screen. The screen comes on, it vibrates, and then it gets stuck. The Moto logo is the same color every single time (purple) instead of changing.. thought that was interesting.
The phone had a pending software update that I never took, and I wonder if something prompted it to actually start the update instead. Either way, I downloaded the 4.4.4 fxz files and flashed it in RSDLite. The flashing went through successfully, but it still will not boot. Fastboot is accessible, but if you pick "Recovery", it shows the Moto logo, then comes back to the Fastboot screen and says "Boot up failed".
I re-downloaded and reflashed the files thinking maybe something is corrupt, but it still won't boot.
I really hate to lose this phone as it'd be really great to have as a backup, but I'm really out of any ideas. Bootloader is locked. Device was originally rooted and "security unlocked" with rockmymoto and whatever the security off program was (it's been a while..)
Any ideas at all?
Click to expand...
Click to collapse
Which FXZ did you actually flash? Go through and manually flash the FXZ and see what happens. Also run an md5 check on the FXZ

Okay, manually flashed it using mfastboot. No difference. Still stuck on the purple Moto logo.
FXZ file used was 1FF-obake-maxx_verizon-user-4.4.4-SU4.21-release-keys.xml.zip from sbf.droid-developers.org.
These are the steps that I used:
mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
MD5 matched. Argh.

digitaloutsider said:
Okay, manually flashed it using mfastboot. No difference. Still stuck on the purple Moto logo.
FXZ file used was 1FF-obake-maxx_verizon-user-4.4.4-SU4.21-release-keys.xml.zip from sbf.droid-developers.org.
These are the steps that I used:
mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
MD5 matched. Argh.
Click to expand...
Click to collapse
Well im out of suggestions. May be bricked

digitaloutsider said:
Huy guys, very strange issue on my XT1080M.
I stopped using this phone a couple of months ago when I got my Moto X and then work provided me with a different device. The phone went dead at some point, and now, even after plugging it in and letting it charge, it will NOT boot up. It will not progress past the Motorola screen. The screen comes on, it vibrates, and then it gets stuck. The Moto logo is the same color every single time (purple) instead of changing.. thought that was interesting.
The phone had a pending software update that I never took, and I wonder if something prompted it to actually start the update instead. Either way, I downloaded the 4.4.4 fxz files and flashed it in RSDLite. The flashing went through successfully, but it still will not boot. Fastboot is accessible, but if you pick "Recovery", it shows the Moto logo, then comes back to the Fastboot screen and says "Boot up failed".
I re-downloaded and reflashed the files thinking maybe something is corrupt, but it still won't boot.
I really hate to lose this phone as it'd be really great to have as a backup, but I'm really out of any ideas. Bootloader is locked. Device was originally rooted and "security unlocked" with rockmymoto and whatever the security off program was (it's been a while..)
Any ideas at all?
Click to expand...
Click to collapse
Why don't you flash the XML with RSD lite, the 444 has no getvar or erase userdata lines in it.

aviwdoowks said:
Why don't you flash the XML with RSD lite, the 444 has no getvar or erase userdata lines in it.
Click to expand...
Click to collapse
He did. Look at the post you just quoted.

Same problem here. Rebooted one day, never booted back up. Can't get the phone to charge enough to even complete most flashing commands.

Well, I was able to get my hands on another DROID MAXX. Unfortunately, this one already has 4.4.4 so I'm screwed for being able to use Sunshine until some sort of 4.4.4 root comes out. Plus, the device is a 2013 model, so I can't get a BL code from that Chinese guy.
Sigh. Such is life!

digitaloutsider said:
Well, I was able to get my hands on another DROID MAXX. Unfortunately, this one already has 4.4.4 so I'm screwed for being able to use Sunshine until some sort of 4.4.4 root comes out. Plus, the device is a 2013 model, so I can't get a BL code from that Chinese guy.
Sigh. Such is life!
Click to expand...
Click to collapse
Can you flash a custom recovery and get it to boot to that using the broken device?

The old one had a locked bootloader.

Have you tried house of moto to flash yet?
what system version were you on prior to having problems?

I ran into this same issue and never recovered from it. I had an unlocked bootloader prior to attempting to recover. Now it fails to boot and shows the boot loader is now locked.

my moto x fails to boot up and shows no command when I boot up the phone. Fastboot shows boot up failed

I have one that's having a similar issue. Shows the Motorola logo then nothing. Stock ROM and nothing modified.
Edit: It's a Verizon model (If that has any bearing)

So is there no fix to this issue? I tried to flash a custom recovery using fastboot and got stuck in fastboot mode because the image was too large, and failure to flash.
Also now adb can't find the device

motorola droid max stuck black screen at BLBROKE. help me

Hanging in bootloop after trying to install 4.4.4

Hello, I registered, hoping that somone maybe could help here.
Yesterday I wanted to get the latest 5.1 update for my moto g, running 5.0.2. Because I rooted the device amd modified some things like uninstalling system apps and replacing system apps with their updates; I wanted to flash a clean system first. I tried to find a german 5.0.2 rom and couldn't find one, so I decided the 4.4.4 version I got should do the same. So I tried to install it via fastboot. For doing this I used these fastboot commands:
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
I got these three errors: version downgraded primary_gp, version downgraded for tz, version downgraded for boot.
On reboot the phone get's stuck on bootloader unlocked screen and won't boot. I can reset by long pressing power, I can also enter fastboot menu.
After searching for two hours I could find this firmware XT1032_FALCON-RETDE_5.0.2_LXB22.46-28.1_1_cid7_CFC_1FF.xml (can't post link) and tried to install, I used the same commands as above and finished without any error. But there's still the bootloop. I tried to install several times and tried also to wipe data and cache. Can anyone help or is the phone bricked forever?

Dont flash motoboot, i had this same problem when flashing motoboot

I tried it again without flashing motoboot, with the same result. I think the problem is, that I flashed it once, so I think I could only fix it by undoing the motoboot flash.
Edit: Seems like the problem is only with stock rom. I tried to install CM12 and it is running fine, except it refuses a wifi connection. If CM would run that would also be ok, but without wifi,...so I just need stock.

Meanwhile I'm using a custom rom as a workaraound.

Try on this order @piet85
logo
boot
recovery
system.img1
system.img2
system.img3
nhlos
erase midem set 1
erase modem set 2
fsg
erase user data
and cache
Mind that the commands are not written on the right way just because im lazy :-

Thank you a lot, don't get me wrong, but for the moment I'm very glad having a running system on my phone and it runs very good for a custom rom. So there is no real need to flash again. Maybe I will do so, when there are major bugs or when I have more time, but for the moment the custom rom does it's job.

1st Gen hangs at splash screen.

I was having some connectivity loss earlier, so I powered off, turned back on and on turning back on, I now get the initial splash screen and nothing further. Can boot into the boot menu and recovery. Tried wiping cache first, then factory reset. Neither option changed anything. Any suggestions?

Were you using stock ROM?
Provide more information as to which ROM you were using.

akiratoriyama said:
Were you using stock ROM?
Provide more information as to which ROM you were using.
Click to expand...
Click to collapse
I apologize, this is completely stock. I left it on overnight (plugged in) and apparently the battery wouldn't charge in this state as it was dead this morning. Plugged it in and charged for a bit and then tried turning it on and it is doing the same thing as before - hanging up at the initial splash screen.

I am helping hipsterdoofus with his phone. I work in the same office.
The only thing I can do is get it into fastboot mode. I was able to get the drivers working in my PC.
When I run fastboot devices, it's showing the moto g.
The bootloader isn't unlocked. I tried to do a "fastboot boot recovery.img" to get it to temp boot into twrp, but it fails since the bootloader is locked.
Is it possible to unlock the bootloader from this state from the fastboot menu?
I assume we can't flash twrp from fastboot without the bootloader being unlocked.
I come from using a Nexus 5, so this device is quite a bit different than what I'm used to. Sorry if I'm asking stupid questions.

Just wanted to do an update.
I was able to unlock the bootloader, then I downloaded the GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip file from a link I found on the forum.
I followed the steps for restoring stock firmware in this thread.
I did the section for flashing from the xml.zip file:
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
If you get "(bootloader) Preflash validation failed" errors on the first two entries, you should be okay to ignore (something I read on another thread here).
After that, the phone rebooted. We weren't sure if it was ever going to finish booting up. It had the boot animation screen for quite some time before it finally loaded the OS.
So the good news is, the phone is booting up, and it's the GPE edition.
Bad news is, it's not detecting the SIM card.
If anyone has any ideas, I would love to hear them.

SoonerDude said:
So the good news is, the phone is booting up, and it's the GPE edition.
Bad news is, it's not detecting the SIM card.
If anyone has any ideas, I would love to hear them.
Click to expand...
Click to collapse
Maybe trying to reflash corresponding radio firmware ?
http://forum.xda-developers.com/showthread.php?t=2649763

Failing System Update : Android System Version : 24.201.2.quark_reteu.reteuall.en.EU

If anyone can advise me on the solution to get upgrade to latest Android System version would be grateful.
Currently I am on India Stock 6.0.1 rooted and TWRP installed (System Version : 24.66.2.quark_reteu.reteuall.en.EU retin). I am getting system update notification to 24.201.2 version. However after download install/update, its failing. It gets restart to TWRP and had manually reboot back to System. And then system detect already downloaded update and starts auto restart. Is there solution to fix this issue....
Thanks

mohangj said:
Currently I am on India Stock 6.0.1 rooted and TWRP installed (System Version : 24.66.2.quark_reteu.reteuall.en.EU retin). I am getting system update notification to 24.201.2 version. However after download install/update, its failing. It gets restart to TWRP and had manually reboot back to System. And then system detect already downloaded update and starts auto restart. Is there solution to fix this issue....
Thanks
Click to expand...
Click to collapse
Your TWRP reference is the clue.
You need to be on pure stock to get any OTA updates. Your TWRP recovery is blocking that, since you don't have stock recovery. It will continue to fail.
You can either flash back to 100% pure stock (including recovery), take the OTA, then re-flash TWRP.
Or you can wait until the full firmware of that update is posted -- not just the OTA, which is not the full version -- and flash that full firmware version manually with ADB or RSD.
If you choose the latter method, until that full firmware is posted you can disable the OTA notification if it bothers you.
(Be aware that some minor OTA updates never have the full firmware version posted.)

ChazzMatt said:
Your TWRP reference is the clue.
You need to be on pure stock to get any OTA updates. Your TWRP recovery is blocking that, since you don't have stock recovery. It will continue to fail.
You can either flash back to 100% pure stock (including recovery), take the OTA, then re-flash TWRP.
Or you can wait until the full firmware of that update is posted -- not just the OTA, which is not the full version -- and flash that full firmware version manually with ADB or RSD.
If you choose the latter method, until that full firmware is posted you can disable the OTA notification if it bothers you.
(Be aware that some minor OTA updates never have the full firmware version posted.)
Click to expand...
Click to collapse
Thanks !!
First method is only the right approach as of now if decide to go for update. Second method won't be possible in near future as Moto Maxx won't be getting Nougat :crying:

Hi ChazzMatt,
I decided to upgrade to 24.201.2 version, had successfully installed stock rom and got OTA update to 24.201.2. Installed TWRP and SuperSu.
Everything is working fine except, it directly booting to TWRP, what could be the issue....any fix.

mohangj said:
Everything is working fine except, it directly booting to TWRP, what could be the issue....any fix.
Click to expand...
Click to collapse
There were other reports about people booting directly to TWRP recovery a few weeks ago, instead of to their system. Sorry, I can't remember the reason or the fix... But there were at least two other people who had that issue. I'll try to research and see if I can find it.
What version of TWRP are you using? Do you have the most recent?
bhb27 said:
TWRP update
twrp-3.0.3-0_MOD_3-quark.img
Download
===================
Feb-17-2016
===================
* All the previously TWRP Mod + the below
* Included the latest TWRP updates to this date
* Kernel Improves
* Latest updates and bugs Fix to the date of TWRP
* Most notable is the fix for Nougat Setting configurations be lost after the wipe of cache or a restore of the ROM Data, only new backups made on the latest MOD TWRP will have this featuring.
Click to expand...
Click to collapse
also, what version of SuperSu are you using? Once rooted with the older version, you can update to newest.
SuperSU v2.79 SR3
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
After flashing the newest TWRP and SuperSu, clear all caches in recovery and reboot. See if that fixes the issue?

OK, I found one of the incidents and I gave him the same advice, but never heard back about results.
However the issue was his phone was booting to the bootloader, not to his TWRP recovery. Is yours actually booting to the TWRP screen or to your bootloader?
Here's his incident, and there was also another I can't find right now. One was going to recovery, but this guy below was going to bootloader.
___
zeeshan.siddique4779 said:
I have isntall this rom every thing is fine , but when ever i restat my phone it goes straight in to bootloader , then i have to press enter to go to the system andriod ? Why it is so ?
Click to expand...
Click to collapse
ChazzMatt said:
Is it going to your TWRP recovery or actually your bootloader screen? Someone else reported this on another ROM and they were mistaken -- it was going to recovery, not the bootloader. I don't remember why. I'll look around and see if I can find the comment.
But try reflashing the latest version of TWRP for Quark by our Quark TWRP maintainer, found here:
twrp-3.0.2-0-Mod_04-quark.img (updated September 2016)
https://www.androidfilehost.com/?fid=529141701856462150
Can't hurt and may help.
You may not have the latest version of TWRP for our Quark, which was released in September 2016. Our Quark maintainer (who has official status) has newer modded versions on Android Host Files the official TWRP website has not yet integrated. It's their fault, not his. So, he provides the newest stuff to us in spite of their neglect.
Once you re-flash that TWRP, then reflash latest SuperSu and clear caches (it's an option you will see after your install something).
Reinstalling SuperSu can't hurt and also may help. Then, let it reboot.
[2017.01.03] SuperSU v2.79 SR2
https://download.chainfire.eu/1019/SuperSU/SR2-SuperSU-v2.79-SR2-20170103215521.zip
When you initially rooted this ROM you had to use beta 2.62 SuperSu, but now you can update to newest if you haven't already.
Click to expand...
Click to collapse
zeeshan.siddique4779 said:
Yes it goes in bootloader screen not in recovery . Then i have to press power button to start phone .
What do you recomenr ? Any solution ?
Click to expand...
Click to collapse
ChazzMatt said:
Have you tried the the three things I suggested?
Install latest TWRP
Install latest SuperSu
Clear all caches in TWRP
In the meanwhile, I'll keep researching -- but any of those may somehow fix your issue.
Click to expand...
Click to collapse
zeeshan.siddique4779 said:
ok i will try and report you back . Thanks for help brother
Click to expand...
Click to collapse
ChazzMatt said:
Also try dirty flashing the ROM again. Boot into TWRP, flash the ROM, clear caches, reboot.
Click to expand...
Click to collapse

My issue is also exactly same what zeeshan.siddique4779 explained. Let me correct what I mentioned TWRP, its bootloader. When I boot/reboot it directly goes to Bootloader (-->START) there I have to press power button to boot system Android. I installed twrp-3.0.3-0_MOD_3-quark.img and cleared all cache, still issue persists.
I tried to go back to stock bootloader and install stock 6.0.1, but install is failing 3/22 error gbt.bin. I searched fix to this...didn't get. Currently I am running LOS 14.1 (root inbuilt in Developer option) with rebooting to bootloader issue

mohangj said:
My issue is also exactly same what zeeshan.siddique4779 explained. Let me correct what I mentioned TWRP, its bootloader. When I boot/reboot it directly goes to Bootloader (-->START) there I have to press power button to boot system Android. I installed twrp-3.0.3-0_MOD_3-quark.img and cleared all cache, still issue persists.
I tried to go back to stock bootloader and install stock 6.0.1, but install is failing 3/22 error gbt.bin. I searched fix to this...didn't get. Currently I am running LOS 14.1 (root inbuilt in Developer option) with rebooting to bootloader issue
Click to expand...
Click to collapse
He was on modified stock ROM for the Droid Turbo XT1254 -- a tweaked, debloated ROM by Computerfreek274 over in the other Quark forum. But same issue...
mohangj said:
I tried to go back to stock bootloader and install stock 6.0.1, but install is failing 3/22 error gbt.bin. I searched fix to this...didn't get. Currently I am running LOS 14.1 (root inbuilt in Developer option) with rebooting to bootloader issue
Click to expand...
Click to collapse
I think this is because with the OTA you took you installed a new bootloader. You can only downgrade to earlier firmware, even with an unlocked bootloader, if you omit gpt.bin from flashing. If you omit gpt.bin from the flash commands you can even downgrade back to Lollipop or Kitkat.

Thanks and I think you are correct. I tried to take stock update and bootloader broke.
How do I omit gbt.bin while flashing. So far I only flashed to stock with RSD. Please refer links, I will give a try.

It worked Thanks brother !!!!
Here what I executed on bootloader
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin (didn't execute this command)
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot erase cache
mfastboot erase userdata
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot

mohangj said:
It worked Thanks brother !!!!
Here what I executed on bootloader
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin (didn't execute this command)
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot erase cache
mfastboot erase userdata
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
Click to expand...
Click to collapse
can u give me the link tostock rom? unable to find one i bricked my xt1225

jigar003 said:
can u give me the link to stock rom? unable to find one i bricked my xt1225
Click to expand...
Click to collapse
EVERY QUARK FIRMWARE EVER RELEASED
http://www.filefactory.com/folder/f9d1880e6c5b4800/?sort=created&order=DESC&show=50
Well, almost the every Quark firmware. See, Motorola has released a few OTAs with security fixes and has not posted the full firmware yet. What @mohangj was able to do was DOWNGRADE to the last full firmware posted. And he was able to do that by having an UNLOCKED bootloader.
If your bootloader is still locked, you will only be able to flash the firmware you are bricked on (or higher), you will not be able to downgrade. And if Motorola has not yet publicly released the full firmware version, you have to send it to a repair center or something. Or wait until they release the full firmware publicly.
This is why having an UNLOCKED bootloader is so helpful sometimes!
If your bootloader is unlocked you can flash any XT1225 firmware listed at that link, just omit the GPT.bin file when flashing.

thanks my bootloader is unlocked

jigar003 said:
thanks my bootloader is unlocked
Click to expand...
Click to collapse
Then you're very smart!

jigar003 said:
can u give me the link tostock rom? unable to find one i bricked my xt1225
Click to expand...
Click to collapse
I am using https://forum.xda-developers.com/moto-maxx/general/moto-turbo-indian-variant-marshmallow-t3422783

mohangj said:
It worked Thanks brother !!!!
Here what I executed on bootloader
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin (didn't execute this command)
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot erase cache
mfastboot erase userdata
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
Click to expand...
Click to collapse
**********************************
ChazzMatt,
I am facing another kind of problem again, I had flashed custom Kernel BHB27 (https://forum.xda-developers.com/moto-maxx/development/kernel-bhb27-kernel-t3207526) on stock 6.0.1, It was successfully installed and but I lost Devinebeats Viper4Android effect. I tried to reinstall driver/relash zip file. It didn't work. So I wanted to reflash to Stock. This time I followed same steps as above. But not able to successfully flash, after executing all commands, device reboots to Motorola Android boot screen and then goes off, its getting switched off in some 15-20 secs. Not able to boot completely back to stock. what am I upto now

mohangj said:
**********************************
ChazzMatt,
I am facing another kind of problem again, I had flashed custom Kernel BHB27 (https://forum.xda-developers.com/moto-maxx/development/kernel-bhb27-kernel-t3207526) on stock 6.0.1, It was successfully installed and but I lost Devinebeats Viper4Android effect. I tried to reinstall driver/relash zip file. It didn't work. So I wanted to reflash to Stock. This time I followed same steps as above. But not able to successfully flash, after executing all commands, device reboots to Motorola Android boot screen and then goes off, its getting switched off in some 15-20 secs. Not able to boot completely back to stock. what am I upto now
Click to expand...
Click to collapse
Since all you replaced with @bhb27's kernel was the the kernel, you wouldn't have to re-flash the entire stock image. All you needed to re-flash -- I think -- would be the boot.img. That would have overwritten the custom kernel...
But at this point, since you have re-flashed the entire image andnow the phone won't boot, I'm not sure what is wrong.
You can always try to flash a custom ROM? I know people use Viper on custom ROMs and I believe even with @bhb27 kernel. So, not sure why your Viper didn't work any more. But you need to get your phone up and working again.
Try this Marshmallow ROM for starters:
[ROM][All Quark][6.x.x]Resurrection Remix
https://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-t3316232

mohangj said:
**********************************
ChazzMatt,
I am facing another kind of problem again, I had flashed custom Kernel BHB27 (https://forum.xda-developers.com/moto-maxx/development/kernel-bhb27-kernel-t3207526) on stock 6.0.1, It was successfully installed and but I lost Devinebeats Viper4Android effect. I tried to reinstall driver/relash zip file. It didn't work. So I wanted to reflash to Stock. This time I followed same steps as above. But not able to successfully flash, after executing all commands, device reboots to Motorola Android boot screen and then goes off, its getting switched off in some 15-20 secs. Not able to boot completely back to stock. what am I upto now
Click to expand...
Click to collapse
Here's a "custom" ROM based on XT1225 stock Marshmallow. It's just stock Brazilian Quark Marshmallow but modified to run on ALL Quarks (including Droid Turbo XT1254) by @iiWoodstocK. Try flashing that?
[ROM][6.0.1][Stock][Odexed]MPG24.107-70.2 Brazilian 6.0.1 for XT1254[TWRP Flashable]
https://forum.xda-developers.com/droid-turbo/development/rom-mpg24-107-70-2-brazilian-6-0-1-t3426234

ChazzMatt said:
Here's a "custom" ROM based on XT1225 stock Marshmallow. It's just stock Brazilian Quark Marshmallow but modified to run on ALL Quarks (including Droid Turbo XT1254) by @iiWoodstocK. Try flashing that?
[ROM][6.0.1][Stock][Odexed]MPG24.107-70.2 Brazilian 6.0.1 for XT1254[TWRP Flashable]
https://forum.xda-developers.com/droid-turbo/development/rom-mpg24-107-70-2-brazilian-6-0-1-t3426234
Click to expand...
Click to collapse
Thanks for the update. It worked by removing gbt.bin entry line from flash file and flashed it by RSD. No issues now

Need help I'm getting this annoying notification to update to 24.201.2 every now and then hence I final tried to install it failed.
Please check the screens for more.
And recovery also does not open says "no command " error I'm not sure whether I had installed or not. How to fix this? And remove that annoying updated notifications without root.