Here is the fully stock Boot.img, Recovery.img and System.img. There are no modifications to any of these. This is all we have until Motorola releases full factory images for Lollipop 5.0.
For the XT1095 Pure Edition ONLY
BUILD: LXE22.46-11 (22.21.11)
http://apollyon-dev.com/motox/XT1095_Lollipop5_22.21.11_BOOT_RECOVERY_SYS.zip
md5: 43888F4EAB74600E6D6DF41FF202C9BA
here's a mirror
https://mega.co.nz/#!a9hymLCD!ek2VVQNPGmUpNHFl6WIQe8znsFtUBjbsvTu0-TyORnM
Previous builds
BUILD: LXE22.39-6 (22.11.6)
http://apollyon-dev.com/motox/XT1095_Lollipop5_22.11.6_BOOT_RECOVERY_SYS.zip
md5: 6A527AFB1DEED2248AE2D3B4ACCF04ED
here's a mirror
https://mega.co.nz/#!H0wn2LoT!hHqhasTUnLjxMxACvODWcRIrtm3jTGjg1MEqxZfP5lo
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, catches on fire or it starts WWIII. Use at your own risk.
how do you flash these, I tried both fastboot and mfastboot but both fail, they crash even
also build prop says this is 4.4.4 not 5
godutch said:
how do you flash these, I tried both fastboot and mfastboot but both fail, they crash even
also build prop says this is 4.4.4 not 5
Click to expand...
Click to collapse
you are doing it wrong...
mrvirginia said:
you are doing it wrong...
Click to expand...
Click to collapse
ok, how can we do it?
thx
overon37 said:
ok, how can we do it?
thx
Click to expand...
Click to collapse
by using mfastboot. this is for advanced users...
yes, i got it, but, can i flash it over XT1092 with Kitkat?
^^I have a conversion guide, that'd help you for sure
mrvirginia said:
you are doing it wrong...
Click to expand...
Click to collapse
so how i am supposed to flash this then?
After some experimentation I cleaned up these instructions a little bit and confirmed this method works for me for rooted (.6):
Here's what I did, real easy:
- Download mfastboot v2 from graffixnyc's thread.
- unzip boot, recovery, system imgs that you downloaded from the OP into the mfastboot folder where the mfastboot.exe is located. Open a cmd prompt on that folder.
- Put phone in fastboot, plug it in:
Code:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
For the new radio, download it from graffixnyc's site, put in mfastboot folder and flash :
Code:
mfastboot flash modem radio.img
After you get a successful boot, put the phone back in fastboot and download CF-Auto-root from graffixnyc's post in "General". Put the CF-Auto-Root.... img (inside the zip in the /image folder) in the mfastboot folder with everything else and flash according to his instrucions :
Code:
mfastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
That's it. Nothing hard about it. Any questions let me know.
Big thanks to both mrvirginia and graffixnyc for their work on this. And of course Chainfire.
*Note- you have to be upgrading from KK for this to work. If you run into issues already on a version of 5.0 and attempt this method to "fresh install", you will get stuck at boot ani. Downgrade and then try this method again. :good:
Can someone provide the bootanimation file in system/bin?
Links dead?
Devans32 said:
Links dead?
Click to expand...
Click to collapse
Nope. they both seem to work here.
updated
for the official 22.21.11 Build.
mirror up shortly
Ok now I am getting a parse invalid file error when I try to flash the system image.
Edit; fixed. Found right files and up and running.
Sent from my Nexus 6 using XDA Free mobile app
Chronzy said:
Code:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
Click to expand...
Click to collapse
I get the error:
Code:
Invalid sparse file format at header magi
when trying to flash system.img
I've verified MD5 of file, but I'm redownloading it. Do I need to manually split it into chunks or something?
Kallb123 said:
I get the error:
Code:
Invalid sparse file format at header magi
when trying to flash system.img
I've verified MD5 of file, but I'm redownloading it. Do I need to manually split it into chunks or something?
Click to expand...
Click to collapse
Are you using mfastboot v2?
The files in this OP worked great for me on .6, but .11's so widespread I'm not sure why one wouldn't downgrade to KK and accept the OTA? Then use chainfire's root?
Chronzy said:
Are you using mfastboot v2?
The files in this OP worked great for me on .6, but .11's so widespread I'm not sure why one wouldn't downgrade to KK and accept the OTA? Then use chainfire's root?
Click to expand...
Click to collapse
Yes, got the new mfastboot, but I've tried with old as well as mfastboot v1. I was trying to flash .11 but I got this error, so I came here to use these files but also got this error :/
EDIT: Flashed KK and upgraded .11 from there. Can't get a signal though, even after flashing my modem back..
EDIT2: erase modemst1 and modemst2 and then flashing my fsg and modem worked
Chronzy said:
After some experimentation I cleaned up these instructions a little bit and confirmed this method works for me for rooted (.6):
Here's what I did, real easy:
- Download mfastboot v2 from graffixnyc's thread.
- unzip boot, recovery, system imgs that you downloaded from the OP into the mfastboot folder where the mfastboot.exe is located. Open a cmd prompt on that folder.
- Put phone in fastboot, plug it in:
Code:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
For the new radio, download it from graffixnyc's site, put in mfastboot folder and flash :
Code:
mfastboot flash modem radio.img
After you get a successful boot, put the phone back in fastboot and download CF-Auto-root from graffixnyc's post in "General". Put the CF-Auto-Root.... img (inside the zip in the /image folder) in the mfastboot folder with everything else and flash according to his instrucions :
Code:
mfastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
That's it. Nothing hard about it. Any questions let me know.
Big thanks to both mrvirginia and graffixnyc for their work on this. And of course Chainfire.
*Note- you have to be upgrading from KK for this to work. If you run into issues already on a version of 5.0 and attempt this method to "fresh install", you will get stuck at boot ani. Downgrade and then try this method again. :good:
Click to expand...
Click to collapse
You did this from -6 rooted? With stock recovery or TWRP?
zgroten said:
You did this from -6 rooted? With stock recovery or TWRP?
Click to expand...
Click to collapse
That was the method I used to upgrade from KK to .6. I don't understand your recovery question. All this is done in bootloader.
I think you guys would benefit from SolarTrans' guide in the "general" section... http://forum.xda-developers.com/moto-x-2014/general/guide-update-xt1095-pure-edition-to-t2937074
Anyone else have issues
I'm on 22.39-6 and I am having issues when the phone. Anyone else have the issue where the home and menu buttons randomly disappear? Or text messages don't appear? The only fix was to reboot the phone. I also have unresponsive issues randomly when the phone is plugged to AC power and charging. Just wondering if I'm the only one with these issues. I'm going to flash the new build, but just wondering.
Related
I foolishly didn't create a backup. I know. Stupid of me.
I have a Moto G 2nd Gen model XT1064 (USA, purchased at Best Buy off contract, Single SIM). I can fastboot and I have TWRP recovery installed. I cannot find a rom that works however. Of all the .zips I've downloaded only one, a dual SIM UK version, boots. But it does not recognize my SIM or wifi chip. The others fail without giving me an error as to why.
UPDATE: This thread.... http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657 helped restore my wifi, though the firmware linked was a dual sim and I cannot enable my SIM card, the option is grayed out.
I have tried over the past day to try and get this to go back to its factory image with no luck at all. I have a Nexus 4, seeing as it has a toolkit and factory images readily available, its always easy to work on. This Moto G is a different story.
What do I need to get this back right? I may already have the files and not even realize it..
Thanks for any help!
canyoudig_it said:
I foolishly didn't create a backup. I know. Stupid of me.
I have a Moto G 2nd Gen model XT1064 (USA, purchased at Best Buy off contract, Single SIM). I can fastboot and I have TWRP recovery installed. I cannot find a rom that works however. Of all the .zips I've downloaded only one, a dual SIM UK version, boots. But it does not recognize my SIM or wifi chip. The others fail without giving me an error as to why.
UPDATE: This thread.... http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657 helped restore my wifi, though the firmware linked was a dual sim and I cannot enable my SIM card, the option is grayed out.
I have tried over the past day to try and get this to go back to its factory image with no luck at all. I have a Nexus 4, seeing as it has a toolkit and factory images readily available, its always easy to work on. This Moto G is a different story.
What do I need to get this back right? I may already have the files and not even realize it..
Thanks for any help!
Click to expand...
Click to collapse
Did you try the this one(Blur_Version.21.11.17.titan_retuaws.retuaws.en.US) from this site(http://sbf.droid-developers.org/phone.php?device=36)
edog11 said:
Did you try the this one(Blur_Version.21.11.17.titan_retuaws.retuaws.en.US) from this site
Click to expand...
Click to collapse
I have tried flashing it from TWRP. I get this error message...
Code:
Package expects build fingerprint of motorola/titan_retuaws/titan_umts:4.4.4/KXB21.85-17/23:user/release-keys or motorola/titan_retuaws/titan_umts:5.0/LXB22.39-6/5:user/release-keys; this device has motorola/titan-retaildsds/titan_umtsds:4.4.4/KXB21.85-14/9:user/release-keys.
E:Error executing updater binary in zip "/sdcard1/Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip"
Error flashing zip "/sdcard1/Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip"
Updating Partition details...
canyoudig_it said:
I have tried flashing it from TWRP. I get this error message...
Code:
Package expects build fingerprint of motorola/titan_retuaws/titan_umts:4.4.4/KXB21.85-17/23:user/release-keys or motorola/titan_retuaws/titan_umts:5.0/LXB22.39-6/5:user/release-keys; this device has motorola/titan-retaildsds/titan_umtsds:4.4.4/KXB21.85-14/9:user/release-keys.
E:Error executing updater binary in zip "/sdcard1/Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip"
Error flashing zip "/sdcard1/Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip"
Updating Partition details...
Click to expand...
Click to collapse
You cannot use custom recovery(TWRP) to flash this.
You need to follow this and you will lose data.
Unlock the bootloader.
Download Blur_Version.21.11.17.titan_retuaws.retuaws.en.US from droid-developers dot org slash phone device 36
Unzip that file into your fastboot folder
Enter Fastboot on your phone (how to: hold power and volume down until your device turns off, then hold it another 5-10 seconds, then let go and you should see a basic text screen)
Use these commands on your computer while being in the fastboot folder.
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
You should now be at stock Android 4.4.4 with an unlocked bootloader.
edog11 said:
You cannot use custom recovery(TWRP) to flash this.
You need to follow this and you will lose data.
Unlock the bootloader.
Download Blur_Version.21.11.17.titan_retuaws.retuaws.en.US from droid-developers dot org slash phone device 36
Unzip that file into your fastboot folder
Enter Fastboot on your phone (how to: hold power and volume down until your device turns off, then hold it another 5-10 seconds, then let go and you should see a basic text screen)
Use these commands on your computer while being in the fastboot folder.
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
You should now be at stock Android 4.4.4 with an unlocked bootloader.
Click to expand...
Click to collapse
THANK YOU! That did it! Everything works as it did before. You were a great help!
canyoudig_it said:
THANK YOU! That did it! Everything works as it did before. You were a great help!
Click to expand...
Click to collapse
Glad you were able to get you phone working again.
Warriors, come out and plaay.
EDIT: Found a link from another XDA thread... here's the direct download from Mega: https://mega.co.nz/#!mlIz0KCQ!lVXP5PCLRV9MRxwRdhEbKesEoq9UCPs4Lv8ec1Nx0ZY
edog11 said:
Did you try the this one(Blur_Version.21.11.17.titan_retuaws.retuaws.en.US) from this site(http://sbf.droid-developers.org/phone.php?device=36)
Click to expand...
Click to collapse
Anyone have another link/mirror? SBF Droid site is down.
While I did download it from another site, it seems a number of files are missing from the download. HEre's what I'm getting:
Kelleys-Mac-mini:Blur_Version.21.11.17.titan_retuaws.retuaws.en.US kelley$ ./fastboot flash motoboot motoboot.img
error: cannot load 'motoboot.img'
Kelleys-Mac-mini:Blur_Version.21.11.17.titan_retuaws.retuaws.en.US kelley$ cd /Users/kelley/Desktop/Blur_Version.21.11.17.titan_retuaws.retuaws.en.US\ 01-12-18-009
Kelleys-Mac-mini:Blur_Version.21.11.17.titan_retuaws.retuaws.en.US 01-12-18-009 kelley$ ./fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (295 KB)...
OKAY [ 0.066s]
writing 'logo'...
OKAY [ 0.108s]
finished. total time: 0.174s
Kelleys-Mac-mini:Blur_Version.21.11.17.titan_retuaws.retuaws.en.US 01-12-18-009 kelley$ ./fastboot flash boot boot.img
error: cannot load 'boot.img'
Kelleys-Mac-mini:Blur_Version.21.11.17.titan_retuaws.retuaws.en.US 01-12-18-009 kelley$ ./fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
Kelleys-Mac-mini:Blur_Version.21.11.17.titan_retuaws.retuaws.en.US 01-12-18-009 kelley$ ./fastboot flash recovery recovery.img
Click to expand...
Click to collapse
The SBF Droid website is down... and only gives an error message stating the following:
An error occurred.
Sorry, the page you are looking for is currently unavailable.
Please try again later.
If you are the system administrator of this resource then you should check the error log for details.
Faithfully yours, nginx.
Click to expand...
Click to collapse
My phone is unusable at this point; not bricked but might as well be as I can't make/receive phone calls nor texts. Can anyone PLEASE send me a valid link to a what's noted above? I accidentally flashed the wrong file to my phone and absolutely need to get it back to stock. THANK YOU... more than you'll EVER know!
thewinelover said:
While I did download it from another site, it seems a number of files are missing from the download. HEre's what I'm getting:
The SBF Droid website is down... and only gives an error message stating the following:
My phone is unusable at this point; not bricked but might as well be as I can't make/receive phone calls nor texts. Can anyone PLEASE send me a valid link to a what's noted above? I accidentally flashed the wrong file to my phone and absolutely need to get it back to stock. THANK YOU... more than you'll EVER know!
Click to expand...
Click to collapse
Sir..if you don't find a known good download soon..let me know, I can upload to my Drive..
Sent from my:
4.4.4_23.3.24 XT1080M
Droid Maxx Developer Edition
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
Oh gosh that would be SO HELPFUL!!! Would you NWKENT? You might just save my phone!
PS - I'm a girl...
NWKENT said:
Sir..if you don't find a known good download soon..let me know, I can upload to my Drive..
Sent from my:
4.4.4_23.3.24 XT1080M
Droid Maxx Developer Edition
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
Click to expand...
Click to collapse
thewinelover said:
Oh gosh that would be SO HELPFUL!!! Would you NWKENT? You might just save my phone!
PS - I'm a girl...
Click to expand...
Click to collapse
Here you go young lady....
RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml
Linky
EDIT: Here's the md5 checksum. ALWAYS verify these prior to installing.
b44ffe73058ebb8b85c853151f8c3e36
*RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml.zip
@fathergweedo, You sir, are the BOMB!! Thank you so much!!!!
thewinelover said:
@fathergweedo, You sir, are the BOMB!! Thank you so much!!!!
Click to expand...
Click to collapse
Once you get back to full stock 4.4.4, take a look at this so you won't need to do that again. This (TWRP) will also backup your PDS should you somehow bork the MEID or anything later...
Cheap insurance
EDIT: TWRP doesn't backup PDS by default. You must select it prior to the backup. Just thought I should clarify that.
fathergweedo said:
Once you get back to full stock 4.4.4, take a look at this so you won't need to do that again. This (TWRP) will also backup your PDS should you somehow bork the MEID or anything later...
Cheap insurance
Click to expand...
Click to collapse
And we're BAAAAAA-AAAAACK!!! With the right file, it's easy peasy, lemon squeezy!
You BETCHA! All of my apps are restoring now and as soon as they finish, that will be my next task!!! @fathergweedo, I cannot thank you enough. I'm thinking you're in the states, and if you are, you'll understand what I mean.... you brought new meaning to a HAPPY THANKSGIVING!!!! Cheers!!!
Thx!
fathergweedo said:
Once you get back to full stock 4.4.4, take a look at this so you won't need to do that again. This (TWRP) will also backup your PDS should you somehow bork the MEID or anything later...
Cheap insurance
Click to expand...
Click to collapse
THX so much! Had the same problem as the OP
fathergweedo said:
Here you go young lady....
RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml
Linky
EDIT: Here's the md5 checksum. ALWAYS verify these prior to installing.
b44ffe73058ebb8b85c853151f8c3e36
*RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml.zip
Click to expand...
Click to collapse
Thank you so much I spent the last 3 hours trying to recover from a softbrick and this did the trick. :good:
I downloaded the flashable zip from https://www.androidfilehost.com/?fid=95851846488293411
I use WugToolKit with TWRP, Unlocked and Decrypted. Stock ROM
I'm confused as to how I should flash this, I've read I should just click flash zip in the toolkit and let it finish and done. Also that I could download the file to my phone and use TWRP to flash straight to the phone. Some say backup and some say don't. Also some threads say I need to flash back to factory image, tho this flashable zip should be a factory image of 5.0.1.
Any help will be appreciated. Thank you.
Sent from my Nexus 6
SoCoCapricorn said:
I downloaded the flashable zip from https://www.androidfilehost.com/?fid=95851846488293411
I use WugToolKit with TWRP, Unlocked and Decrypted. Stock ROM
I'm confused as to how I should flash this, I've read I should just click flash zip in the toolkit and let it finish and done. Also that I could download the file to my phone and use TWRP to flash straight to the phone. Some say backup and some say don't. Also some threads say I need to flash back to factory image, tho this flashable zip should be a factory image of 5.0.1.
Any help will be appreciated. Thank you.
Sent from my Nexus 6
Click to expand...
Click to collapse
Apparently the new update OTA or zip will update blocks instead of files so from my understanding, even the slightest change from stock will cause this ZIP to fail when flashing. I'm rooted, decrypted, and changed mixer_paths.xml and as expected the flash failed in TWRP and adb sideload so I'm backing up via Titanium and flashing the 5.0.1 stock. I'll decrypt/root/restore after the flash.
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
So if I am stock but rooted I cannot sideload the OTA?
I keep getting status 7 error when trying to sideload with ADB using the update OTA.
It actual unzips and installs about 50% and then I get the Status 7 Error
mzimand said:
So if I am stock but rooted I cannot sideload the OTA?
I keep getting status 7 error when trying to sideload with ADB using the update OTA.
It actual unzips and installs about 50% and then I get the Status 7 Error
Click to expand...
Click to collapse
Rooting causes a change to the system partition, so no, you can't sideload the OTA anymore. (not since Lollipop)
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Worked like a CHAMP!!
:highfive:
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Are you using nexus toolkit by wug?
Sent from my Nexus 6
SoCoCapricorn said:
Are you using nexus toolkit by wug?
Sent from my Nexus 6
Click to expand...
Click to collapse
No, just used the steps I listed.
SoCoCapricorn said:
Are you using nexus toolkit by wug?
Sent from my Nexus 6
Click to expand...
Click to collapse
No, he used fastboot. Be wary of toolkits. They can do damage that a novice wont be able to fix.
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Jeezus! perfect!
Thats similar to what I did.
Only thing to do if you are already decrypted is to download this boot file, rename it to boot.img and flash it instead of the one included in the google zip package.
http://forum.xda-developers.com/showpost.php?p=57406510&postcount=360
I had to manually flash each file separately. For some reason when the flash.bat file was running it kept reporting that the system.img file was too big. Not had that before.
dunjamon said:
I had to manually flash each file separately. For some reason when the flash.bat file was running it kept reporting that the system.img file was too big. Not had that before.
Click to expand...
Click to collapse
yeah - since 5.0, the flash-all.bat isn't working for a lot of users.
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
What about the cache.img? do we not flash the cache?
mzimand said:
What about the cache.img? do we not flash the cache?
Click to expand...
Click to collapse
From what I understand, if you flash cache.img, you will go back to stock and lose all of your settings.
Awesome man, worked perfect, you sir rock!
Great!!!!
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
It works like a champ! THX man :good:
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Excellent, works perfectly as described. Thanks
The only thing that I'd add, to avoid any confusion, is that the factory image can be downloaded from:
https://developers.google.com/android/nexus/images
Thanks again, stevetrooper :good:
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Curious as to why so many steps?
All i did was flash the radio and system images. Went to 5.0.1 just fine, all settings/data retained.
Didn't flash bootloader, kept unlocked during process, only had to re-root.
Having an issue while flashing system.img file. I flashed radio, and flashed system.img then flashed cf-auto-root. On first start up I was having issues with my radio. LTE was not connecting to T Mobile. So I Nandroid back to stock. Then of course I noticed this didnt change my radio back to stock. Starting everything over, I reflashed radio, reboot bootloader, Flash system.img, reboot bootloader, then fash autoroot. Restart device. Radio was flashed and I had root, but stuck on 5.0 Tried to reflash system.img and I am getting error. "access denied" when flashing. I have read this is an issue with mounting the drive, I have even tried to do this in fast boot but I am coming up with nothing. Any help on this will be greatly appreciated.
theblizzard2010 said:
Curious as to why so many steps?
All i did was flash the radio and system images. Went to 5.0.1 just fine, all settings/data retained.
Didn't flash bootloader, kept unlocked during process, only had to re-root.
Click to expand...
Click to collapse
Requirements:
you need to have a pc with adb working
a stock firmware on your device (any)
unlocked bootloader
a working backup just in case
Pro:
you will not lose your data / application
Cons:
you will lose all system modification (root, busybox, custom kernel...)
you'll take all the risk of operation (I've tested on my device)
Guide:
some file names changes depending on version so please complete the {version_here} placeholder with the file you download
* prepend "sudo" on command line if you are on a Linux machine
download last version for your device here (if you want to root download the zip file in the section below to speed up the operations)
extract
extract image-{device_here}-{version_here}.zip in the same folder (no subdir)
command line* (or reboot device with vol down pressed):
Code:
adb reboot bootloader
command line*:
Code:
cd {your_path_here}
command line*:
Code:
fastboot flash bootloader bootloader-{device_here}-{version_here}.img
command line*:
Code:
fastboot reboot-bootloader
command line*:
Code:
fastboot flash radio radio-{device_here}-{version_here}.img
command line*:
Code:
fastboot flash system system.img
command line*:
Code:
fastboot flash boot boot.img
ONLY IF YOU FOUND A VENDOR.IMG IN THE ZIP command line*:
Code:
fastboot flash vendor vendor.img
command line*:
Code:
fastboot flash cache cache.img
command line*:
Code:
fastboot reboot
Now you have the lastest stock image and all your data.
Change recovery (TWRP) and root:
Note that we haven't flash the stock recovery, but during every boot of an unmodified system there's a script that do that (supersu usually deactive this behavior during install).
If you had TWRP installed and the SuperSU zip on your device, at the end of the above procedure you can boot directly from bootloader to recovery and go directly to last step:
download: TWRP image (twrp-{version_here}-{device_here}.img) for your device
download: chainfire SuperSU 2.71 on your device
command line*:
Code:
fastboot flash recovery twrp-{version_here}-{device_here}.img
alternatively you can keep the original recovery and use TWRP one time with
Code:
fastboot boot twrp-{version_here}-{device_here}.img
boot in recovery and flash supersu zip
working fine for me, all correct, thanks
Just tried with flash_all.bat. I'm getting the message "Can not generate image". How can I solve this, please?
Thank you, works like a charm!
Same here, cant flash system
There's not flash-all.bat in my steps (that delete you data!), can't give help about it sorry
i've gone your way, but i tried also the flash-all.bat with the -w switch, didnt work.
Tnx mate. Helped a lot
Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?
Sp0KI said:
Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?
Click to expand...
Click to collapse
I think that all who has flashed the developer preview got an broken filesystem or the partitions missmatch.
Before i used the preview the -w update flag worked well to rebuild the partitions, now it didnt work anymore, tried all factory images don to 4.4
c3k said:
Requirements:
you need to have a pc with adb working
a stock firmware on your device (any)
a working backup just in case
Click to expand...
Click to collapse
so if i have twrp, before i have to return stock 5.0.1??
or i flash directly 5.1 over twrp?
tnx
chikess said:
I think that all who has flashed the developer preview got an broken filesystem or the partitions missmatch.
Before i used the preview the -w update flag worked well to rebuild the partitions, now it didnt work anymore, tried all factory images don to 4.4
Click to expand...
Click to collapse
I didn't flash the preview.
Sp0KI said:
I didn't flash the preview.
Click to expand...
Click to collapse
Hmm ok, but u got the same problems. So, in this way we had to wait for a flashable zip or maybe ota.
@c3k why do you mention to flash twrp while in steps above stock recovery is not included to flash... ? Doesn't that mean that custom recovery (twrp) is still on device?
Doesn't this require an unlocked bootloader, and not necessarily root, or am I confused?
Sp0KI said:
Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?
Click to expand...
Click to collapse
Are you using the latest version for the fastboot.exe file?
foosion said:
Doesn't this require an unlocked bootloader, and not necessarily root, or am I confused?
Click to expand...
Click to collapse
This requires an unlocked bootloader. But, there are users like us who have rooted the stock ROM.
This guide is meant for the users who has unlocked bootloader with rooted stock ROM.
This guide will also work for phones with unlocked bootloaders with STOCK ROM(rooted or un-rooted).
efrant said:
Are you using the latest version for the fastboot.exe file?
Click to expand...
Click to collapse
I had faced the same issue while flashing LRX22C. It got fixed by rebooting the phone and switching the cable to a different USB port. Might work for him too.
PS: I have flashed the images from Linux.
In my case I guess all the issues are from a previous attempt to flash OptiPop ROM. The flashing process it's a little tricky to understand (with that F2FS file system). I remember that after flashed OptiPop and the phone didn't boot, I tried to restore to stock ROM and it was a lot of errors until it worked fine again.
efrant said:
Are you using the latest version for the fastboot.exe file?
Click to expand...
Click to collapse
I'm using the newest Minimal ADB.
The strange thing is, that i can flash the LRX22C system.img and all other new lmy47d files but not the lmy47d system.img.
I guess i'll wait for the OTA update and hope it works then.
Tried rebooting and switching port and usb cabel..
You actually don't need to manually install supersu or root. Flash the 5.1 images and then (after the first full boot) flash twrp.
Once you boot into twrp and exit out of it, you will be promoted with a message that your phone is not rooted, and you're asked if you want to install supersu. It's built into twrp.
Hello need help tracking down stock turbo firmware. The Motofirmware website (http://motofirmware.center/files/category/23-droid-turbo/downloads) are corrupted. The links in this thread are all dead: http://forum.xda-developers.com/moto-maxx/general/quark-stock-firmware-moto-maxx-droid-t3063470. Does anyone know of another source for stock 5.1?
http://motofirmware.center/
Stanleywinthrop said:
Hello need help tracking down stock turbo firmware. Does anyone know of another source for stock 5.1?
Click to expand...
Click to collapse
Here is the file download link for the latest xt1254 droid turbo 5.1 lollipop firmware:
https://www.androidfilehost.com/?fid=24052804347843637
Thanks, jala, but if you had bothered to fully read you'd see that the files on that website are corrupted.
jalal-jap said:
http://motofirmware.center/
Click to expand...
Click to collapse
Thanks, classic, i'll give this a try.
classic757 said:
Here is the file download link for the latest xt1254 droid turbo 5.1 lollipop firmware:
https://www.androidfilehost.com/?fid=24052804347843637
Click to expand...
Click to collapse
Stanleywinthrop said:
Thanks, classic, i'll give this a try.
Click to expand...
Click to collapse
No problem. Please let me know how it turns out.
Stanleywinthrop said:
Thanks, jala, but if you had bothered to fully read you'd see that the files on that website are corrupted.
Click to expand...
Click to collapse
i have same problem. extract it whit "7ZIP" and no corrupted for me.
http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip -> Full firmware (not OTA) of the most recent version of 5.1
TheSt33v said:
http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip -> Full firmware (not OTA) of the most recent version of 5.1
Click to expand...
Click to collapse
I get this error:
http://i.imgur.com/EOPsxnB.png
dmginc said:
I get this error:
http://i.imgur.com/EOPsxnB.png
Click to expand...
Click to collapse
Are you using RSDlite? If so, you're getting this error (I think) because the PRODUCT_CONFIGURATION.xml file has instructions for other phone models besides the Turbo in it. If I remember correctly, I got around this by deleting the info for everything not labeled QUARK_VERIZON in this file. However, since RSDlite basically just automates fastboot, a better option is to use fastboot to flash this firmware, in my opinion.
If you decide to flash the firmware this way, place all of the files from the full firmware into the directory that you installed fastboot, and enter the following commands after your phone is plugged into your computer in bootloader mode:
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
<repeat until all sparsechunks are flashed>
fastboot erase ddr
fastboot erase cache
fastboot erase userdata (NOTE: this command effectively performs a factory reset, and will erase all of your data)
Then boot, and you will have done everything that RSDlite would have done.
Oh thanks. Good info. Is there a write up on using fastboot anywhere? These forums are pretty poorly maintained and no good stickies anywhere
Edit: Oh, you edited your post. Awesome. Thanks.
The root junky fxz is that for rsd lite when I look at the contents the system image is in several sections and says system.img sparsechunk and has 10 sections. I have never seen this in an fxz. Is this a new way of flashing the system image.
TheSt33v said:
Are you using RSDlite? If so, you're getting this error (I think) because the PRODUCT_CONFIGURATION.xml file has instructions for other phone models besides the Turbo in it. If I remember correctly, I got around this by deleting the info for everything not labeled QUARK_VERIZON in this file. However, since RSDlite basically just automates fastboot, a better option is to use fastboot to flash this firmware, in my opinion.
If you decide to flash the firmware this way, place all of the files from the full firmware into the directory that you installed fastboot, and enter the following commands after your phone is plugged into your computer in bootloader mode:
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
<repeat until all sparsechunks are flashed>
fastboot erase ddr
fastboot erase cache
fastboot erase userdata (NOTE: this command effectively performs a factory reset, and will erase all of your data)
Then boot, and you will have done everything that RSDlite would have done.
Click to expand...
Click to collapse
Is it possible for me to relock my bootloader using adb fastboot? I don't want to do it accidentally while messing around with different roms and wiping my way back to stock.
When in fastboot, type "fastboot oem lock" (without the quotations"
Btrusa said:
When in fastboot, type "fastboot oem lock" (without the quotations"
Click to expand...
Click to collapse
Wouldn't that lock the bootloader?
Is it even possible to re-lock?
From what I understand he wants to avoid locking the bootloader...
Edit: nevermind I looked it up... Should have just done that the first time... ("I have seen quite of few people screw up their devices by not knowing what they are doing. So I am making this thread to simply tell people not familiar with fastboot what they should and should not do.
Fastboot oem unlock will unlock your bootloader and do a complete wipe of your device. As far as I know the only way for something to go wrong here is if you're device is low on battery and shuts off during the process. Either plug it in or have a "good" amount of juice left in your battery. To be 100 percent sure plug it in.
Before I get into oem lock IMHO you should only use this command for one thing only. Getting the device ready to send into motorola for the LGT upgrade or a another warranty repair or some sort. When done properly it is completely safe but there is no reason to do to go back to "stock".
Fastboot oem lock. Do not issue this command unless you are absolutely sure you have the correct software on your device. The correct software is what you get from the motodev site for your device. You need the official sofware images for your specific device AND REGION. If it is not released then DO NOT re-lock the device. If you have a OTA installed you will need to flash back to the motodev images first.")
dmginc said:
Is it possible for me to relock my bootloader using adb fastboot? I don't want to do it accidentally while messing around with different roms and wiping my way back to stock.
Click to expand...
Click to collapse
Nope
So is the fastboot flash motoboot bootloader.img just the Motorola "M" splash screen?
Sent from my XT1254 using Tapatalk
dmginc said:
So is the fastboot flash motoboot bootloader.img just the Motorola "M" splash screen?
Click to expand...
Click to collapse
No, that is the actual bootloader. The code that manages device startup, takes fastboot commands, and prohibits unsigned images from booting (when locked).
The splash screen is flashed with:
fastboot flash logo logo.bin
unhappybirthday said:
No, that is the actual bootloader. The code that manages device startup, takes fastboot commands, and prohibits unsigned images from booting (when locked).
The splash screen is flashed with:
fastboot flash logo logo.bin
Click to expand...
Click to collapse
So, back to my original question. When flashing back to stock with adb, but wanting to keep my bootloader unlocked, what should I do?
dmginc said:
So, back to my original question. When flashing back to stock with adb, but wanting to keep my bootloader unlocked, what should I do?
Click to expand...
Click to collapse
I can only speak from my experience. I was on the KitKat bootloader and used mofo to flash lollipop. I unlocked with sunshine and installed twrp. Then I flashed the lollipop bootloader with the fastboot command . Still unlocked.
Sent from my DROID Turbo using Tapatalk.
Hi All!
Here is my situation, I have a moto g xt1072 (Jan 2016) which came with a faulty problem, no sound after 5 seconds of been started. I checked everything (Factory reset via recovery), including both speakers, (both working at 7.5 ohms). Do you think a firmware change or a different ROM can help or it's time to let it go?
Base band: M8926_309101.02.03.19R THEA_EMEA_CUST
Kernel: 3.4.42-gef77327 [email protected] #1
System Version: 24.41.34.thea_retes.retesall.en.EU retes
Complation numer: MPB24.65-34
Everything is stock, no changes were made.
Thanks in advance!!!
@lost101
did you look here
http://forum.xda-developers.com/moto-g-lte
sd_shadow said:
did you look here
http://forum.xda-developers.com/moto-g-lte
Click to expand...
Click to collapse
Yep, if you are familliar with this process could you mind writing me a list of steps in order? I'll investigate 1 by 1 later, I've found so much info that's confusing. My phone is unlcock for any cellphone company, but It's not root, it's stock.
I used to install custom ROM's on my old Defy + but I things are very different now for what I'm seening. :S
Fastboot flash the latest full factory firmware image for your model.
mfastboot download: https://www.androidfilehost.com/?fid=24052804347778493
XT1072 Retail Spain Android 6.0 Factory Firmware Image: https://www.androidfilehost.com/?fid=24533103863143791
Fastboot tutorial: http://forum.xda-developers.com/showthread.php?t=2542219 (See specific fastboot commands below)
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_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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
murrayhawk said:
Yep, if you are familliar with this process could you mind writing me a list of steps in order? I'll investigate 1 by 1 later, I've found so much info that's confusing. My phone is unlcock for any cellphone company, but It's not root, it's stock.
I used to install custom ROM's on my old Defy + but I things are very different now for what I'm seening. :S
Click to expand...
Click to collapse
please dont mess up the flash.. because then you're pretty much ****ed.. as far ive seen and read and heard and tried, there will be no fix..
lost101 said:
Fastboot flash the latest full factory firmware image for your model.
mfastboot download: https://www.androidfilehost.com/?fid=24052804347778493
XT1072 Retail Spain Android 6.0 Factory Firmware Image: https://www.androidfilehost.com/?fid=24533103863143791
Fastboot tutorial: http://forum.xda-developers.com/showthread.php?t=2542219 (See specific fastboot commands below)
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_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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Click to expand...
Click to collapse
mfastboot download: Done
firmware download : Done
Fastboot: I'm not quite sure what is this about, is this for the new firmware installation? The guide you point says something about downgrading 4.3 to 4.2 and I'm running 6.0 stock.
I tried the first command (mfastboot flash partition gpt.bin) and it got stuck at : Waiting for device.
should I root the phone first?
can I use RSD Lite?
ora69 said:
please dont mess up the flash.. because then you're pretty much ****ed.. as far ive seen and read and heard and tried, there will be no fix..
Click to expand...
Click to collapse
I don't have anything to lose, this phone is rebooting itselft every 2 minutes.
murrayhawk said:
I don't have anything to lose, this phone is rebooting itselft every 2 minutes.
Click to expand...
Click to collapse
please, if anything gives a fail, post it on the thread! I myself have hard bricked this device, and now im trying to find the testpoint for it, ive already invested hours into this.. and i have no progress!, its worth it to post it on a thread
murrayhawk said:
mfastboot download: Done
firmware download : Done
Fastboot: I'm not quite sure what is this about, is this for the new firmware installation? The guide you point says something about downgrading 4.3 to 4.2 and I'm running 6.0 stock.
I tried the first command (mfastboot flash partition gpt.bin) and it got stuck at : Waiting for device.
should I root the phone first?
can I use RSD Lite?
Click to expand...
Click to collapse
The guide I linked to is not about downgrading. Ignore references to Android 4.3 - it still applies to Android 6.0. It sounds like you have not installed the usb drivers for your phone in Windows. This is a prerequisite. These Moto G drivers will also work for your phone:
Moto G USB Drivers (WinXP/7/8/10 32Bit-64Bit)
Test Fastboot is working by typing: fastboot devices
You may also be able to use RSD Lite - but this again will require you have installed USB drivers for your phone.
murrayhawk said:
mfastboot download: Done
firmware download : Done
Fastboot: I'm not quite sure what is this about, is this for the new firmware installation? The guide you point says something about downgrading 4.3 to 4.2 and I'm running 6.0 stock.
I tried the first command (mfastboot flash partition gpt.bin) and it got stuck at : Waiting for device.
should I root the phone first?
can I use RSD Lite?
Click to expand...
Click to collapse
my opinion is use RSD lite first, unless there is not a specific firmware file for your carrier/region...
or there is a high rate of flashing failure with the firmware available.
if RSD lite fails, best to post errors from pc and phone here
before try again, if there's not an obvious fix
then try mfastboot.exe
fastboot.exe is generic android, mfastboot.exe is Motorola specific, for moto's unique system.img...
avoid usb 3.0 ports
make sure the firmware downloaded is correct size, verified MD5 is best.
verify drivers are correct when the device is in fastboot mode
I have generic moto instructions in my
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my KFFOWI using XDA Labs
sd_shadow said:
my opinion is use RSD lite first, unless there is not a specific firmware file for your carrier/region...
or there is a high rate of flashing failure with the firmware available.
if RSD lite fails, best to post errors from pc and phone here
before try again, if there's not an obvious fix
then try mfastboot.exe
fastboot.exe is generic android, mfastboot.exe is Motorola specific, for moto's unique system.img...
avoid usb 3.0 ports
make sure the firmware downloaded is correct size, verified MD5 is best.
verify drivers are correct when the device is in fastboot mode
I have generic moto instructions in my
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
i think the tip you gave to avoid usb 3.0 ports will really help, didnt realize i was using the usb 3.0 port
Ok, this is what I did so far: (I'm running Windows 7 64b).
1. RSD Lite 6.2.4: Installed
2. Motorola Mobile Drivers Installation 6.4.0: Installed
3. Motorola Device Manager: Installed
1. I started the mobile into the recovery mode
2. Connected the moto cable to the pc
3. Opened RSD Lite, loaded the new firmware and hit start boton
4. The process reached a "please reboot manually...."
5. The phone starts but with the old firmware in it.
More Updates: I ran mfastboot sequence and every command returned OKAY. The issue still remains intact, sound works for 5 seconds, and the firmware has not been updated.
Any thoughts?
murrayhawk said:
More Updates: I ran mfastboot sequence and every command returned OKAY. The issue still remains intact, sound works for 5 seconds, and the firmware has not been updated.
Any thoughts?
Click to expand...
Click to collapse
I want to see a full and complete log of the fastboot flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
lost101 said:
I want to see a full and complete log of the fastboot flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Click to expand...
Click to collapse
Ok, please check the attachment.
It looks increasingly like your issue is hardware, not software related. The only remaining software option I can suggest is via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
lost101 said:
It looks increasingly like your issue is hardware, not software related. The only remaining software option I can suggest is via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
Click to expand...
Click to collapse
Can you explain why does it retain the original firmware after mfastboot commandas ran well?
Just a quick reminder. This moto g XT1702 Jan2016, is not rooted, bootloader is locked and has everything stock, it came with Android 6.0 installed.
murrayhawk said:
Can you explain why does it retain the original firmware after mfastboot command as ran well?
Click to expand...
Click to collapse
How do you mean original Firmware? You are flashing a Stock Android 6.0 firmware image.
lost101 said:
How do you mean original Firmware? You are flashing a Stock Android 6.0 firmware image.
Click to expand...
Click to collapse
What I have right now is : System Version: 24.41.34.thea_retes.retesall.en.EU retes and after flashing to XT1072_THEA_RETES_6.0_MPB24.65-34_cid7_subsidy-DEFAULT_CFC.xml. I'm still having 24.41.34.thea_retes.retesall.en.EU retes.