Hi all great minds of XDAdev
I have a Motorola 4G LTE XT1040, with unlocked bootloader , fastboot version 41.1A, TWRP 3.0.2.0 and stock 5.1 ROM.
I didn't have a downgrade and my phone is not bricked.
The thing is, my phone works normally until it randomly just freezes, then when I turn it on it goes to the dreaded screen with "fastboot reason: failed to initialize partition table status code 0"
If I try to select "normal startup" or something, it says "Failed to find boot image" or something like that, yet when I turn it off and on again, it starts normally. The problem is that the freezes are completely random.
I find very weird that whenever that forced restart happens it says "Status: LOCKED" when the phone isn't, and when I start fastboot manually it says unlocked and status code 3. Not only that, but can also select "Normal Startup" with no problem.
I've tried to install many ROMs and stuff through fastboot and recovery with no luck, the phone keeps restarting to the error screen and then starts normally until the next freeze.
What can I do? Is there something you think I could do to stop this? Should I post more info for you? Thank you!
fastboot flash partition
我日你打夜 said:
fastboot flash partition
Click to expand...
Click to collapse
Excuse me, what partirion should I flash? Still no luck and it's getting worse.
Flash the latest XT1040 Factory Firmware Image using Fastboot. If this does not resolve your issue, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
lost101 said:
Flash the latest XT1040 Factory Firmware Image using Fastboot. If this does not resolve your issue, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Hi Lost. First of all, thank you very much, you're a great member.
Second, well, I don't know what to do. The symptoms are very random, sometimes it just goes to sleep and never wakes up, sometimes it freezes completely, then the screen locks itself and starts to flash until I hard reboot it, sometimes it goes to the corrupt fastboot screen I'm talking about. One special case which is very common under "stress" is that it goes to the lockscreen and while the screen becomes unresponsive, the lockscreen goes on and off, and the volume/power buttons work normally. Still, as it's unresponsive, it needs a hard reset to work again.
I tried your ROM and while the proccess goes normally the problem hasn't gone away (specially the "surprise lockscreen" thing). I tried to re-unlock the bootloader in one of the lucky times the phone got into the corrupt fastboot but it only says
(bootloader) fastboot oem unlock disabled!
FAILED (remote failure)
finished. total time: 0.016s
I tried to use the reset to fastboot option and the phone went to a black screen with no sings of life. Then, after a hard reset and normal fastboot reboot, there's nothing "wrong" and the screen says "unlocked".
The phone is almost unusable, as it seems to work fine until it suddenly doesn't. I'm certainly baffled.
If it helps, the phone was /probably/ in KitKat when I downloaded a stock Brazil ROM months ago to make the update to Lollipop. The phone didn't have this sudden reboot problem until a month or so ago.
This is the flash log, as you requested.
D:\Minimal ADB and Fastboot>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.028s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.336s]
finished. total time: 0.368s
D:\Minimal ADB and Fastboot>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.117s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.099s]
finished. total time: 1.221s
D:\Minimal ADB and Fastboot>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.063s]
writing 'logo'...
OKAY [ 0.070s]
finished. total time: 0.136s
D:\Minimal ADB and Fastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.458s]
writing 'boot'...
OKAY [ 0.718s]
finished. total time: 1.181s
D:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk0
target max-sparse-size: 256MB
sending 'system' (257719 KB)...
OKAY [ 10.299s]
writing 'system'...
OKAY [ 11.126s]
finished. total time: 21.447s
D:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk1
target max-sparse-size: 256MB
sending 'system' (257518 KB)...
OKAY [ 10.311s]
writing 'system'...
OKAY [ 9.891s]
finished. total time: 20.206s
D:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk2
target max-sparse-size: 256MB
sending 'system' (256627 KB)...
OKAY [ 10.376s]
writing 'system'...
OKAY [ 15.416s]
finished. total time: 25.796s
D:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk3
target max-sparse-size: 256MB
sending 'system' (189925 KB)...
OKAY [ 7.656s]
writing 'system'...
OKAY [ 8.848s]
finished. total time: 16.508s
D:\Minimal ADB and Fastboot>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (60236 KB)...
OKAY [ 2.465s]
writing 'modem'...
OKAY [ 1.531s]
finished. total time: 4.001s
D:\Minimal ADB and Fastboot>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.023s]
finished. total time: 0.025s
D:\Minimal ADB and Fastboot>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.023s]
finished. total time: 0.024s
D:\Minimal ADB and Fastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (661 KB)...
OKAY [ 0.098s]
writing 'fsg'...
OKAY [ 5.681s]
finished. total time: 5.787s
D:\Minimal ADB and Fastboot>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.348s]
finished. total time: 0.353s
D:\Minimal ADB and Fastboot>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 2.999s]
finished. total time: 3.002s
D:\Minimal ADB and Fastboot>mfastboot reboot
rebooting...
finished. total time: 0.003s
Click to expand...
Click to collapse
You're not giving me enough information. I need to know exactly what Firmware Image you are flashing.
A new XT1040 Firmware Image was added in the last few days: XT1040_PEREGRINE_RETBR_5.1_LPBS23.13-35.5-1_cid12
Hi Lost, that's just the one I flashed (Brasil's newest build).
Ahasverus said:
Hi Lost, that's just the one I flashed (Brasil's newest build).
Click to expand...
Click to collapse
In the fastboot log you provided, the sparsechunks are incorrectly named.
lost101 said:
In the fastboot log you provided, the sparsechunks are incorrectly named.
Click to expand...
Click to collapse
Yeah that was due to the fastboot commands I copy/pasted, for them to work I needed to change their names. Did I do wrong?
Ahasverus said:
Yeah that was due to the fastboot commands I copy/pasted, for them to work I needed to change their names. Did I do wrong?
Click to expand...
Click to collapse
I just wanted to make sure. I do not believe the issues are related to the ROM change you mention doing a month ago. Over time, a certain percentage of Moto Gs experience corruption / failure that require a new mainboard - even if they are never dropped or get wet. The only other thing I can suggest you try is via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
lost101 said:
I just wanted to make sure. I do not believe the issues are related to the ROM change you mention doing a month ago. Over time, a certain percentage of Moto Gs experience corruption / failure that require a new mainboard - even if they are never dropped or get wet. The only other thing I can suggest you try is via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
Click to expand...
Click to collapse
Oh, I see Well, this puts me a little wary of buying a MotoG 2015 as replacement. Will try the adb thing, thank you very much.
Ahasverus said:
Oh, I see Well, this puts me a little wary of buying a MotoG 2015 as replacement. Will try the adb thing, thank you very much.
Click to expand...
Click to collapse
Perhaps I should clarify; a certain percentage of any phone (from any manufacturer) as old as Moto G Falcon / Peregrine will fail. The phones were manufactured in 2013/2014. I still have more confidence in Motorola handsets than the alternatives in the same price range.
lost101 said:
Perhaps I should clarify; a certain percentage of any phone (from any manufacturer) as old as Moto G Falcon / Peregrine will fail. The phones were manufactured in 2013/2014. I still have more confidence in Motorola handsets than the alternatives in the same price range.
Click to expand...
Click to collapse
I see. I did the adb command formatting and it kept the same. Well, off to repair it goes. I wonder if you have an idea such I can tell the technician where to look at? Thank you so much for your help!
Ahasverus said:
I see. I did the adb command formatting and it kept the same. Well, off to repair it goes. I wonder if you have an idea such I can tell the technician where to look at? Thank you so much for your help!
Click to expand...
Click to collapse
I suspect you will be told the mainboard needs to be replaced - at pretty much the cost of a new phone. The cheapest fix would be to find a used, but functional Peregrine handset with broken screen on ebay and have the mainboard transplanted by someone who knows what they are doing.
Hi All! Just so you know, something REALLY WEIRD happened.
My phone kept locking as usual, it became ever more frequent to the point it was unusable. As a final measure I flashed the lastest brazil optimized stock rom because I thought "Well, if I'm getting it repaired, better have it on the best ROM and start anew". Then something weird happened, just as the ROM flashed and it turned into the very first "Welcome" screen, the phone froze in black, to never return. No hard reset, no corrupted fastboot screen, nothing. There I thought "Yep, it's done".
I waited for like 4 hours (was really busy) and after trying to turn it on again, I decided maybe it had no battery charge, so I plugged it in on my wall charger and then, oh god, some kind of whistling sound came from inside the phone. I could just thought "Yep it's going to explode", I was sure smoke was about to come out of the phone.. but it didn't. The sound eventually died out and then the notification LED turned on. No screen however, but the LED was permanently on.
I went to sleep with my dead phone in that state. Then after a night I woke up and went to check it, and I found.. the phone turned on, working normally. Of course I thought it was just a temporal thing but, well, it's been 3 days of normal use and it hasn't turned off, or froze, or anything. It's... fine.
It sounds like magic or voodoo, I have no idea what I did, if it's fixed or it's going to die again soon. But I thought it would be good to write this as a final post, as maybe someone will experience the same in the future and would like to have some hope, if only because he may need to backup his data.
So, what I /think/ did was
- Use TWRP Recovery and do a complete wipe of everything, even in advanced setting, just everything.
- Reboot to recovery
- Use the TWRP console command to manually insert the wiping commands lost101 suggested me as "last resort"
- Flash the lastest Brazil Optimized ROM as suggested by lost101
- ??? (Probably dry its battery to the lowest possible? like, when not even the screens turns on)
- ??? (Let it charging overnight or more, use a high voltage charger -I used Blackberry's-)
- Success.
Thank you very much lost101! And well, if you had an explanation for this weird behavior it would be much appreciated. Thanks!
Related
Dear Team Members
Good day to all
Hope this thread will find all the members in good health and in high spirits.
This is my first post and i need all your support since i am totally in bad shape for the past five days browsing this XDA developers for some answers and I tried all but no hope.
First and foremost thing my MOTOG got bricked by myself and I am stuck with SD cant mount I tried all the ways posted in XDA developers. I can install TWRP & CWM and can install any ROM, problem ???? is I am stuck with the logo of cyanogenmod logo after that it stops.
Once entered, but no access to Wifi, no network, nothing
Problem:
SD cant mount, I tried all the ways but unsuccessful
secondly sd card partition is corrupted i guess
I cant see the sd card option in Computer so i can have access inside the SD card
Battery dropped sometimes to 0 %
Nutshell - My phone is royally messed up
Note:
Needing all the team members substantiate support to make alive my new MOTO G.
Awaiting for your reply and support.
Cheers
Prasad Gangadharan
Just reflash the stock firmware! No need to be scared !
---------------------------------------------------------
Hit the thanks button if I helped you 8)
---------------------------------------------------------
pfufle said:
Just reflash the stock firmware! No need to be scared !
---------------------------------------------------------
Hit the thanks button if I helped you 8)
---------------------------------------------------------
Click to expand...
Click to collapse
Hello Sir
I did all that what is mentioned in my forum, i even erase the phone and tried as per one of the senior member but that also failed, as i said in my forum it cant mound the SD Card. i guess that's the problem. I tired all possible ways in the forum mentioned but i am still helpless. If someone cant tell the process one by one then i can do something. But to be more precise i did all that said in forum, all failed.
I don't see that you have written that you have reflashed the stock firmware
---------------------------------------------------------
Hit the thanks button if I helped you 8)
---------------------------------------------------------
prasadgangadharan said:
Hello Sir
I did all that what is mentioned in my forum, i even erase the phone and tried as per one of the senior member but that also failed, as i said in my forum it cant mound the SD Card. i guess that's the problem. I tired all possible ways in the forum mentioned but i am still helpless. If someone cant tell the process one by one then i can do something. But to be more precise i did all that said in forum, all failed.
Click to expand...
Click to collapse
I did the reflash stock firmware also but that also havent helped, i bought the phone one weeks back. i bricked it thats the biggest mistake i had done and i am suffering a lot on this.
Please help help me
Assuming that it is the xt1033 version, reflash the stock Asian firmware again, flash the LATEST version if the philz recovery, and then just do a factory reset to clean install a new ROM(that option will be there in philz recovery in the data wipe option), then flash the latest nightly of cm11 and you should be good...
---------------------------------------------------------
Hit the thanks button if I helped you 8)
---------------------------------------------------------
pfufle said:
Assuming that it is the xt1033 version, reflash the stock Asian firmware again, flash the LATEST version if the philz recovery, and then just do a factory reset to clean install a new ROM(that option will be there in philz recovery in the data wipe option), then flash the latest nightly of cm11 and you should be good...
---------------------------------------------------------
Hit the thanks button if I helped you 8)
---------------------------------------------------------
Click to expand...
Click to collapse
Dear Boss,
Good day
Sir, as per your instructions, i did the same but haven't flashed, but side loaded using ADB mode. ( first wiped - then stock asian firmware, then CM11). I am thankful to the same:good::good::good::good:, now the problem is wifi working - both the sim's are disabled , when i was in stock firmware there was some update i updated it now, it keep switch off automatically and then again going to Philz on it own..?????
Sir, is there any possibilities to give an exact zip file of stock firmware- where both the SIM's shall be working and WIFI.
Kindly do accept my sincere thanks for helping me to get back the phone alive, but Both the SIM's not working only wifi working
Awaiting your substantiate support on the above concern.
regards
Prasad
prasadgangadharan said:
Dear Boss,
Good day
Sir, as per your instructions, i did the same but haven't flashed, but side loaded using ADB mode. ( first wiped - then stock asian firmware, then CM11). I am thankful to the same:good::good::good::good:, now the problem is wifi working - both the sim's are disabled , when i was in stock firmware there was some update i updated it now, it keep switch off automatically and then again going to Philz on it own..?????
Sir, is there any possibilities to give an exact zip file of stock firmware- where both the SIM's shall be working and WIFI.
Kindly do accept my sincere thanks for helping me to get back the phone alive, but Both the SIM's not working only wifi working
Awaiting your substantiate support on the above concern.
regards
Prasad
Click to expand...
Click to collapse
Dear Sir,
In the stock firmware Both the SIM's disabled -when i try to enable it keeps going to OFF mode.
In the CM11 - it says NO service for the both the SIM's
What would be the solution, i tried both the SIM's in another local phone both are working prefectly - just to reconfirm myself is there is anything wrong with the SIM
Needing you sincere advice and solution.
Prasad
prasadgangadharan said:
Dear Boss,
Good day
Sir, as per your instructions, i did the same but haven't flashed, but side loaded using ADB mode. ( first wiped - then stock asian firmware, then CM11). I am thankful to the same:good::good::good::good:, now the problem is wifi working - both the sim's are disabled , when i was in stock firmware there was some update i updated it now, it keep switch off automatically and then again going to Philz on it own..?????
Sir, is there any possibilities to give an exact zip file of stock firmware- where both the SIM's shall be working and WIFI.
Kindly do accept my sincere thanks for helping me to get back the phone alive, but Both the SIM's not working only wifi working
Awaiting your substantiate support on the above concern.
regards
Prasad
Click to expand...
Click to collapse
Do not use the firmware zip...Download the Asia retail firmware for xt1033 and then flash it using fastboot...There is a detailed guide on this procedure in the troubleshooting section...After that you will get network and your phone will work perfectly...If you had ever updated you phone via OTA to 4.4.4 then flash the 4.4.4 stock firmware or flash the 4.4.2 firmware if you were had never updated stock to 4.4.4...here is a link to that guide...
http://forum.xda-developers.com/showthread.php?t=2542219
---------------------------------------------------------
Hit the thanks button if I helped you 8)
---------------------------------------------------------
pfufle said:
Do not use the firmware zip...Download the Asia retail firmware for xt1033 and then flash it using fastboot...There is a detailed guide on this procedure in the troubleshooting section...After that you will get network and your phone will work perfectly...
---------------------------------------------------------
Hit the thanks button if I helped you 8)
---------------------------------------------------------
Click to expand...
Click to collapse
Dear Sir
Good day
Apologies, as i was not aware of the same, is it possible to give me the exact rom for dual SIM and please do advice is it the same way to do as mentioned in your previous reply.
Awaiting your advice.
prasadgangadharan said:
Dear Sir
Good day
Apologies, as i was not aware of the same, is it possible to give me the exact rom for dual SIM and please do advice is it the same way to do as mentioned in your previous reply.
Awaiting your advice.
Click to expand...
Click to collapse
Dear Boss
Good day
Accept my apologies in bothering you for all small things, please do guide me, I saw most of the forums and I am not able to choose which is the right Asian Rom and i stuck in that, my humble request to bare with all my nonsense and stupid questions.
Hoping you will guide as required.
Dear Boss
As you said i download (fastboot_falcon_asia_ds_user_4.3_14.10.0Q3.X-84-7-LCG-4_4_release-keys-cid7-AsiaRetail_03.tar) - unzipped the file. typed - fastboot flash flashall.dat/eu it says wrong partition, on the screen it says ( version downgraded for primary_gpt). Needing your advice.
Any advice boss
prasadgangadharan said:
Dear Boss
Good day
Accept my apologies in bothering you for all small things, please do guide me, I saw most of the forums and I am not able to choose which is the right Asian Rom and i stuck in that, my humble request to bare with all my nonsense and stupid questions.
Hoping you will guide as required.
Dear Boss
As you said i download (fastboot_falcon_asia_ds_user_4.3_14.10.0Q3.X-84-7-LCG-4_4_release-keys-cid7-AsiaRetail_03.tar) - unzipped the file. typed - fastboot flash flashall.dat/eu it says wrong partition, on the screen it says ( version downgraded for primary_gpt). Needing your advice.
Any advice boss
Click to expand...
Click to collapse
Do not use the flash all command... Manually put all the commands...It will work...
---------------------------------------------------------
Hit the thanks button if I helped you 8)
---------------------------------------------------------
pfufle said:
Do not use the flash all command... Manually put all the commands...It will work...
---------------------------------------------------------
Hit the thanks button if I helped you 8)
---------------------------------------------------------
Click to expand...
Click to collapse
Dear Boss
Good day
Kindly find below are the message i got as per your instruction.
Brand: Moto G ; SIM: Dual Sim : Model No: XT1033
Version used: RETAIL-AS_FALCON_KXB20.25-1.31_cid7_CFC_1FF
Below are the feedback's i got on the fast boot screen: - FYI
Note: Now i stuck with boot loader back as i was saying in the my first message - Its been weeks its the same things i been explaining to all. Nothing is getting materialized.
mfastboot getvar max-sparse-size
mfastboot oem fb_mode_set
mfastboot flash aboot emmc_appsboot.mbn - prevalidation failed
mfastboot reboot-bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img - ( (bootloader) Motoboot: Preflash validation for tz ; (bootloader) Preflash validation failed) - failed
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0 - Image file is big
mfastboot flash system system.img_sparsechunk.1 - Image file is big
mfastboot flash system system.img_sparsechunk.2 -- Image file is big
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot oem fb_mode_clear
mfastboot reboot-bootloader
C:\Users\prasadg\Downloads\Compressed\Retail Falcon>mfastboot devices
TA89900OG4 fastboot
C:\Users\prasadg\Downloads\Compressed\Retail Falcon>mfastboot getvar max-sparse-
size
max-sparse-size: 268435456
finished. total time: 0.003s
C:\Users\prasadg\Downloads\Compressed\Retail Falcon>mfastboot oem fb_mode_set
...
OKAY [ 0.009s]
finished. total time: 0.010s
C:\Users\prasadg\Downloads\Compressed\Retail Falcon>mfastboot flash aboot emmc_a
ppsboot.mbn
target max-sparse-size: 256MB
sending 'aboot' (512 KB)...
OKAY [ 0.102s]
writing 'aboot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.411s
C:\Users\prasadg\Downloads\Compressed\Retail Falcon>mfastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
C:\Users\prasadg\Downloads\Compressed\Retail Falcon>mfastboot flash partition gp
t.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.370s]
finished. total time: 0.405s
C:\Users\prasadg\Downloads\Compressed\Retail Falcon>mfastboot flash motoboot mot
oboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1940 KB)...
OKAY [ 0.090s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.394s
C:\Users\prasadg\Downloads\Compressed\Retail Falcon>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (619 KB)...
OKAY [ 0.073s]
writing 'logo'...
OKAY [ 0.126s]
finished. total time: 0.203s
C:\Users\prasadg\Downloads\Compressed\Retail Falcon>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.361s]
writing 'boot'...
OKAY [ 1.049s]
finished. total time: 1.415s
C:\Users\prasadg\Downloads\Compressed\Retail Falcon>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.368s]
writing 'recovery'...
OKAY [ 1.024s]
finished. total time: 1.395s
C:\Users\prasadg\Downloads\Compressed\Retail Falcon>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (262142 KB)...
OKAY [ 8.244s]
writing 'system'...
OKAY [ 13.130s]
finished. total time: 21.378s
C:\Users\prasadg\Downloads\Compressed\Retail Falcon>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (237949 KB)...
OKAY [ 7.484s]
writing 'system'...
OKAY [ 11.699s]
finished. total time: 19.186s
C:\Users\prasadg\Downloads\Compressed\Retail Falcon>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (243326 KB)...
OKAY [ 7.654s]
writing 'system'...
OKAY [ 12.011s]
finished. total time: 19.669s
C:\Users\prasadg\Downloads\Compressed\Retail Falcon>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (47476 KB)...
OKAY [ 1.535s]
writing 'modem'...
OKAY [ 2.404s]
finished. total time: 3.943s
C:\Users\prasadg\Downloads\Compressed\Retail Falcon>mfastboot erase modemst1erasing 'modemst1'...
OKAY [ 0.026s]
finished. total time: 0.028s
C:\Users\prasadg\Downloads\Compressed\Retail Falcon>mfastboot erase modemst2erasing 'modemst2'...
OKAY [ 0.026s]
finished. total time: 0.027s
C:\Users\prasadg\Downloads\Compressed\Retail Falcon>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.089s]
writing 'fsg'...
OKAY [ 5.301s]
finished. total time: 5.395s
C:\Users\prasadg\Downloads\Compressed\Retail Falcon>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.042s]
finished. total time: 0.045s
C:\Users\prasadg\Downloads\Compressed\Retail Falcon>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.407s]
finished. total time: 0.409s
C:\Users\prasadg\Downloads\Compressed\Retail Falcon>mfastboot oem fb_mode_clear
...
OKAY [ 0.008s]
finished. total time: 0.010s
C:\Users\prasadg\Downloads\Compressed\Retail Falcon>mfastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
STUCKED WITH BOOT LOADER, THEN WITH GREEN ANDRIOD ICON WITH RED TRIANGLE ON HIS HEART.
Kindly do advice what more i should do ( i tried all possible ways to get back my phone, but i guess it not working out - I would give one last short after you reply this mail, if not take a hammer and smash into pieces and throw it dustbin.) that's all i can do. Its been a week i am been having sleepless night to find some solution to the problem.
Good day
Prasad
http://forum.xda-developers.com/showthread.php?t=2542219
This is a very detailed guide to restore the stock firmware...Just do exactly what it says and you should be done...
---------------------------------------------------------
Hit the thanks button if I helped you 8)
---------------------------------------------------------
Retail Asia 4.4.4 Firmware Image:
http://forum.xda-developers.com/showpost.php?p=54487261&postcount=332
I have somehow totally trashed my Android install. I have a UK retail Moto G XT1032.
While downloading the OTA lollipop update, the download appeared to stall. I decided to give up on the update, so I switched the phone off. When I turned it back on again, every single process crashed. "Unfortunately dialler/android.process.acore/Calendar/android.process.media/etc has stopped". I can keep tapping "OK" for ever to clear these notifications, but can't actually use the phone for anything at all.
So I decided to do a factory reset from fastboot. It made no difference.
I tried a factory reset from recovery. It made no difference.
Using fastboot, I attempted to install the stock ROM according to the guide at http://forum.xda-developers.com/showthread.php?t=2542219. Everything seemed to flash OK - I got OKAY on the PC and the commands appeared to be running on the phone OK, but when it restarted, the phone was exactly the same - my wallpaper photo was still there, and the app icons that I could glimpse behind the endless notifications were my apps.
I tried several more times, this time flashing the 4.4.4 ROM (RETAIL-GB_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF). Exactly the same results - nothing changes when I restart.
It's as if the mfastboot flash commands do nothing at all! I have run all the mfastboot commands described by the guide in the order given.
I've also tried booting to recovery and connecting to ADB, but the PC cannot see the device.
I've tried replacing the recovery with CWM and TWRP .img files, but the flash command, while seeming to work, doesn't change anything at all! The recovery that I have installed is the standard KXB21.14-L1.40.
I have tried "mfastboot.exe erase recovery", before attempting to update the recovery, but it makes no difference.
Does anybody have any idea what I am doing wrong? It seems that no "mfastboot flash xxx yyy" command works at all on my phone.
Did you installfastboot or mfastboot? ADB commands only work if the is booted and USB debugging is on.
Got the same problem. I've already posted this in a few threads and didn't get any answer, though
Sounds crazy but, when you type fastboot devices with your phone connected in fastboot mode, does the command return your phone's serial #?
Yes, everything via fastboot works (says complete, done etc.) except it doesn't affect the real system. If you sideload ADB you will see that the system, data and cache partition become read-only. I've managed to remount only data partition with write privileges, but that doesn't help.
Are you flashing each partition manually? You can see your device's serial # in fastboot?
audit13 said:
Did you install fastboot or mfastboot? ADB commands only work if the is booted and USB debugging is on.
Click to expand...
Click to collapse
Originally, I used the version of fastboot that came with the first stock ROM I tried (falcon_retgb_user_4.3_14.10.0Q3.X-76-LGG-8_54_release-keys-cid7-Retail_GB).
Later on, I installed mfastboot and used that instead. The results were the same. Nothing seems to actually be flashed, but there are no errors on either the PC or the phone.
ADB does not work in fastboot (I don't believe it's supposed to!), but it also will not work with the version of recovery that I have, which is why I was attempting to install CWM and TWRP in its place.
audit13 said:
Are you flashing each partition manually? You can see your device's serial # in fastboot?
Click to expand...
Click to collapse
Yes. I'm currently trying the following sequence with the XT1032_RETAIL-GB_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml ROM...
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
The mfastboot command returns OKAY for each of these, and a couple of yellow lines appear on the phone for each command, indicating that the right command is running, with no error messages.
I have never used mfastboot. Maybe try using fastboot to flash? I have used fastboot on my Moto G and Moto Atrix HD with great success.
Tried with fastboot, tried with mfastboot, got no errors but nothing changes. The real problem I suppose is corrupted partitions.
Have you tried the moto flash tool??
http://forum.xda-developers.com/showthread.php?t=2934358
@IcyBee, I see you're flashing the GB retail. Is it possible to try a different ROM such as the GPE?
dog121 said:
Have you tried the moto flash tool??
http://forum.xda-developers.com/showthread.php?t=2934358
Click to expand...
Click to collapse
I've just given it a go.
When flashing the ROMs, it basically runs the same mfastboot commands that I was running before, so the result was exactly the same.
However, the ADB Driver install button was worth trying. The driver supplied has enabled my PC to communicate with the phone using ADB when in recovery mode!
Unfortunately, after selecting "apply update from ADB" on the phone, and running "adb sideload <ROM zip file>", it sends it to the phone (taking a couple of minutes), and the phone says "Verifying update package", followed by "Installation aborted".
When you sideload, do you need some sort of special format ROM file?
audit13 said:
@IcyBee, I see you're flashing the GB retail. Is it possible to try a different ROM such as the GPE?
Click to expand...
Click to collapse
I was hoping to use the stock ROM, just to get the phone back to its original state.
If the mfastboot command does nothing, I doubt trying different ROMs will help. But I'll probably try it if I can't get anything else to work.
thanks a lot!
@IcyBee - I have seen this before. Try using fastboot on a Linux PC / Laptop. You can use a live cd to do this - no need to actually install Linux.
sudo apt-get install android-tools-adb android-tools-fastboot
lost101 said:
@IcyBee - I have seen this before. Try using fastboot on a Linux PC / Laptop. You can use a live cd to do this - no need to actually install Linux.
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
Thanks for the idea. I happen to have a laptop running the latest Lubuntu.
I installed fastboot as you directed and re-flashed everything. Exactly the same. The commands all say OKAY, the yellow text on the phone says it's running the commands, but when I reboot - everything is exactly as it was before - including my wallpaper photo and app icons. And every single process on the phone is crashing.
I do not believe fastboot is actually working on this phone. The only commands that seem to work are the ones to unlock the bootloader and the one to reboot the phone.
@IcyBee - does the fastboot commands for flashing the system.img files actually match the files in the firmware folder?
I.e first file is sparsechunk.0 not sparsechunk1
EDIT: Next I would try the only available XT1032 factory firmware image: http://forum.xda-developers.com/showthread.php?p=58534609
It's retail Brazil, but will work anywhere in the world.
I suggest you skip flashing the bootloader - motoboot.img
lost101 said:
@IcyBee - does the fastboot commands for flashing the system.img files actually match the files in the firmware folder?
Click to expand...
Click to collapse
Yup.
Next I would try the only available XT1032 factory firmware image: http://forum.xda-developers.com/showthread.php?p=58534609
Click to expand...
Click to collapse
OK - I downloaded this and flashed it. Exactly the same as all the previous attempts. It appears to work, but when I restart, the phone is in exactly the same state as before, as if no flashing has happened.
Here is the command line output:
Code:
C:\>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.024s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.353s]
finished. total time: 0.380s
C:\>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.084s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.110s]
finished. total time: 1.197s
C:\>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.040s]
writing 'logo'...
OKAY [ 0.060s]
finished. total time: 0.105s
C:\>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.360s]
writing 'boot'...
OKAY [ 0.670s]
finished. total time: 1.030s
C:\>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.360s]
writing 'recovery'...
OKAY [ 0.695s]
finished. total time: 1.060s
C:\>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257883 KB)...
OKAY [ 8.140s]
writing 'system'...
OKAY [ 8.155s]
finished. total time: 16.295s
C:\>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256754 KB)...
OKAY [ 8.185s]
writing 'system'...
OKAY [ 8.690s]
finished. total time: 16.885s
C:\>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260090 KB)...
OKAY [ 8.265s]
writing 'system'...
OKAY [ 8.755s]
finished. total time: 121.145s
C:\>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (165316 KB)...
OKAY [ 5.255s]
writing 'system'...
OKAY [ 6.475s]
finished. total time: 11.735s
C:\>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.605s]
writing 'modem'...
OKAY [ 0.825s]
finished. total time: 2.435s
C:\>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.015s]
finished. total time: 0.020s
C:\>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.015s]
finished. total time: 0.015s
C:\>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.070s]
writing 'fsg'...
OKAY [ 3.180s]
finished. total time: 3.250s
C:\>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.020s]
finished. total time: 0.020s
C:\>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.025s]
finished. total time: 0.025s
C:\>mfastboot reboot
rebooting...
finished. total time: 0.005s
Attached is a very blurry picture taken in poor light with my very old spare phone of the Moto G just before boot. All commands seemed OK, except for recovery.img and motoboot.img, which displayed "hab check error" in pink (not pictured).
Thanks again to all of you for your assistance in this matter.
IcyBee said:
Attached is a very blurry picture taken in poor light with my very old spare phone of the Moto G just before boot. All commands seemed OK, except for recovery.img and motoboot.img, which displayed "hab check error" in pink (not pictured).
Click to expand...
Click to collapse
Recovery mode ADB will work in Linux. You could try side-loading the 5.0.2 OTA Update.
I have a Moto G (XT1032) running Android 5.0.2 that went out of charge one day. It then decided to boot into a black screen - i.e. I can see the Motorola splash screen (animation) but all I get after that is a black (grey) screen, not responsive to touch.
I tried a few things and they didn't work -
Fastbooted and selected 'Recovery' option - The Motorola logo (first screen of startup splash screen) appears briefly. Then the device returns to fastboot menu saying 'Boot Up failed'
Fastbooted and selected 'Factory' - The Motorola splash screen appears, boots into same black (grey) screen again.
The fastboot menu says "Device is LOCKED. Status Code: 0". I did not enable USB debugging before my phone stopped working.
How do I get my phone working again?
You do not need an unlocked Bootloader to flash one of the factory firmware images: (I suggest using only one of the 5.0.2 images)
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Is there important data on the phone? Then do not use the command: mfastboot erase userdata
lost101 said:
You do not need an unlocked Bootloader to flash one of the factory firmware images: (I suggest using only one of the 5.0.2 images)
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Is there important data on the phone? Then do not use the command: mfastboot erase userdata
Click to expand...
Click to collapse
i do it, and nothing happend, just the black screen at the end of boot animation, also i unlock the bootloader and try to install a recovery (i try cwm, twrp and philz), but when i enter into recovery, only shows a android robot and says "No Command".
Joncillo said:
i do it, and nothing happend, just the black screen at the end of boot animation, also i unlock the bootloader and try to install a recovery (i try cwm, twrp and philz), but when i enter into recovery, only shows a android robot and says "No Command".
Click to expand...
Click to collapse
Please provide a log from mfastboot of those commands being performed. Make sure to actually use mfastboot.
https://www.androidfilehost.com/?fid=23578570567719065
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash partition gpt.b
in
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.084s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.330s]
finished. total time: 0.418s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash motoboot motobo
ot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.151s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.957s]
finished. total time: 1.112s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.095s]
writing 'logo'...
OKAY [ 0.035s]
finished. total time: 0.132s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.447s]
writing 'boot'...
OKAY [ 0.599s]
finished. total time: 1.049s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash recovery recove
ry.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.446s]
writing 'recovery'...
OKAY [ 0.599s]
finished. total time: 1.049s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257883 KB)...
OKAY [ 9.591s]
writing 'system'...
OKAY [ 7.728s]
finished. total time: 17.323s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256754 KB)...
OKAY [ 8.955s]
writing 'system'...
OKAY [ 8.082s]
finished. total time: 17.042s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260090 KB)...
OKAY [ 9.657s]
writing 'system'...
OKAY [ 8.179s]
finished. total time: 17.843s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (165316 KB)...
OKAY [ 6.347s]
writing 'system'...
OKAY [ 6.282s]
finished. total time: 12.635s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash modem NON-HLOS.
bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.943s]
writing 'modem'...
OKAY [ 0.780s]
finished. total time: 2.727s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.015s]
finished. total time: 0.022s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.012s]
finished. total time: 0.013s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.090s]
writing 'fsg'...
OKAY [ 3.185s]
finished. total time: 3.279s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.017s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.020s]
finished. total time: 0.021s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot reboot
Click to expand...
Click to collapse
Thats all that i got... i don't know what else to do...
Joncillo said:
i do it, and nothing happend, just the black screen at the end of boot animation, also i unlock the bootloader and try to install a recovery (i try cwm, twrp and philz), but when i enter into recovery, only shows a android robot and says "No Command".
Click to expand...
Click to collapse
At this stage you should press power button for few seconds and tap vol +, it is the way to enter recovery in lollippp, correct me if I am wrong.
Sent from my XT1033 using Tapatalk 2
pradeeppk said:
At this stage you should press power button for few seconds and tap vol +, it is the way to enter recovery in lollippp, correct me if I am wrong.
Sent from my XT1033 using Tapatalk 2
Click to expand...
Click to collapse
i do it, but i get the same message, "No Command"
lost101 said:
Please provide a log from mfastboot of those commands being performed. Make sure to actually use mfastboot.
Click to expand...
Click to collapse
I see something wierd now, looks like the memory of the phone dosent save anything... sometimes, when the boot animation stops, i see the message of "1 of 1 Updates, android its updating" and then go to the black screen again... but, if i flash the phone, i shouldn't see that message, rigth? so, why i can still see it? how can i erase all the memory for sure???
Try flashing TWRP: https://www.androidfilehost.com/?fid=24052804347764184
Command: mfastboot flash recovery twrp-2.8.7.0.-falcon_STOCK.img - enter recovery afterwards.
If that fails to flash, try: mfastboot boot twrp-2.8.7.0.-falcon_STOCK.img
lost101 said:
Try flashing TWRP: https://www.androidfilehost.com/?fid=24052804347764184
Command: mfastboot flash recovery twrp-2.8.7.0.-falcon_STOCK.img - enter recovery afterwards.
If that fails to flash, try: mfastboot boot twrp-2.8.7.0.-falcon_STOCK.img
Click to expand...
Click to collapse
flash recovery dosen't work, but with boot yes! now i'm on TWRP! so, what next?? tell me what to do, i don't wanna screw it!!! jajaja
Joncillo said:
flash recovery dosen't work, but with boot yes! now i'm on TWRP! so, what next?? tell me what to do, i don't wanna screw it!!! jajaja
Click to expand...
Click to collapse
Do you have anything you need to backup from the phone? Do you have ADB installed?
ADB Installer: http://forum.xda-developers.com/showthread.php?t=2588979
Backup command: ADB pull /sdcard c:/motog_backup/
lost101 said:
Do you have anything you need to backup from the phone? Do you have ADB installed?
ADB Installer: http://forum.xda-developers.com/showthread.php?t=2588979
Backup command: ADB pull /sdcard c:/motog_backup/
Click to expand...
Click to collapse
Done, i backup all that i need... so, what next??? wipe? or i try to install 5.0.2 again but as zip?
Joncillo said:
Done, i backup all that i need... so, what next??? wipe? or i try to install 5.0.2 again but as zip?
Click to expand...
Click to collapse
Wipe > Format Data. Wipe > Factory reset. ADB push or sideload ROM.zip
lost101 said:
Wipe > Format Data. Wipe > Factory reset. ADB push or sideload ROM.zip
Click to expand...
Click to collapse
when i wipe the device, i get some errors.
E: MTP already enable
Formatting data using mkfs.f2fs...
Done
E: Unknown MTP message type 1:
You may need to reboot recovery to be able to use /data again.
Updating partition details...
E: Unable to stat '/data/data/com.google.android.gms/app_sslcache/www.googleapis.com.443'
E: Unable to stat '/data/data/com.google.android.calendar/databases/timelydata.db-shm'
...done
but don't wipe anything...
i try ADB Sideload but get an error too.
Starting ADB sideload feature... (After 10 minutes)
FAILED ADB Sideload complete.
and the CMD on windows says "Error: device not found"
also i try to install TWRP as zip, but when i restarted, enter into recovery and then i have the same android with error "No Command".
@Joncillo - See the last post in this thread: http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492 - you are both in the same situation I believe.
It's a known issue; where battery is allowed to die and has resulted in Bootloader / Partition corruption.
Try what I have suggested there - if that does not solve it, you may have to wait for a working Lollipop hardbrick solution, which would allow you to repair the Bootloader: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
lost101 said:
@Joncillo - See the last post in this thread: http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492 - you are both in the same situation I believe.
It's a known issue; where battery is allowed to die and has resulted in Bootloader / Partition corruption.
Try what I have suggested there - if that does not solve it, you may have to wait for a working Lollipop hardbrick solution, which would allow you to repair the Bootloader: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Click to expand...
Click to collapse
ahhhhhhhhh... i see... so, i have a dead phone... well, i'm going to try what you said in that post, thanks for all your help!!!
The reason I ask is that mine is still buggered.
I had an xt1039 originally, drove over it in a 44 tonner and broke the digitiser. 2 new screens later and neither worked.
Bit the bullet and bought a used xt1039 one off eBay. Tesco version, already unlocked, but it was already upgraded to 5.02. Soft bricked it trying to restore to stock 4.3, sorted that by reinstalling stock 4.4.4, downgraded that to 4.4.3 but couldn't find a 4.4.2 Rom before I tried 4.3 again. Flashed different fsg and HLOS-NON files clearing the two modem files each time but to no avail. I have hunted high and low trying to get to the bottom of this reading through various threads on here, and I found theories along the lines of it only happens to those with O2 or Vodafone Sims or those networks who piggyback on them.
I did find a useful snippet that if I selected 2g I would at least get a stable phone signal which has worked fixing that, but I am on talktalk mobile(Vodafone) paying for 4 gig internet every month but ATM not using anywhere near that obviously. Vodafone's 3g coverage of the motorway network sucks anyway but something is better than nothing.
Before I give up and rip the motherboard out of my old one, is there any definitive to fix this? I am quite happy to supply any required information and answer any questions, and obviously any assistance would be greatly appreciated.
Ta muchly.
Lennie
Sent from my Hudl 2 using Tapatalk
Trying to find out which exact model I had, just though maybe it wasn't an xt1039, but in the regulatory information it says xt1039 but the information is for india! How does this relate to the UK? Do all of them say SAR information for India or is this country specific?
Just trying to find a way forward peeps.
Cheers
Lennie
Sent from my Hudl 2 using Tapatalk
If I install cyanogenmod and cwm or twrp will this cure the problem?
Sent from my Hudl 2 using Tapatalk
XT1039 is the model sold in UK / EU. What does: Settings > About phone say?
lost101 said:
XT1039 is the model sold in UK / EU. What does: Settings > About phone say?
Click to expand...
Click to collapse
Model Number: Moto G
Android Version: 5.1
Baseband Version: M8926_309101.02.03.14r TESCOGB_CUST
Kernel Version: 3.4.42-geb8cd52e-00003-g52c4c71 [email protected] #1 Mon May 11 05:31:09 CDT 2015
System Version: 23.21.17.peregrine_tescogb.tescogball.en.GB tescogb
Build Number: LPB23.13-17
I had just tried flashing a 5.1 Tesco Rom to see if it worked, but it is just doing the same. Was originally trying to get 4.3 Tesco rom for the 4g, but I am not sure what the LTE version on Tesco was originally released on, 4.3 or 4.4.x.
Thanks for the reply
Lennie
With Moto G Falcon - Motorola made it impossible to boot 4.3, after upgrading to KitKat. It's probably the same case here. I would be careful with the file: motoboot.img (Bootloader) - it's unnecessary and dangerous to repeatedly flash it.
Provide a fastboot log of what happens when you try to flash the 5.1 Firmware Image. You can flash either Tesco or Retail GB from here:
http://forum.xda-developers.com/showpost.php?p=60793911&postcount=2
lost101 said:
With Moto G Falcon - Motorola made it impossible to boot 4.3. It's probably the same case here. I would be careful with the file: motoboot.img (Bootloader) - it's unnecessary and dangerous to repeatedly flash it.
Provide a fastboot log of what happens when you try to flash the 5.1 Firmware Image. You can flash either Tesco or Retail GB from here:
http://forum.xda-developers.com/showpost.php?p=60793911&postcount=2
Click to expand...
Click to collapse
Hi lost101
This is the firmware I just tried this morning, took two full flashes and a force shutdown before it booted properly. First time it got stuck and fell into dead android screen for recovery. Rebooted into bootloader again and reflashed, then it booted past the changing planet pic to the blue M, then hung there. Forced restart and it booted to optimizing apps and started fine. Turned it off, then restarted and deleted all the apns, installed the one I got in a text from Talktalk, selected network, and restarted again. Unfortunately, unless I select 2g in the preferred network types, it just keeps dropping signal.
Should I try the retail version rather than the Tesco Version?
Cheers
Lennie
Show me a fastboot log. The tool is in no way user-friendly - it can fail to flash completely, yet still appear as if everything was an amazing success.
lost101 said:
Show me a fastboot log. The tool is in no way user-friendly - it can fail to flash completely, yet still appear as if everything was an amazing success.
Click to expand...
Click to collapse
By Fastboot Log, do you want me to reflash and post the results that show in the command prompt, or what appears on the phone, or am I getting mixed up?
Thanks
Lennie
Jalipero said:
By Fastboot Log, do you want me to reflash and post the results that show in the command prompt, or what appears on the phone, or am I getting mixed up?
Click to expand...
Click to collapse
Yes, reflash the firmware image files. Do the commands manually, one at a time. Copy and paste the entire process into a post here. Try to skip flashing motoboot.img.
lost101 said:
Yes, reflash the firmware image files. Do the commands manually, one at a time. Copy and paste the entire process into a post here. Try to skip flashing motoboot.img.
Click to expand...
Click to collapse
OK Will do, I will skip the partition and the motoboot and start at logo. Both these files flashed fine allegedly, but I will go through the rest again and post them up.
Thanks
Lennie
Hi lost101
I have listed below the log as requested:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
F:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.047s]
writing 'logo'...
OKAY [ 0.078s]
finished. total time: 0.125s
F:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.361s]
writing 'boot'...
OKAY [ 0.780s]
finished. total time: 1.141s
F:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash recovery recover
y.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.374s]
writing 'recovery'...
OKAY [ 0.811s]
finished. total time: 1.186s
F:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257455 KB)...
OKAY [ 8.416s]
writing 'system'...
OKAY [ 12.951s]
finished. total time: 21.367s
F:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (257669 KB)...
OKAY [ 8.426s]
writing 'system'...
OKAY [ 12.008s]
finished. total time: 20.434s
F:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (261644 KB)...
OKAY [ 8.534s]
writing 'system'...
OKAY [ 17.718s]
finished. total time: 26.252s
F:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (189917 KB)...
OKAY [ 6.336s]
writing 'system'...
OKAY [ 10.529s]
finished. total time: 16.864s
F:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash modem NON-HLOS.b
in
target max-sparse-size: 256MB
sending 'modem' (60232 KB)...
OKAY [ 2.012s]
writing 'modem'...
OKAY [ 2.075s]
finished. total time: 4.087s
F:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.031s]
finished. total time: 0.031s
F:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.031s]
finished. total time: 0.031s
F:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (517 KB)...
OKAY [ 0.109s]
writing 'fsg'...
OKAY [ 5.276s]
finished. total time: 5.385s
F:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.125s]
finished. total time: 0.125s
F:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.468s]
finished. total time: 0.468s
F:\Program Files (x86)\Minimal ADB and Fastboot>
Any of this any use to you?
Thanks
Lennie
@Jalipero - The log is incomplete - are you flashing 4 sparsechunk files? in the correct order: sparsechunk.0, sparsechunk.1, sparsechunk.2 and sparsechunk.3?
lost101 said:
@Jalipero - The log is incomplete - are you flashing 4 sparsechunk files? in the correct order: sparsechunk.0, sparsechunk.1, sparsechunk.2 and sparsechunk.3?
Click to expand...
Click to collapse
Sorry about that copied and pasted the whole thing into notepad then only pasted the 2nd half like a tube.
I have edited the original list to include it all now.
Apologies for the stupidity.
Thanks
Lennie
Did the phone boot into Android without problem after this re-flash?
lost101 said:
Did the phone boot into Android without problem after this re-flash?
Click to expand...
Click to collapse
Yes it did, oddly. Took an age, but I remembered seeing somewhere that it can take up to 8 minutes for it to initialise after flashing, so I left it at the planet with the M in it, and it booted up to start procedure fine. I was just about to restart it, then erase the cache again and reboot to clear it out if that is ok?
Lennie
You should not need to do anything else.
lost101 said:
You should not need to do anything else.
Click to expand...
Click to collapse
No problem I will leave it as it is then.
Thanks
Lennie
I was looking for the APN utility Tweakker but appears to no longer exist. There area alternatives on Google Play - if you want to try to make sure your APN info is correct.
Yes the biggest problem I have is that if I select anything other than 2g it just keeps dropping signal. Other than that the phone is great. I will have a look for a similar app to tweakker and see if there any changes to be made.
Ta muchly
Lennie
Hello! My phone's stuck in a bootloop and flashing Stock ROM doesn't help, so I was thinking of rooting the phone. Problem is I don't have Allow OEM Unlock ticked and I can't get onto the phone to do it. Is there any way to Allow OEM Unlock from bootloader? Or any other solution that might fix the problem?
Thank you!
axbom said:
Hello! My phone's stuck in a bootloop and flashing Stock ROM doesn't help, so I was thinking of rooting the phone. Problem is I don't have Allow OEM Unlock ticked and I can't get onto the phone to do it. Is there any way to Allow OEM Unlock from bootloader? Or any other solution that might fix the problem?
Thank you!
Click to expand...
Click to collapse
The phone MUST be bootable to enable OEM Unlocking, if you can't get it to boot to turn it on, there is no way to unlock the bootloader, thus no way to root.
It might be useful if you gave us some more details about how you got into this state... what you did or what happened, specific variant, etc.
acejavelin said:
The phone MUST be bootable to enable OEM Unlocking, if you can't get it to boot to turn it on, there is no way to unlock the bootloader, thus no way to root.
It might be useful if you gave us some more details about how you got into this state... what you did or what happened, specific variant, etc.
Click to expand...
Click to collapse
Oh okay. I've got a Motorola G3, XT1541. I tried updating it to Marshmallow which resulted in the phone bootlooping so I tried following this guide http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750 to fix it. Everything works fine when following the guide, I get [OKAY] on all steps in fastboot but it still doesn't work. I actually did miss the last sparsechunk file the first time I did it, so I ran it again. I can still get to the bootloader, but when trying to reach the recovery menu from there it just goes into bootloop again.
Thank you very much for helping out!
axbom said:
Oh okay. I've got a Motorola G3, XT1541. I tried updating it to Marshmallow which resulted in the phone bootlooping so I tried following this guide http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750 to fix it. Everything works fine when following the guide, I get [OKAY] on all steps in fastboot but it still doesn't work. I actually did miss the last sparsechunk file the first time I did it, so I ran it again. I can still get to the bootloader, but when trying to reach the recovery menu from there it just goes into bootloop again.
Thank you very much for helping out!
Click to expand...
Click to collapse
Did you factory default prior to flashing? That is a required step...
acejavelin said:
Did you factory default prior to flashing? That is a required step...
Click to expand...
Click to collapse
Yeah the first time I did it through the recovery mode, after that I was unable to get into the recovery menu so I've used:
fastboot erase userdata
fastboot erase cache
Still not working..
axbom said:
Yeah the first time I did it through the recovery mode, after that I was unable to get into the recovery menu so I've used:
fastboot erase userdata
fastboot erase cache
Still not working..
Click to expand...
Click to collapse
And you are positive it is the correct image for your device? If you got a success message for each piece and it still won't boot, I'm not sure what to say. Can you post a log or screenshot of the process?
Sent from my MotoG3 using Tapatalk
acejavelin said:
And you are positive it is the correct image for your device? If you got a success message for each piece and it still won't boot, I'm not sure what to say. Can you post a log or screenshot of the process?
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
On the back of the phone it says Model: XT1541 and I'm using the XT1541 6.0 version from this thread http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 so it should be the right one!
Here's the log I get when flashing:
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot oem fb_mode_set
...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.708s]
finished. total time: 0.723s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash bootloader bootloader.img
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing hyp ...
(bootloader) flashing rpm ...
OKAY [ 1.551s]
finished. total time: 1.645s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (1352 KB)...
OKAY [ 0.047s]
writing 'logo'...
OKAY [ 0.078s]
finished. total time: 0.125s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.519s]
writing 'boot'...
OKAY [ 0.936s]
finished. total time: 1.471s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.531s]
writing 'recovery'...
OKAY [ 0.954s]
finished. total time: 1.486s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (243355 KB)...
OKAY [ 7.717s]
writing 'system'...
OKAY [ 8.975s]
finished. total time: 16.723s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.1
target reported max download size of 268435456 bytes
sending 'system' (233538 KB)...
OKAY [ 7.478s]
writing 'system'...
OKAY [ 7.597s]
finished. total time: 15.092s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.2
target reported max download size of 268435456 bytes
sending 'system' (256922 KB)...
OKAY [ 8.213s]
writing 'system'...
OKAY [ 8.308s]
finished. total time: 16.521s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.3
target reported max download size of 268435456 bytes
sending 'system' (257262 KB)...
OKAY [ 8.198s]
writing 'system'...
OKAY [ 8.303s]
finished. total time: 16.500s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.4
target reported max download size of 268435456 bytes
sending 'system' (255507 KB)...
OKAY [ 8.142s]
writing 'system'...
OKAY [ 8.575s]
finished. total time: 16.717s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.5
target reported max download size of 268435456 bytes
sending 'system' (258021 KB)...
OKAY [ 8.225s]
writing 'system'...
OKAY [ 8.266s]
finished. total time: 16.507s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.6
target reported max download size of 268435456 bytes
sending 'system' (210541 KB)...
OKAY [ 6.716s]
writing 'system'...
OKAY [ 11.695s]
finished. total time: 18.410s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
sending 'modem' (36984 KB)...
OKAY [ 1.165s]
writing 'modem'...
OKAY [ 0.974s]
finished. total time: 2.155s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
sending 'fsg' (2159 KB)...
OKAY [ 0.078s]
writing 'fsg'...
OKAY [ 0.094s]
finished. total time: 0.172s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase customize
erasing 'customize'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase clogo
erasing 'clogo'...
OKAY [ 0.031s]
finished. total time: 0.047s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot oem fb_mode_clear
...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot reboot
rebooting...
finished. total time: -0.000s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>
From what I can see it all looks fine?
axbom said:
On the back of the phone it says Model: XT1541 and I'm using the XT1541 6.0 version from this thread http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 so it should be the right one!
Here's the log I get when flashing:
...
From what I can see it all looks fine?
Click to expand...
Click to collapse
Actually, that looks perfect... And it just bootloops afterwards, meaning it actually does a reboot and NOT just getting "stuck"?
I do not have a copy of this firmware image, it has exactly 7 sparcechunk pieces (0-6)?
One more thing... before you issue the fb_mode_set command, did you do a 'fastboot format cache' and 'fastboot format userdata' or do a factory reset from recovery?
acejavelin said:
Actually, that looks perfect... And it just bootloops afterwards, meaning it actually does a reboot and NOT just getting "stuck"?
I do not have a copy of this firmware image, it has exactly 7 sparcechunk pieces (0-6)?
One more thing... before you issue the fb_mode_set command, did you do a 'fastboot format cache' and 'fastboot format userdata' or do a factory reset from recovery?
Click to expand...
Click to collapse
After issuing the reboot command at the end it goes to the white screen with the motorola logo, then the screen goes black, and then back to the motorola logo, and keep on going like that.
Yeah that's correct, 0-6 sparsechunk files. I did fastboot ERASE cache and ERASE userdata, since I can't get into the recovery menu (goes into bootloop if I try). When I try any of those commands it says Formatting is not supported for filesystem with type 'raw'.
im having the exact same problem, used the same software and carried out the same steps as you with no luck either.
from what ive read its because you need to wipe all the data first but because we get the, cant its RAW message, it wont download the firmware onto the phone even though it says it went ok. at the minute i havnt found anyone whos successfully been able to repair this fault.
mine was working perfectly untill the ota update
There is no fix for that, use your warranty if you have so
Hi,
I have the same problem, I've made the same steps after faulty OTA update. And the Motorola warranty shop has told me that the warranty is void because of interference in the software. I have to add that in the fastboot after "getvar all" command there's a line "iswarrantyvoid = no", so as I understand the warranty should be still valid.
Regards.
yobac said:
Hi,
I have the same problem, I've made the same steps after faulty OTA update. And the Motorola warranty shop has told me that the warranty is void because of interference in the software. I have to add that in the fastboot after "getvar all" command there's a line "iswarrantyvoid = no", so as I understand the warranty should be still valid.
Regards.
Click to expand...
Click to collapse
Contact Moto directly via their website.
Sent from my MotoG3 using Tapatalk
1st Flash via Adb !
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 system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
mfastboot reboot
Post result !
FaizanChauhaan said:
1st Flash via Adb !
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 system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
mfastboot reboot
Post result !
Click to expand...
Click to collapse
It's fastboot not adb lol. Contradictory sentences
Edit: BTW motoboot.img is not present, it may refer to earlier generation of moto g. There is an line to flash bootloader.img instead. Have a look here : http://forum.xda-developers.com/showthread.php?t=3187750. Thanks.
Broadcasted from Zeta Reticuli