Today, i Flash Stock US retail 4.4.2. Install Recovery CMW and root. y try to update with OTA, when the update reboot the phone, CMW error say something of certification. when i try to flash again the rom, i have this problem:
C:\Users\Sebastian\Desktop\US_retail_XT1032_KXB20.9-1.8-1.4_CFC.xml>mfastboot fl
ash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
Flashing primary GPT image...
Flashing backup GPT image...
OKAY [ 0.440s]
finished. total time: 0.471s
C:\Users\Sebastian\Desktop\US_retail_XT1032_KXB20.9-1.8-1.4_CFC.xml>mfastboot fl
ash motoboot motoboot.img
sending 'motoboot' (1940 KB)...
Click to expand...
Click to collapse
and never continue... And when i try to Power Up the phone, it say: "Fastboot reason: UTAG "bootmode" configured as fastboot.
Really sorry for my english!!
I need help .
Can you do something in that menu? Or noting?
I'm not sure but you can try:
Code:
fastboot oem fb_mode_clear
If this doesent help you can try to reflash the right version of motoboot.img.
Best way to start all over is follow this thread, make your updates and then make any modifications (root, cwm,.....) you want.
Thats the easiest way to get out of trouble.
mokkami said:
Can you do something in that menu? Or noting?
I'm not sure but you can try:
Code:
fastboot oem fb_mode_clear
If this doesent help you can try to reflash the right version of motoboot.img.
Best way to start all over is follow this thread, make your updates and then make any modifications (root, cwm,.....) you want.
Thats the easiest way to get out of trouble.
Click to expand...
Click to collapse
Thanks for Reply!!
Okay! The phone now boot ! But when i try to flash something, the problem persist. I cant flash motoboot.img, or recovery.img...
Error msg? Please be precise.
mokkami said:
Error msg? Please be precise.
Click to expand...
Click to collapse
No one, just stay here:
C:\Users\Sebastian\Desktop\US_retail_XT1032_KXB20. 9-1.8-1.4_CFC.xml>mfastboot fl
ash motoboot motoboot.img
sending 'motoboot' (1940 KB)...
Click to expand...
Click to collapse
And after this, it boot to fastboot mode whit this msg : "utag "flashfail" configured as fastboot "
Hmmm......no idea atm, but you said, you flashed stock US retail 4.4.2.
What was on your phone before? Maybe the 4.3 version? Or was 4.4.2 already on it?
Try to flash stock 4.3 completly if it was like that.
Try to erase all partitions via fastboot before.
mokkami said:
Hmmm......no idea atm, but you said, you flashed stock US retail 4.4.2.
What was on your phone before? Maybe the 4.3 version? Or was 4.4.2 already on it?
Try to flash stock 4.3 completly if it was like that.
Try to erase all partitions via fastboot before.
Click to expand...
Click to collapse
I cane from 4.4.2 GPE.
HOW TO ERASE ALL?
Ahhhhhh..............did you try to go back to GPE Stock?
I would recommend to do that first.
mokkami said:
Ahhhhhh..............did you try to go back to GPE Stock?
I would recommend to do that first.
Click to expand...
Click to collapse
Yep, and nothing...
Code:
fastboot erase motoboot
?
Problem solved.
The drivers in my pc are bugged, i try in other pc and it work! I'm so happy
i solved it
linqen said:
Today, i Flash Stock US retail 4.4.2. Install Recovery CMW and root. y try to update with OTA, when the update reboot the phone, CMW error say something of certification. when i try to flash again the rom, i have this problem:
and never continue... And when i try to Power Up the phone, it say: "Fastboot reason: UTAG "bootmode" configured as fastboot.
Really sorry for my english!!
I need help .
Click to expand...
Click to collapse
Look i have the same just when you boot it up you enter the fastboot there you have some comands you must chose normal powerup and press volume up to chose use volume down, that works at me ,just when i power it up i press volume up and it works
mokkami said:
Code:
fastboot erase motoboot
?
Click to expand...
Click to collapse
Don't do that. DON'T! It will most likely result in an error message or a hard brick, and the device will only have HS-USB QDloader.
I never had a Problem with that.
Of course you have flash it later again....
Code:
fastboot flash motoboot motoboot.img
mokkami said:
I never had a Problem with that.
Of course you have flash it later again....
Code:
fastboot flash motoboot motoboot.img
Click to expand...
Click to collapse
When you restart without reflashing motoboot, RIP.
but is possible to downgrade bootloader? I have a problem, i make kitkat rom and for me is best to have kitkat bootloader. Can I downgrade bootloader?
Sent from my Moto G using XDA-Developers mobile app
thnkssss broooo its work very well thnkkkks alot
thanks bro its working
Thanks!
This help: "fastboot oem fb_mode_clear"
( OT1072 )
thanks
nice job very helpfull
Related
Hello, so i have a Moto G XT1032 from Telus. Not too long ago i decided to root it (bad idea). Later on i decided that i don't want the root anymore and decided to unroot it. I thought i succeeded but when time came to update from Android 4.4.4 to 5.0 i proved myself wrong. When Android 5.0 started to install, it was installing through CWM and it was ending up giving me a error. I wanted to get rid of CWM and searched up some tutorials and ended up finding out that i have to flash my phone back to stock firmware. I flashed the wrong firmware and ended up converting my XT1032 to XT1033 Dual-Sim. I then found the good Telus firmware for my XT1032 but when i flashed it and connect my phone to my pc, my pc says that a XT1033 is connected. I'm also not able to lock bootloader, it gives me "bootloader sst lock failure". So please help me!
-Thank You
Did you flash the 4.4.4 firmware? Did you flash all partitions manually? No need to lock the bootloader to get the OTA update.
audit13 said:
Did you flash the 4.4.4 firmware? Did you flash all partitions manually? No need to lock the bootloader to get the OTA update.
Click to expand...
Click to collapse
Yes i flashed the 4.4.4 firmware XT1032_TELUS-CA_4.4.4_KXB21.14-L1.50_52_cid14_CFC_1FF.xml.
By flashing all partitions manually, do you mean this?
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 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
Then yes.
Which bootloader version is on your phone? All partitions flashed without issue?
audit13 said:
Which bootloader version is on your phone? All partitions flashed without issue?
Click to expand...
Click to collapse
How do i check the version? and yes all partitions flashed without any issue
Boot into fastboot on the phone and look at the top. It will be 41.xx
audit13 said:
Boot into fastboot on the phone and look at the top. It will be 41.xx
Click to expand...
Click to collapse
41.18
dystieguy said:
41.18
Click to expand...
Click to collapse
With TWRP installed wipe data, cache and system partitions, and then reinstall with mfastboot again. :good:
Feche said:
With TWRP installed wipe data, cache and system partitions, and then reinstall with mfastboot again. :good:
Click to expand...
Click to collapse
I lost you over here, what's TWRP and how do i wipe data, cache and system partitions? (Sorry, i'm a noob in this)
dystieguy said:
I lost you over here, what's TWRP and how do i wipe data, cache and system partitions? (Sorry, i'm a noob in this)
Click to expand...
Click to collapse
TWRP is a custom recovery (like CWM) that will let you flash .zips, and do other things like wipe data partition, system partition, etc.
You can download it here
If you have TeamViewer I can help you :highfive:
You have the LP bootloader which is 41.18.
You didn't get an error trying to flash the motoboot.img file?
Feche said:
TWRP is a custom recovery (like CWM) that will let you flash .zips, and do other things like wipe data partition, system partition, etc.
You can download it here
If you have TeamViewer I can help you :highfive:
Click to expand...
Click to collapse
I need ROOT for this but i already removed root from my phone.
audit13 said:
You have the LP bootloader which is 41.18.
You didn't get an error trying to flash the motoboot.img file?
Click to expand...
Click to collapse
I think i did actually, it said in purple downgraded something.
dystieguy said:
I need ROOT for this but i already removed root from my phone.
Click to expand...
Click to collapse
You don't need to be rooted, just bootloader unlocked.
Feche said:
You don't need to be rooted, just bootloader unlocked.
Click to expand...
Click to collapse
Wait, i don't need to download the android app?
dystieguy said:
I think i did actually, it said in purple downgraded something.
Click to expand...
Click to collapse
If it downgraded the bootloader while flashing KK, you would not have a 41.18 bootloader.
audit13 said:
If it downgraded the bootloader while flashing KK, you would not have a 41.18 bootloader.
Click to expand...
Click to collapse
Should i try re-flashing it and tell you if i get any issues?
Try flashing just the motoboot file and let me know if it goes through. If it does and you are still on the 41.18 bootloader, that indicates to me that you're re-flashing the same bootloader.
audit13 said:
Try flashing just the motoboot file and let me know if it goes through. If it does and you are still on the 41.18 bootloader, that indicates to me that you're re-flashing the same bootloader.
Click to expand...
Click to collapse
it gives this:
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.078s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.328s
The bootloader is not flashing because you are trying to downgrade from 41.18 to 41.13.
Do you receive any error messages when flashing the rest of the ROM?
Hi,
I really need some help. I had a stock 5.0.2 Lollipop and an unlocked device when I decided to flash CM 12.1. I get into the bootloader and tried to flash the recovery image but it always get the error "Mismatch partition size" witch I ignored because of the posts and suggestion here. But when I selected recovery from the bootloader it didn't load. At first it just restarted normally. I've tried every single possible custom recovery but none worked. Now I've tried something different. fastboot boot recovery.img to try to flash the rom. But it just appear a battery with a question mark on it. The only thing I can flash is a stock rom 4.4.3 that doesn't have any service at all.
Thanks for your help :fingers-crossed:
I think you get that error because your recovery is outdated (use latest twrp from here), try to flash by using "fastboot flash recovery yourfilename.img"
try that and see if you still had any problems
sayash5 said:
I think you get that error because your recovery is outdated (use latest twrp from here), try to flash by using "fastboot flash recovery yourfilename.img"
try that and see if you still had any problems
Click to expand...
Click to collapse
Can you tell me the version to download it? The link is broken.
sayash5 said:
I think you get that error because your recovery is outdated (use latest twrp from here), try to flash by using "fastboot flash recovery yourfilename.img"
try that and see if you still had any problems
Click to expand...
Click to collapse
same error, still can't enter recovery, it is just like power-off. should i try to rebuild the recovery specially for xt1033 and not for xt1032?
lung1 said:
same error, still can't enter recovery, it is just like power-off. should i try to rebuild the recovery specially for xt1033 and not for xt1032?
Click to expand...
Click to collapse
sorry the latest twrp was here, try this and see if it works
sayash5 said:
sorry the latest twrp was here, try this and see if it works
Click to expand...
Click to collapse
same error, same behaviour
lung1 said:
same error, same behaviour
Click to expand...
Click to collapse
flash from bootloader not from the recovery, power + down
sayash5 said:
flash from bootloader not from the recovery, power + down
Click to expand...
Click to collapse
I flash from bootloader, I can't enter to recovery, that's my problem. If I can't get into recovery I can't flash any ROM.
lung1 said:
I flash from bootloader, I can't enter to recovery, that's my problem. If I can't get into recovery I can't flash any ROM.
Click to expand...
Click to collapse
weird, if you cant get into recovery that means there isnt any recovery in first place but when you flashed twrp from bootloader, it should be there or the twrp didnt really flashed..
sayash5 said:
weird, if you cant get into recovery that means there isnt any recovery in first place but when you flashed twrp from bootloader, it should be there or the twrp didnt really flashed..
Click to expand...
Click to collapse
Exactly, it is like the bootloader doesn't let me to flash it. If I try to flash a stock recovery it lets me to do that, but not any other.
lung1 said:
Exactly, it is like the bootloader doesn't let me to flash it. If I try to flash a stock recovery it lets me to do that, but not any other.
Click to expand...
Click to collapse
maybe the bootloader is locked? what is your bootloader current version?
sayash5 said:
maybe the bootloader is locked? what ia you r bootloader current version?
---------- Post added at 08:24 PM ---------- Previous post was at 08:22 PM ----------
maybe the bootloader is locked? what is your bootloader current version?
Click to expand...
Click to collapse
AP Fastboot Flash mode (S)
41.19 (sha-291b089, 2015-02-09 12:46:46)
CPU: MSM8226 CS
eMMC> 16GB Toshiba RV=06 PV=01TY=17
DRAM: 1024MB Samsung S4 SDRAM DIE=4GB
Battery OK
Device is UNLOCKED. Status Code: 3
lung1 said:
AP Fastboot Flash mode (S)
41.19 (sha-291b089, 2015-02-09 12:46:46)
CPU: MSM8226 CS
eMMC> 16GB Toshiba RV=06 PV=01TY=17
DRAM: 1024MB Samsung S4 SDRAM DIE=4GB
Battery OK
Device is UNLOCKED. Status Code: 3
Click to expand...
Click to collapse
hmm seems fine, what about the log when you try to flash twrp?
C:\Users\RazvanCristian\Desktop>fastboot flash recovery twrp-2.8.6.0-falcon.img
target reported max download size of 536870912 bytes
sending 'recovery' (10184 KB)...
OKAY [ 0.426s]
writing 'recovery'...
OKAY [ 0.554s]
finished. total time: 0.987s
and on the device is:
cmd: getvar: partition-type:recovery
cmd:getvar:max-download-size
cmd:download:009f2000
cmd:flash:recovery
Mismatched partition size (recovery)
lung1 said:
C:\Users\RazvanCristian\Desktop>fastboot flash recovery twrp-2.8.6.0-falcon.img
target reported max download size of 536870912 bytes
sending 'recovery' (10184 KB)...
OKAY [ 0.426s]
writing 'recovery'...
OKAY [ 0.554s]
finished. total time: 0.987s
and on the device is:
cmd: getvar: partition-type:recovery
cmd:getvar:max-download-size
cmd:download:009f2000
cmd:flash:recovery
Mismatched partition size (recovery)
Click to expand...
Click to collapse
Try flash using mfastboot.exe from this thread http://forum.xda-developers.com/showthread.php?p=47820707
Same result. I want to mention again that it is an xt1033 not xt1032.
lung1 said:
C:\Users\RazvanCristian\Desktop>fastboot flash recovery twrp-2.8.6.0-falcon.img
target reported max download size of 536870912 bytes
sending 'recovery' (10184 KB)...
OKAY [ 0.426s]
writing 'recovery'...
OKAY [ 0.554s]
finished. total time: 0.987s
and on the device is:
cmd: getvar: partition-type:recovery
cmd:getvar:max-download-size
cmd:download:009f2000
cmd:flash:recovery
Mismatched partition size (recovery)
Click to expand...
Click to collapse
I dont see any problem here, it is flashed successfully and the mismatched partition is nothing serious, what you do after this?
perhaps after trying to go recovery, you should wait a little waiting for the twrp to load, let phone may sleep for a while
sayash5 said:
I dont see any problem here, it is flashed successfully and the mismatched partition is nothing serious, what you do after this?
perhaps after trying to go recovery, you should wait a little waiting for the twrp to load, let phone may sleep for a while
Click to expand...
Click to collapse
I will load a video.
I got an xt1031 on ebay that was flashed to work on Page Plus. I have restored the ROM to falcon_KXB21.14-L1.57.zip but the baseband still says "VZW_CUST" and I get activation stuff when I start it up. How can I get this working like a regular xt1031 again? I am rooted, unlocked and have CWM installed. I also have a regular, working xt1031 if I need anything off of it.
I can't find any information about restoring baseband or anything like that. After flashing the stock ROM I restored the phone.
HardOnChairs said:
I got an xt1031 on ebay that was flashed to work on Page Plus. I have restored the ROM to falcon_KXB21.14-L1.57.zip but the baseband still says "VZW_CUST" and I get activation stuff when I start it up. How can I get this working like a regular xt1031 again? I am rooted, unlocked and have CWM installed. I also have a regular, working xt1031 if I need anything off of it.
I can't find any information about restoring baseband or anything like that. After flashing the stock ROM I restored the phone.
Click to expand...
Click to collapse
Factory Firmware Images are available here: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
I would start by only flashing the 'system.img.sparsechunk' files:
mfastboot flash system system.img_sparsechunk1 (CHANGE NAME TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk2 (CHANGE NAME TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk3 (CHANGE NAME TO MATCH ACTUAL FILE IN FOLDER)
mfastboot erase userdata
mfastboot reboot​
lost101 said:
by only flashing
Click to expand...
Click to collapse
Would that be more effective? Because I would be just as happy to flash the entire ROM again and start over if it would work as well.
Edit: nevermind I see what's going on now with the zip
HardOnChairs said:
Would that be more effective? Because I would be just as happy to flash the entire ROM again and start over if it would work as well.
Edit: nevermind I see what's going on now with the zip
Click to expand...
Click to collapse
My recommendation is for your safety. Messing with fastboot has destroyed many phones.
Code:
C:\Users\User\Desktop\New folder>mfastboot devices
'mfastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\User\Desktop\New folder>mfastboot devices
TA96506RJD fastboot
C:\Users\User\Desktop\New folder>mfastboot flash system system.img_sparsechunk1
target max-sparse-size: 256MB
sending 'system' (262084 KB)...
OKAY [ 8.213s]
writing 'system'...
OKAY [ 14.144s]
finished. total time: 22.361s
C:\Users\User\Desktop\New folder>mfastboot flash system system.img_sparsechunk2
target max-sparse-size: 256MB
sending 'system' (256888 KB)...
OKAY [ 8.052s]
writing 'system'...
OKAY [ 12.088s]
finished. total time: 20.142s
C:\Users\User\Desktop\New folder>mfastboot flash system system.img_sparsechunk3
target max-sparse-size: 256MB
sending 'system' (238359 KB)...
OKAY [ 7.485s]
writing 'system'...
OKAY [ 11.907s]
finished. total time: 19.393s
C:\Users\User\Desktop\New folder>mfastboot flash system system.img_sparsechunk4
target max-sparse-size: 256MB
sending 'system' (26644 KB)...
OKAY [ 0.875s]
writing 'system'...
OKAY [ 8.438s]
finished. total time: 9.313s
C:\Users\User\Desktop\New folder>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.500s]
finished. total time: 0.500s
C:\Users\User\Desktop\New folder>mfasboot reboot
'mfasboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\User\Desktop\New folder>mfastboot reboot
rebooting...
finished. total time: -0.000s
C:\Users\User\Desktop\New folder>
Everything seems to have gone well but I still get the activation screen and the baseband still has VZW_CUST.
Edit: Here are all of the files in the zip for my phone if that helps:
HTML:
boot.img
falcon_boost_user_4.4.4_KXB21.14-L1.57_57_release-keys-cid9.bat
falcon_boost_user_4.4.4_KXB21.14-L1.57_57_release-keys-cid9.xml
fsg.mbn
gpt.bin
logo.bin
mfastboot.exe
motoboot.img
NON-HLOS.bin
recovery.img
system.img_sparsechunk1
system.img_sparsechunk2
system.img_sparsechunk3
system.img_sparsechunk4
Now flash the Radio Firmware only. Use the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn​
The baseband says BOOST_CUST now but I am still getting these activation screens that I never get on my other boost phones.
HardOnChairs said:
The baseband says BOOST_CUST now but I am still getting these activation screens that I never get on my other boost phones.
Click to expand...
Click to collapse
From memory, I do recall Verizon software being present in the Boost Firmare Images. But you can delete certain apks to stop those activation screens appearing. If you install TWRP, you can use the file explorer to delete the folders. I will try to get the correct names soon, but you might be able to guess them - they are located in /system/priv-app
The weird this is that it is a boost/sprint app.
com.motorola.android.omadm.sprint.client
Click to expand...
Click to collapse
But I have a bunch of these phones and none of them do this. There are some activation apps, but they are never intrusive like this.
On one hand I'd like to get it to go away any way I can, but I would most prefer all of my devices to be set up the same. Is there anything I can do given that I have an identical model that is set up the right way? I don't know enough about how android partitions work to understand why flashing a stock ROM and resetting it wouldn't make it act exactly the same as my other devices that I have done the same with.
HardOnChairs said:
The weird this is that it is a boost/sprint app.
But I have a bunch of these phones and none of them do this. There are some activation apps, but they are never intrusive like this.
On one hand I'd like to get it to go away any way I can, but I would most prefer all of my devices to be set up the same. Is there anything I can do given that I have an identical model that is set up the right way? I don't know enough about how android partitions work to understand why flashing a stock ROM and resetting it wouldn't make it act exactly the same as my other devices that I have done the same with.
Click to expand...
Click to collapse
Those are the stock activation apps that are needed if you plan to use the phone. Typically, they "go away" or are "unseen" when the device is activated.
Sent from my XT1031
@HardOnChairs - Apologies, I got confused between Verizon and Sprint. There are no Verizon files in the Boost Firmware, only those for Sprint.
The conversion to PagePlus includes flashing the XT1028 Bootloader - so that's still the Bootloader you have. Flashing the XT1031 Boost Bootloader may be a necessary step, but if something goes wrong you have a brick on your hands.
ATTACK said:
Those are the stock activation apps that are needed if you plan to use the phone. Typically, they "go away" or are "unseen" when the device is activated.
Sent from my XT1031
Click to expand...
Click to collapse
I do still get activation alerts on my other ones but they are not intrusive and they can be disabled. All of the xt1031 phones I have are on wifi only. Does that mean that they are still "activated" from before? In that case is it possible to activate these two that I have without actually buying service for them?
lost101 said:
@HardOnChairs - Apologies, I got confused between Verizon and Sprint. There are no Verizon files in the Boost Firmware, only those for Sprint.
The conversion to PagePlus includes flashing the XT1028 Bootloader - so that's still the Bootloader you have. Flashing the XT1031 Boost Bootloader may be a necessary step, but if something goes wrong you have a brick on your hands.
Click to expand...
Click to collapse
I have managed to update the bootloader of one of my devices and it actually caused some issues. The display constantly glitches. This was when I was trying to update to bootloader to work on 5.x. Do you know where I can find the original bootloader for 4.x? I never managed to find it. Is it possible to pull it off of one of my other devices? Or do you know if that zip I got has the original one?
HardOnChairs said:
I have managed to update the bootloader of one of my devices and it actually caused some issues. The display constantly glitches. This was when I was trying to update to bootloader to work on 5.x. Do you know where I can find the original bootloader for 4.x? I never managed to find it. Is it possible to pull it off of one of my other devices? Or do you know if that zip I got has the original one?
Click to expand...
Click to collapse
Be very careful with Bootloaders. You cannot go back now that you have upgraded. The display 'glitch' is caused by running KitKat ROM with a Lollipop Bootloader. Turn screen off once to stop it.
lost101 said:
Be very careful with Bootloaders. You cannot go back now that you have upgraded. The display 'glitch' is caused by running KitKat ROM with a Lollipop Bootloader. Turn screen off once to stop it.
Click to expand...
Click to collapse
I see. Well that aside, thats a different phone altogether, is it possible for me to check which bootloader these new phones have? And if they are on the 1028, is it possible for me to go back to the 1031 KK version?
HardOnChairs said:
I see. Well that aside, thats a different phone altogether, is it possible for me to check which bootloader these new phones have? And if they are on the 1028, is it possible for me to go back to the 1031 KK version?
Click to expand...
Click to collapse
Check the Fastboot screen:
i) The 'hardware' way.
a) Unplug the USB cable and power off the phone.
b) Press and hold 'Volume down' then power on the phone.
c) Connect USB cable to your computer.
ii) The 'software' way.
a) Enable developer mode on the Moto G (Settings-> 'About Phone'. Tap 7 times on 'Build Number')
b) Enable USB debugging. (Settings -> 'Developer options' -> 'USB Debugging' -> check)
c) Connect phone to computer via USB, you should see a new ADB device detected and drivers installed.
d) Open Command Prompt or Terminal, navigate to the Firmware / ADB folder (i.e CD C:\motog_firmware ) and type:
Code:
adb reboot-bootloader
I don't know if you can safely flash the XT1031 KitKat Bootloader now that the phone has been converted to XT1028 - but it's likely considering that's the original Model of the phone.
The fastboot screen says
41.13 (sha-7dc8e78, 2014-06-16 16:33:29)
Click to expand...
Click to collapse
HardOnChairs said:
The fastboot screen says
Click to expand...
Click to collapse
v41.13 is KitKat, v41.18 is Lollipop.
lost101 said:
v41.13 is KitKat, v41.18 is Lollipop.
Click to expand...
Click to collapse
So I should try reflashing motoboot.img? Is there a way to be sure that it is KK?
HardOnChairs said:
So I should try reflashing motoboot.img? Is there a way to be sure that it is KK?
Click to expand...
Click to collapse
To be sure what is KitKat? v41.13 is 100% not a Lollipop Bootloader.
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
sticktornado said:
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
Click to expand...
Click to collapse
I know, I flashed the correct number of system images that were in the zip file.
Thanks,
rent0n said:
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
Click to expand...
Click to collapse
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
rent0n said:
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
Click to expand...
Click to collapse
I tried that and it didn't work. When I try to go into recovery mode the phone keeps bootlooping.
One thing I noticed is that when I try to format cache or userdata I get this error:
Code:
$ fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.013s
I think there might be something wrong with the file system in my partitions. How can I manually format my partitions?
Thanks,
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
therealduff1 said:
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
Click to expand...
Click to collapse
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
rent0n said:
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
Click to expand...
Click to collapse
What os were you running when the phone screwed up ?
therealduff1 said:
What os were you running when the phone screwed up ?
Click to expand...
Click to collapse
I was running 5.1.1 when I got the notification for the 6.0 update.
I've noticed that trying to flash 5.1.1 firmware with fastboot gives me errors (preflash validation failed) while the 6.0 work "fine" (i.e.: I get OKAY after every step but then the phone is always stuck in a bootloop).
Thanks!
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
therealduff1 said:
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
Click to expand...
Click to collapse
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
rent0n said:
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
Click to expand...
Click to collapse
Have you gave this a try?
heavy_metal_man said:
Have you gave this a try?
Click to expand...
Click to collapse
Yes, no luck unfortunately.
I think I might have flashed the 5.1.1 bootloader after all - is there any way to recover from there?
Thanks,
Bump!
Does anyone have any other suggestion please?
Thanks,
Last bump
I'm going to sell this on eBay as non-working then unless someone comes up with a clever solution?
Thanks for your help!
Try flashing once more starting with the gpt.bin (that should hopefully take care of raw partition error) and skipping the bootloader altogether. Also, may be worthwhile to try mfastboot.exe instead of fastboot.exe.
I have this same issue, but I haven't flash 5.1.1 Files, I Only tried with 6.0 Brazil Retail.
I also tried to flash gpt to get rid of the "raw" partition, everything goes ok but still displaying that error. Anyone can help?
I got the same problem with my Moto E 2015... If I find a solution I will reply it in this topic..
Well, I was messing around in TWRP without really knowing what I was doing, and selected all boxes in the Wipe section. Now, when I try to install the stock rom, I get an error telling me that gpt.bin can't be downgraded, and when I try to sideload a rom via TWRP, I get another error saying that the .zip file is invalid. Can't send pictures of anything on the phone since it is the only one I have. Sorry.
Are you using fastboot to flash stock ROM? Then simply leave the gpt.bin and bootloader.img and flash the rest. The phone should boot up fine.
For the Custom ROM, maybe the zip file is corrupted, have you compared SHA/MD5 hash sums if one is provided with the download? They are a good way to check that downloaded file is complete and not corrupted.
Broadcasted from Zeta Reticuli
Gravemind2015 said:
Are you using fastboot to flash stock ROM? Then simply leave the gpt.bin and bootloader.img and flash the rest. The phone should boot up fine.
For the Custom ROM, maybe the zip file is corrupted, have you compared SHA/MD5 hash sums if one is provided with the download? They are a good way to check that downloaded file is complete and not corrupted.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Already tried using fastboot and leaving the gpt out, but the phone keep getting stuck in a bootloop where it goes into recovery and tries to wipe something, and get an error(failed to mount /data). And the rom is not corrupted, since I tried a LOT of different sources, and nobody ever complained of it being corrupted or so.
ctcsilva said:
Already tried using fastboot and leaving the gpt out, but the phone keep getting stuck in a bootloop where it goes into recovery and tries to wipe something, and get an error(failed to mount /data). And the rom is not corrupted, since I tried a LOT of different sources, and nobody ever complained of it being corrupted or so.
Click to expand...
Click to collapse
i would suggest you to revert back to og firmware and then trying to flash twrp again then you can try to flash roms again
just go into fastboot and follow the instructions
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
i was too in this situation but in a different device hope this helps you
Amar 721 said:
i would suggest you to revert back to og firmware and then trying to flash twrp again then you can try to flash roms again
just go into fastboot and follow the instructions
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
i was too in this situation but in a different device hope this helps you
Click to expand...
Click to collapse
Can't actually install those firmwares too, since I keep getting the error followed by the bootloop.
ctcsilva said:
Can't actually install those firmwares too, since I keep getting the error followed by the bootloop.
Click to expand...
Click to collapse
you get errors on adb?
if no then just press the power and volume down button simultaneously then release the dont go into recovery wait there and follow the guide
let it be a side just after pressing the buttons dont go to recovery or anything just wait there and do relock the device bootloader using adb and fastboot you can get tutorials of it everywhere
Amar 721 said:
you get errors on adb?
if no then just press the power and volume down button simultaneously then release the dont go into recovery wait there and follow the guide
let it be a side just after pressing the buttons dont go to recovery or anything just wait there and do relock the device bootloader using adb and fastboot you can get tutorials of it everywhere
Click to expand...
Click to collapse
Yes, I do. Just tried right now.
C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot oem lock begin
(bootloader) Please fully flash the signed build before locking phone!
OKAY [ 0.104s]
finished. total time: 0.105s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot flash partition zip/gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.168s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
Along with version downgraded for primary_gpt on bootloader
The same thing with boot.img
@ctcsilva : Flash TWRP
Code:
fastboot flash recovery twrp.img
where twrp.img is the name of twrp file. Now boot into TWRP, go to Mount and check that /data is selected, if not, then mark it and select back.
Now go to Wipe>Advanced Wipe. Select data and tap Repair or Change File System. Now select Repair File system and swipe to confirm. Now go to Wipe> Factory Reset and swipe to confirm. Then Reboot>bootloader.
Connect the phone to pc and flash stock recovery
Code:
fastboot flash recovery recovery.img
, and boot into it. Press and hold power and press volume up key once, you should see the options now. Select factory reset and confirm. Now reflash the stock firmware from fastboot and see if it boots.
Edit :- Use this guide, do not attempt to relock bootloader, it won't lock unless every file is flashed, which is again impossible because the firmware is older than the one present in the phone.
Broadcasted from Zeta Reticuli
ctcsilva said:
Yes, I do. Just tried right now.
Along with version downgraded for primary_gpt on bootloader
The same thing with boot.img
Click to expand...
Click to collapse
oem is not unlocked : ( you should try asking help from a senior member like ishubhamsingh or other i guess they can definetly help you