OFFICIAL Build MOTO G 2014,XT1068 Marshmallow 6.0 Stock ROM Indian version
Install stock Marshmallow XT1068 by just a single click.
Downloads:
https://drive.google.com/open?id=0B1DHXoau_BBLQ0huYnF4amNuNk0 [Easy Installer]
https://drive.google.com/open?id=0B1DHXoau_BBLS0NBeENMZDJaa28 [Instructions to Install]
Instructions to Install:
Please follow the readme.txt file attached.
What's Working:
Everything!
What's Not Working:
You tell me!
Version Information:
Build Number : MPB24.65-34
System Version : 24.41.34 titan retaildsds.retaildsdsall.en.03 retin
ROM OS Version: 6.0 Marshmallow
Based On: Stock Motorola OS
Status: Stable
Thanks:
Motorola
Lenovo
Special thanks to @reefuge for his easy installer batch file
IF YOU THINK I HELPED YOU PLEASE PRESS THE THANKS BUTTON THAT WON'T COST YOU A THING
Image is too large messgae
Hi,
I followed the steps provided in the readme doc and when I run the EASY INSTALLER.bat file and select option 1, I am consistently seeing 'Image is too large' on my phone screen when in AP Fastboot Flash Mode. If after waiting for this process I exit using option 6 and attempt to reboot my phone then my phone always boots into AP Fastboot Flash Mode with the following message:
Fastboot Reason: Fall-through from normal boot mode
How do I get my phone to boot? I take it the images failed to write and the phone no longer has a ROM to use, is this correct? Any help would be much appreciated.
My installer.bat output is as follows when selecting option 1:
Choose a option:
1 - Flash stock ROM
2 - Flash stock ROM and ReLock
3 - Flash Fixed Logo
4 - Reboot Phone
5 - Factory Reset
6 - Exit
Select your option : 1
RETURNING TO STOCK ROM - FLASH
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) Preflash validati
FAILED (remote failure)
finished. total time: 0.125s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)..
OKAY [ 0.125s]
writing 'motoboot'...
(bootloader) Motoboot: Preflas
(bootloader) Preflash validati
FAILED (remote failure)
finished. total time: 0.187s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.094s]
writing 'logo'...
OKAY [ 0.094s]
finished. total time: 0.187s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.406s]
writing 'boot'...
OKAY [ 0.374s]
finished. total time: 0.780s
FLASHING RECOVERY.....
target max-sparse-size: 256MB
sending 'recovery' (10280 KB).
OKAY [ 0.421s]
writing 'recovery'...
(bootloader) Image size exeede
(bootloader) image size exceed
(bootloader) Failed to flash p
FAILED (remote failure)
finished. total time: 0.484s
FLASHING SYSTEM IMAGE IN MULTI
target max-sparse-size: 256MB
sending 'system' (257467 KB)..
OKAY [ 8.410s]
writing 'system'...
OKAY [ 8.932s]
finished. total time: 17.342s
target max-sparse-size: 256MB
sending 'system' (255482 KB)..
OKAY [ 8.289s]
writing 'system'...
OKAY [ 9.417s]
finished. total time: 17.722s
target max-sparse-size: 256MB
sending 'system' (257534 KB)..
OKAY [ 8.394s]
writing 'system'...
OKAY [ 7.904s]
finished. total time: 16.298s
target max-sparse-size: 256MB
sending 'system' (244425 KB)..
OKAY [ 7.879s]
writing 'system'...
(bootloader) Invalid sparse im
(bootloader) Failed to flash s
FAILED (remote failure)
finished. total time: 10.388s
FLASHING MODEM.......
target max-sparse-size: 256MB
sending 'modem' (50136 KB)...
OKAY [ 1.677s]
writing 'modem'...
OKAY [ 1.468s]
finished. total time: 3.145s
erasing 'modemst1'...
OKAY [ 0.031s]
finished. total time: 0.031s
erasing 'modemst2'...
OKAY [ 0.047s]
finished. total time: 0.047s
target max-sparse-size: 256MB
sending 'fsg' (652 KB)...
OKAY [ 0.109s]
writing 'fsg'...
OKAY [ 5.651s]
finished. total time: 5.760s
ERASING CACHE ......
erasing 'cache'...
OKAY [ 0.366s]
finished. total time: 0.366s
Check your model no.
And if it is correct:
DOWNGRADING from Custom ROM or HIGHER version of STOCK ROM OPTIONS 5,1,3,5,4,6
sanketmsonar said:
Check your model no.
And if it is correct:
DOWNGRADING from Custom ROM or HIGHER version of STOCK ROM OPTIONS 5,1,3,5,4,6
Click to expand...
Click to collapse
Sorry but this sortware is for which country? Is it compatible with UK DS ?
garyben60 said:
Sorry but this sortware is for which country? Is it compatible with UK DS ?
Click to expand...
Click to collapse
Only for Indian device
Please answer
if i flash to stock rom..the twrp will get delete..? the phone will turn back to unrooted..? should i wipe all the cache and system files before installing this rom?
thanks in advance..:good:
iajinkya said:
if i flash to stock rom..the twrp will get delete..? the phone will turn back to unrooted..? should i wipe all the cache and system files before installing this rom?
thanks in advance..:good:
Click to expand...
Click to collapse
TWRP will get replaced by stock recovery and phone will get unrooted,you can wipe cache and system before installing
sanketmsonar said:
TWRP will get replaced by stock recovery and phone will get unrooted,you can wipe cache and system before installing
Click to expand...
Click to collapse
thanks..bro..:good:
when installing this file will it also upgrade my bootloader version from v48.83 to 48.86??
Help devs WiFi won't turn on there is no persist folder in root need to a WiFi fix
Try clean flashing
akashbhosale said:
Help devs WiFi won't turn on there is no persist folder in root need to a WiFi fix
Click to expand...
Click to collapse
Try clean flashing again...
1) Install TWRP recovery
2)Go to wipe > advance wipe > dalvik, cache, system, data
3)Turn off phone > Go to recovery mode (hold volume down + power)
4)Connect to PC with proper drivers installed
5) Run the installer again
Hope this fixes...waiting for your reply
Cheers​
I have locked bootloader with stock marshmallow. Can I use this method to reinstall marshmallow
koboji said:
I have locked bootloader with stock marshmallow. Can I use this method to reinstall marshmallow
Click to expand...
Click to collapse
For the safer side you should unlock the bootloader because the bootloader itself is a firmware which is OS dependent and some bootloader versions wont work for 6.0.
go to http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818
Dont worry its just 10 mins work.. Happy flashing dude
Click Thanks if it helped
upgrading from custom rom 4.4.4 to 6.0
sanketmsonar said:
Only for Indian device
Click to expand...
Click to collapse
i also want to upgrade my moto g2014 from custom rom 4.4.4 to 6.0 marshmallow, will there be any kind of problem or my mobile will get dead during this process? pls help, my handset is an indian device.
Hi. I have MotoG2 XT 1068 in India. I want to know how to get VoLTE and 4G from Reliance Jio on my MotoG2. Please let em know any ROM which will work for this. Thanks
clive48 said:
Hi. I have MotoG2 XT 1068 in India. I want to know how to get VoLTE and 4G from Reliance Jio on my MotoG2. Please let em know any ROM which will work for this. Thanks
Click to expand...
Click to collapse
An XT1068 doesn't support 4g/LTE.
Send with my Moto G4 Plus with CM13 (XT1642) using Tapatalk!
I m on turbo rom MM 6.0.1 and want to flash stock MM but without relocking bootloader so which steps i have to follow and more querry will my touch bug problem resolved after flashing this rom bcoz for last 2 month i have encountered with this touch problem before that my Stock MM works flawlessly
Sent from my Moto G 2014 using Tapatalk
chandan kumar_92 said:
I m on turbo rom MM 6.0.1 and want to flash stock MM but without relocking bootloader so which steps i have to follow and more querry will my touch bug problem resolved after flashing this rom bcoz for last 2 month i have encountered with this touch problem before that my Stock MM works flawlessly
Click to expand...
Click to collapse
I am on stock MM and touch problem is killing me.I even installed lollipop but no benefit. Now i am gonna try some custom roms
koboji said:
I am on stock MM and touch problem is killing me.I even installed lollipop but no benefit. Now i am gonna try some custom roms
Click to expand...
Click to collapse
I have same problem bro after trying lots of custom ROM now I am on cm 13 and it eliminated my touch latency issue try it...
A biiiiiiiiiiiiiiiiiiiiiiig Thanks
I had trouble with "No Service" with brazilian version.
You made my device restored to normal situation.
Thanks a TON.
Related
Hi all.
Had a moto g for a while and had no problems at all, until yesterday: WhatsApp crashed and said do I want to restore the history - I chose yes, and then it looked as if the app crashed, a black screen appeared
Turn the phone on/off and after the boot process has finished (android/motorola logo) the phone is once again stuck on the black screen -
Tried clearing the cache from the recovery mode , I've tried using fastboot and flashing the ROM back to 4.4.4 - but had absolutely no success
It was suggested to install ClockWordMod recovery or TWM, and I did this using fastboot, fastboot says it's complete and ok, but then everytime I go to recovery mode I have the lying down android saying no command, and the only place I can get too from there is the normal android recovery screen , I've tried reseting the factory defaults, clearing cache , but I can'#t get anything to work
Any help/advice is really appreciated - does anyone know why I cant boot into clockwork recovery after having flashed it successfully according to fastboot?
Thanks
Mark
You just can flash the factory firmware (stock) and relock the bootloader using mfastboot v2. It will fix this, I had this problem two times and the process above got me out of it. Also if first flash gives errors like partition and fallthrough, you will have to flash the commands once again. It will completely restore your device to normal.
Press thanks if this helps.
ArtRahul said:
You just can flash the factory firmware (stock) and relock the bootloader using mfastboot v2. It will fix this, I had this problem two times and the process above got me out of it. Also if first flash gives errors like partition and fallthrough, you will have to flash the commands once again. It will completely restore your device to normal.
Press thanks if this helps.
Click to expand...
Click to collapse
Thanks for the reply
Ive been looking at fastboot/adb -I had tried flshing back to 4.4.4 using fastboot also tried recovery roms like twrm
I'm not really sure how to do what you describe above , I cant find the stock firmware....I need UK 4.4.4 -- the links i come across are always dead
iyou got a link?
thanks!
You don't need the files for UK. Files for any other country will also work. Here's a tool how to restore to 4.4.4, and there are the images for UK too, I just checked, the link is working. http://forum.xda-developers.com/showthread.php?t=2983295
mapito said:
Thanks for the reply
Ive been looking at fastboot/adb -I had tried flshing back to 4.4.4 using fastboot also tried recovery roms like twrm
I'm not really sure how to do what you describe above , I cant find the stock firmware....I need UK 4.4.4 -- the links i come across are always dead
iyou got a link?
thanks!
Click to expand...
Click to collapse
But why you want 4.4.4 firmware, haven't you yet updated it to 5.0.2??
And if you want the factory firmware image for stock 5.0.2, it's here -> https://drive.google.com/open?id=0Bzr0qvz6uRerOGRfOEptU2p0ZkU
and
also you'll first need to update your bootloader to lollipop then you're ready to go.
ArtRahul said:
But why you want 4.4.4 firmware, haven't you yet updated it to 5.0.2??
And if you want the factory firmware image for stock 5.0.2, it's here -> https://drive.google.com/open?id=0Bzr0qvz6uRerOGRfOEptU2p0ZkU
and
also you'll first need to update your bootloader to lollipop then you're ready to go.
Click to expand...
Click to collapse
I was on Lollipop yea, but I was havng issues as above so thought id downgrade
how do i update the bootloader?!
I'm a bit confused by what I'm reading everywhere
do I need to go back to 4,4,4 or stay on Lollipop?! and also why would i need to update the bootloader
mapito said:
I was on Lollipop yea, but I was havng issues as above so thought id downgrade
how do i update the bootloader?!
I'm a bit confused by what I'm reading everywhere
do I need to go back to 4,4,4 or stay on Lollipop?! and also why would i need to update the bootloader
Click to expand...
Click to collapse
any chance you could put that stock firmware somewhere else? EVERY time i try and dl off google drive it NEVER ever finishes gets near and then says download interrupted
I did try 4.4.4.
and i got the following;
MOTO G 2nd GEN Kitkat 4.4.4 FIRMWARE Flasher
Plug in USB CABLE and Put Phone in AP FASTBOOT Flash Mode
Press any key to continue . . .
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
To cancel Unplug and Close program
Press any key to continue
FLASHING PARTITIONS.
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.020s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.310s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.100s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.360s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.045s]
writing 'logo'...
OKAY [ 0.078s]
finished. total time: 0.130s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.370s]
writing 'boot'...
OKAY [ 0.235s]
finished. total time: 0.610s
FLASHING RECOVERY.....
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.380s]
writing 'recovery'...
OKAY [ 0.200s]
finished. total time: 0.585s
FLASHING SYSTEM IMAGE IN MULTIPLE SECTIONS......
target max-sparse-size: 256MB
sending 'system' (257527 KB)...
OKAY [ 8.376s]
writing 'system'...
OKAY [ 4.691s]
finished. total time: 13.072s
target max-sparse-size: 256MB
sending 'system' (260629 KB)...
OKAY [ 8.502s]
writing 'system'...
OKAY [ 4.423s]
finished. total time: 12.931s
target max-sparse-size: 256MB
sending 'system' (255304 KB)...
OKAY [ 8.312s]
writing 'system'...
OKAY [ 4.786s]
finished. total time: 13.109s
target max-sparse-size: 256MB
sending 'system' (76792 KB)...
OKAY [ 2.531s]
writing 'system'...
OKAY [ 1.273s]
finished. total time: 3.804s
FLASHING MODEM.......
target max-sparse-size: 256MB
sending 'modem' (49252 KB)...
OKAY [ 1.641s]
writing 'modem'...
OKAY [ 0.827s]
finished. total time: 2.478s
erasing 'modemst1'...
OKAY [ 0.015s]
finished. total time: 0.015s
erasing 'modemst2'...
OKAY [ 0.010s]
finished. total time: 0.015s
target max-sparse-size: 256MB
sending 'fsg' (650 KB)...
OKAY [ 0.095s]
writing 'fsg'...
OKAY [ 0.075s]
finished. total time: 0.170s
ERASING CACHE ......
erasing 'cache'...
OKAY [ 0.020s]
finished. total time: 0.020s
ERASING USERDATA.......
erasing 'userdata'...
OKAY [ 0.025s]
finished. total time: 0.025s
DONE!.........PRESS ANY KEY TO REBOOT
which is because the firmware isnt suitable for the device?
also bootloader is 48.82 - thats ok? dont need to update it , right?
I just tried the easy installer for lollipop and while it looked like it had worked (see below)
it STILL stuck on the black creen after boot logos
Plug in USB CABLE and Put Phone in AP FASTBOOT Flash Mode
Press any key to continue . . .
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
To cancel Unplug and Close program
Press any key to continue
erasing 'userdata'...
OKAY [ 0.035s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.022s]
erasing 'cache'...
OKAY [ 0.018s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.028s]
finished. total time: 0.135s
FLASHING PARTITIONS.
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.036s]
writing 'partition'...
OKAY [ 0.310s]
finished. total time: 0.354s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.112s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.969s]
finished. total time: 1.088s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.079s]
writing 'logo'...
OKAY [ 0.051s]
finished. total time: 0.136s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.390s]
writing 'boot'...
OKAY [ 0.217s]
finished. total time: 0.615s
FLASHING RECOVERY.....
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.400s]
writing 'recovery'...
OKAY [ 0.211s]
finished. total time: 0.625s
FLASHING SYSTEM IMAGE IN MULTIPLE SECTIONS......
target max-sparse-size: 256MB
sending 'system' (258868 KB)...
OKAY [ 8.879s]
writing 'system'...
OKAY [ 4.770s]
finished. total time: 17.575s
target max-sparse-size: 256MB
sending 'system' (254994 KB)...
OKAY [ 8.729s]
writing 'system'...
OKAY [ 5.009s]
finished. total time: 13.750s
target max-sparse-size: 256MB
sending 'system' (260623 KB)...
OKAY [ 9.289s]
writing 'system'...
OKAY [ 4.744s]
finished. total time: 14.039s
target max-sparse-size: 256MB
sending 'system' (255649 KB)...
OKAY [ 8.650s]
writing 'system'...
OKAY [ 4.390s]
finished. total time: 13.044s
target max-sparse-size: 256MB
sending 'system' (32272 KB)...
OKAY [ 1.126s]
writing 'system'...
OKAY [ 0.553s]
finished. total time: 1.687s
FLASHING MODEM.......
target max-sparse-size: 256MB
sending 'modem' (49364 KB)...
OKAY [ 1.738s]
writing 'modem'...
OKAY [ 0.835s]
finished. total time: 2.578s
erasing 'modemst1'...
OKAY [ 0.015s]
finished. total time: 0.018s
erasing 'modemst2'...
OKAY [ 0.015s]
finished. total time: 0.019s
target max-sparse-size: 256MB
sending 'fsg' (651 KB)...
OKAY [ 0.096s]
writing 'fsg'...
OKAY [ 0.047s]
finished. total time: 0.150s
ERASING CACHE ......
erasing 'cache'...
OKAY [ 0.022s]
finished. total time: 0.031s
ERASING USERDATA.......
erasing 'userdata'...
OKAY [ 0.033s]
finished. total time: 0.043s
DONE!.........PRESS ANY KEY TO REBOOT
rebooting...
finished. total time: 0.005s
Press any key to exit
mapito said:
I just tried the easy installer for lollipop and while it looked like it had worked (see below)
it STILL stuck on the black creen after boot logos
Plug in USB CABLE and Put Phone in AP FASTBOOT Flash Mode
Press any key to continue . . .
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
To cancel Unplug and Close program
Press any key to continue
erasing 'userdata'...
OKAY [ 0.035s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.022s]
erasing 'cache'...
OKAY [ 0.018s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.028s]
finished. total time: 0.135s
FLASHING PARTITIONS.
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.036s]
writing 'partition'...
OKAY [ 0.310s]
finished. total time: 0.354s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.112s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.969s]
finished. total time: 1.088s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.079s]
writing 'logo'...
OKAY [ 0.051s]
finished. total time: 0.136s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.390s]
writing 'boot'...
OKAY [ 0.217s]
finished. total time: 0.615s
FLASHING RECOVERY.....
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.400s]
writing 'recovery'...
OKAY [ 0.211s]
finished. total time: 0.625s
FLASHING SYSTEM IMAGE IN MULTIPLE SECTIONS......
target max-sparse-size: 256MB
sending 'system' (258868 KB)...
OKAY [ 8.879s]
writing 'system'...
OKAY [ 4.770s]
finished. total time: 17.575s
target max-sparse-size: 256MB
sending 'system' (254994 KB)...
OKAY [ 8.729s]
writing 'system'...
OKAY [ 5.009s]
finished. total time: 13.750s
target max-sparse-size: 256MB
sending 'system' (260623 KB)...
OKAY [ 9.289s]
writing 'system'...
OKAY [ 4.744s]
finished. total time: 14.039s
target max-sparse-size: 256MB
sending 'system' (255649 KB)...
OKAY [ 8.650s]
writing 'system'...
OKAY [ 4.390s]
finished. total time: 13.044s
target max-sparse-size: 256MB
sending 'system' (32272 KB)...
OKAY [ 1.126s]
writing 'system'...
OKAY [ 0.553s]
finished. total time: 1.687s
FLASHING MODEM.......
target max-sparse-size: 256MB
sending 'modem' (49364 KB)...
OKAY [ 1.738s]
writing 'modem'...
OKAY [ 0.835s]
finished. total time: 2.578s
erasing 'modemst1'...
OKAY [ 0.015s]
finished. total time: 0.018s
erasing 'modemst2'...
OKAY [ 0.015s]
finished. total time: 0.019s
target max-sparse-size: 256MB
sending 'fsg' (651 KB)...
OKAY [ 0.096s]
writing 'fsg'...
OKAY [ 0.047s]
finished. total time: 0.150s
ERASING CACHE ......
erasing 'cache'...
OKAY [ 0.022s]
finished. total time: 0.031s
ERASING USERDATA.......
erasing 'userdata'...
OKAY [ 0.033s]
finished. total time: 0.043s
DONE!.........PRESS ANY KEY TO REBOOT
rebooting...
finished. total time: 0.005s
Press any key to exit
Click to expand...
Click to collapse
It's because your bootloader is updated and it cannot accept kitkat now and you will have to flash the 5.0.2 over this bootloader else you'll get these errors(black screen) again. Atlast what you need to do is to flash the stock 5.0.2 firmware via mfastboot v2 and you'll get back your device fully working.
These are the commands ->
Code:
------------------------------------------------------------------|
Moto G 2014 Stock 5.0.2 Restore Script
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
mfastboot.exe reboot
------------------------------------------------------------------|
And if the link I provided doesn't work then try searching for these two files
1. Motorola Moto G 2014 Stock 5.0.2 Factory Firmware
2. mfastboot v2
You can easily get that on XDA, after you download, just unzip the firmware file in the mfastboot's folder and then in cmd flash above commands.
ArtRahul said:
It's because your bootloader is updated and it cannot accept kitkat now and you will have to flash the 5.0.2 over this bootloader else you'll get these errors(black screen) again. Atlast what you need to do is to flash the stock 5.0.2 firmware via mfastboot v2 and you'll get back your device fully working.
These are the commands ->
Code:
------------------------------------------------------------------|
Moto G 2014 Stock 5.0.2 Restore Script
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
mfastboot.exe reboot
------------------------------------------------------------------|
And if the link I provided doesn't work then try searching for these two files
1. Motorola Moto G 2014 Stock 5.0.2 Factory Firmware
2. mfastboot v2
You can easily get that on XDA, after you download, just unzip the firmware file in the mfastboot's folder and then in cmd flash above commands.
Click to expand...
Click to collapse
hey thanks
so needs to be mfastboot2 not fastboot?
is there anyway to check exact version of android i had without being able to get in os..i ink it was 5.0.2
mapito said:
hey thanks
so needs to be mfastboot2 not fastboot?
is there anyway to check exact version of android i had without being able to get in os..i ink it was 5.0.2
Click to expand...
Click to collapse
If last time, on your phone, you used Lollipop, then it's 5.0.2 and if KitKat then it's 4.4.4, simple.
And you'll need mfastboot2
turns out the problem could be more than i thought..when i try to wipe user data/clear cache i get failed errors on the phone
..while it says the phone has been flashed successfully it never works
i guess this has something to do with the fact cant erase user data/clear cache
other people have had the same issues and no fix reported beyond getting a replacement
http://forum.xda-developers.com/moto-g-2014/help/factory-reset-t3075587/page4
mapito said:
turns out the problem could be more than i thought..when i try to wipe user data/clear cache i get failed errors on the phone
..while it says the phone has been flashed successfully it never works
i guess this has something to do with the fact cant erase user data/clear cache
other people have had the same issues and no fix reported beyond getting a replacement
Click to expand...
Click to collapse
what errors are you getting now...
are these (failed to validate system image/ fall-through from normal boot)??
If these are the errors you will have to re-flash the commands given above(as I told you in previous post).
I had same problem twice yet, and fixed by this process, so I can make you sure that you too should try again, and report the news here. I am here to help you.
Try using fastboot to boot philz cwm temporarily.
Fastboot boot Phil'srecovery.IMG
(or whatever its named)
Then use philz to format your partitions. Assuming twrp is installed already, Reboot to enter twrp. then use twrp to format partitions. Install ROM.
Sent from my Moto G 2014 using XDA Free mobile app
no TWR installed can i still use this recovery img or wont it work?
mapito said:
no TWR installed can i still use this recovery img or wont it work?
Click to expand...
Click to collapse
Install twrp recovery.
Sent from my Moto G 2014 using XDA Free mobile app
I cant mate, everytime I install it it says successfu;l but when i reboot its not there..I think there's a problem with the motherboard oe eeMC memory as when i try andwipe user data/cache it comes back saying failed
so I guess it cant write to the storage which is why i cant get TWRP to work
any ideas what to do here? fastboot says everythings worked..but clearly hasn't as cant get into TWRP or CWM even tried flashing stock sand nothing..but fastboot - w shows errors
reading on here people suggest its to do with the eeMC, itsa almost like the storage is set to read only
mapito said:
I cant mate, everytime I install it it says successfu;l but when i reboot its not there..I think there's a problem with the motherboard oe eeMC memory as when i try andwipe user data/cache it comes back saying failed
so I guess it cant write to the storage which is why i cant get TWRP to work
any ideas what to do here? fastboot says everythings worked..but clearly hasn't as cant get into TWRP or CWM even tried flashing stock sand nothing..but fastboot - w shows errors
reading on here people suggest its to do with the eeMC, itsa almost like the storage is set to read only
Click to expand...
Click to collapse
Did you try booting into philz with the command I gave you yet? Doesn't install, just boots the recovery image.
Sent from my Moto G 2014 using XDA Free mobile app
hey thanks for replyingI hadn't yet
I'll try that in a minute just grabbing the Philz recovery image
hope this works
thanks!
This phone has not been rooted or unlocked, I was running official MM OTA when suddenly last night it stopped booting. The Moto logo appears and then it goes to black and stays there for eternity while draining battery. I tried going into recovery mode and wiping cache + factory reset, but it didn't help. The "restore-to-stock" tool floating around the internet fails as well:
Test
error: device not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.003s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.366s
target reported max download size of 536870912 bytes
sending 'bootloader' (2699 KB)...
OKAY [ 0.061s]
writing 'bootloader'...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing pmic ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing hyp ...
(bootloader) flashing sdi ...
OKAY [ 2.715s]
finished. total time: 2.778s
target reported max download size of 536870912 bytes
sending 'logo' (2001 KB)...
OKAY [ 0.046s]
writing 'logo'...
OKAY [ 0.040s]
finished. total time: 0.090s
target reported max download size of 536870912 bytes
sending 'boot' (40960 KB)...
OKAY [ 0.922s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.617s
target reported max download size of 536870912 bytes
sending 'recovery' (41040 KB)...
OKAY [ 0.916s]
writing 'recovery'...
OKAY [ 1.370s]
finished. total time: 2.288s
target reported max download size of 536870912 bytes
sending 'system' (260220 KB)...
OKAY [ 5.515s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
Click to expand...
Click to collapse
If I attempt to unlock the bootloader I get '(bootloader) Check 'Allow OEM Unlock' in Developer Options.' - which I can't do since the phone is bricked.
What can I do?
DrGamut said:
This phone has not been rooted or unlocked, I was running official MM OTA when suddenly last night it stopped booting. The Moto logo appears and then it goes to black and stays there for eternity while draining battery. I tried going into recovery mode and wiping cache + factory reset, but it didn't help. The "restore-to-stock" tool floating around the internet fails as well:
If I attempt to unlock the bootloader I get '(bootloader) Check 'Allow OEM Unlock' in Developer Options.' - which I can't do since the phone is bricked.
What can I do?
Click to expand...
Click to collapse
If you are not rooted or unlocked, time to take it to Motorola... Call em!
Naddict said:
If you are not rooted or unlocked, time to take it to Motorola... Call em!
Click to expand...
Click to collapse
This is my only option then? I was hoping for something faster, but if that's the only option I'll take it.
Problem was solved by flashing the 6.0 stock firmware found here!!!
DrGamut said:
Problem was solved by flashing the 6.0 stock firmware found here!!!
Click to expand...
Click to collapse
I'm in the same exact boat as you. I tried flashing everything under Android 6.0 on that page but no luck. Mine still bootloops. Exactly how did you do it? Thanks
iflyimpilot said:
I'm in the same exact boat as you. I tried flashing everything under Android 6.0 on that page but no luck. Mine still bootloops. Exactly how did you do it? Thanks
Click to expand...
Click to collapse
Another XT1575 user in the same boat. What procedures did you follow?
** View the making of moto downgrade tool at https://youtu.be/xaJKx9Vqdjc ***
Please like and subscribe to my youtube channel to encourage me to create more tools for the members of xda ! I really really appreciate it
Moto Downgrade Tool is a tool that I have quickly created to SAFELY downgrade android marshmallow to android lollipop on the XT1541 model.
You need Python 3.5 installed to run this program !!
make sure your phone is plugged into your pc and in fastboot mode when you start the tool.
INSTALL MOTO DRIVERS BEFORE USING THE TOOL !!!!
ADB and Fastboot is included in the downgrade tool.
Please comment if you have any issues ! This tool has been tested a few times by myself on my phone. , so it is guaranteed to be able to function correctly !
XDA:DevDB Information
Moto Downgrade Utility, Tool/Utility for the Moto G 2015
Contributors
therealduff1
Version Information
Status: Stable
Current Stable Version: 1.0
Created 2016-03-02
Last Updated 2016-03-02
Keep going on Master!
Sorry for the off topic questions
I'm searching a Rom with multi window feature + floating windows apps like last Sammy's roms for XT1541 do you know any?
Currently using last Resurrection Remix from Vatsal that have multi window but not floating windows
One off topic more:
I have XT1541 European version obtained in Spain but I'm using it in Argentina and my mobile connection (4g) its very slow
I have to change the modem or something else?
Thanks a lot mate!
Enviado desde mi XT1541 mediante Tapatalk
fedez said:
Keep going on Master!
Sorry for the off topic questions
I'm searching a Rom with multi window feature + floating windows apps like last Sammy's roms for XT1541 do you know any?
Currently using last Resurrection Remix from Vatsal that have multi window but not floating windows
One off topic more:
I have XT1541 European version obtained in Spain but I'm using it in Argentina and my mobile connection (4g) its very slow
I have to change the modem or something else?
Thanks a lot mate!
Enviado desde mi XT1541 mediante Tapatalk
Click to expand...
Click to collapse
No need to be sorry for off topic questions !
About the rom , i am not to sure about finding a rom with floating windows , but i would like that aswell !
Also , about using a european device in a different location, this is probably due to different network bands. I would NOT reccomend you flash another models modem, as this could hard brick your phone .
I foyu have any other questions, dont hesitate to ask !
I want to downgrade from stock mm(not rooted) to LP, possible?
arun356y said:
I want to downgrade from stock mm(not rooted) to LP, possible?
Click to expand...
Click to collapse
Using my tool , yes ! . Remember not to accept ota tho
How are you doing the downgrade without having the bootloader unlocked???
Also, is this flashing EVERYTHING, including the bootloader and partition table, or is this just a tool to perform the "normal" downgrade of flashing a factory firmware image and skipping gpt.bin and bootloader.img?
therealduff1 said:
Using my tool , yes ! . Remember not to accept ota tho
Click to expand...
Click to collapse
not to accept ota, why? if in future I want to update then?
acejavelin said:
How are you doing the downgrade without having the bootloader unlocked???
Also, is this flashing EVERYTHING, including the bootloader and partition table, or is this just a tool to perform the "normal" downgrade of flashing a factory firmware image and skipping gpt.bin and bootloader.img?
Click to expand...
Click to collapse
This tool flashes SIGNED images, which means it does not need bootloader unlock. Also , it skips gpt.bin and bootloader.img . It is a normal downgrade, but i made this tool for people who dont want to risk bricking their phones typing the wrong command or accidentally flashing gpt.bin or bootloader.img
therealduff1 said:
This tool flashes SIGNED images, which means it does not need bootloader unlock. Also , it skips gpt.bin and bootloader.img . It is a normal downgrade, but i made this tool for people who dont want to risk bricking their phones typing the wrong command or accidentally flashing gpt.bin or bootloader.img
Click to expand...
Click to collapse
So if I use fastboot and flash a lp I just need to skip those 2 files right?
Downgrading from Rooted Stock MM
I have the XT1541 rooted on stock MM, can i downgrade to stock lollipop without bricking the phone ?
I also flashed the squid kernel r15b (latest)
BurningKoala said:
So if I use fastboot and flash a lp I just need to skip those 2 files right?
Click to expand...
Click to collapse
No need to use fastboot if you trust my programming . but yes , skip gpt.bin and bootloader.IMG and you will be fine my program automatically does that
Hello does my xt1541 need to be unlocked and rooted for this tool to work and downgrade from mm to lollipop?
Agiofws said:
Hello does my xt1541 need to be unlocked and rooted for this tool to work and downgrade from mm to lollipop?
Click to expand...
Click to collapse
No root needed !
Luigi_Manga said:
Ok then, I'll try tonight, does this work whit every rom despite the different number of sparsechunks?
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Yes it should work perfectly
Didn't work, still on the crappy 6.0
Partition table has been skipped!
Bootloader has been skipped!
target reported max download size of 268435456 bytes
sending 'logo' (917 KB)...
OKAY [ 0.040s]
writing 'logo'...
OKAY [ 0.071s]
finished. total time: 0.114s
boot logo has been flashed
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.649s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.183s
boot.img has been flashed
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.651s]
writing 'recovery'...
OKAY [ 0.961s]
finished. total time: 1.616s
Stock lollipop recovery has now been flashed
target reported max download size of 268435456 bytes
sending 'system' (262140 KB)...
OKAY [ 10.071s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.515s
System part 1 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (262143 KB)...
OKAY [ 10.079s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.124s
System part 2 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (232632 KB)...
OKAY [ 8.988s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.060s
System part 3 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (233355 KB)...
OKAY [ 8.971s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.014s
System part 4 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (257122 KB)...
OKAY [ 9.884s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.927s
System part 5 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (236089 KB)...
OKAY [ 9.090s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.124s
System part 7 has been flashed
system partitions successfully flashed
target reported max download size of 268435456 bytes
sending 'modem' (36940 KB)...
OKAY [ 1.423s]
writing 'modem'...
OKAY [ 0.994s]
finished. total time: 2.423s
Flashed Mobile Data Connection Chip Data
erasing 'modemst1'...
OKAY [ 0.019s]
finished. total time: 0.021s
erasing 'modemst2'...
OKAY [ 0.014s]
finished. total time: 0.015s
Old data erased
target reported max download size of 268435456 bytes
sending 'fsg' (2031 KB)...
OKAY [ 0.083s]
writing 'fsg'...
OKAY [ 0.083s]
finished. total time: 0.169s
Flashed FSG
erasing 'cache'...
OKAY [ 0.019s]
finished. total time: 0.021s
cache erased
erasing 'userdata'...
OKAY [ 0.199s]
finished. total time: 0.201s
userdata partition formatted
rebooting...
finished. total time: 0.006s
flash finished
***PLEASE READ BELOW***
YOU MUST NOT ACCEPT ANY OTA UPDATES ON YOUR PHONE WHILE IT IS RUNNING LOLLIPOP
OR YOU ARE RISKING A HARD BRICK DUE TO UPGRADING THE BOOTLOADER WHICH IS AT A DI
FFERENT VERSION
THAN EXPECTED
and thats all !
enjoy lollipop again!
Press any key to continue . . .
Click to expand...
Click to collapse
Sorry for the noob question but does the bootloader have to be unlocked?
BurningKoala said:
Didn't work, still on the crappy 6.0
Click to expand...
Click to collapse
Agiofws said:
Sorry for the noob question but does the bootloader have to be unlocked?
Click to expand...
Click to collapse
Downgrade using fastboot it's not possible without unlocked bootloader, that's why I think it didn't work.
coolizard said:
Downgrade using fastboot it's not possible without unlocked bootloader, that's why I think it didn't work.
Click to expand...
Click to collapse
I flashed mine using a locked bootloader
BurningKoala said:
Didn't work, still on the crappy 6.0
Click to expand...
Click to collapse
Ok right , this is a problem with the image, not my program . Are you flashing the correct image for your phone ?
therealduff1 said:
Ok right , this is a problem with the image, not my program . Are you flashing the correct image for your phone ?
Click to expand...
Click to collapse
Yes, I flashed the xt1541 vodafone EU that was on my phone (now I'm on vodafone 6.0), did you think that it's better I flash the no brand eu version?
edit: same errors with the retail eu
Hello all,
I'm from France, I just get one XT1581 (Moto X Force from China), all was ok, but I was frustrated when i saw that it was stucked in 5.1.1, with no updates.
So I flashed with 6.0 MX (for Mexico...found that AFTER), and if SIM is found (SIM code is needed), no carrier at all. But when i go to mobile network settings, I can see that he got apn settings from the SIM (my provider apn is here).
I downloaded an EU 6.0, flashed it : WIFI is OK, SIM is found (SIM code is needed), but no carrier. Exactly as if i was MX version.
I tried to flash back to 5.1.1 CN, worse : no SIM detected (SIM code not needed), no WIFI (if I activate WIFI, it auto deactivate 1 second after).
I don't know what to do now
Please help !
Are you sure that you got all OK after flashing with fastboot? Do you see IMEI?
Thanks for your reply,
Yes I see IEMI.
Do you think I would be able to use XT1581 (from China) in 6.0 and get carrier ?
I will try to flash 5.1.1CN with fastboot another time.
EDIT : flashed
C:\Users\laure\Desktop\FastBoot_Motorola - Copie>mfastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
sending 'bootloader' (2781 KB)...
OKAY [ 0.084s]
writing 'bootloader'...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing pmic ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing hyp ...
(bootloader) flashing sdi ...
OKAY [ 1.508s]
finished. total time: 1.594s
C:\Users\laure\Desktop\FastBoot_Motorola - Copie>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (40960 KB)...
OKAY [ 1.263s]
writing 'boot'...
OKAY [ 0.910s]
finished. total time: 2.176s
C:\Users\laure\Desktop\FastBoot_Motorola - Copie>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (41040 KB)...
OKAY [ 1.276s]
writing 'recovery'...
OKAY [ 0.900s]
finished. total time: 2.178s
C:\Users\laure\Desktop\FastBoot_Motorola - Copie>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (259725 KB)...
OKAY [ 7.784s]
writing 'system'...
OKAY [ 6.694s]
finished. total time: 14.481s
C:\Users\laure\Desktop\FastBoot_Motorola - Copie>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (252133 KB)...
OKAY [ 7.564s]
writing 'system'...
OKAY [ 5.744s]
finished. total time: 13.311s
C:\Users\laure\Desktop\FastBoot_Motorola - Copie>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (259762 KB)...
OKAY [ 7.791s]
writing 'system'...
OKAY [ 5.864s]
finished. total time: 13.658s
C:\Users\laure\Desktop\FastBoot_Motorola - Copie>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (253228 KB)...
OKAY [ 7.555s]
writing 'system'...
OKAY [ 5.570s]
finished. total time: 13.131s
C:\Users\laure\Desktop\FastBoot_Motorola - Copie>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (236197 KB)...
OKAY [ 7.080s]
writing 'system'...
OKAY [ 5.708s]
finished. total time: 12.791s
C:\Users\laure\Desktop\FastBoot_Motorola - Copie>mfastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
sending 'system' (247221 KB)...
OKAY [ 7.421s]
writing 'system'...
OKAY [ 5.400s]
finished. total time: 12.823s
C:\Users\laure\Desktop\FastBoot_Motorola - Copie>mfastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
sending 'system' (32776 KB)...
OKAY [ 0.982s]
writing 'system'...
OKAY [ 0.710s]
finished. total time: 1.695s
C:\Users\laure\Desktop\FastBoot_Motorola - Copie>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (40532 KB)...
OKAY [ 1.206s]
writing 'modem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.221s
C:\Users\laure\Desktop\FastBoot_Motorola - Copie>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (40532 KB)...
OKAY [ 1.208s]
writing 'modem'...
OKAY [ 1.104s]
finished. total time: 2.317s
C:\Users\laure\Desktop\FastBoot_Motorola - Copie>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.012s]
finished. total time: 0.013s
C:\Users\laure\Desktop\FastBoot_Motorola - Copie>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.010s]
finished. total time: 0.011s
C:\Users\laure\Desktop\FastBoot_Motorola - Copie>mfastboot flash bluetooth BTFM.bin
target max-sparse-size: 256MB
sending 'bluetooth' (1294 KB)...
OKAY [ 0.040s]
writing 'bluetooth'...
OKAY [ 0.054s]
finished. total time: 0.097s
C:\Users\laure\Desktop\FastBoot_Motorola - Copie>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (384 KB)...
OKAY [ 0.013s]
writing 'fsg'...
OKAY [ 0.055s]
finished. total time: 0.071s
C:\Users\laure\Desktop\FastBoot_Motorola - Copie>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.030s]
finished. total time: 0.032s
C:\Users\laure\Desktop\FastBoot_Motorola - Copie>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 2.525s]
finished. total time: 2.527s
C:\Users\laure\Desktop\FastBoot_Motorola - Copie>mfastboot erase customize
erasing 'customize'...
OKAY [ 0.012s]
finished. total time: 0.014s
C:\Users\laure\Desktop\FastBoot_Motorola - Copie>mfastboot oem fb_mode_clear
...
OKAY [ 0.001s]
finished. total time: 0.001s
Click to expand...
Click to collapse
After a last mfastboot reboot, the smartphonerebooted and i got WIFI and modem but...no more playstore ??
I flashed this one XT1581_KINZIE_RETCN_DS_5.1.1_LPK23.229-1_cid11_subsidy-DEFAULT_CFC.xml
Moto do not support/recommend downgrade. Maybe you can flash only radio but most probably radio for 5.1.1 will not be compatible with 6.0 and vice versa.
Understood.
For now, i'm unable to install apps because no playstore in this ROM.
Do you think I can install EU ROM 5.1.1 without any problems, or do I need to flash specific file from CHINA ROM, and if yes, wich ones ?
You play with fire, flashing older version, then newer, etc.
Once modem flash failed but you repeated and then was successful. Do you have network now? Everything works? Except playstore?
Yes, many apps in chinese, but no playstore.
EDIT :
I progress : I finally managed to have :
system in EU 5.1.1,
carrier is working,
playstore is present,
bluetooth is working,
But no WIFI
You're still flashing like crazy. You may end with the bricked device...
Try to calm down. Looks like that everything works with Chinese rom, except playstore. Did you have playstore when you just got your phone from China?
When you got fully working device (carrier, wifi, bt...), try to flash Android only (without radio, etc.) but for the same version as the working rom. If that is gonna work, then you can try to flash latest available Androi. But again, only system, no radio, etc.
Disclaimer, whatever you do is strictly up to you. I'm not responsible if you brick your device.
You're right, I'm in panic :/
Okay so :
When I just received the phone, ROM was CN, and playstore was working.
1. If I flashed CN ROM 5.1.1, all is working, but no playstore.
2. If I flashed EU ROM 5.1.1, playstore, but no WIFI no carrier.
3. I tried what you were saying : I installed CN ROM, then flash system and only system from EU ROM : no WIFI but carrier is ok.
I'm so stucked :/
Panic is bad for troubleshooting. I know, is hard to calm down but is highly recommended.
Strange, what a hell happened with the playstore?! It was working with CN rom and, as far I understand, you flashed back the same CN rom and now playstore is missing. Are you sure that you logged in with google account? Have you checked under apps? Maybe is disabled?
There's a way to flash playstore separatelly but bootloader must be unlcocked, custom recovery flashed... I don not recommend you to do that for now. It is better to figure out what happened with playstore in the original rom.
When you're on the current rom, check wifi advanced. Check logcat, maybe dmesg, to see what's system is reporting when you try to turn on wifi. Maybe will give you idea what's wrong with wifi.
I can't be sure this is the same ROM. This is the only CN ROM i found and 874MB, I guess this one don't have GAPPS.
For the bootloader : I can assure you I didn't do anything with that, but in fastboot mode there is 2 yellow lines saying : "Unlocked" and "Software : Modified"
I think for their EU customers, they flash their XT1581 with GAPPS, and to do that, they unlocked bootloader.
With that in my head, I do something you will say stupid (but actually, I thought !) :
I downloaded via Opengapps.org the good gapps,
I downloaded TWRP-3.0.2.0-KINZIE.IMG from xda,
I flashed full CN ROM 5.1.1,
I typed "mfastboot boot twrp-3.0.2.0-KINZIE.IMG".
And in TWRP I installed GAPPS, wiped dalvik, rebooted.
Cache has been reconstructed, WIFI is alive, carrier is good, 4G is on, Playstore and all others GAPPS are up
I thank you very much, your help, your kindness were really helpfull.
Merry christmas to you, and to me
Well, if bl is already unlocked then you did right thing
And yes, afaik in China phones are usually without gapps. Strange is that Moto is selling such phones.
I'm glad that you've managed to fix your phone. Merry Christmas to you as well
---------- Post added at 05:53 AM ---------- Previous post was at 05:51 AM ----------
Fanny is that you are now on the same Android version as before? A lot of effort for nothing. Sounds familiar
Zeljko1234 said:
...
Fanny is that you are now on the same Android version as before? I lot of effort for nothing. Sounds familiar
Click to expand...
Click to collapse
So true !! :laugh:
Now you can start over (make backup first with twrp), trying to get to 6.0.1 with everything working Or to try CM.
Well, i could....if it was not my son's smartphone LOL
ElLoloFR said:
Well, i could....if it was not my son's smartphone LOL
Click to expand...
Click to collapse
So you messed your son smartphone. If he's old enough, he can mess by himself.
You were in panic, but I can imagine panic if you messed up your wife's phone
no wii etc with android 6 on moto x force chinese model
ElLoloFR said:
I can't be sure this is the same ROM. This is the only CN ROM i found and 874MB, I guess this one don't have GAPPS.
For the bootloader : I can assure you I didn't do anything with that, but in fastboot mode there is 2 yellow lines saying : "Unlocked" and "Software : Modified"
I think for their EU customers, they flash their XT1581 with GAPPS, and to do that, they unlocked bootloader.
With that in my head, I do something you will say stupid (but actually, I thought !) :
I downloaded via Opengapps.org the good gapps,
I downloaded TWRP-3.0.2.0-KINZIE.IMG from xda,
I flashed full CN ROM 5.1.1,
I typed "mfastboot boot twrp-3.0.2.0-KINZIE.IMG".
And in TWRP I installed GAPPS, wiped dalvik, rebooted.
Cache has been reconstructed, WIFI is alive, carrier is good, 4G is on, Playstore and all others GAPPS are up
I thank you very much, your help, your kindness were really helpfull.
Merry christmas to you, and to me
Click to expand...
Click to collapse
Hay
I have the same problem you have (had).
Please can you explain to me what you exactly did to go back to 5.1. and with a working playstore and wifi etc?
a desperate newbie
I've got kind of the same problem.
I bought a Chinese XT1581 and flashed the Mexican rom right after the phone arrived. Because I still had another mobile as my main-phone I didn't try to use the cellular connection. Everything else, including wifi, was working just fine.
Well, today I put in my Sim-card. It was detected, buy the phone can't find any services.
I tried to go back to the Chinese rom I found on this forum, but after flashing it (as described in this Thread) it didnt. Neither the cellular connection nor the wifi worked.
No I flashed it back to the Mexican rom, wifi is working again, but not the radio.
Does someone know how I could get a fully working phone again?
linuxpro said:
I've got kind of the same problem.
I bought a Chinese XT1581 and flashed the Mexican rom right after the phone arrived. Because I still had another mobile as my main-phone I didn't try to use the cellular connection. Everything else, including wifi, was working just fine.
Well, today I put in my Sim-card. It was detected, buy the phone can't find any services.
I tried to go back to the Chinese rom I found on this forum, but after flashing it (as described in this Thread) it didnt. Neither the cellular connection nor the wifi worked.
No I flashed it back to the Mexican rom, wifi is working again, but not the radio.
Does someone know how I could get a fully working phone again?
Click to expand...
Click to collapse
Did you flash XT1580_KINZIE_RETMX-IUSMX_6.0_MPK24.78-8_cid12_subsidy-IUSMXLA_CFC.xml.zip or XT1580_KINZIE_RETMX_DS_6.0_MPK24.78-8_cid12_subsidy-DEFAULT_CFC.xml.zip ?
hiep_hv said:
Did you flash XT1580_KINZIE_RETMX-IUSMX_6.0_MPK24.78-8_cid12_subsidy-IUSMXLA_CFC.xml.zip or XT1580_KINZIE_RETMX_DS_6.0_MPK24.78-8_cid12_subsidy-DEFAULT_CFC.xml.zip ?
Click to expand...
Click to collapse
I flashed the default-version.
The info-file says:
BUILD REQUEST INFO:
SW Version: kinzie_retla_ds-user 6.0 MPK24.78-8 9 release-keysM8994_1255339.41.01.92R
MBM Version: A8.56
Modem Version: M8994_1255339.41.01.92R
FSG Version: FSG-8994-01.98
Build Fingerprint: motorola/kinzie_retla_ds/kinzie_uds:6.0/MPK24.78-8/9:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 24.11.8.kinzie_retla_ds.retla.en.01
Model number: Moto X Force
Android Version: 6.0
Baseband Version: M8994_1255339.41.01.92R
Build Number: MPK24.78-8
Build Date: Fri Nov 20 18:59:07 CST 2015
Click to expand...
Click to collapse
Hello guys,
I know this question is very common but I have looked many posts and couldn't find any that solved my problem.
I am trying to flash the stock moto X pure edition (xt1575) again in my device. The trouble starts because fastboot doesn't work.
I already installed Motorola device manager (2.5.4) and booted windows without driver signature enforcement.
I tried adb-setup-1.4.3.exe and installing android SDK, but still get same trouble.
The phone works and get normally funcional when android is loaded, but no responde in fastboot screen!
I am using windows 10.15063.296 (creators update). When I open device manager, now I see "Motorola adb device" with an exclamation.
A lot of windows, especially windows 10, users seem to struggle with drivers. I use Linux and never have any problems.
Maybe you could give this a try. https://www.xda-developers.com/forget-windows-use-linux-is-a-usb-bootable-distro-for-your-android-recovery-needs-xda-spotlight/
jason2678 said:
A lot of windows, especially windows 10, users seem to struggle with drivers. I use Linux and never have any problems.
Maybe you could give this a try. https://www.xda-developers.com/forg...or-your-android-recovery-needs-xda-spotlight/
Click to expand...
Click to collapse
Thanks. After hours trying, I could get fastboot working.
The issue now is that I got "preflash failed" when trying the officially image available.
Enviado de meu XT1575 usando Tapatalk
Belotto said:
Thanks. After hours trying, I could get fastboot working.
The issue now is that I got "preflash failed" when trying the officially image available.
Enviado de meu XT1575 usando Tapatalk
Click to expand...
Click to collapse
Just on bootloader and gpt.bin, or everything?
That happens when you try to downgrade the partition table, but usually as long as you flash all the other parts successfully it works. Keep a close eye on the output when you flash modem; it tends to fail on the first try.
https://forum.xda-developers.com/showthread.php?t=2588979
This is the one... I had this on my window's 10. I upgraded to creators update and i doubted that this might not work but it did work for me
jason2678 said:
Just on bootloader and gpt.bin, or everything?
That happens when you try to downgrade the partition table, but usually as long as you flash all the other parts successfully it works. Keep a close eye on the output when you flash modem; it tends to fail on the first try.
Click to expand...
Click to collapse
I really wasn´t successful...
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> adb reboot-bootloader
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.370s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash motoboot motoboot.img
error: cannot load 'motoboot.img'
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (3687 KB)...
OKAY [ 0.137s]
writing 'logo'...
OKAY [ 0.200s]
finished. total time: 0.337s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (40960 KB)...
OKAY [ 1.518s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.888s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (41040 KB)...
OKAY [ 1.534s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.887s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (509631 KB)...
OKAY [ 17.857s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 18.357s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot reboot
rebooting...
finished. total time: 0.016s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot erase userdata
erasing 'userdata'...
OKAY [ 6.423s]
finished. total time: 6.423s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot erase cache
erasing 'cache'...
OKAY [ 0.031s]
finished. total time: 0.031s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.015s]
finished. total time: 0.015s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot oem lock begin
...
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.017s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US>
jason2678 said:
Just on bootloader and gpt.bin, or everything?
That happens when you try to downgrade the partition table, but usually as long as you flash all the other parts successfully it works. Keep a close eye on the output when you flash modem; it tends to fail on the first try.
Click to expand...
Click to collapse
Sagar_1401 said:
https://forum.xda-developers.com/showthread.php?t=2588979
This is the one... I had this on my window's 10. I upgraded to creators update and i doubted that this might not work but it did work for me
Click to expand...
Click to collapse
I have tried it before... wasn't working but i realized that i needed to push "allow oem unlock" and "usb debugging" buttons ... LOL.