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.
Related
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:_)
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.
THE ISSUE HAS BEEN RESOLVED BY THE UNAMAZING MOI
But feel free to read the issue.
######################################
######################################
######################################
Hello everyone, Like usual I managed to destroy to some extend the way my very old phone works. Its Rooted. And after an issue with my phone I reverted to a backup (using CWM) and everything went fine (expect SU Binairy wich failed, but got fixed easily).
Now I'm on stock rom. On Kitkat 4.4.4. So I wanted to install a new rom because I did it many times and never really encountered anything I couldn't fix myself (I've been working with overall technology for 4 years now). While searching the new roms xda offered, I realised that they where all for lolipop (or 90% of them) So I decided to update.
It didn't worked. It didn't worked so hard It bootlooped at least 5 times before I shut it down myself.
I don't remember where it failed, but it had to do with my System Version (Somewhere in a folder)
More info:
MOTO G XT1034 Kitkat 4.4.4
System version:
210.12.41.falcon_umts.AWSRetail.en.CA
Kernel :
3.4.42-gaf6580c
[email protected] #1
Click to expand...
Click to collapse
TL;DR: How do I install this god forsaken lolipop update. (More info right up)
EDIT: this is the CWM error message
Clockworkmod recovery v6.0.4.7
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E: signature verification failed
installing update...
Package expects build fingerprint of motorola/fa
lcon_retca/falcon_umts: 4.4.4/KXB21.14-L1/37:user/releaser-keys
or
motorola/falcon_retca/falcon_umts:5.0.2/LXB22.46-32/31:user/release-keys;
this device has
motorola/falcon_retcaws/falcon_umts:4.4.2/KXB20.9
E:Error in /cache/Blur_Version.210.12.41.falcon_umts.AWSRetail.en.ca .zip
(status 7)
Installation aborted.
Rebooting
Click to expand...
Click to collapse
Please flash one of the factory images that is right for your phone in your case is XT1034:
https://www.androidfilehost.com/?fid=24052804347780781
Download it, extract it, and then flash it using these mfastboot commands:
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 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
and then type mfastboot reboot to reboot the device. If you don't have ADB and fastboot installed then install this ADB and fastboot installer:
https://drive.google.com/file/d/0B0MKgCbUM0itSUhpUklCTFpzWkE/view
also these drivers from Motorola: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
and then extract this to C:\adb folder created by the ADB and fastboot installer
https://www.androidfilehost.com/?fid=95916177934532795
and type "Y" and enter for all questions.
To flash the images just hold the SHIFT key and then right click in the folder and select open command window and apply that commands above (like mfastboot flash etc...)
Good luck !
Eurofighter_ty said:
Please flash one of the factory images that is right for your phone in your case is XT1034:
https://www.androidfilehost.com/?fid=24052804347780781
Download it, extract it, and then flash it using these mfastboot commands:
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 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
and then type mfastboot reboot to reboot the device. If you don't have ADB and fastboot installed then install this ADB and fastboot installer:
https://drive.google.com/file/d/0B0MKgCbUM0itSUhpUklCTFpzWkE/view
also these drivers from Motorola: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
and then extract this to C:\adb folder created by the ADB and fastboot installer
https://www.androidfilehost.com/?fid=95916177934532795
and type "Y" and enter for all questions.
To flash the images just hold the SHIFT key and then right click in the folder and select open command window and apply that commands above (like mfastboot flash etc...)
Good luck !
Click to expand...
Click to collapse
I actually Wrote down the error message down
Clockworkmod recovery v6.0.4.7
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E: signature verification failed
installing update...
Package expects build fingerprint of motorola/fa
lcon_retca/falcon_umts: 4.4.4/KXB21.14-L1/37:user/releaser-keys or motorola/falcon_retca/falcon_umts:5.0.2
/LXB22.46-32/31:user/release-keys;
this device has motorola/falcon_retcaws/falcon_umts:4.4.2/KXB20.9
E:Error in /cache/Blur_Version.210.12.41.falcon_umts.AWSRetail.en.ca.zip
(status 7)
Installation aborted.
Rebooting
Click to expand...
Click to collapse
So if you still think I should flash stock rom tell me. I think I accidentally flashed the wrong stock rom. Im not sure though.
Please follow the instructions I wrote beacuse what you are doing is wrong.
First you can't flash OTA updates with CWM just with Motorola official recovery for your device version in your case is XT1034 AWS the recovery for XT1032 will not flash OTA for XT1034.
Second you're trying to flash a 5.0.2 based image over 4.4.2 and that's is not going to work.
So please follow my instructions and you will get the Android 5.0.2 with no problems like this
Eurofighter_ty said:
Please follow the instructions I wrote beacuse what you are doing is wrong.
First you can't flash OTA updates with CWM just with Motorola official recovery for your device version in your case is XT1034 AWS the recovery for XT1032 will not flash OTA for XT1034.
Second you're trying to flash a 5.0.2 based image over 4.4.2 and that's is not going to work.
So please follow my instructions and you will get the Android 5.0.2 with no problems like this
Click to expand...
Click to collapse
I am not choosing to reboot it in recovery, it does it automatically.
Keep pressed these buttons for 10-15 seconds to enter fastboot mode and then flash the files above: Volume down + power and then connect via usb the moto g and flash the files.
Eurofighter_ty said:
Keep pressed these buttons for 10-15 seconds to enter fastboot mode and then flash the files above: Volume down + power and then connect via usb the moto g and flash the files.
Click to expand...
Click to collapse
I got a soft brick after flashing it. I'm suck at the logo (the bootloader unlocked logo)
Are you flashed all the files ? There were any errors ?
Eurofighter_ty said:
Are you flashed all the files ? There were any errors ?
Click to expand...
Click to collapse
Yes I did and no it didn't had apparent errors. I tried erasing the cache, Dalvik cache and user data. Didn't worked.
So here what ended up happening:
I fixed it without your help.
But now that I flashed motoboot from the file you sent me its uncompatible with my old rom and now my screen flickers everytime I open it (I need to close it to fix it)
Final note. I fixed everything the way I should of.
I got the lolipop stock rom, Pushed it into CWM using adb and flashed it like that.
I got no problems with anything regarding it and will make a backup.
Thanks for the help
Yes, the new bootloader ic ompatibile with 5.0.2 and 5.1. On kitkat you will get screen flicker.
Eurofighter_ty said:
Please flash one of the factory images that is right for your phone in your case is XT1034:
https://www.androidfilehost.com/?fid=24052804347780781
Download it, extract it, and then flash it using these mfastboot commands:
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 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
and then type mfastboot reboot to reboot the device. If you don't have ADB and fastboot installed then install this ADB and fastboot installer:
https://drive.google.com/file/d/0B0MKgCbUM0itSUhpUklCTFpzWkE/view
also these drivers from Motorola: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
and then extract this to C:\adb folder created by the ADB and fastboot installer
https://www.androidfilehost.com/?fid=95916177934532795
and type "Y" and enter for all questions.
To flash the images just hold the SHIFT key and then right click in the folder and select open command window and apply that commands above (like mfastboot flash etc...)
Good luck !
Click to expand...
Click to collapse
Thank you.
I had an M8 and it stopped charging last night. I bought the Moto G from someone on Craigslist while I wait for the next Nexus(s)(i)(whatever). The one I bought was the XT1034 model and I've been searching and reading for a few hours on how to upgrade it from 4.4.4. I tried installing CM 12.1 and got the Bootloader error, I installed a 5.0.2 based rom and got the screen flicker. Now I'm on 5.0.2 with no flicker.
I know what I'm doing, I've been rooting and roming since 2010 with my OG EVO 4G but I still followed your instructions exactly and it worked. The only issue was the first boot hung on the splash screen for a while and I got a bit nervous but everything worked out.
Hi, I've flashed my Moto G and I messed up real bad, multiple flashes and so... I can still get into fastboot, but trying to power up normally just gives me the warning about unlocked bootloader, which hangs indefinitely.
The phone is Moto G 8GB XT1032, Retail DE, originally 4.4.2.
-> What can be done about this? Is there a way to reformat the partitions and flash them all fresh and new?
Just so you know, I've been flashing with this batch below. Whatever I flash with it now, doesn't help.
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash 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
Btw, I know I probably made a lot of stupid mistakes, but in the past I've succesfully flashed dozens of phones and I never messed up like this... Feel free to mock me
Updated: I installed TWRP and found out I am unable to mount or repair system and cache. Also, both partitions show 0 MB size.
The restore to stock should work. Make sure you have mfastboot, the exact factory firmware images for your device, and that each file flashes successfully. Maybe you could post the cmd output if it doesn't flash correctly.
Swamp_cz said:
Hi, I've flashed my Moto G and I messed up real bad, multiple flashes and so... I can still get into fastboot, but trying to power up normally just gives me the warning about unlocked bootloader, which hangs indefinitely.
The phone is Moto G 8GB XT1032, Retail DE, originally 4.4.2.
-> What can be done about this? Is there a way to reformat the partitions and flash them all fresh and new?
Just so you know, I've been flashing with this batch below. Whatever I flash with it now, doesn't help.
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash 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
Btw, I know I probably made a lot of stupid mistakes, but in the past I've succesfully flashed dozens of phones and I never messed up like this... Feel free to mock me
Click to expand...
Click to collapse
Use this tool: http://forum.xda-developers.com/moto-g/general/gpe-lollipop-5-1-1click-installer-t3075522
SLATE21&MOTOG said:
Use this tool: http://forum.xda-developers.com/moto-g/general/gpe-lollipop-5-1-1click-installer-t3075522
Click to expand...
Click to collapse
It initially worked, the phone booted up fine, but after I switched it off, it came back up in recovery mode. Now it only boots up in recovery.
Swamp_cz said:
It initially worked, the phone booted up fine, but after I switched it off, it came back up in recovery mode. Now it only boots up in recovery.
Click to expand...
Click to collapse
so you can't boot into system?
Finally, I solved it.
I couldn't, but then I found many people have this issue and the solution was to somehow repair the misc directory through ADB in TWRP (instructions are somewhere here at xda-dev). Now works well.
Hi guys,
Im from the UK and I have a Moto G XT1032 device which was running Cyanogenmod 12 up until yesterday when I decided to re-install the stock rom. Unfortunately, I have well and truly botched it. The current situation is that I have TWRP set up as the recovery image, so I can get into 'AP Fastboot Flash Mode (S)' OR into TWRP.
I accidentally wiped the 'system' via TWRP which seems to have caused most of my problems. I have tried to install the stock rom using a flashable zip (which failed) and I have also tried around 10 times to install the stock rom using the fastboot commands:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
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
When I try to do a basic wipe using TWRP, this is what shows up: hxxps://s27.postimg.org/r1dax21mb/falcon.jpg (change xx for tt, I don't yet have 10 posts so I cannot post links)
I just cannot seem to get the stock rom installed and booting no matter what I try. Can someone please work with me to get this sorted?
I would very, very much appreciate the help.
Thank you
Ok so i've managed to fix the 'unable to mount storage' issue via TWRP. I changed 'data' to EXT4 and I don't get any errors now.
But the problem is, for whatever reason, I am just unable to install a stock rom. I've used tutorials and still cannot seem to get a stock rom to load/work.
I used fastboot to install the rom files is this zip: XT1032_FALCON_TESCOGBSL_5.1_LPBS23.13-56-2_cid7_CFC.xml.zip
When I do a normal boot it gets stuck on 'Warning bootloader unlocked'
When I go to 'recovery', it boots up to a dead android which says 'no command'
When I go to factory restore, it gets stuck on the 'Warning bootloader unlocked' screen
What am I doing wrong?
edit: I even tried sideloading cyanogenmod and it said it was successful, but then it boots up to TWRP. Totally confused! In desperate need of help.
EDIT: I have now made progress. Here are my basic instructions:
put all the files from the zip file in a folder
put mfastboot.exe files into the same folder
install TWRP, erase
run bat file (add/remove sparse depending on files)
reboot and wait. Should work
I have managed to install the OS but wifi isn't working. And i'm now learning about a file called persist that I need to look into regarding wifi.