Hi I been flashing the CM 12.1 nightlies, starting from the mexican 5.0.2 stock firmware for a while. Suddenly, the power button and the screen got unresponsive.... i've tried to flash back to stock several times, either kitkat or lollipop, with the same results... The only different thing I noticed was when I started the bootloader menu the baseband line was empty. One of the times I flashed to stock it came back and start working correctly, but when I flashed CM again the same thing happened.
Now I have the baseband line black and the OS keeps crushing....
I tried flashing the radio only with the same results....
Any thoughts?
PS: RSD lite 6.2.4 doesn't recognize my devices so I flash with cmd and mfastboot using these commands:
mfastboot getvar max-sparse-size
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.0
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 erase cache
mfastboot erase userdata
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
Please help!
I had a similar problem with my XT1254. I was using a modified stock 5.1 system image (since that's all we can do with our locked bootloaders...for now. Our hope lies with you, jcase and beaups!) and after months of using it without any issues, it crashed. I got it working again by using similar steps to what you did to flash 4.4.4, but with a few exceptions:
1. I used fastboot instead of mfastboot.
2. I flashed something called gbt.bin I think to the "partition" partition. I'll re-download the firmware that I used and confirm that. I was following the flash sequence in the full firmware's xml file.
3. When the phone finally booted (it seems like it took between 5-10 minutes), I went through the initial setup, and I noticed a notification that said "complete uninstall." I clicked on it, and it said that it wanted to restore the motorola sensor firmware to a previous version. I said okay, and it did whatever it needed to do and rebooted the phone.
Now the phone boots fine (phew), but the baseband line in the bootloader is still blank. It might be related, but I remember that the moto app and also the moto actions (I think?) app updated itself recently, so maybe that sensor firmware update is the cause of the problem?
EDIT: Here are my exact flash steps. Keep in mind that this is for a Droid Turbo, not the Moto Maxx that you must be using. I'm not sure if that matters.
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash system system.img_sparsechunk5
fastboot flash system system.img_sparsechunk6
fastboot flash system system.img_sparsechunk7
fastboot erase ddr
fastboot erase cache
fastboot erase userdata
fastboot reboot
EDIT2: I set up my 5.1 image just to see if I could replicate the crash and sure enough, once I updated Moto Actions, everything fell apart.
TheSt33v said:
I had a similar problem with my XT1254. I was using a modified stock 5.1 system image (since that's all we can do with our locked bootloaders...for now. Our hope lies with you, jcase and beaups!) and after months of using it without any issues, it crashed. I got it working again by using similar steps to what you did to flash 4.4.4, but with a few exceptions:
1. I used fastboot instead of mfastboot.
2. I flashed something called gbt.bin I think to the "partition" partition. I'll re-download the firmware that I used and confirm that. I was following the flash sequence in the full firmware's xml file.
3. When the phone finally booted (it seems like it took between 5-10 minutes), I went through the initial setup, and I noticed a notification that said "complete uninstall." I clicked on it, and it said that it wanted to restore the motorola sensor firmware to a previous version. I said okay, and it did whatever it needed to do and rebooted the phone.
Now the phone boots fine (phew), but the baseband line in the bootloader is still blank. It might be related, but I remember that the moto app and also the moto actions (I think?) app updated itself recently, so maybe that sensor firmware update is the cause of the problem?
EDIT: Here are my exact flash steps. Keep in mind that this is for a Droid Turbo, not the Moto Maxx that you must be using. I'm not sure if that matters.
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash system system.img_sparsechunk5
fastboot flash system system.img_sparsechunk6
fastboot flash system system.img_sparsechunk7
fastboot erase ddr
fastboot erase cache
fastboot erase userdata
fastboot reboot
EDIT2: I set up my 5.1 image just to see if I could replicate the crash and sure enough, once I updated Moto Actions, everything fell apart.
Click to expand...
Click to collapse
EDIT3: I just noticed that on Rootjunky's video, his baseband appears blank too, so maybe it was always blank and we just didn't notice before.
---------- Post added at 10:39 AM ---------- Previous post was at 09:41 AM ----------
Did you ever fix your problem? If so, how? Because my phone is messing up again and my previous method isn't working.
TheSt33v said:
EDIT3: I just noticed that on Rootjunky's video, his baseband appears blank too, so maybe it was always blank and we just didn't notice before.
---------- Post added at 10:39 AM ---------- Previous post was at 09:41 AM ----------
Did you ever fix your problem? If so, how? Because my phone is messing up again and my previous method isn't working.
Click to expand...
Click to collapse
Yeah I was Ok for a few days without the moto updates, but then it started crashing again... I don't know how to fix it... the baseband keeps going on and off in the fastboot mode and everytime it goes off the problem arise
andrescarre87 said:
Yeah I was Ok for a few days without the moto updates, but then it started crashing again... I don't know how to fix it... the baseband keeps going on and off in the fastboot mode and everytime it goes off the problem arise
Click to expand...
Click to collapse
That's weird. I got a warranty replacement from Motorola that appeared to be brand new and before I modified it, I checked the bootloader. Baseband was blank. So even on a stock, unmodified phone, it can be blank. Here's my thread that details everything that I tried to fix this problem: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to temporarily fix it, but it always broke again once I reflashed 5.1. I posted the system image that I made that temporarily fixed the problem, but remember that is for an XT1254, so I don't think it will work for you.
Hello Sir
I was about to update to computerfreak's .49 rom (version 1.37 that is). Prior to that I wanted to update to the latest modem, So i flashed the modem cleaner, and then the radio from firstencounter's thread
(http://forum.xda-developers.com/droid-turbo/development/droid-turbo-xt1254-bootloader-radio-t3259327)
Since then my baseband is unknown. I can't connect to wifi and my sim isn't being read
You seem to have fixed the problem? I was on computerfreaks 1.35 till now with no issues (except GPS wouldn't lock)
Hi all.
I just wanted to share my finding regarding this problem.
I realise that this may not fix the problem for everyone, but searching the forum, I have found MANY folks that have tried all the things that I have to no avail..
So I am posting this in hope that some of them might see this and hopefully cure their "Unknown Baseband", "No IMEI" and "No SIM card"
I recently upgraded to RR Marshmallow witch fixed some other problems I have had with my XT1254 Droid Turbo (Bluetooth related)
I also upgraded my Radio.img from 02r to 03r (44 to 49?)
While this fixed my Bluetooth problems and everything was running really well for 2-3 days, out of nowhere, in the middle of a phone call, I got: No IMEI, Unknown Baseband and no SIM card...
I searched the forum (and google) and have tried just about everything..
Upgrade / downgrade firmware
Install stock rom
Backup/restore EFS / IMEI partition
Different radios
A few third party programs
Loads of ADB commands (learned a lot in the process though!)
I was kinda ready to give up and buy a new phone, so I thought I might as well try something daring WITCH FIXED MY PROBLEM!!!
I sprayed a little electrical cleaner into the SIM slot and let it dry out. When I pushed in the SIM card, I felt some resistance that definitely wasn't there before! I know this for sure because I removed / inserted the SIM card a LOT of times to see if it would connect.
My guess is that there is a mechanism that pushes the SIM connection points away from the SIM card when it is being pushed in, and when it is al the way in, it will snap back up against the card. (or some other mechanism that tells the phone that a SIM card has been inserted. I don't know)
This mechanism must have gotten stuck and the cleaner must have removed whatever was keeping it from moving.
I DO NOT recommend people doing this, since it may damage your device (I suppose if you are really unlucky, it might even blow up your battery?¿)
A more gentle approach would be to pray off the back cover (haven't tried this myself, but youtube suggest this is fairly easy) and clean / massage the mechanism in a more controlled manor.
Best of luck to all of you! I hope you find a fix for your problem!
^GaMbi
Related
while attempting root on my sprint moto x using the moto x tool kit I decided hey the verizon root might work since theyre both cdma. bad idea. now every time i turn on my phone. com.android.phone force closes and it tells me sim card error. ive already flashed the stock image and I still get the error. any help would be greatly appreciated. thank you.
I attempted the slapmymoto method in the motoxtool kit and selected verizon
bradsinram said:
I attempted the slapmymoto method in the motoxtool kit and selected verizon
Click to expand...
Click to collapse
not sure what you did at all because all the phones are rooted the same way.
i would download the 4.2.2 firmware here
http://sbf.droid-developers.org/download.php?device=0&file=18
then go to this guide
http://forum.xda-developers.com/showthread.php?t=2603358
and follow the guide for returning to stock.
then after you are stock decide if you want to unlock your bootloader or not. then pick the guide based on what you decide and follow it for root
dray_jr said:
not sure what you did at all because all the phones are rooted the same way.
i would download the 4.2.2 firmware here
http://sbf.droid-developers.org/download.php?device=0&file=18
then go to this guide
http://forum.xda-developers.com/showthread.php?t=2603358
and follow the guide for returning to stock.
then after you are stock decide if you want to unlock your bootloader or not. then pick the guide based on what you decide and follow it for root
Click to expand...
Click to collapse
I've my device is 4.4 and ive already returned to stock and am still having the issue?
bradsinram said:
I've my device is 4.4 and ive already returned to stock and am still having the issue?
Click to expand...
Click to collapse
ok but if you did it threw the toolkit you might of still returned to the stock firmware for a different device
i restored completely to stock and am still having the same issue. please help
bradsinram said:
i restored completely to stock and am still having the same issue. please help
Click to expand...
Click to collapse
im going to bump this in hopes someone else takes a look.
can you look under settings/About phone/Status
what dose it way for
Network
signal strength
Mobile netowork type
also do you have a valid imei/meid please dont post this number here just check the number there with the number on the side of the box the phone came in
dray_jr said:
im going to bump this in hopes someone else takes a look.
can you look under settings/About phone/Status
what dose it way for
Network
signal strength
Mobile netowork type
also do you have a valid imei/meid please dont post this number here just check the number there with the number on the side of the box the phone came in
Click to expand...
Click to collapse
it says sprint for network then com.android.phone force closes. then it switches to searching for service. it say no signal strength and mobile network type is unknown. but it seriosuly force closes ever 2 seconds.
bradsinram said:
it says sprint for network then com.android.phone force closes. then it switches to searching for service. it say no signal strength and mobile network type is unknown. but it seriosuly force closes ever 2 seconds.
Click to expand...
Click to collapse
if it keeps force closing then you are not returning the phone to stock. because if you did that would not happen.
so i need you to explain to me what you are using when returning your phone to stock because it is not taking for some reason.
dray_jr said:
if it keeps force closing then you are not returning the phone to stock. because if you did that would not happen.
so i need you to explain to me what you are using when returning your phone to stock because it is not taking for some reason.
Click to expand...
Click to collapse
im using the 4.4 file that the motox toolkit downloads then i extract it to my adb folder and run these commands
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
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
everything appears to sucessfully flash
bradsinram said:
im using the 4.4 file that the motox toolkit downloads then i extract it to my adb folder and run these commands
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
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
everything appears to sucessfully flash
Click to expand...
Click to collapse
so what your now telling me 3-4 post later is that you did not listen to me at all so you asked for help and when i gave you the correct answer on what to do you did not listen.
so i will try this one more time the 4.4 firmware package you keep using from the Moto x toolkit is not the Sprint firmware so STOP using it and download the firmware from the link below. and flash it with the above commands like i told you to do in my first post
http://sbf.droid-developers.org/download.php?device=0&file=734
dray_jr said:
so what your now telling me 3-4 post later is that you did not listen to me at all so you asked for help and when i gave you the correct answer on what to do you did not listen.
so i will try this one more time the 4.4 firmware package you keep using from the Moto x toolkit is not the Sprint firmware so STOP using it and download the firmware from the link below. and flash it with the above commands like i told you to do in my first post
http://sbf.droid-developers.org/download.php?device=0&file=734
Click to expand...
Click to collapse
okay I will do. so i just find it weird they have an almost identical name and both say sprint. but thank you and im download the one you provided now.
dray_jr said:
so what your now telling me 3-4 post later is that you did not listen to me at all so you asked for help and when i gave you the correct answer on what to do you did not listen.
so i will try this one more time the 4.4 firmware package you keep using from the Moto x toolkit is not the Sprint firmware so STOP using it and download the firmware from the link below. and flash it with the above commands like i told you to do in my first post
http://sbf.droid-developers.org/download.php?device=0&file=734
Click to expand...
Click to collapse
so ive used the file you provided me with and am still having the same exact issues. I appreciate your help.
I feel like i need to rewrite the radio partition but which I'm assumung is the NON-HLOS but every time i try to write to it i get permission denied
ok sorry i left out a command i think i know what is going on
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
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
i know you just did this but do it one more time and make sure you do the erase userdata and cache commands and then reboot.
after wiping everything i am not sure what would be wrong i have a sprint device and i have never had this issue.
dray_jr said:
ok sorry i left out a command i think i know what is going on
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
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
i know you just did this but do it one more time and make sure you do the erase userdata and cache commands and then reboot.
after wiping everything i am not sure what would be wrong i have a sprint device and i have never had this issue.
Click to expand...
Click to collapse
yeah I've tried it about ten times now and i think theres something else from the verizon root that mustve gotten flashed and is causing this
Well you have to flash the NON-HLOS.bin or it is not going to work.
Why not just download the full Sprint firmware file(I believe you've already done this) download rsdlite, remove the var line from the xml, and with one click your phone will work fine again.
Steve-x said:
Well you have to flash the NON-HLOS.bin or it is not going to work.
Why not just download the full Sprint firmware file(I believe you've already done this) download rsdlite, remove the var line from the xml, and with one click your phone will work fine again.
Click to expand...
Click to collapse
Thank you so much! I was wondering what kept causing rsd lite to fail. Im lead technician at a spring store and could just AE it but really dont want a refurb, especially since this phone is two days old
sorry but how do I remove the var line?
ive got it figured out thank you for your help
Hi,
I have a Brazilan version XT1097, bootloader unlocked but no root yet.
I cannot install anything from play store because I get an error that does not say much.
All I did was trying to root using a guide I found that tells you to use CF-Autoroot, but it just did not work.
Then I installed TWRP to see if there was any ROMs available since I came from the Nexus 5 and was used to see tons of ROMs on xda to grab and flash.
To my surprise, none is available so far.
Now I am trying to find the original 1097 images to flash on my device and go back to stock.
Might even give up on root, if necessary, but I need the phone back
Any ideas on how to proceed?
A different problem now
The user seco2004 (http://forum.xda-developers.com/member.php?u=4946010) has provided me with his backup image.
I followed the steps on the motorola website to flash all the files but my phone is stuck at the bootloader warning message, that one that says that the bootloader is unlocked.
When I entered TWRP to wipe all over again, it says there is no system installed...
Any pointers are most welcome!
leandroqm said:
The user seco2004 (http://forum.xda-developers.com/member.php?u=4946010) has provided me with his backup image.
I followed the steps on the motorola website to flash all the files but my phone is stuck at the bootloader warning message, that one that says that the bootloader is unlocked.
When I entered TWRP to wipe all over again, it says there is no system installed...
Any pointers are most welcome!
Click to expand...
Click to collapse
I'm not sure if this is what you tried before, but there's pretty much no chance of anything going wrong if you follow the commands:
fastboot oem fb_mode_set
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
mfastboot flash system system.img (maybe you missed this part? instead of the "system.img", you need to flash the system files one at a time, something like: mfastboot flash system systemfile_1.img, the mfastboot flash system systemfile_2.img, and then proceed with the commands below)
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
After all this the phone should boot normally into stock 4.4.4. Sorry for the delay, Tapatalk didn't notify me , hope you got it fixed already.
seco2004 said:
I'm not sure if this is what you tried before, but there's pretty much no chance of anything going wrong if you follow the commands:
fastboot oem fb_mode_set
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
mfastboot flash system system.img (maybe you missed this part? instead of the "system.img", you need to flash the system files one at a time, something like: mfastboot flash system systemfile_1.img, the mfastboot flash system systemfile_2.img, and then proceed with the commands below)
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
After all this the phone should boot normally into stock 4.4.4. Sorry for the delay, Tapatalk didn't notify me , hope you got it fixed already.
Click to expand...
Click to collapse
Yes, I dit it that same night (morning, I should say) by the very same process you described.
Thank you a lot for the images and responses!
leandroqm said:
Yes, I dit it that same night (morning, I should say) by the very same process you described.
Thank you a lot for the images and responses!
Click to expand...
Click to collapse
Did you get it working?
Sent from my XT1097 using Tapatalk
seco2004 said:
Did you get it working?
Sent from my XT1097 using Tapatalk
Click to expand...
Click to collapse
Yes, absolutely!
I upgraded it to lollipop and rooted right afterwards
How did you get a 1097 stock Lollipop image?
TheAquanox said:
How did you get a 1097 stock Lollipop image?
Click to expand...
Click to collapse
secco2004 shared me his backups
But is it 1097 lollipop or 1095 with the módem from 1097? Can you share dais backup? I'm Being unable to tether and would like to find out if it is the rom or the phone.
Greetings !
It was actually the KK 4.4.4 original images.
I had to update to lollipop right after via OTA.
IDK if secco2004 allows me to share it. Could you PM him, please?
He posted recently on the topic.
Yeah, it was actually the 4.4.4 Brazilian firmware, feel free to share it. For lollipop I have just the flasheable zip.
Sent from my XT1097 using Tapatalk
Since secco2004 said it is ok to share, tell me if you want me to sent it somewhere...
It is the XT1097 4.4.4 brazilian original images.
hey, can I have XT1097 stock images please?
I also need it
I flashed NX CM12.1 v3.0 rom and lost gps.
Someone in the thread said that i have to go back to stock, verify gps is working properly... blah, blah, blah.....
So the thing is that i don´t know what stock image to use on my phone and where to get it.
It is a XT1097.
Can any of you guys help me?
Need help please
I've flashed ATT_XT1097_5.0.2_system_ ext4_ root.zip using Mofo.exe and followed directions to the T but soon as its done flashing I reboot back into fastboot mode to wipe the cache but gives me error hab check failed for recovery failed to validate recovery image boot up failed. Please any help would be a life savor i'm lost. Anyone know where to find recovery.img file for Moto X XT1097 stock image file maybe I can flash in fastboot mode? I just hope I Dont have a bricked device. I am stuck in bootloop mode and can't wipe cache.
Thanks!
I really thank you, it worked for me! :good:
let me explain what exactly happened. l was running LiquidSmooth v3.2 on my Moto X. I have flashed few roms previously as well. I was facing no issues whatsoever but still wanted to upgrade to LiquidSmooth v4.0. So this time when I got on fastboot menu
and chose recovery, I got invalid kernel/ ramdisk size error. I was not able to enter recovery menu and this has happened to me for the first time. I chose normal reboot and then even the phone was working fine. But now, things have gone worse. I entered fastboot menu again and by mistake chose factory option instead of recovery. Phone started rebooting i think. As i had installed LiveLog app on my phone all I could see was logs on the screen. I waited for around 45 minutes but phone didnt boot up. I switched off and restarted again but same result. I think it is bricked. Is there any way I can get my phone back to working state? Any kind of help would be appreciated.
Thanks.
Returning to Stock
Step one
Downloading the required drivers and software
Motorola Device Drivers
https://motorola-global-portal.custh...ail/a_id/88481
Android SDK
http://developer.android.com/sdk/index.html
MFastboot(Used for manually downgrading to 4.2.2)
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
For firmware Download from the link below
http://www.filefactory.com/file/3qr..._4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Two
Returning device Stock and Locking Bootloader
1. Open your firmware and extract the files to the same folder as adb/fastboot and mfastboot.
2. open a CMD window and CD into the directory that we just extracted all the files too
3. type below commands one by one
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
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot oem lock
i recommend wiping your device also but that is up to you if you dont want
to then skip the next two commands and just type the reboot command
fastboot erase userdata
fastboot erase cache
fastboot reboot
after your phone is done rebooting you will be completely stock firmware of your choice
Enjoy
crazyworm said:
Returning to Stock
Step one
Downloading the required drivers and software
Motorola Device Drivers
https://motorola-global-portal.custh...ail/a_id/88481
Android SDK
http://developer.android.com/sdk/index.html
MFastboot(Used for manually downgrading to 4.2.2)
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
For firmware Download from the link below
http://www.filefactory.com/file/3qr..._4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Two
Returning device Stock and Locking Bootloader
1. Open your firmware and extract the files to the same folder as adb/fastboot and mfastboot.
2. open a CMD window and CD into the directory that we just extracted all the files too
3. type below commands one by one
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
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot oem lock
i recommend wiping your device also but that is up to you if you dont want
to then skip the next two commands and just type the reboot command
fastboot erase userdata
fastboot erase cache
fastboot reboot
after your phone is done rebooting you will be completely stock firmware of your choice
Enjoy
Click to expand...
Click to collapse
you can def do that but if you want to try to bring it back to life without going to stock you can try this.
Flash your custom recovery again threw fastboot. then after that if you can boot into it just reinstall LS rom and try and boot your phone up if no luck then just follow the above guide from my thread and return to stock and redo everything
Thanks for the help guys. I have a question here : Will returning to stock undo root ? And do I have to unlock the bootloader again ??
Sent from my GT-S5360 using xda app-developers app
d1nesh said:
Thanks for the help guys. I have a question here : Will returning to stock undo root ? And do I have to unlock the bootloader again ??
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
Yes Root Romoved, don't use last command "fastboot oem lock" if you want bootloader still unlocked
Sound advice above... Except there's no reason to lock your bootloader again. I'd skip that part. And remain unlocked. ?
Thanks a lot. I will try this method today and then flash LiquidSmooth v4.0. Just in case if I face any problem, I'll be back.
Sent from my GT-S5360 using xda app-developers app
I'm facing problems downloading the firmware from the filefactory. Is there any mirror link ?
Also, for this operation do I have to use this file only or can I use LiquidSmooth v3.2 file as well?
Sent from my GT-S5360 using xda app-developers app
d1nesh said:
I'm facing problems downloading the firmware from the filefactory. Is there any mirror link ?
Also, for this operation do I have to use this file only or can I use LiquidSmooth v3.2 file as well?
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
what carrier is your phone from i will try and find a good like for the stock firmware.
but like i said i would try to just flash the custom recovery and see if you can boot into it. if you can you might not have to go back to completely stock from the recovery you can iinstall liquid smooth rom. it has its own kernel so it should fix the kernel issue and system issues. if not then you can go back to flashing everything to stock.
It didn't come with any carrier. I bought it here in India.
Sorry for the noobie question here, but does USB debugginv needs to be on for this, as I dont remember if its on or not.
Also, can you please guide me through the steps so that I do not make any mistakes this time. I'm really scared this time and I don't wanna hard brick my phone. I'd be really very thankful.
Sent from my GT-S5360 using xda app-developers app
Thank you for your help, guys.
I think I am back to factory because I'm no longer getting the LiveLogs on the boot up screen. I'm getting the stock Motorola bootup screen that means LiveLogs and all other apps have been removed. But again, I'm still stuck on boot. Its not going past Motorola logo.
One more thing, while returning back to recovery, on cmd screen I was getting <bootloader> Variable not supported error.
PFA
d1nesh said:
It didn't come with any carrier. I bought it here in India.
Sorry for the noobie question here, but does USB debugginv needs to be on for this, as I dont remember if its on or not.
Click to expand...
Click to collapse
No. USB Debugging does not need to be on when using RSDLite or mFastboot.
d1nesh said:
I think I am back to factory because I'm no longer getting the LiveLogs on the boot up screen. I'm getting the stock Motorola bootup screen that means LiveLogs and all other apps have been removed. But again, I'm still stuck on boot. Its not going past Motorola logo.
One more thing, while returning back to recovery, on cmd screen I was getting <bootloader> Variable not supported error.
PFA
Click to expand...
Click to collapse
At this point, I would consider redoing the steps outlined by @dray_jr earlier in this thread.. with a few tweaks...
its important to be using the correct ROM for your phone. Is there fine print on the back of your phone, does it say XT1052? If so, the link to the Asia XT1052 4.4.4 rom should be correct.
Next... use mfastboot for ALL parts, not just system.img, and follow these steps.. Yes, the are very similar to what you did already, and yes, i know some are repeated, that is intentional.
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 reboot
OPTIONAL, but in your case might be necessary: just before the final mfastboot reboot command, issue... mfastboot erase userdata this will erase your apps and data.
If any of these commands fail, please make sure you capture it and post it. (NOTE: there is a way to select and copy on the text from the CMD Prompt window, please do that, rather than screen shot)
Once your phone boots up properly, it will be back to stock, unrooted, but as long as you don't do the "oem lock" command with mfastboot or fastboot, your bootloader will remain unlocked. You can then flash TWRP or other custom recovery and re-root.
Hi guys,
So I have an XT1092. It all started out innocently enough, when I flashed the 5.1 full firmware from the fourth post in this thread. It didn't want to work and got stuck in a... let's just call it a bootloop..., no matter what I did. So I re-flashed the 5.0 firmware that had worked previously. Same thing.
So then I figured that since it's not working, I may as well try converting it to a XT1095 as per this thread. Which worked! I was running 4.4.4 last night and all was good.
Then, it took an OTA in the early hours of this morning, which has since resulted in me losing all ability to use the phone at all.
When I hold the power button, a green light briefly flashes, which typically means that's the battery is dead (it was on charge all night, and still connected at this time). But when I hook it up to my PC, it shows up as a "QHUSB_BULK" - whatever that is.
...what can I do, guys?
Sorry, but there is nothing you can do if it says that. You will have to send it in for repair.
Sent from my XT1095
OP said:
So I have an XT1092. It all started out innocently enough, when I flashed the 5.1 full firmware from the fourth post in this thread. It didn't want to work and got stuck in a... let's just call it a bootloop..., no matter what I did.
Click to expand...
Click to collapse
When you did that, you upgraded the bootloader and partition table to 5.1.
OP said:
So I re-flashed the 5.0 firmware that had worked previously. Same thing.
Click to expand...
Click to collapse
When you did that, it did not downgrade the bootloader and partition table - they stayed on 5.1.
OP said:
So then I figured that since it's not working, I may as well try converting it to a XT1095 as per this thread. Which worked! I was running 4.4.4 last night and all was good.
Click to expand...
Click to collapse
When you did that, it did not downgrade the BL and PT - they stayed on 5.1.
OP said:
Then, it took an OTA in the early hours of this morning, which has since resulted in me losing all ability to use the phone at all.
Click to expand...
Click to collapse
When you did that, the OTA tried to patch the 5.1 BL and PT as if they were the 4.4.4 BL and PT. But you were running the 5.1 BL and PT. That caused a brick.
OP said:
When I hold the power button, a green light briefly flashes, which typically means that's the battery is dead (it was on charge all night, and still connected at this time). But when I hook it up to my PC, it shows up as a "QHUSB_BULK" - whatever that is.
...what can I do, guys?
Click to expand...
Click to collapse
Wait for someone to release the blankflash files for 5.1 (which were never leaked for 4.4.4 or 5.0 so they may never be leaked) or send it in for warranty replacement.
unfnknblvbl said:
Hi guys,
So I have an XT1092. It all started out innocently enough, when I flashed the 5.1 full firmware from the fourth post in this thread. It didn't want to work and got stuck in a... let's just call it a bootloop..., no matter what I did. So I re-flashed the 5.0 firmware that had worked previously. Same thing.
So then I figured that since it's not working, I may as well try converting it to a XT1095 as per this thread. Which worked! I was running 4.4.4 last night and all was good.
Then, it took an OTA in the early hours of this morning, which has since resulted in me losing all ability to use the phone at all.
When I hold the power button, a green light briefly flashes, which typically means that's the battery is dead (it was on charge all night, and still connected at this time). But when I hook it up to my PC, it shows up as a "QHUSB_BULK" - whatever that is.
...what can I do, guys?
Click to expand...
Click to collapse
Well, I see you used my post to downgrade to 4.4.4 and worked for you. And that's odd, because you flashed the "official" firmware of your model previously and got a bootloop. And some people are saying that downgrading your firmware from 5.1 to 4.4.4 will brick and that's not your case.... You bricked after taking the OTA and that's weird because after flashing the 5.1 of your model you upgraded your partition and your boot loader. What I am guessing here is that maybe the partitions and the boot loader of a different version like yours are incompatible with the pure edition. Maybe you can share with us what did you do after the first bootloop to downgrade to the 4.4.4, like what files did your use and what fastboot commands did you use too.
Sorry for your phone, but in several post people are warning that after downgrading from a 5.1 soak you don't have to take OTA.
juliospinoza said:
Sorry for your phone, but in several post people are warning that after downgrading from a 5.1 soak you don't have to take OTA.
Click to expand...
Click to collapse
These aren't Nexus devices. People can't flash whatever they want, downgrade and then take OTAs and never have to worry about bricking.
Rule of thumb - when in doubt don't flash the bootloader or partition table and never take an OTA after downgrading the bootloader.
JulesJam said:
These aren't Nexus devices. People can't flash whatever they want, downgrade and then take OTAs and never have to worry about bricking.
Rule of thumb - when in doubt don't flash the bootloader or partition table and never take an OTA after downgrading the bootloader.
Click to expand...
Click to collapse
That's exactly what I said, but you made it more "sophisticated" taking Nexus devices as an example. Don't see the point to repost.
juliospinoza said:
Don't see the point to repost.
Click to expand...
Click to collapse
My response was succinct, used a memorable distinction as well as a catchy rule of thumb and had adequate paragraph breaks. IOW easier to understand with a nice rhythm to it.
Try to sent to warranty centre , but in my case Motorola didn't cover me this issue.
juliospinoza said:
Maybe you can share with us what did you do after the first bootloop to downgrade to the 4.4.4, like what files did your use and what fastboot commands did you use too.
Click to expand...
Click to collapse
Right, so here's what I did.
1) the 5.1 OTA never worked for me - would always fail during flashing for some reason. So when I found the above post, I flashed the "VICTARA_RETEU_XT1092__5.1_LPE23.32-25.1_cid7_CFC.xml" package with the following commands:
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot reboot
Then seeing as it didn't want to work, and from prior experience with TWRP being annoying, I then flashed the recovery with "mfastboot flash recovery recovery.img"
Then came the bootloops. Now, I say "bootloops" but it was more complicated than that. What would happen is the boot animation would load up, then once the screen "dimmed" it would turn off. As I didn't clear userdata the first time, it would do the whole "android is upgrading x/65749823562743 apps" message... then reboot after the last one, and start again from the start. I cleared cache and userdata and then something else happened; after the screen dimming, it would turn 'off' but apparently still load. Every now & then, the screen would flash on for just an instant. Long enough for me to see some kind of error, but not long enough to find out what.
2) Giving up on this, I re-flashed the 5.0 "RETEUALL_XT1092_5.0_LXE22.46-19_cid7_CFC.xml" package with the following script:
Code:
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash boot boot.img
mfastboot flash recovery twrp-2.8.6.0-victara.img
mfastboot flash system system.img_sparsechunk.0
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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot reboot
Nothing remarkable there, although I notice that I didn't flash gpt.bin. Can't think why I didn't do that right now, tbh
Anyway, exactly the same issue occurred!
3) not having the patience to deal with that **** as it was nearing 3am, I flashed 4.4.4 "TMO_21.21.42.victara_tmo.tmo.en.US" with the following script:
Code:
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 flash fsg fsg.mbn
mfastboot erase userdata
mfastboot erase cache
mfastboot reboot
...which worked! The phone started normally and all seemed good. I was pretty chuffed.
Then, without thinking I accepted the 5.0 OTA when I awoke all bleary-eyed this morning, and she died. And here we are.
Motorola support seems to think I should return it to them, so they're coming to pick it up on Friday morning. heh.
unfnknblvbl said:
Motorola support seems to think I should return it to them, so they're coming to pick it up on Friday morning. heh.
Click to expand...
Click to collapse
They should give you a warranty replacement - their OTAs should have checks in them to fail to update rather than brick a device when you are running a newer BL than the one the OTA was written to update. This is their fault. Poor coding on the part of the software devs who wrote the OTAs.
The OTAs should check the bootloader version. If it is not the version the OTA was meant to update, the OTA should simply fail to update. End of problem. One simple IF-THEN statement would prevent this.
you'd think so....
unfnknblvbl said:
Right, so here's what I did.
1) the 5.1 OTA never worked for me - would always fail during flashing for some reason. So when I found the above post, I flashed the "VICTARA_RETEU_XT1092__5.1_LPE23.32-25.1_cid7_CFC.xml" package with the following commands:
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot reboot
Then seeing as it didn't want to work, and from prior experience with TWRP being annoying, I then flashed the recovery with "mfastboot flash recovery recovery.img"
Then came the bootloops. Now, I say "bootloops" but it was more complicated than that. What would happen is the boot animation would load up, then once the screen "dimmed" it would turn off. As I didn't clear userdata the first time, it would do the whole "android is upgrading x/65749823562743 apps" message... then reboot after the last one, and start again from the start. I cleared cache and userdata and then something else happened; after the screen dimming, it would turn 'off' but apparently still load. Every now & then, the screen would flash on for just an instant. Long enough for me to see some kind of error, but not long enough to find out what.
Click to expand...
Click to collapse
I think I know what generated the bootloop, happened to me two days ago. When you upgraded your system and data partition and didn't erased your data, the old data tried to "fit" the new partition, that's why the system the first time was trying to update your apps, but after failing entered again on bootloop. Don't know why this happens, from 4.4.4 to 5.0 you could upgrade without erasing data and nothing happened.
unfnknblvbl said:
2) Giving up on this, I re-flashed the 5.0 "RETEUALL_XT1092_5.0_LXE22.46-19_cid7_CFC.xml" package with the following script:
Code:
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash boot boot.img
mfastboot flash recovery twrp-2.8.6.0-victara.img
mfastboot flash system system.img_sparsechunk.0
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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot reboot
Nothing remarkable there, although I notice that I didn't flash gpt.bin. Can't think why I didn't do that right now, tbh
Anyway, exactly the same issue occurred!
Click to expand...
Click to collapse
Although you didn't flashed the gpt nothing would happened, just an error on fastboot, because you can't downgrade bootloader, the first time you flashed the new version 60.16 and the version on 5.0 is the 60.11.
The bootloop happened because the same reason, your data was there and the system wasn't able to make it "fit" to the new partition, the one you flashed with the 5.1.[/QUOTE]
unfnknblvbl said:
3) not having the patience to deal with that **** as it was nearing 3am, I flashed 4.4.4 "TMO_21.21.42.victara_tmo.tmo.en.US" with the following script:
Code:
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 flash fsg fsg.mbn
mfastboot erase userdata
mfastboot erase cache
mfastboot reboot
...which worked! The phone started normally and all seemed good. I was pretty chuffed.
Then, without thinking I accepted the 5.0 OTA when I awoke all bleary-eyed this morning, and she died. And here we are.
Motorola support seems to think I should return it to them, so they're coming to pick it up on Friday morning. heh.
Click to expand...
Click to collapse
OK. After your final flash you flashed the system and erased data and cache, and the partitions were "clear" from all apps and other stuff, so the system was able to "fit" your data to the partitions properly, that's why your phone booted as brand new, am I right??? Seems that the partitions are compatible from 4.4.4 to 5.1 only if you erase data.
The problem is the next. The first flash set the new bootloader 60.16 and the new partitions, but when you didn't erase your data and cache the phone created a conflict with the old data and new partitions (that's the reason of the bootloop) but, when you flashed the 4.4.4 and erased your data the phone was able to boot with the new partitions. The brick was caused because of the OTA of 5.0 and that's because 5.0 uses bootloader version 60.11 and you were already on 60.16 and, the big problem with motorola OTA's is that they didn't check the mismatch between bootloaders like fastboot does, so the OTA forced the downgrade "thinking" it was an upgrade and bricked your phone. Fastboot didn't allow you to downgrade bootloader, but clearly OTA does and that's the reason of bricked devices.
Your phone should be on warranty because it wasn't your fault (not entirely) because of faulty OTA's.
Resuming. After you are on bootloader version 60.14 or 60.16 you can't take any 5.0 OTA because the mismatch between old and nw bootloaders.
Glad to see that motorola are taking to warranty. And thanks for your well explained situation so everybody could take it as reference!
juliospinoza said:
I think I know what generated the bootloop, happened to me two days ago. When you upgraded your system and data partition and didn't erased your data, the old data tried to "fit" the new partition, that's why the system the first time was trying to update your apps, but after failing entered again on bootloop. Don't know why this happens, from 4.4.4 to 5.0 you could upgrade without erasing data and nothing happened.
Click to expand...
Click to collapse
I forgot to mention; before attempting the downgrade to 5.0, I was able to enter recovery and do a factory reset - I wiped userdata and even the sdcard, and that's where it started just 'looping' with the odd screen flicker.
The fact that it still shows up as something in Windows Device Manager gives me hope. If it were completely out of warranty, I'd try to hack the Qualcomm rescue tools for other phones that report that same QHSUSB_BULK device into doing something with this.
unfnknblvbl said:
I forgot to mention; before attempting the downgrade to 5.0, I was able to enter recovery and do a factory reset - I wiped userdata and even the sdcard, and that's where it started just 'looping' with the odd screen flicker.
The fact that it still shows up as something in Windows Device Manager gives me hope. If it were completely out of warranty, I'd try to hack the Qualcomm rescue tools for other phones that report that same QHSUSB_BULK device into doing something with this.
Click to expand...
Click to collapse
The issue isn't the tools. The tool for reflashing is there. But you need a bin and hex file specific to your device/bootloader that only Moto has right now. Unless it is released/leaked, SOL right now unfortunately.
Sent from my Moto X 2014 Pure Edition using Tapatalk
So, the phone has been sent back to me on the same day they received it. No call, no email. nothing. Weird. I hope they fixed it - I assume they did, otherwise they would have contacted me for payment info.
I'll report back!
Success!
Replaced main PCB, rear inlay - software upgraded to current version 5.1.1 - checked current drain - QC/CIT passed to manufacturer's specifications. New IMEI.
Click to expand...
Click to collapse
...this is probably because I'm in Australia though, and the warranty-voiding disclaimer about unlocking your bootloader isn't legal here. I think. I am not a lawyer.
New bootloader: 60.16
Bam.
Same Model .. Hard Bricked xt1092
i bought it a month ago from flipkart.
when i was doing the OTA update from 4.4.4 to 5.0.2 the installation finished from the recovery and never booted.
when i try to plug in to PC its shows QHUSB_BULK
i tried blankflash but it says FAILED
all the drivers are installed something that ends with Qualcomm.. 9008
is there any way that i cn unbrick it myself?
warmachine68 said:
i bought it a month ago from flipkart.
when i was doing the OTA update from 4.4.4 to 5.0.2 the installation finished from the recovery and never booted.
when i try to plug in to PC its shows QHUSB_BULK
i tried blankflash but it says FAILED
all the drivers are installed something that ends with Qualcomm.. 9008
is there any way that i cn unbrick it myself?
Click to expand...
Click to collapse
Sorry it is impossible to fix yourself. You will have to send it in for repair.
Sent from my XT1095 using Tapatalk
I downloaded Android Marshmallow after reading news about it through settings/about/system updates.
After downloading, the phone restarted but updatation was stuck after flashing TWRP screen (error screen photo attached)
My phone is
bootloader unlocked,
recovery TWRP
rooted
ROM is stock.
It seems the OTA update will be completed once I have stock recovery,
I have following queries
Is it necessary to revert to stock recovery to complete OTA update?
If yes, how to achieve it, what i learnt through search, I need to find Stock ROM zips and extract recovery (boot.img) and then flash it through adb?
where to look for thea stock rom and is there any easier method
It's risky, a lot of users here for some reasons got stuck whit locked/unlocked bootloader unable to boot and flash anything.
Here you can find all the motog stock roms http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=50
You should wait for the complete rom image for your country/model to pop there instead doing that risky thing you want do.
Thanks
Recently stock rom for xt1079 has been added to the list.
But I m trying to download from filefactory since yesterday but due to some reason, it stops in between and resume isn't supported.
Are there any other hosts
Are you sure the region of that xt1079 is right for your phonr ? check the phone box and the info inside settings to know which region/carrier you have, you must use the same identical 100% stock to avoid problems
And, do no relock bootloader !!!
yes i bought this through online retailer in India.
It is xt1079 Asia
I see in xda forum of moto g 2nd gen most of the time ppl are talking about xt1078.
What's the difference between xt1078/1079 and can't I use xt1078 ROM.
Rooting procedure meant for xt1078 worked fine for me
And Sir is relocking bootloader very risky ? suppose something goes wrong wont I be able to unlock or restore nandroid backup.
Thanks to support from Dr.nic I am finally on android 6.0
Although I have relocked my bootloader, but it is recommended to leave as it is.
If anyone stumbles here with same problem like mine i.e. unable to upgrade to android 6.0 just because of custom recovery, then pls download the firmware from filefactory.com link and flash. I'll add flashing commands as well to this post in near future.
if you have already done this rom change etc, the you must already be having fastboot, adb etc.
after connecting in fastboot mode holding VolDown and Power for few secs
run following commands
[this is for android 6.0 firmware]
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 system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
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 am not great expert, do this only if you have some idea, I may not be able to help you much if something goes wrong.
I can only say it worked for me