After the dumbest idea ever of downgrading to KitKat, I think i soft bricked my phone, it doesn't boot up.
When i try to flash a stock rom from bootloader it says:
Code:
hab check failed for recovery
hab check failed for boot
And when i try flashing a ROM or wiping on TWRP says:
Code:
unable to mount /data
unable to mount /cache
I tried everything i saw on XDA after googling many times the errors, nothing worked :crying:
One strange thing I saw was that when I tried "fastboot format data" it returned: "formatting is not supported for filesystem with type '' " , so, maybe, is a problem with the filesystem?
Help me, please :crying:
Done
Finally, I made it work, I erased and formatted all what i can, then through TWRP I formatted Data and now it works
Tizianop6 said:
Finally, I made it work, I erased and formatted all what i can, then through TWRP I formatted Data and now it works
Click to expand...
Click to collapse
Can you tell me the detail how to operate? Thanks!
Mr.Ju said:
Can you tell me the detail how to operate? Thanks!
Click to expand...
Click to collapse
I formatted all partitions through "fastboot erase" and other commands,flashed TWRP recovery, and then through TWRP I re-formatted all partitions
Tizianop6 said:
I formatted all partitions through "fastboot erase" and other commands,flashed TWRP recovery, and then through TWRP I re-formatted all partitions
Click to expand...
Click to collapse
Hi Mr. Ju,
I am having the exact same problem. I tried to use:
mfastboot devices
mfastboot erase userdata
mfastboot erase cache
mfastboot reboot
But it did not work. I sitll have the "hab check failed for boot" and hancheck failed for recovery" when I tried to reflash the GPE5.1 rom.
Can you please post all the mfastboot commands you used?
Thanks
Jº
Fastboot erase command is extremely dangerous and should not be played with.
@jpmaroco - Is your Bootloader locked?
Thanks lost101
No my boatloader is unlocked. I can't even wipe/factory reset with TWRP
jpmaroco said:
Thanks lost101
No my boatloader is unlocked. I can't even wipe/factory reset with TWRP
Click to expand...
Click to collapse
Try using mfastoot: https://www.androidfilehost.com/?fid=24052804347778493
Providing a log is helpful. Copy and paste command prompt after doing fastboot commands.
lost101 said:
Try using mfastoot: https://www.androidfilehost.com/?fid=24052804347778493
Providing a log is helpful. Copy and paste command prompt after doing fastboot commands.
Click to expand...
Click to collapse
Dear lost101,
Thanks for answering back. Here is the log:
E:\>mfastboot devices
TA92908ERZ fastboot
E:\>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.016s]
finished. total time: 0.016s
E:\>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
E:\>mfastboot reboot
rebooting...
finished. total time: 0.000s
@jpmaroco - I meant a log of you flashing the Firmware Image.
lost101 said:
@jpmaroco - I meant a log of you flashing the Firmware Image.
Click to expand...
Click to collapse
Thanks lost101, here it goes:
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>SET fastboot=fastboot.exe
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.003s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.004s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.069s]
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.339s]
finished. total time: 0.410s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.100s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.941s]
finished. total time: 1.078s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49368 KB)...
OKAY [ 1.586s]
writing 'modem'...
OKAY [ 0.802s]
finished. total time: 2.406s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (708 KB)...
OKAY [ 0.084s]
writing 'fsg'...
OKAY [ 3.179s]
finished. total time: 3.265s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.002s]
finished. total time: 0.002s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.002s]
finished. total time: 0.018s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (76 KB)...
OKAY [ 0.100s]
writing 'logo'...
OKAY [ 0.060s]
finished. total time: 0.178s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.384s]
writing 'boot'...
OKAY [ 0.644s]
finished. total time: 1.030s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.379s]
writing 'recovery'...
OKAY [ 0.621s]
finished. total time: 1.016s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257288 KB)...
OKAY [ 8.130s]
writing 'system'...
(bootloader) WARNING: System partition size is 0x34800000
(bootloader) Only multiples of 0x1000000 allowed for write-protection
(bootloader) Write protect will not be enabled
OKAY [ 8.051s]
finished. total time: 16.184s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (260812 KB)...
OKAY [ 8.239s]
writing 'system'...
(bootloader) WARNING: System partition size is 0x34800000
(bootloader) Only multiples of 0x1000000 allowed for write-protection
(bootloader) Write protect will not be enabled
OKAY [ 8.069s]
finished. total time: 16.309s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 8.290s]
writing 'system'...
(bootloader) WARNING: System partition size is 0x34800000
(bootloader) Only multiples of 0x1000000 allowed for write-protection
(bootloader) Write protect will not be enabled
OKAY [ 10.090s]
finished. total time: 18.380s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (18680 KB)...
OKAY [ 0.640s]
writing 'system'...
(bootloader) WARNING: System partition size is 0x34800000
(bootloader) Only multiples of 0x1000000 allowed for write-protection
(bootloader) Write protect will not be enabled
OKAY [ 0.633s]
finished. total time: 1.274s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe erase cache
erasing 'cache'...
OKAY [ -0.000s]
finished. total time: -0.000s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe erase userdata
erasing 'userdata'...
OKAY [ 0.027s]
finished. total time: 0.027s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe oem fb_mode_clear
...
OKAY [ 0.006s]
finished. total time: 0.022s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>pause
Press any key to continue . . .
---------- Post added 12th December 2015 at 12:14 AM ---------- Previous post was 11th December 2015 at 11:59 PM ----------
lost101 said:
@jpmaroco - I meant a log of you flashing the Firmware Image.
Click to expand...
Click to collapse
... and I get the same results if I use mfastboot instead of fastboot.
In the Phone, after
cmd: flash:boot
I get
hab check failed for boot
after
cmd: flash: recovery
i get
hab check failed for recovery
So, this seems to me that nothing is being flashed (It still keep my old twrp-2.8.7.0.-falcon_GPE.img recovery, not the stock one in GPE5.1 Lollipop)
I can boot in TWRP (after waiting for 5-6 minutes) but I can't factory reset because it says:
E: Could not mount /data and unable to find crypto footer
E: unable to mount /data
E:unbale to recreate /data/media/folder
... done
Does the same for "Storage" (unable to mount storage)...
Factory reset complete
failed
Should I try to flash the twrp-2.8.7.0.-falcon_STOCK.img?
Thanks for all your help lost101.
Latest GPE 5.1 Firmware Image: https://www.androidfilehost.com/?fid=24269982086992480
Use mfastboot.
Use these commands only:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
lost101 said:
Latest GPE 5.1 Firmware Image: https://www.androidfilehost.com/?fid=24269982086992480
[/COLOR]
lost101 said:
Latest GPE 5.1 Firmware Image: https://www.androidfilehost.com/?fid=24269982086992480
I just reflashed the rom you sent me. I have the same "hab check failed" errors ;-(
And the phone just stays at the swirling dots after reboot... I think It is not writing anything ;-(. It still keeps the twrp recovery. if mfastboot was working than mfastboot flash recovery recovery.img should flash the stock (gpe) recovery, correct?
Thanks once again lost101, I appreciate your help!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
jpmaroco said:
I just reflashed the rom you sent me. I have the same "hab check failed" errors ;-(
And the phone just stays at the swirling dots after reboot... I think It is not writing anything ;-(. It still keeps the twrp recovery. if mfastboot was working than mfastboot flash recovery recovery.img should flash the stock (gpe) recovery, correct?
Click to expand...
Click to collapse
Yes. Emmc appears now to be read-only - an issue that is regularly reported on this forum and one that has no solution.
lost101 said:
Yes. Emmc appears now to be read-only - an issue that is regularly reported on this forum and one that has no solution.
Click to expand...
Click to collapse
No solution? Só my moto g is dead for good and there's no way to recover it?
moto g2 4g model rooted after booting is failed
hi i am venkat
i am rooted my moto g2 4g , battery is low mobile is shutdown, after i am trying to power on the device one binary code is coming in that device is Locked status code : 0 showing
i am trying to start normal mode ,recovery mode, factory mode, but i am fail , i dont know how to solve this, please help me,
thank you ...
Hi was wondering if anyone could help me, i unlocked the bootloader and tried to root and install CWM recovery, now my phone boots up to the logo then fades out and there are lines flashing on the screen
I have tried to install the stock rom with mfastboot using this procedure...
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
I do each line one by one and this is my log file....
I:\Moto G\mfastboot-v2>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.061s
I:\Moto G\mfastboot-v2>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1940 KB)...
OKAY [ 0.100s]
writing 'motoboot'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.136s
I:\Moto G\mfastboot-v2>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (619 KB)...
OKAY [ 0.072s]
writing 'logo'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.113s
I:\Moto G\mfastboot-v2>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.378s]
writing 'boot'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.397s
I:\Moto G\mfastboot-v2>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.389s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.437s
I:\Moto G\mfastboot-v2>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (252700 KB)...
OKAY [ 7.946s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 7.963s
I:\Moto G\mfastboot-v2>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (247709 KB)...
OKAY [ 7.790s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 7.820s
I:\Moto G\mfastboot-v2>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (110360 KB)...
OKAY [ 3.498s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 3.546s
I:\Moto G\mfastboot-v2>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (47996 KB)...
OKAY [ 1.567s]
writing 'modem'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 1.581s
I:\Moto G\mfastboot-v2>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.035s]
finished. total time: 0.035s
I:\Moto G\mfastboot-v2>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.021s]
finished. total time: 0.022s
I:\Moto G\mfastboot-v2>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.092s]
writing 'fsg'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.148s
I:\Moto G\mfastboot-v2>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.302s]
finished. total time: 0.303s
I:\Moto G\mfastboot-v2>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 2.339s]
finished. total time: 2.340s
I:\Moto G\mfastboot-v2>mfastboot reboot
rebooting...
finished. total time: 0.001s
I:\Moto G\mfastboot-v2>
Now when it reboots it goes to the boot logo then the screen goes black and white lines start flickering and it stops like that
Leave phone fastboot screen - charge battery until at least 50% - then try again.
ok will try that
still not working
mimicuk said:
still not working
Click to expand...
Click to collapse
What Model / Firmware is that phone? Could you provide a new fastboot log?
this is the stock rom i am using RETAIL-GB_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF_svc.xml.modaco.r3
I have the 1st gen moto g 4G one not the 2nd gen
This is the Mfastboot log.......
I:\Moto G\mfastboot-v2>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.027s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.330s
I:\Moto G\mfastboot-v2>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1940 KB)...
OKAY [ 0.096s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.377s
I:\Moto G\mfastboot-v2>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (619 KB)...
OKAY [ 0.075s]
writing 'logo'...
OKAY [ 0.125s]
finished. total time: 0.204s
I:\Moto G\mfastboot-v2>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.368s]
writing 'boot'...
OKAY [ 0.734s]
finished. total time: 1.111s
I:\Moto G\mfastboot-v2>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.374s]
writing 'recovery'...
OKAY [ 0.729s]
finished. total time: 1.104s
I:\Moto G\mfastboot-v2>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (252700 KB)...
OKAY [ 7.963s]
writing 'system'...
OKAY [ 11.125s]
finished. total time: 19.096s
I:\Moto G\mfastboot-v2>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (247709 KB)...
OKAY [ 7.794s]
writing 'system'...
OKAY [ 9.566s]
finished. total time: 17.367s
I:\Moto G\mfastboot-v2>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (110360 KB)...
OKAY [ 3.498s]
writing 'system'...
OKAY [ 18.411s]
finished. total time: 21.915s
I:\Moto G\mfastboot-v2>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (47996 KB)...
OKAY [ 1.550s]
writing 'modem'...
OKAY [ 1.262s]
finished. total time: 2.818s
I:\Moto G\mfastboot-v2>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.023s]
finished. total time: 0.026s
I:\Moto G\mfastboot-v2>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.023s]
finished. total time: 0.025s
I:\Moto G\mfastboot-v2>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.084s]
writing 'fsg'...
OKAY [ 5.612s]
finished. total time: 5.702s
I:\Moto G\mfastboot-v2>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.280s]
finished. total time: 0.281s
I:\Moto G\mfastboot-v2>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 2.382s]
finished. total time: 2.384s
I:\Moto G\mfastboot-v2>mfastboot reboot
rebooting...
finished. total time: 0.003s
I:\Moto G\mfastboot-v2>
The firmware image you are using is too old. Your current Bootloader will not accept it.
I suggest you try one of the newer XT1039 Retail UK/GB firmware images from here:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
It may be the case that only the 5.1 firmware image will flash correctly for you.
lost101 said:
The firmware image you are using is too old. Your current Bootloader will not accept it.
I suggest you try one of the newer XT1039 Retail UK/GB firmware images from here:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
It may be the case that only the 5.1 firmware image will flash correctly for you.
Click to expand...
Click to collapse
will this work on a xt1045 with the same problem??
hecmarrufo said:
will this work on a xt1045 with the same problem??
Click to expand...
Click to collapse
The XT1045 5.1 firmware image is not yet available. Hopefully that will change soon. Flashing a different models firmware is a very bad idea.
Dear Members,
My friend owns a Moto G XT1033 (dual sim Indian version) and recently had the software go wrong. Now the phone boots - shows boot unlocked warning, booting animation. After the MOTO symbol, all that we get is a blank screen.
Now, things that I tried to recover the phone is as follows -
1. Booted into recovery menu - tried accessing the RECOVERY option. I get a NO COMMAND error (with the android lying down on his back)
2. Tried flashing custom recovery (both TWRP and CWM) - using fastboot option - I get "MISMATCHED PARTITION SIZE" error. I ignored that error (as read somewhere in this forum), I still get "NO COMMAND" while accessing the RECOVERY option
3. Tried to sideload stock 4.4.4 version using adb - the system pushes the rom to the phone successfully, but in couple of minutes I get "installation aborted" error.
I've done all I could with the help of other threads with no success. I would request your help to recover the phone. Apologies if I have started another duplicate thread on this issue. Please help. Thanks in advance.
AP Fastboot Flash Mode (S)
41.13 (sha07dc8e78, 2014-06-16 16:33:29)
CPU: MSM8226 CS
eMMC: 16GB Sandisk RV=06 PV=07 TY=17
DRAM: 1024MB Elpida S4 SDRAM DIE=4GB
Battery OK
Device is UNLOCKED. Status Code: 3
Connect USB data Cable
Flash the latest XT1033 Factory Firmware Image using Fastboot. If this is not successful, 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 XT1033 Factory Firmware Image using Fastboot. If this is not successful, 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
Thanks for your reply and your time!
However, please find the error message and flash log below.
My image file - XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml
mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.025s]
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.359s]
finished. total time: 0.388s
mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.095s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.116s]
finished. total time: 1.216s
mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.055s]
writing 'logo'...
OKAY [ 0.037s]
finished. total time: 0.097s
mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.394s]
writing 'boot'...
OKAY [ 0.654s]
finished. total time: 1.053s
mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.403s]
writing 'recovery'...
OKAY [ 0.659s]
finished. total time: 1.068s
mfastboot flash system system.img_sparsechunk1
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk1': No error
mfastboot flash system system.img_sparsechunk2
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk2': No error
Please help further.
billa vimal said:
mfastboot flash system system.img_sparsechunk1
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk1': No error
mfastboot flash system system.img_sparsechunk2
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk2': No error
Please help further.
Click to expand...
Click to collapse
Use the file names that actually exist on your computer - there may be dots in the name or some other minor differences. And if chunk 0 exists, start with that one.
_that said:
Use the file names that actually exist on your computer - there may be dots in the name or some other minor differences. And if chunk 0 exists, start with that one.
Click to expand...
Click to collapse
Thanks for highlighting that! I actually went by the steps listed in the tutorial and didnt notice the chunk.0! I have now followed every other step - but still the problem exists! I have attached the screenshot of the rom contents. And also the flash logs. Please let me know if I'm missing anything here.
Thanks for your time!
mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
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.359s]
finished. total time: 0.375s
mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.094s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.109s]
finished. total time: 1.219s
mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.391s]
writing 'boot'...
OKAY [ 0.656s]
finished. total time: 1.047s
mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.391s]
writing 'recovery'...
OKAY [ 0.656s]
finished. total time: 1.047s
mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257755 KB)...
OKAY [ 9.031s]
writing 'system'...
OKAY [ 8.064s]
finished. total time: 17.110s
mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256949 KB)...
OKAY [ 8.994s]
writing 'system'...
OKAY [ 8.234s]
finished. total time: 17.229s
mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260404 KB)...
OKAY [ 9.139s]
writing 'system'...
OKAY [ 8.235s]
finished. total time: 17.375s
mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (166184 KB)...
OKAY [ 5.859s]
writing 'system'...
OKAY [ 6.453s]
finished. total time: 12.328s
mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49376 KB)...
OKAY [ 1.766s]
writing 'modem'...
OKAY [ 0.844s]
finished. total time: 2.609s
mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ -0.000s]
finished. total time: -0.000s
mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.016s]
finished. total time: 0.016s
mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (103 KB)...
OKAY [ 0.078s]
writing 'fsg'...
OKAY [ 3.188s]
finished. total time: 3.266s
mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
Appreciate if someone can help rescue the phone. Thanks.
Dear friends, I am bumping this thread as I am still having the phone as a brick. Thanks to anyone who volunteer to help.
Hello
I really hopes one of you brilliand guys can help me. I'm at a loss (sorry in advance for bad english).
I have a xt1039 with an unlocked BL 41.1A which I can't get back to stock or flash any other ROM.
In mfastboot, my phone is recognized as TA4750I1SK, and the device is UNLOCKED and my CID is 7.
I tried flashing different stock version from here
https://firmware.center/firmware/Motorola/Moto%20G%20%281st%20gen-2013%29/Stock/XT1039/"]https://firmware.center/firmware/Motorola/Moto%20G%20%281st%20gen-2013%29/Stock/XT1039/
trying both 4.4.4 and 5.1 but without success:
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.090s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.430s
(version downgraded for primary gpt)
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.170s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.020s]
finished. total time: 1.200s
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.100s]
writing 'logo'...
OKAY [ 0.090s]
finished. total time: 0.190s
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.520s]
writing 'boot'...
OKAY [ 0.810s]
finished. total time: 1.330s
(This sometimes fails as well, preflash validation, and on mobile says "version downgraded for boot")
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe flash recovery recovery.i
mg
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.520s]
writing 'recovery'...
OKAY [ 0.810s]
finished. total time: 1.330s
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257451 KB)...
OKAY [ 10.715s]
writing 'system'...
OKAY [ 13.060s]
finished. total time: 23.776s
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (257661 KB)...
OKAY [ 10.383s]
writing 'system'...
OKAY [ 12.192s]
finished. total time: 22.580s
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (261552 KB)...
OKAY [ 10.710s]
writing 'system'...
OKAY [ 17.881s]
finished. total time: 28.606s
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (60232 KB)...
OKAY [ 2.527s]
writing 'modem'...
OKAY [ 2.090s]
finished. total time: 4.627s
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.030s]
finished. total time: 0.030s
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.064s]
finished. total time: 0.066s
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (517 KB)...
OKAY [ 0.080s]
writing 'fsg'...
OKAY [ 5.272s]
finished. total time: 5.362s
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.140s]
finished. total time: 0.140s
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe erase userdata
erasing 'userdata'...
OKAY [ 0.440s]
finished. total time: 0.440s
I managed to flash twrp, but the phone will hang on Bootloader logo when rebooting, and I don't know what to do next.
Any good ideas?
visit here https://forum.xda-developers.com/showthread.php?t=2317790
and download version 1.4.2
then visit this https://forum.xda-developers.com/attachment.php?attachmentid=3476163&d=1442444179 (direct download link for mfastboot)
now copy mfastboot.exe to adb folder (created from version 1.4.2 .exe)
and try to install 5.1 lollipop stock rom with mfastboot commands thats it everything will works fine
dont download adb file from google website always use version 1.4.2
enjoy
Thank you for your reply. That made no difference. Same error messages. Also when I reboot in the end, it still shows unlocked bootloader message, continues straight to periodically blinking the "no command" and then just hangs.
I tried to flash XT1039_PEREGRINE_RETEU_5.1_LPB23.13-17_cid7_CFC.xml.
Also, when I go to twrp and try to make a wipe, it shows 'unable to mount /data' and 'unable to mount internal storage'.
Any new ideas?
SunilSuni said:
visit here https://forum.xda-developers.com/showthread.php?t=2317790
and download version 1.4.2
then visit this https://forum.xda-developers.com/attachment.php?attachmentid=3476163&d=1442444179 (direct download link for mfastboot)
now copy mfastboot.exe to adb folder (created from version 1.4.2 .exe)
and try to install 5.1 lollipop stock rom with mfastboot commands thats it everything will works fine
dont download adb file from google website always use version 1.4.2
enjoy
Click to expand...
Click to collapse
Powerleech said:
Hello
I really hopes one of you brilliand guys can help me. I'm at a loss (sorry in advance for bad english).
I have a xt1039 with an unlocked BL 41.1A which I can't get back to stock or flash any other ROM.
In mfastboot, my phone is recognized as TA4750I1SK, and the device is UNLOCKED and my CID is 7.
I tried flashing different stock version from here
https://firmware.center/firmware/Motorola/Moto%20G%20%281st%20gen-2013%29/Stock/XT1039/"]https://firmware.center/firmware/Motorola/Moto%20G%20%281st%20gen-2013%29/Stock/XT1039/
trying both 4.4.4 and 5.1 but without success:
I managed to flash twrp, but the phone will hang on Bootloader logo when rebooting, and I don't know what to do next.
Any good ideas?
Click to expand...
Click to collapse
Flashing twrp 3.1 or high in bootloader .
Wipe "system" "data" and "cache" in twrp .
Dont flash "partition" and "motoboot" when you flashing stock firmware .
Using AEX's AOSP 7.1 rom(Indian quark) from few days. Facing many issues like app crashes and no LTE mostly. Today i wanted to call someone and clicked on phone app on home screen. Suddenly a message popped up saying phone has stopped. It showed whenever i clicked on phone app. I restarted the phone. Thatsit. Its only booting into fastboot mode. Whenever i chose to select recovery mode it only boots into fastboot. checked the bootloaderlogs and found "failed to validate boot image ret=-1 bootup failed" this message.Please, I need a serious help.
krishna13 said:
Using AEX's AOSP 7.1 rom(Indian quark) from few days. Facing many issues like app crashes and no LTE mostly. Today i wanted to call someone and clicked on phone app on home screen. Suddenly a message popped up saying phone has stopped. It showed whenever i clicked on phone app. I restarted the phone. Thatsit. Its only booting into fastboot mode. Whenever i chose to select recovery mode it only boots into fastboot. checked the bootloaderlogs and found "failed to validate boot image ret=-1 bootup failed" this message.Please, I need a serious help.
Click to expand...
Click to collapse
It's booting to the bootloader screen? You should be able to arrow up from there using the volume keys to the "recovery" option and boot to TWRP.
Once in TWRP, restore the backup you made. You did make a recent backup in TWRP, right?
OR in TWRP, do a factory reset and install a ROM. In TWRP, you can drag over whatever you want if you are connected to a PC. Works just like a flash drive. Drag over a ROM, GAPPs, etc if you don't want to install AEX's AOSP 7.1 again.
ChazzMatt said:
It's booting to the bootloader screen? You should be able to arrow up from there using the volume keys to the "recovery" option and boot to TWRP.
Once in TWRP, restore the backup you made. You did make a recent backup in TWRP, right?
OR in TWRP, do a factory reset and install a ROM. In TWRP, you can drag over whatever you want if you are connected to a PC. Works just like a flash drive. Drag over a ROM, GAPPs, etc if you don't want to install AEX's AOSP 7.1 again.
Click to expand...
Click to collapse
Its not going to recovery mode again. In bootloader logs i can see boot.img failed and the ret value is -1. Even in RSD flash tool i can see that 2/18 error or 2/22 fastboot oem fb_clear error. Tried flashing original 6.0 and 5.0 firmwares both in RSD flashtool and individual fastboot commands.But i failed. ALways booting only in Fastboot. Please help me. Im living with no phone from 3 days. Please provide me a solution...
krishna13 said:
Its not going to recovery mode again. In bootloader logs i can see boot.img failed and the ret value is -1. Even in RSD flash tool i can see that 2/18 error or 2/22 fastboot oem fb_clear error. Tried flashing original 6.0 and 5.0 firmwares both in RSD flashtool and individual fastboot commands.But i failed. ALways booting only in Fastboot. Please help me. Im living with no phone from 3 days. Please provide me a solution...
Click to expand...
Click to collapse
But you can go to recovery mode. If it's booting to the bootloader, you can arrow up to recovery and choose that.
Oh no, you flashed original 6.0 and 5.0 firmware? OK, now you have not only wiped out your custom TWRP recovery you have have flashed older bootloader over newer bootloader which BRICKS the phone. You never, never, never flash older firmware over newer firmware unless you omit gpt.bin in the flash commands.
Even then you should also omit recovery.img in the flash commands to keep custom recovery.
Your bootloader is unlocked, right? If so, there is still hope. Hold on.
ChazzMatt said:
But you can go to recovery mode. If it's booting to the bootloader, you can arrow up to recovery and choose that.
Oh no, you flashed original 6.0 and 5.0 firmware? OK, now you have not only wiped out your custom TWRP recovery you have have flashed older bootloader over newer bootloader which BRICKS the phone. You never, never, never flash older firmware over newer firmware unless you omit gpt.bin in the flash commands.
Even then you should also omit recovery.img in the flash commands to keep custom recovery.
Your bootloader is unlocked, right? If so, there is still hope. Hold on.
Click to expand...
Click to collapse
Yes. Still my device is unlocked. In fastboot mode, the text showing in yello color saying, Device is UNLOCKED. Status code :3.
Please help me.. Is it possible through teamviewer?? please please help me..
OK, read this thread.
https://forum.xda-developers.com/moto-maxx/help/bootloader-locked-acess-recovery-os-t3662683
and this one:
https://forum.xda-developers.com/moto-maxx/help/maxx-xt1225-br-hard-brick-help-please-t3661803
After that, specifically you want to download this file:
https://forum.xda-developers.com/showpost.php?p=73528589&postcount=19
Yes, it's for Brazil XT1225 but your bootloader is unlocked and there's no India equivalent posted online. You need the very latest Marshmallow stock (with latest bootloader) from Motorola and that's it. For stock you can only flash the same version bootloader you have or newer.
You will NOT be using RSDLite. You will have to use ADB fastboot. Read this post for instructions.
https://forum.xda-developers.com/dr...force-how-to-manually-flash-official-t3282077
Yes, it's for the Moto X Force, but the steps are still the same for any bootloader unlocked Motorola device. You are flashing cross-region firmware on your India XT1225 to get it back working again.
You will need to omit gpt.bin when flashing the commands.
Once your phone is working again, you will need to re-flash TWRP and root with that older SuperSu version or whatever you did the first time.
After that you can reinstall a custom ROM if you wish.
ChazzMatt said:
OK, read this thread.
https://forum.xda-developers.com/moto-maxx/help/bootloader-locked-acess-recovery-os-t3662683
and this one:
https://forum.xda-developers.com/moto-maxx/help/maxx-xt1225-br-hard-brick-help-please-t3661803
After that, specifically you want to download this file:
https://forum.xda-developers.com/showpost.php?p=73528589&postcount=19
Yes, it's for Brazil XT1225 but your bootloader is unlocked and there's no India equivalent posted online. You need the very latest Marshmallow stock (with latest bootloader) from Motorola and that's it. For stock you can only flash the same version bootloader you have or newer.
You will NOT be using RSDLite. You will have to use ADB fastboot. Read this post for instructions.
https://forum.xda-developers.com/dr...force-how-to-manually-flash-official-t3282077
Yes, it's for the Moto X Force, but the steps are still the same for any bootloader unlocked Motorola device. You are flashing cross-region firmware on your India XT1225 to get it back working again.
You will need to omit gpt.bin when flashing the commands.
Once your phone is working again, you will need to re-flash TWRP and root with that older SuperSu version or whatever you did the first time.
After that you can reinstall a custom ROM if you wish.
Click to expand...
Click to collapse
Downloaded the files from http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/ and tried all the steps from the link u provided.These are the steps i followed.
mfastboot flash bootloader bootloader.img
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot flash system system.img_sparsechunk.10
mfastboot flash system system.img_sparsechunk.11
mfastboot erase cache
mfastboot erase userdata
mfastboot oem fb_mode_clear
mfastboot reboot
But failed to reboot. In bootloader logs its showing as
"failed to validate boot image ret :-1"
Fastboot reason : fall-through from normal boot mode
any other method please?? help me with this.
krishna13 said:
Downloaded the files from http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/ and tried all the steps from the link u provided.These are the steps i followed.
mfastboot flash bootloader bootloader.img
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot flash system system.img_sparsechunk.10
mfastboot flash system system.img_sparsechunk.11
mfastboot erase cache
mfastboot erase userdata
mfastboot oem fb_mode_clear
mfastboot reboot
But failed to reboot. In bootloader logs its showing as
"failed to validate boot image ret :-1"
Fastboot reason : fall-through from normal boot mode
any other method please?? help me with this.
Click to expand...
Click to collapse
One thing...
On that Brazil firmware link I only see 10 sparse chunks, numbered 0-9, Yet, in your post above you have 12 listed. how are you flashing 12? (0-11) You can only flash as many sparse chunks as there are, that example from the Moto X Force thread is just an example. You have to flash the exact number.
I see you did NOT flash gpt.bin, which is good.
If your bootloader is still unlocked, this should work.
The only thing else I can suggest is this powerful temp root command first, before flashing the Brazil image. But you then have to flash an "end"/"finish" command or the next time you reboot, that itself will cause a bootloop. Over in the Droid Turbo forum, they use that temp root command to flash Sunshine, so Sunshine can then unlock the bootloader. You don't need Sunshine, I am only pointing you to the temp root file, which may help you flash this Brazil Marshmallow image.
There was another thread I can't find right now, from a person in very similar circumstances to you. His bootloader was even locked -- which was worse than you. But using that temp command, he was able to revive his phone using ADB fastboot flashing. His only problem then was not ending the temp root, and now I've lost the thread.
So, try this. Flash the temp root, followed by all the ADB fastboot commands to flash that image, followed by the command to end the temp root (it's double quotation marks with a space before them).
ChazzMatt said:
One thing...
On that Brazil firmware link I only see 10 sparse chunks, numbered 0-9, Yet, in your post above you have 12 listed. how are you flashing 12? (0-11) You can only flash as many sparse chunks as there are, that example from the Moto X Force thread is just an example. You have to flash the exact number.
I see you did NOT flash gpt.bin, which is good.
If your bootloader is still unlocked, this should work.
The only thing else I can suggest is this powerful temp root command first, before flashing the Brazil image. But you then have to flash an "end"/"finish" command or the next time you reboot, that itself will cause a bootloop. Over in the Droid Turbo forum, they use that temp root command to flash Sunshine, so Sunshine can then unlock the bootloader. You don't need Sunshine, I am only pointing you to the temp root file, which may help you flash this Brazil Marshmallow image.
There was another thread I can't find right now, from a person in very similar circumstances to you. His bootloader was even locked -- which was worse than you. But using that temp command, he was able to revive his phone using ADB fastboot flashing. His only problem then was not ending the temp root, and now I've lost the thread.
So, try this. Flash the temp root, followed by all the ADB fastboot commands to flash that image, followed by the command to end the temp root (it's double quotation marks with a space before them).
Click to expand...
Click to collapse
Yes. My bad. i had just copied commands to show u that i followed them. But in real, i had only flashed 9 of them.
and coming to your post, so should I need to download the initroot from "got the initroot working with internet for Droid Turbo - https://forum.xda-developers.com/g4-...ader-t3639316/" and install in my system and run the .bat file? would it work for my xt1225? there mentioned other than xt1225. after flashing all the 9 system sparse chunks from brazil firmware, is this the command to end the temp root?? fastboot oem config fsg-id " "
I am confused
ChazzMatt said:
One thing...
On that Brazil firmware link I only see 10 sparse chunks, numbered 0-9, Yet, in your post above you have 12 listed. how are you flashing 12? (0-11) You can only flash as many sparse chunks as there are, that example from the Moto X Force thread is just an example. You have to flash the exact number.
I see you did NOT flash gpt.bin, which is good.
If your bootloader is still unlocked, this should work.
The only thing else I can suggest is this powerful temp root command first, before flashing the Brazil image. But you then have to flash an "end"/"finish" command or the next time you reboot, that itself will cause a bootloop. Over in the Droid Turbo forum, they use that temp root command to flash Sunshine, so Sunshine can then unlock the bootloader. You don't need Sunshine, I am only pointing you to the temp root file, which may help you flash this Brazil Marshmallow image.
There was another thread I can't find right now, from a person in very similar circumstances to you. His bootloader was even locked -- which was worse than you. But using that temp command, he was able to revive his phone using ADB fastboot flashing. His only problem then was not ending the temp root, and now I've lost the thread.
So, try this. Flash the temp root, followed by all the ADB fastboot commands to flash that image, followed by the command to end the temp root (it's double quotation marks with a space before them).
Click to expand...
Click to collapse
This is how i did this time..
C:\Users\SRK\Downloads\Motorola firmware>fastboot oem config fsg-id " "
...
OKAY [ 0.003s]
finished. total time: 0.006s
C:\Users\SRK\Downloads\Motorola firmware>
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
sending 'bootloader' (2163 KB)...
OKAY [ 0.077s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing rpm ...
OKAY [ 0.204s]
finished. total time: 0.285s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.590s]
writing 'boot'...
OKAY [ 0.123s]
finished. total time: 0.714s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (16400 KB)...
OKAY [ 0.599s]
writing 'recovery'...
OKAY [ 0.110s]
finished. total time: 0.715s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (262143 KB)...
OKAY [ 8.335s]
writing 'system'...
OKAY [ 1.698s]
finished. total time: 10.118s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (239764 KB)...
OKAY [ 7.597s]
writing 'system'...
OKAY [ 1.551s]
finished. total time: 9.155s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (250695 KB)...
OKAY [ 7.947s]
writing 'system'...
OKAY [ 1.617s]
finished. total time: 9.569s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (255001 KB)...
OKAY [ 8.070s]
writing 'system'...
OKAY [ 1.592s]
finished. total time: 9.669s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (257746 KB)...
OKAY [ 8.156s]
writing 'system'...
OKAY [ 1.622s]
finished. total time: 9.782s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
sending 'system' (261982 KB)...
OKAY [ 8.291s]
writing 'system'...
OKAY [ 1.695s]
finished. total time: 9.992s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
sending 'system' (262140 KB)...
OKAY [ 8.296s]
writing 'system'...
OKAY [ 1.608s]
finished. total time: 9.911s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.7
target max-sparse-size: 256MB
sending 'system' (247037 KB)...
OKAY [ 7.819s]
writing 'system'...
OKAY [ 1.568s]
finished. total time: 9.393s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.8
target max-sparse-size: 256MB
sending 'system' (262140 KB)...
OKAY [ 8.307s]
writing 'system'...
OKAY [ 1.613s]
finished. total time: 9.926s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.9
target max-sparse-size: 256MB
sending 'system' (219553 KB)...
OKAY [ 6.985s]
writing 'system'...
OKAY [ 1.379s]
finished. total time: 8.371s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.013s]
finished. total time: 0.016s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.012s]
finished. total time: 0.015s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot oem fb_mode_clear
...
OKAY [ 0.002s]
finished. total time: 0.005s
C:\Users\SRK\Downloads\Motorola firmware>fastboot oem config fsg-id "end"
...
FAILED (remote failure)
finished. total time: 0.011s
C:\Users\SRK\Downloads\Motorola firmware>fastboot oem config fsg-id "finish"
...
FAILED (remote failure)
finished. total time: 0.007s
C:\Users\SRK\Downloads\Motorola firmware>fastboot oem config fsg-id ""
...
FAILED (remote failure)
finished. total time: 0.006s
C:\Users\SRK\Downloads\Motorola firmware>fastboot oem config fsg-id " "
...
OKAY [ 0.002s]
finished. total time: 0.004s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot reboot
rebooting...
finished. total time: 0.004s
but same problem..no success ..same ret :-1 in bootloader logs. Did i do wrong??
krishna13 said:
and coming to your post, so should I need to download the initroot from "got the initroot working with internet for Droid Turbo - https://forum.xda-developers.com/g4-...ader-t3639316/" and install in my system and run the .bat file? would it work for my xt1225? there mentioned other than xt1225. after flashing all the 9 system sparse chunks from brazil firmware, is this the command to end the temp root?? fastboot oem config fsg-id " "
Click to expand...
Click to collapse
Yes, but to end the temp root -- it's hard to tell due to XDA formatting --but It's fastboot oem config fsg-id "", with a space between the fsg-id part and the double quotation marks. There's NO space IN the quotation marks, just a space before it.
ChazzMatt said:
Yes, but to end the temp root -- it's hard to tell due to XDA formatting --but It's fastboot oem config fsg-id "", with a space between the fsg-id part and the double quotation marks. There's NO space IN the quotation marks, just a space before it.
Click to expand...
Click to collapse
i have downloaded auto-intiroot-xt1254_quark.so shall i simply install it in my system and run the bat file? so no problem for my phone? to end that, simply ill follow the command without spaces.
first ill install bat file,then flash all the fastboot commands of firmware,and before fastboot reboot, ill end the temp flash and reboot my device.is this the procedure???
krishna13 said:
i have downloaded auto-intiroot-xt1254_quark.so shall i simply install it in my system and run the bat file? so no problem for my phone? to end that, simply ill follow the command without spaces.
first ill install bat file,then flash all the fastboot commands of firmware,and before fastboot reboot, ill end the temp flash and reboot my device.is this the procedure???
Click to expand...
Click to collapse
Yes, you downloaded the right version. It's this one, even though you have an XT1225:
http://downloads.codefi.re/autoprime/Motorola/autoinitroot/XT1254
Yes, install the bat file via fastboot, then run the fastboot commands for firmware, then end the temp flash and try to reboot.
IF this doesn't work, I have no other ideas really. Just variations of making sure you are flashing the firmware correctly, which you seem to be doing.
ChazzMatt said:
There was another thread I can't find right now, from a person in very similar circumstances to you.
Click to expand...
Click to collapse
That was in [All Quark][Official] Stock Firmware Moto Maxx Droid Turbo Moto Turbo, and started on page 48 - post #475.
hitokage004 said:
That was in [All Quark][Official] Stock Firmware Moto Maxx Droid Turbo Moto Turbo, and started on page 48 - post #475.
Click to expand...
Click to collapse
Thank you! Thought I was going crazy. I KNEW I had discussed this just recently and the person used temp root and got the phone working again. Then I couldn't find the posts. But it was you who suggested the temp root tool and it worked.
Yeah, start on this page, with post 475:
https://forum.xda-developers.com/mo...tock-firmware-moto-maxx-droid-t3063470/page48
There was no final resolution to that person's problem but he was able to reboot the phone and it was working again, thanks to the temp root.
ChazzMatt said:
Yes, but to end the temp root -- it's hard to tell due to XDA formatting --but It's fastboot oem config fsg-id "", with a space between the fsg-id part and the double quotation marks. There's NO space IN the quotation marks, just a space before it.
Click to expand...
Click to collapse
I had run auto-init.bat which booted my phone in fastboot mode asusual.then i followed the same steps by ending the temp root like mentioned.But same happened. in bootloader logs the same ret=-1 and also Fastboot reason : Reboot mode set to fastboot.This was all i followed.
C:\Users\SRK\Downloads\NewMoto>mfastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
sending 'bootloader' (2163 KB)...
OKAY [ 0.124s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing rpm ...
OKAY [ 0.247s]
finished. total time: 0.377s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.579s]
writing 'boot'...
OKAY [ 0.107s]
finished. total time: 0.692s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (16400 KB)...
OKAY [ 0.590s]
writing 'recovery'...
OKAY [ 0.108s]
finished. total time: 0.705s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (262143 KB)...
OKAY [ 8.292s]
writing 'system'...
OKAY [ 1.721s]
finished. total time: 10.018s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (239764 KB)...
OKAY [ 7.592s]
writing 'system'...
OKAY [ 1.582s]
finished. total time: 9.180s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (250695 KB)...
OKAY [ 7.937s]
writing 'system'...
OKAY [ 1.618s]
finished. total time: 9.561s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (255001 KB)...
OKAY [ 8.069s]
writing 'system'...
OKAY [ 1.592s]
finished. total time: 9.666s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (257746 KB)...
OKAY [ 8.157s]
writing 'system'...
OKAY [ 1.625s]
finished. total time: 9.787s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
sending 'system' (261982 KB)...
OKAY [ 8.288s]
writing 'system'...
OKAY [ 1.703s]
finished. total time: 9.996s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
sending 'system' (262140 KB)...
OKAY [ 8.293s]
writing 'system'...
OKAY [ 1.608s]
finished. total time: 9.907s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.7
target max-sparse-size: 256MB
sending 'system' (247037 KB)...
OKAY [ 7.821s]
writing 'system'...
OKAY [ 1.547s]
finished. total time: 9.375s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.8
target max-sparse-size: 256MB
sending 'system' (262140 KB)...
OKAY [ 8.293s]
writing 'system'...
OKAY [ 1.614s]
finished. total time: 9.912s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.9
target max-sparse-size: 256MB
sending 'system' (219553 KB)...
OKAY [ 6.959s]
writing 'system'...
OKAY [ 1.375s]
finished. total time: 8.341s
C:\Users\SRK\Downloads\NewMoto>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.010s]
finished. total time: 0.011s
C:\Users\SRK\Downloads\NewMoto>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.010s]
finished. total time: 0.013s
C:\Users\SRK\Downloads\NewMoto>mfastboot oem fb_mode_clear
...
OKAY [ 0.003s]
finished. total time: 0.005s
C:\Users\SRK\Downloads\NewMoto>fastboot oem config fsg-id ""
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.056s]
finished. total time: 0.060s
C:\Users\SRK\Downloads\NewMoto>mfastboot reboot
rebooting...
finished. total time: 0.003s
could you or someone assist me in team viewer please?? I really having bad days. no phone from 4 days.
krishna13 said:
I had run auto-init.bat which booted my phone in fastboot mode asusual.then i followed the same steps by ending the temp root like mentioned.But same happened. in bootloader logs the same ret=-1 and also Fastboot reason : Reboot mode set to fastboot.This was all i followed.
C:\Users\SRK\Downloads\NewMoto>mfastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
sending 'bootloader' (2163 KB)...
OKAY [ 0.124s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing rpm ...
OKAY [ 0.247s]
finished. total time: 0.377s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.579s]
writing 'boot'...
OKAY [ 0.107s]
finished. total time: 0.692s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (16400 KB)...
OKAY [ 0.590s]
writing 'recovery'...
OKAY [ 0.108s]
finished. total time: 0.705s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (262143 KB)...
OKAY [ 8.292s]
writing 'system'...
OKAY [ 1.721s]
finished. total time: 10.018s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (239764 KB)...
OKAY [ 7.592s]
writing 'system'...
OKAY [ 1.582s]
finished. total time: 9.180s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (250695 KB)...
OKAY [ 7.937s]
writing 'system'...
OKAY [ 1.618s]
finished. total time: 9.561s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (255001 KB)...
OKAY [ 8.069s]
writing 'system'...
OKAY [ 1.592s]
finished. total time: 9.666s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (257746 KB)...
OKAY [ 8.157s]
writing 'system'...
OKAY [ 1.625s]
finished. total time: 9.787s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
sending 'system' (261982 KB)...
OKAY [ 8.288s]
writing 'system'...
OKAY [ 1.703s]
finished. total time: 9.996s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
sending 'system' (262140 KB)...
OKAY [ 8.293s]
writing 'system'...
OKAY [ 1.608s]
finished. total time: 9.907s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.7
target max-sparse-size: 256MB
sending 'system' (247037 KB)...
OKAY [ 7.821s]
writing 'system'...
OKAY [ 1.547s]
finished. total time: 9.375s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.8
target max-sparse-size: 256MB
sending 'system' (262140 KB)...
OKAY [ 8.293s]
writing 'system'...
OKAY [ 1.614s]
finished. total time: 9.912s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.9
target max-sparse-size: 256MB
sending 'system' (219553 KB)...
OKAY [ 6.959s]
writing 'system'...
OKAY [ 1.375s]
finished. total time: 8.341s
C:\Users\SRK\Downloads\NewMoto>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.010s]
finished. total time: 0.011s
C:\Users\SRK\Downloads\NewMoto>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.010s]
finished. total time: 0.013s
C:\Users\SRK\Downloads\NewMoto>mfastboot oem fb_mode_clear
...
OKAY [ 0.003s]
finished. total time: 0.005s
C:\Users\SRK\Downloads\NewMoto>fastboot oem config fsg-id ""
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.056s]
finished. total time: 0.060s
C:\Users\SRK\Downloads\NewMoto>mfastboot reboot
rebooting...
finished. total time: 0.003s
could you or someone assist me in team viewer please?? I really having bad days. no phone from 4 days.
Click to expand...
Click to collapse
These three errors you got which I'm pasting below are normal:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Click to expand...
Click to collapse
But other than that, everything shows it's flashing OK? Yet it still won't boot...
Searching the internet for that " ret=-1" error message, came across this:
https://productforums.google.com/forum/#!topic/nexus/Z-Ek9spUUMk;context-place=topicsearchin/nexus/authorid$3AAPn2wQd-FQicFC7RbavvPMsMOeXIILaxmrMVo3XYrb0P_pWrMw5VVUQIz_Dx8Ty4va61Ty_aMSFj%7Csort:date%7Cspell:false
and this:
https://productforums.google.com/forum/#!topic/nexus/9pgTA6RG85Y
Both were told they probably had hardware failure, most like flash memory.
I'm almost out of ideas. Since all your flashing did seem to go OK, how about now trying to flash TWRP again? You would be replacing stock recovery with a TWRP image. Then with phone off try using the volume + power button to boot to bootloader screen, if it will let you. Then from there you can choose TWRP. Once in TWRP (if you get that far) you can try dragging over a ROM to flash.
But if you are experiencing a hardware failure you probably won't be able to get that far.
I'm generally not very good walking people through things, but here is something to try. It's almost exactly what you've done before, except you will use mfastboot erase for specific partitions before flashing. Do NOT erase the bootloader - it can brick the phone. You shouldn't need to temp root, since your bootloader is unlocked.
From a command prompt, in the directory/folder you have ADB/(m)fastboot:
reminder do NOT erase the bootloader:
Code:
mfastboot flash bootloader bootloader.img
Code:
mfastboot erase boot
mfastboot flash boot boot.img
mfastboot erase recovery
for stock recovery use:
Code:
mfastboot flash recovery recovery.img
for TWRP (download link) use:
Code:
mfastboot flash recovery twrp-3.1.1-mod_2-quark.img
Code:
mfastboot erase system
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot erase cache
mfastboot erase userdata
if you installed TWRP:
Code:
mfastboot reboot-bootloader
then start recovery to let it make the changes to keep it from being replaced, and then reboot
for stock recovery just reboot:
Code:
mfastboot reboot
If this doesn't work it's either failing hardware as ChazzMatt stated, or time to do things you shouldn't.
hitokage004 said:
I'm generally not very good walking people through things, but here is something to try. It's almost exactly what you've done before, except you will use mfastboot erase for specific partitions before flashing. Do NOT erase the bootloader - it can brick the phone. You shouldn't need to temp root, since your bootloader is unlocked.
From a command prompt, in the directory/folder you have ADB/(m)fastboot:
reminder do NOT erase the bootloader:
Code:
mfastboot flash bootloader bootloader.img
Code:
mfastboot erase boot
mfastboot flash boot boot.img
mfastboot erase recovery
for stock recovery use:
Code:
mfastboot flash recovery recovery.img
for TWRP (download link) use:
Code:
mfastboot flash recovery twrp-3.1.1-mod_2-quark.img
Code:
mfastboot erase system
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot erase cache
mfastboot erase userdata
if you installed TWRP:
Code:
mfastboot reboot-bootloader
then start recovery to let it make the changes to keep it from being replaced, and then reboot
for stock recovery just reboot:
Code:
mfastboot reboot
If this doesn't work it's either failing hardware as ChazzMatt stated, or time to do things you shouldn't.
Click to expand...
Click to collapse
thanku for ur help. I just saw this post now. Ill try today and will update you the status.
hitokage004 said:
I'm generally not very good walking people through things, but here is something to try. It's almost exactly what you've done before, except you will use mfastboot erase for specific partitions before flashing. Do NOT erase the bootloader - it can brick the phone. You shouldn't need to temp root, since your bootloader is unlocked.
From a command prompt, in the directory/folder you have ADB/(m)fastboot:
reminder do NOT erase the bootloader:
Code:
mfastboot flash bootloader bootloader.img
Code:
mfastboot erase boot
mfastboot flash boot boot.img
mfastboot erase recovery
for stock recovery use:
Code:
mfastboot flash recovery recovery.img
for TWRP (download link) use:
Code:
mfastboot flash recovery twrp-3.1.1-mod_2-quark.img
Code:
mfastboot erase system
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot erase cache
mfastboot erase userdata
if you installed TWRP:
Code:
mfastboot reboot-bootloader
then start recovery to let it make the changes to keep it from being replaced, and then reboot
for stock recovery just reboot:
Code:
mfastboot reboot
If this doesn't work it's either failing hardware as ChazzMatt stated, or time to do things you shouldn't.
Click to expand...
Click to collapse
Nope.Bad news. Even this didnt work. All this happened because of AEX rom I suppose. Since I flashed that rom, most of the apps were force closing. I thought these bugs might be solved in future updates and continued using it. I shouldnt have flashed that rom. Should have continued RR rom. Huge terrible mistake of mine. I am not blaming the developer.Please dont take this as an offence.I know all this is our own risk and already mentioned at the beginning of the posts.Just Blaming myself...
Thanks for your and @ChazzMatt help anyways.thanku soo much..
RIP my Moto
Edit 1 : Bought new Samsung A9 pro which fulfills my needs with a good battery backup. Goodbye to my Moto Turbo.Also to this forum.
Once again My Heartful thanks to @ChazzMatt and @hitokage004