hi all
Im trying to flash stock recovery and stock 4.4.2 so i can get the 4.4.4 update.
All drivers installed done the adb boot command get to that screen then get this error on first line
C:\Users\Michael1\Desktop\new1\VODAFONE-GB-SL_FALCON_KLB20.9-1.10-1.24-1.1_cid7_
CFC_1FF_SVC.xml>mfastboot flash partition gpt.bin
********'mfastboot' is not recognized as an internal or external command,
operable program or batch file.*********
Ive followed this exactly always getting this error please could someone help out there I thank you for your time cheers
3b) If you downloaded and extracted a firmware in .xml.zip format.
Flash each of the partitions in sequence using mfastboot, you need to enter the following commands one-by-one checking that each one returns an [OKAY]
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
AndroidHtc101 said:
hi all
Im trying to flash stock recovery and stock 4.4.2 so i can get the 4.4.4 update.
All drivers installed done the adb boot command get to that screen then get this error on first line
C:\Users\Michael1\Desktop\new1\VODAFONE-GB-SL_FALCON_KLB20.9-1.10-1.24-1.1_cid7_
CFC_1FF_SVC.xml>mfastboot flash partition gpt.bin
********'mfastboot' is not recognized as an internal or external command,
operable program or batch file.*********
Ive followed this exactly always getting this error please could someone help out there I thank you for your time cheers
Click to expand...
Click to collapse
Sounds like you don't have mfastboot.exe in the same folder as the files you are trying to flash. Make sure you have downloaded and extracted THIS package to the same folder as the firmware you're flashing.
hi finish i put fastboot in working until now i get this error
mfastboot flash system system.img_sparsechunk2 max sparse size 256 error cannot load system image
thanks for your help on this one
Confirm that you are inputing the correct filenames. For example my first system chunkfile number was zero, and maybe it had a dot before the number.
There is an XT1032 Global GSM 4.4.4 firmware image now available:
http://forum.xda-developers.com/showpost.php?p=54365926&postcount=292
It's intended for Retail Brasil, but should work anywhere.
Your are a Legend thank you very much it worked Now I will be able to get the 4.4.4 update because i had a touch to retry error before.
Much appreciated Finish Flash
AndroidHtc101 said:
Your are a Legend thank you very much it worked Now I will be able to get the 4.4.4 update because i had a touch to retry error before.
Much appreciated Finish Flash
Click to expand...
Click to collapse
You're welcome.
One quick question Ive noticed I dont have superuser do I needed to do that all again after i upgrade to 4.4.4?
cheers
To avoid possible problems with upgrading process, first upgrade and then re-root.
ok thanks
Did that last process make my bootloader locked again? It was so long ago cant remember how I unlocked bootloader and rooted
No, bootloader is still unlocked.
Rooting method described here might be the easiest:
http://www.modaco.com/topic/366771-root-your-moto-g-option-1-superboot/
Finnish Flash said:
No, bootloader is still unlocked.
Rooting method described here might be the easiest:
http://www.modaco.com/topic/366771-root-your-moto-g-option-1-superboot/
Click to expand...
Click to collapse
thanks for all your help:_)
Related
Hello guys, I´m in doubt here, and although i´ve been reading some posts, I cannot seem to understand the procedure to install Motorola´s 5.0.2 in my Moto G, actually on 5.0.1 GPE.
As far as I know, I need to wipe it off, then convert partitions to f2fs and then flash via custom recovery?
I´ve tried twice, but cannot install TWRP, will try with Phillz.
BTWy, my device is rooted and bootloader unlocked.
Thanx for any guidance you may lend me, I´m at work and cannot dwelve deep into hundreds of threads. I have already downloaded Blur_Version.210.12.40.falcon_umts.Brasil.en.BR.zip the official Motorola 5.0.2.
Thanks!!
you need the 4.4.4 firmware first and mfastboot v2 files to go back to stock motorola firmware.
and since you updated to 5.0.1 GPE, your bootloader has been updated, so when you downgrade to 4.4.4, you will see screen flickers.
Here are the commands,you must enter these commands one by one using command prompt (hold shift, and right click and choose open command window here) in the folder where the firmware files are (including the mfastboot files)
connect your phone to the computer with usb cable and type the command to go into the bootloader
adb reboot bootloader
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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
and you need this firmware to be installed first before installing the lollipop update
XT1032_RETAIL-BR-SS_4.4.4_KXB21.14-L1.40_42_cid12_CFC_1FF
Thanx!
Well thank.you sir, very informative response.
Just to be super super-sure, no need to un-root or lock the bootloader right?
AgentChaos said:
you need the 4.4.4 firmware first and mfastboot v2 files to go back to stock motorola firmware.
and since you updated to 5.0.1 GPE, your bootloader has been updated, so when you downgrade to 4.4.4, you will see screen flickers.
Here are the commands,you must enter these commands one by one using command prompt (hold shift, and right click and choose open command window here) in the folder where the firmware files are (including the mfastboot files)
connect your phone to the computer with usb cable and type the command to go into the bootloader
adb reboot bootloader
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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
and you need this firmware to be installed first before installing the lollipop update
XT1032_RETAIL-BR-SS_4.4.4_KXB21.14-L1.40_42_cid12_CFC_1FF
Click to expand...
Click to collapse
Hello guys I would like to do the same, I have the Gpe and install Motorola 5.0.2, but before I want to know how to fix the flicker screen, I don't get it using android but when I'm on twrp, it's annoying, do you have any idea how to fix it?
Sent from my XT1058 using XDA Premium 4 mobile app
nice!
So i´ve flashed 5.0.2, with the method described here, it was *too* easy.
I did not, how ever, get the flickering screen bug...
So thanks again. and this is a safe way to go from gpe 5.0.1 to moto 5.0.2.
donlloreda said:
So i´ve flashed 5.0.2, with the method described here, it was *too* easy.
I did not, how ever, get the flickering screen bug...
So thanks again. and this is a safe way to go from gpe 5.0.1 to moto 5.0.2.
Click to expand...
Click to collapse
Which recovery do you have?
antarix said:
Which recovery do you have?
Click to expand...
Click to collapse
Stock recovery mate, well my happy story has come to a misterious error I cannot by any means sort out..
please see this post: Weird issue
I only just rooted my wife's Moto G a couple of nights ago as I was going to install the Brazilian lollipop version but thought better of it. Now the official update and I can't install it for her, even though it has stock recovery and stock 4.4.4, so I take it its because the su payload is still installed.
So what's the best way to unroot? Surely all that manually installing each part separately crap is totally out of date?
faster and without problems- reflash current rom
plantator said:
faster and without problems- reflash current rom
Click to expand...
Click to collapse
Just flash it in fastboot?
Balls. So I did what was suggested on here, copied the 4.4.4 file to the internal memory, wiped the phone and the zip won't install in twrp. What do I do now?
mickrick said:
Balls. So I did what was suggested on here, copied the 4.4.4 file to the internal memory, wiped the phone and the zip won't install in twrp. What do I do now?
Click to expand...
Click to collapse
You need stock recovery and no root. Then you need to flash the stock firmware with fastboot. It's a simple process that I've done a few times. I'm on my phone right now and don't have time to provide a link, but search the forum for flash stock firmware.
Sent from my XT1034 using Tapatalk
Copy your brain to internal memory... you read any tutorial? so many... go and read, but be carefull to not broke your device
The stock xml.zip file needs to be unzipped and each partition needs to be flashed using fastboot or mfastboot commands.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
You may get a prevalidation error when trying to flash motoboot.img. If you do, just skip it.
When flashing the sparsechunk files, change the name to match the sparsechunk files in the zip.
Hey guys. I got a telus moto g xt1032. It was on official 5.0.2. I flashed TWPR 2.8.5.0, and encountered the bootloop bug. I proceeded to flash the only stock telus firmware i could find- 4.4.4. I followed the guide on XDA to the tee and resulted in my moto go being stuck at the "Warning, boot loader unlocked" screen. I have no idea what to do and would really appreciate some help, as I am new to this. Am even willing to donate if it results in me fixing my phone. Thank for taking the time to read
Try doing the following Fastboot commands manually:
mfastboot flash partition gpt.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
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
Provide a log of what happens, if this does not work.
lost101 said:
Try doing the following Fastboot commands manually:
mfastboot flash partition gpt.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
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
Provide a log of what happens, if this does not work.
Click to expand...
Click to collapse
I also have this problem. I am trying to downgrade to 4.4.4 stock firmware (from 5.02) and I'm getting an this error:
$ fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.042s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.336s
Click to expand...
Click to collapse
All the other commands are successful but the device remain stucked on the boot screen after the reboot :crying:
I have this problem too, trying to factory reset my phone but it's still stuck on the bootloader. CWM says can't mount sd card now aswell so any help would be appreciated
I got the stock Telus 4.4.4 firmware from here: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=1
lost101 said:
Try doing the following Fastboot commands manually:
mfastboot flash partition gpt.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
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
Provide a log of what happens, if this does not work.
Click to expand...
Click to collapse
hey man, ok ill try that again. The only thing is, there is no boot.img in the telus file I downloaded. Its named "motoboot." Should i replace that with the boot img part? Also, i recently read somewhere trying to downgrde from 5.0.2 to 4.4.4 will mess my phone up. Is that true?
EDIT- I do remember the first time i tried this after sparsechunk.1, is sad "image file is too large" but kept on goiing anyways
audit13 said:
I got the stock Telus 4.4.4 firmware from here: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=1
Click to expand...
Click to collapse
theres 2 telus ones. How do you know which one to use? Also i tried flashing one of them im pretty sure and am stuck at the screen in OP
butthurtlocker said:
hey man, ok ill try that again. The only thing is, there is no boot.img in the telus file I downloaded. Its named "motoboot." Should i replace that with the boot img part? Also, i recently read somewhere trying to downgrde from 5.0.2 to 4.4.4 will mess my phone up. Is that true?
EDIT- I do remember the first time i tried this after sparsechunk.1, is sad "image file is too large" but kept on goiing anyways
Click to expand...
Click to collapse
motoboot.img and boot.img are not the same thing. Be careful renaming these files, or else you will destroy your phone. If there is no boot.img included then that zip has been messed with by someone.
The 'image file is too large' message should not be ignored - it means the firmware has not flashed at all. Nothing has changed on your phone; flash has not been successful.
butthurtlocker said:
theres 2 telus ones. How do you know which one to use? Also i tried flashing one of them im pretty sure and am stuck at the screen in OP
Click to expand...
Click to collapse
I used this one: XT1032_TELUS-CA_4.4.4_KXB21.14-L1.50_52_cid14_CFC_1FF.xml
Then I updated Motorola Apps via Play store, then get the OTA update to 5.02.
lost101 said:
motoboot.img and boot.img are not the same thing. Be careful renaming these files, or else you will destroy your phone. If there is no boot.img included then that zip has been messed with by someone.
The 'image file is too large' message should not be ignored - it means the firmware has not flashed at all. Nothing has changed on your phone; flash has not been successful.
Click to expand...
Click to collapse
good to know thanks. theres only 2 stock telus files, and one didnt have the boot.img. so ill have to hope the other does. I managed to get my phone booted on GpE 4.4. now im just trying to get back to stock motorola. Is there a guide you could link me to?
audit13 said:
I used this one: XT1032_TELUS-CA_4.4.4_KXB21.14-L1.50_52_cid14_CFC_1FF.xml
Then I updated Motorola Apps via Play store, then get the OTA update to 5.02.
Click to expand...
Click to collapse
did that file have a boot.img?
butthurtlocker said:
good to know thanks. theres only 2 stock telus files, and one didnt have the boot.img. so ill have to hope the other does. I managed to get my phone booted on GpE 4.4. now im just trying to get back to stock motorola. Is there a guide you could link me to?
Click to expand...
Click to collapse
Fastboot Tutorial:
http://forum.xda-developers.com/showthread.php?t=2542219
Yes, the boot.img file is included.
While using my moto g last last night it suddenly got freezed, & when i restarted it....., it just doesn't boot up!! :crying:
Screenshots attached!!
I tried every....... every possible thing, tried reverting back to 5.0.2 & 4.4.4. But it just doesn't work!! RECOVERY gets stuck at TWRP logo!!
It shows everything as success success on fastboot mode while flashing (STOCK, RECOVERY, Anything......) but when it boots up there is nothing changed even the bootlogo is still the same.
No error of any sort comes up!!
Tried everything, tried flashing gpt.bin, reflashed bootloader, even tried flashing STOCK using RsD Lite but nothing happens, as if nothing was flashed!!
When left for a while it boots up(After showing AICP is Upgrading 3 exact times), just to give me a screen where it asks to put my password to Reset The Device(Screenshot attached), & whatever i put there as my password it accepts it & shows DECRYPTION SUCCESSFUL, PRESS OK TO REBOOT UR DEVICE, when pressed, it takes me to my RECOVERY where it gets stuck at TWRP logo!!
Is there any hope left or is my moto g gone forever!! Please someone help me!! I m not ale to sleep from 2 days......!! :crying: :crying:
Quick question: how many times do you flashed a ROM on your Moto G ? It seems that your eMMC flash storage is dying.
Eurofighter_ty said:
Quick question: how many times do you flashed a ROM on your Moto G ? It seems that your eMMC flash storage is dying.
Click to expand...
Click to collapse
on my moto g hardly 10 times untill now!! is there any way to recover it?? :crying:
animesh1558 said:
on my moto g hardly 10 times untill now!! is there any way to recover it?? :crying:
Click to expand...
Click to collapse
You can try one more thing: flash the files with mfastboot instead of fastboot but I don't think that it will work
Eurofighter_ty said:
You can try one more thing: flash the files with mfastboot instead of fastboot but I don't think that it will work
Click to expand...
Click to collapse
already did that!! :crying: more than 10 times still nothing!! :crying: :crying:
RIP :angel:
DavaySuka said:
RIP :angel:
Click to expand...
Click to collapse
can,t anything be done??
To fix TWRP, use: mfastboot erase userdata
EDIT: What Model Moto G do you have?
Download the latest Factory Firmware for that model from here: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Download mFastboot: https://www.androidfilehost.com/?fid=23578570567719065
Manually do ONLY the following Fastboot commands: (enter commands one at a time - don't use a flash.bat)
mfastboot flash partition gpt.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
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
Provide a log of what happens when you do these commands in Fastboot.
lost101 said:
To fix TWRP, use: mfastboot erase userdata
EDIT: What Model Moto G do you have?
Download the latest Factory Firmware for that model from here: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Download mFastboot: https://www.androidfilehost.com/?fid=23578570567719065
Manually do ONLY the following Fastboot commands: (enter commands one at a time - don't use a flash.bat)
mfastboot flash partition gpt.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
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
Provide a log of what happens when you do these commands in Fastboot.
Click to expand...
Click to collapse
here is the log. also its the first time that flashing gpt gave an error!! my model is XT1033 retail asia
animesh1558 said:
here is the log. also its the first time that flashing gpt gave an error!! my model is XT1033 retail asia
Click to expand...
Click to collapse
Was that log from flashing the 5.0.2 firmware image?
lost101 said:
Was that log from flashing the 5.0.2 firmware image?
Click to expand...
Click to collapse
4.4.4
animesh1558 said:
4.4.4
Click to expand...
Click to collapse
That is why you got the error with gpt.bin. Flash the 5.0.2 firmware if you still have issues.
lost101 said:
That is why you got the error with gpt.bin. Flash the 5.0.2 firmware if you still have issues.
Click to expand...
Click to collapse
5.0.2 log!!
shows everything as done but when boots up everything is same......... even the boot logo is same no warning message came!!
sorry for the image quality its from my moto e!!
also it makes a weird noise every 5 secs knock knock noise......, or more like a time bomb is ticking (rename .zip to .amr) to hear it
animesh1558 said:
5.0.2 log!!
shows everything as done but when boots up everything is same......... even the boot logo is same no warning message came!!
Click to expand...
Click to collapse
Your system partition has become read-only. This is a known symptom of Bootloader corruption.
Search XDA for potential solutions, but ultimately you may have to wait for the Lollipop Bootloader 'unbrick' method to arrive.
Related: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
lost101 said:
Your system partition has become read-only. This is a known symptom of Bootloader corruption.
Search XDA for potential solutions, but ultimately you may have to wait for the Lollipop Bootloader 'unbrick' method to arrive.
Related: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Click to expand...
Click to collapse
means this user guide is not useful for me??
animesh1558 said:
means this user guide is not useful for me??
Click to expand...
Click to collapse
What user guide?
lost101 said:
What user guide?
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
will this work on my current rom(AICP)?? or i should have been on 4.4.4 to try this??
animesh1558 said:
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
will this work on my current rom(AICP)?? or i should have been on 4.4.4 to try this??
Click to expand...
Click to collapse
That guide will not work if you have the Lollipop Bootloader - v41.18. In the future, hopefully the newer Bootloader will be supported.
lost101 said:
To fix TWRP, use: mfastboot erase userdata
EDIT: What Model Moto G do you have?
Download the latest Factory Firmware for that model from here: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Download mFastboot: https://www.androidfilehost.com/?fid=23578570567719065
Manually do ONLY the following Fastboot commands: (enter commands one at a time - don't use a flash.bat)
mfastboot flash partition gpt.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
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
Provide a log of what happens when you do these commands in Fastboot.
Click to expand...
Click to collapse
Hello, @lost101 I was willing to know which of the above commands should be used if I want to flash stock ROM on my MOTO G xt1033 without my internal data being harmed? My Moto G is rooted. I have access only to bootloader and fastboot. Phone is in bootloop as well the the recovery isn't moving ahead of the TWRP logo. I tried flashing different verisons of TWRP even I tried ADB as well but my device isn't detected in command "adb devices" though in command "fastboot devices" it is detected. Please help me out.
I read this thread http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492 from starting to end. My problem is somehow same with @ravibhat but his phone was on stock ROM and mine is not.
I was on LOLLIPOP (don't remember the exact version 5.0.2 or 5.1 or whatever) with Tesla ROM.
@sahil_arora05 - Please don't post about the same problem in multiple threads. fastboot erase userdata will make TWRP work again, however it will also wipe internal data. Try booting into stock recovery, enabling ADB sideloading and using the following command:
adb pull /sdcard
Device: XT1031 converted to XT1028 for use on Page Plus. Bootloader unlocked. Rooted with SuperSU 2.46 Running Stock Verizon 5.1 ROM 221.26.7.falcon_cdma.Verizon.en.US
Recovery: TWRP 2.8.7.0
I accepted the new security update - http://forum.xda-developers.com/moto-g/general/moto-g-1st-gen-actually-security-update-t3362323
and when it tried to install the update, the phone just rebooted into TWRP Recovery.
So I flashed stock recovery from the Verizon 5.1 ROM and then tried the update again. This time it completed the update and rebooted but is now stuck at the Motorola bootlogo.
I'm able to reboot into fastboot.
I tried flashing system.img_sparsechunk.0, .1, .2, and .3, and rebooted but there is no change.
What can I try to get past this?
Before starting this I made a backup using TWRP Recovery, can I reinstall TWRP and restore that backup?
it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
If the TWRP backup is still on phone, it might be worth transferring it to a PC / external OTG usb drive, as using the following fastboot command will erase it, along with everything else on internal storage:
fastboot command erase userdata
lost101 said:
it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
If the TWRP backup is still on phone, it might be worth transferring it to a PC / external OTG usb drive, as using the following fastboot command will erase it, along with everything else on internal storage:
fastboot command erase userdata
Click to expand...
Click to collapse
The TWRP backup was saved to an external OTG USB drive, so that's safe.
I was originally going to do the same as I did for the last update - http://forum.xda-developers.com/showpost.php?p=63976723&postcount=109 but tried it first and when it went straight to recovery, I figured I needed to flash stock recovery. I also figured I needed to flash system also, but it through me off when the sparsechunks were numbered 0 - 3 instead of 1 - 4.
I didn't see any errors when I did the flashes.
Right now my battery is drained all the way to 0%. Hopefully it charges back up.
I appreciate the response. Thanks.
Do all fastboot commands including erase userdata. Change sparsechunk names to match the files in the firmware folder you have downloaded. Phone should charge on fastboot screen, but probably not if at a very low percentage.
lost101 said:
Do all fastboot commands including erase userdata. Change sparsechunk names to match the files in the firmware folder you have downloaded. Phone should charge on fastboot screen, but probably not if at a very low percentage.
Click to expand...
Click to collapse
I'm using this stock ROM: XT1028_FALCON_VERIZON_5.1_LPB23.13-33.7_cid2_CFC.xml.zip
The sparsechunk files in that zip are named:
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
system.img_sparsechunk.3
and I need to rename them:
system.img_sparsechunk1
system.img_sparsechunk2
system.img_sparsechunk3
system.img_sparsechunk4
Correct?
Then I would run the following commands one at a time and checking for an OK on each, correct?
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_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
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
After that I can check that I can boot into the OS and then I can flash TWRP and restore my saved backup.
Does that sound right?
Thanks.
Don't rename the sparsechunk files. I said change the name when doing the fastboot commands.
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
Edit: Use mfastboot: https://www.androidfilehost.com/?fid=24052804347778493
lost101 said:
Don't rename the sparsechunk files. I said change the name when doing the fastboot commands.
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
Edit: Use mfastboot: https://www.androidfilehost.com/?fid=24052804347778493
Click to expand...
Click to collapse
OK, I got an error on the first one I tried:
C:\Moto G Flashing\MotoG_Verizon_5.1_ROM>mfastboot devices
TA965000I5 fastboot
C:\Moto G Flashing\MotoG_Verizon_5.1_ROM>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.029s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.318s
C:\Moto G Flashing\MotoG_Verizon_5.1_ROM>
And on the Moto G's screen:
cmd: getvar:max-sparse-size
cmd: download:00008000
cmd: flashartition
version downgraded for primary_gpt
Is that a problem?
Try flashing the latest available XT1028 Verizon 5.1 Factory Firmware Image:
XT1028_FALCON_VERIZON_5.1_LPBS23.13-33.7-2_cid2
lost101 said:
Try flashing the latest available XT1028 Verizon 5.1 Factory Firmware Image:
XT1028_FALCON_VERIZON_5.1_LPBS23.13-33.7-2_cid2
Click to expand...
Click to collapse
OK, that worked. I was able to flash back to the stock ROM.
I'm wondering if there would be any issue if I were to flash TWRP recovery and restore my saved backup?
Thanks for your help.
bw 1 said:
I'm wondering if there would be any issue if I were to flash TWRP recovery and restore my saved backup?
Click to expand...
Click to collapse
I don't personally restore TWRP backups because of bad experiences, but as long as you are using the latest available TWRP you should be okay.
lost101 said:
I don't personally restore TWRP backups because of bad experiences, but as long as you are using the latest available TWRP you should be okay.
Click to expand...
Click to collapse
I decided to start over and not try to recover from the saved file. I don't think there was anything on there that I really needed anyway. All my pictures and stuff was synced to Google.
I'm guessing that I ran into a problem by not flashing the 4 system sparsechunks from the stock ROM to remove root and I wasn't able to flash the same 5.1 that I had on there since it was updated. Flashing the latest newer build Verizon ROM worked because it was the same as what was contained in the update.
I didn't receive another OTA update and system update shows my phone as up to date with:
Android version: 5.1
Android security patch level: 2016-03-01
System version: 221.201.2.falcon_cdma.Verizon.en.US
Build number: LPBS23.13-33.7-2
I'm back to having a working phone. Thanks for your help. Hopefully this will help others too.