Related
Hello everyone
I am new here.
I need some assistance with my moto g.
I previously unlocked my Moto G's bootloader but realised that I just wanted it on stock and locked so I didn't damage it, so I managed to relock my
phone's bootloader and got it back to a stock rom.
After installing a system update a few days ago, my phone came back with the
"Warning - bootloader unlocked!" logo after installing a system update.
So I decided to try and reflash the stock firmware and original logo.bin from the XDA Site.
However, my flashes are failing and my moto g is stuck in a bootloop with no rom to boot up to, I have adb minimal fastboot and motorola drivers
/ adb drivers installed.
What happens: I power on the phone into bootloader mode, then I try to flash the ROM I got from droid-developers site, but whenever I try to relock
my bootloader it shows the following:
...
Ready to flash signed images!
OK: (time)
I do fastboot flash partition gpt.bin and I get:
Preflash validation failed!
SST lock failure!
Also trying to issue the command to relock the bootloader gives me
SST lock failure!
I get other errors too when flashing the sparsechunk images, it gives: Invalid PIV signed image! and for motoboot and boot images it gives: Preflash validation failed!
version downgraded for boot.
etc
I cannot recover my stock rom due to these errors, I've searched everywhere (on google) and here and I am desperate to flash the stock rom back and relock bootloader again so I can use the phone.
I am really stuck and my phone will not get out of a bootloop
Any help is really much appreciated as I need to get my phone working so I can use it
You don't need to relock the bootloader. Just follow this tutorial:
http://forum.xda-developers.com/showthread.php?t=2542219
lost101 said:
You don't need to relock the bootloader. Just follow this tutorial:
http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
I followed the tutorial, but when I get to the flashing stage, I get:
Preflash validation failed,
SST lock failure!
And version downraded for gpt.bin
it seems to be failing to flash these files.
What do I need to do?
You need to provide more information for people to help you. Have you upgraded to 4.4.4?
I had a similar issue when rooting my phone, and all I had to do was unplug the phone from the computer, restart the phone and computer, and then try again.
GrammarNazi said:
I had a similar issue when rooting my phone, and all I had to do was unplug the phone from the computer, restart the phone and computer, and then try again.
Click to expand...
Click to collapse
But did you downgrade from 4.4.4 to 4.4.2?
What model do you have?
Can you explain us all the steps?
Thanks
First unlock your bootloader again. You have to downgrade from 4.4.4 to 4.4.3 then to 4.4.2. During the downgrades you have to follow the same kind of firmware (example: 4.4.4 retail EU -> 4.4.3 retail EU -> 4.4.2 retail EU). When you're done if you want you can relock the bootloader.
Hi everyone, I hope you guys can get me a hand with this issue.
My Moto G, is briked. Its with bootloader version 41.18 (Lollipop) and its imposible to downgrade it becouse I get this message
"(bootloader) Preflash validation failed
FAILED (remote failure)¨
But is only that command, all others commands to flash the phone work properly (but I dont have any clue why its imposible to make Lollipop works, and I cant make KitKat runs with an 41.18 bootloader)
At this time, I dont care any more upgrade to Lollipop, I just want my phone back :crying:
Please help.
Thanks for you time.
unlock phone
preflash validation fail happens due to the locked bootloader . Either unlock bootloader to skip boot flash validation checks or flash stock factory image without unlockingbootloader in recovery mode . Standard recovery and factory firmware image .
I had this problem, I eventually took it back to the point of purchase after trying EVERYTHING! Have you tried flashing stock ROM ignoring the preflash validation error?
Sent from my XT1039 using XDA Free mobile app
You would have executed the following command when trying to downgrade to KitKat:
fastboot flash motoboot motoboot.img
It should not be done. Nevertheless, try installing paranoid android via a custom recovery.
fastboot flash recovery cwm-*.img
Once you are on 41.18 bootloader, you cannot flash an older motoboot.img over the existing image.
Even with a Lollipop bootloader, you can flash all images and the phone should boot.
I have an xt1032 and flash stock 4.4.4 Retail US with no problem.
ankushv said:
preflash validation fail happens due to the locked bootloader . Either unlock bootloader to skip boot flash validation checks or flash stock factory image without unlockingbootloader in recovery mode . Standard recovery and factory firmware image .
Click to expand...
Click to collapse
My bootloader is unlocked ("Status Code: 3"), but I cant flash the 41.13 bootloader, neverthles, I can re-flash the 41.18 without problem.
jasond567 said:
I had this problem, I eventually took it back to the point of purchase after trying EVERYTHING! Have you tried flashing stock ROM ignoring the preflash validation error?
Click to expand...
Click to collapse
Yes, if I flash my Stock ROM (Retail LATAM) it's never pass the "Warning Bootloader", just keep there until I turn it off. If I flash an 5.0.2 Rom, when I start the phone, takes me back to the bootloader with "Boot up failed" message
layman806 said:
You would have executed the following command when trying to downgrade to KitKat:
fastboot flash motoboot motoboot.img
It should not be done. Nevertheless, try installing paranoid android via a custom recovery.
fastboot flash recovery cwm-*.img
Click to expand...
Click to collapse
The problem is that I cant flash any recovery, I try CWM and TWRP. Always gives me an errero when I try too boot in to Recovery Mode.
Are you flashing the correct recovery? Try the latest Philz for your model of phone. The xt1032 is also known as falcon.
What errors are you getting when trying to flash recovery in fastboot?
audit13 said:
Once you are on 41.18 bootloader, you cannot flash an older motoboot.img over the existing image.
Even with a Lollipop bootloader, you can flash all images and the phone should boot.
I have an xt1032 and flash stock 4.4.4 Retail US with no problem.
Click to expand...
Click to collapse
Yep, I try installing Lollipop firmwares with "fastboot flash ......" but no one work
I have an XT1040, and there isnt an official 5.0.2 for this version of Moto G, but it should works, no?
audit13 said:
Are you flashing the correct recovery? Try the latest Philz for your model of phone. The xt1032 is also known as falcon.
What errors are you getting when trying to flash recovery in fastboot?
Click to expand...
Click to collapse
You were right! I was flashing a wrong recovery, I have XT1040 and for this one the name is "Peregrine", I already installed CWM and TWRP (both works, but no one read the SD Card)
I found an NIGHTLESS CyanogenMOD 12 for XT1040 but when I try to install it. I get this message (installing de *.zip with TWRP and CWM):
Code:
E: Unable to mount "/data"
E: Unable to mount "/cache"
E: Unable to mount "/system"
E: Unable to mount internal storage
Any ideas? :crying:
iyurcic95 said:
Yep, I try installing Lollipop firmwares with "fastboot flash ......" but no one work
I have an XT1040, and there isnt an official 5.0.2 for this version of Moto G, but it should works, no?
You were right! I was flashing a wrong recovery, I have XT1040 and for this one the name is "Peregrine", I already installed CWM and TWRP (both works, but no one read the SD Card)
I found an NIGHTLESS CyanogenMOD 12 for XT1040 but when I try to install it. I get this message (installing de *.zip with TWRP and CWM):
Code:
E: Unable to mount "/data"
E: Unable to mount "/cache"
E: Unable to mount "/system"
E: Unable to mount internal storage
Any ideas? :crying:
Click to expand...
Click to collapse
First, format /data/media
Then, /system
Then, /cache
Then, try to install the ROM.
Are you running GPE version of Lollipop on your xt1040? If you are, you may need to re-install stock 4.4.4, including flashing gpt.bin because the partition sizes may be slightly different between stock Lollipop and GPE Lollipop.
layman806 said:
First, format /data/media
Then, /system
Then, /cache
Then, try to install the ROM.
Click to expand...
Click to collapse
I'll try, but, where I should do that? I'm kind of lost with all this.
audit13 said:
Are you running GPE version of Lollipop on your xt1040? If you are, you may need to re-install stock 4.4.4, including flashing gpt.bin because the partition sizes may be slightly different between stock Lollipop and GPE Lollipop.
Click to expand...
Click to collapse
No, I dont install the GPE in the XT1040. Maybe could be what are you saying. Yesterday, I cant remember what I was trying to install and in fastboot, while I was flashing, said "Image is too large", but in de DOS windows on PC, it says "OK"
The issue is that I cant do a downgrade of gpt and de motoboot.
So, I should install 4.4.4 KitKat, (without flashing those 2 files) and try with the recovery installing CyanogenMOD 12? Or CMod12 not uses 41.18 bootloader?
Edit: I think that I cant install KitKat, bootloader gives me "Image is too large", the DOS windows says "OK", but Im thinking that really its not OK.
I install """succesfully""" an 5.0.2 Retail of Brazil, but for the XT1033 version. Really, I dont know if is GPE, but I was able to install all the files and the fastboot dont showme the "Image is to large" message.
Edit2: Withi is command in Terminal of TWRP
mke2fs -T ext4 /dev/block/mmcblk0p8
Click to expand...
Click to collapse
When I try to install the CyanogenMOD's zip, says "Unable to mount /system". So I think I fix the problem with /data. But if I'm right, now what?
Since your bootloader is unlocked and you never flashed a GPE ROM, go back to the start.
If you want to install a custom ROM, flash the recovery for your phone. If you get an error message in fastboot, write it down and post it here.
If you want to flash back to a stock ROM, are you flashing every partition except motoboot.img? Are you erasing cache and userdata at the end?
audit13 said:
Since your bootloader is unlocked and you never flashed a GPE ROM, go back to the start.
If you want to install a custom ROM, flash the recovery for your phone. If you get an error message in fastboot, write it down and post it here.
If you want to flash back to a stock ROM, are you flashing every partition except motoboot.img? Are you erasing cache and userdata at the end?
Click to expand...
Click to collapse
I cant flash any stock ROM for my phone yet becouse, stocks ROMs are until 4.4.4 KitKat using bootloader 41.13. and y cant downgrade my 41.18 bootloader
I am trying to instal CyanogenMOD 12 from my recovery (CWM and TWRP works properly) but I get this message
Code:
"E: Unable tu mount /system"
Here is a photo of the error
http://imageshack.com/a/img661/1201/n9u9Jy.jpg
Edit: I try "fastboot erase system" and "fastboot format system"... Both are done succesfuly, but I stil geting the same error. (Also, I cant mount /storage/sdcard1)
Where did you get the Lollipop bootloader?
Did you try to use fastboot or mfastboot to flash a stock ROM. I have an xt1032 with 41.18 and I can flash stock 4.4.4 ROM.
audit13 said:
Where did you get the Lollipop bootloader?
Did you try to use fastboot or mfastboot to flash a stock ROM. I have an xt1032 with 41.18 and I can flash stock 4.4.4 ROM.
Click to expand...
Click to collapse
I get it when I flash with fastboot an firmware from Brasil wich have 5.0.2.
I will try installing the firmware you have, could you paste me a link please? Is with Recovery installation or with fastboot?
You need to download the stock 4.4.4 firmware for your phone and follow this guide: http://forum.xda-developers.com/moto-g/general/restore-to-kitkat-lollipop-moto-g-t3011553
Did you install the right recovery? Try using Philz for the peregrine to install custom ROM: http://forum.xda-developers.com/moto-g/4g-development/recovery-unofficial-philz-touch-t2827332
audit13 said:
You need to download the stock 4.4.4 firmware for your phone and follow this guide: http://forum.xda-developers.com/moto-g/general/restore-to-kitkat-lollipop-moto-g-t3011553
Did you install the right recovery? Try using Philz for the peregrine to install custom ROM: http://forum.xda-developers.com/moto-g/4g-development/recovery-unofficial-philz-touch-t2827332
Click to expand...
Click to collapse
I followed the first guide and in the DOS window where you put the commands "fastboot flash...." everything goes "OK", but in the phone, the fastboot says "Image is to large" when is going to flash the "system" so Im thinking that its not flashing really
After reboots, the phones dont go further than "Warning Bootloader Unlocked"
I installed Philz for Peregrine, I try to install 2 customs ROMs differetns for XT1040 and I get
Code:
Opening update package...
Installing update...
detected filesystem ext4 for /dev/block/plataform/msm_sdcc.1/by-name/system at /system: invalid argument
unmount of /system failed; no such volume
detected filesystem f2fs for /dev/block/plataform
E: Error in /tmp/update.zip
(Status 1)
Installation aborted.
I 'm about to give up
After flashing the gpt.bin file, type fastboot reboot-bootloader and continue flashing. Maybe this will help.
did you find a way to fix it yet?
im having the same issue. and not able to do anything, i tried flashing cm12 didnt work.
Hey guys
First of all: I think, I ****ed up.
So I was on a custom 5.0.2 Rom and it was really buggy (forceclose, lowmemory, etc.) and so I decided,
that it would be a good idea to go back to stock and flash Slimrom. As far, as I remember, I did the following:
1. Go into my custom recovery and delete everything (I know, I'm an idiot :crying: )
2. Go into fastboot and flash 4.4.4 via a script on my PC
3. Get problems, which I somehow resolve (pls don't ask me, how. I was pretty drunk last night.)
4. 4.4.4 is up and running. I download the stock 5.0.2 OTA files form XDA and try to flash them with TWM.
5. Everything is super buggy under 5.0.2, so I decide to flash back 4.4.4 and use the stock recovery.
6. 5.0.2 runs just fine and I begin to prepare for the custom Slimrom.
7. Install custom recovery, download Slimrom and GApps.
8. Flash Slimrom and get some weird error, that /system and /date can't be mounted. Everything ****ed up from there on...
9. Try to flash the stock 4.4.4 from before (using the script). Doesn't work, gets stuck on bootloader unlocked messege.
10. Try random **** (literally everything, I can find on the web.)
11. Write this post.
Some information, you could need:
XT1032
Fastboot version: 41.18
Unlocked (Status Code: 3)
Boots into recovery
Recovery is TWM 2.8.6.0
Things, I've tried: Flash the stock 4.4.4 system and then flash a custom rom, using TWM Didn't work
Reflash the stock "Kernel Module", found under /showthread.php?t=2649763 Didn't work
Flash an alternate "bootloader unlocked" Screen Didn't work
Please help me, guys :fingers-crossed:
Did you try manually flashing each partition for the 4.4.4 stock ROM? Since you are on a 41.18 bootloader, you should be able to flash every file except motoboot.
audit13 said:
Did you try manually flashing each partition for the 4.4.4 stock ROM? Since you are on a 41.18 bootloader, you should be able to flash every file except motoboot.
Click to expand...
Click to collapse
First of all, thank you for your quick response!
I was able to flash everything without any errors, but unfortunately, it is still stuck on the Warning screen.
Did you erase cache and userdata in fastboot?
audit13 said:
Did you erase cache and userdata in fastboot?
Click to expand...
Click to collapse
Yes, but it did not help
Edit: it gives me an error, when flashing gpt.bin.
it says:
(bootloader) Preflash validation failed
FAILED (remote failure)
So all files flahed except motoboot and gpt? The motoboot file from the stock 4.4.4 flash won't install becuase the 4.4.4 bootloader is older than the bootloader currently installed on your phone.
Even if the gpt.bin file doesn't flash, it doesn't always prevent the phone from booting a stock ROM.
Was the 5.02 ROM the GPE?
audit13 said:
So all files flahed except motoboot and gpt? The motoboot file from the stock 4.4.4 flash won't install becuase the 4.4.4 bootloader is older than the bootloader currently installed on your phone.
Even if the gpt.bin file doesn't flash, it doesn't always prevent the phone from booting a stock ROM.
Was the 5.02 ROM the GPE?
Click to expand...
Click to collapse
When trying to flash the motoboot.img, it says "permission denied" and when trying to flash the gpt.bin, it says "(bootloader) Preflash validation failed FAILED (remote failure)".
The 5.0.2 ROM was the OTA update, which in my case, is the normal motorola one. I did convert my device to a GPE, when Lollipop for the moto G GPE became availible (arround december),
but went back to the normal ROM to get the 5.0.2 OTA.
Thank you for your help :laugh:
Ok, I have used this: http://forum.xda-developers.com/moto-g/development/rom-4-4-4-stock-eu-1-click-easy-flash-t2879757 and i'm back in Stock 4.4.4. I have got no idea, how that worked but it's done
That's great that it worked.
If you want to get 5.02 OTA update, be sure to update Motorola Update Services app in the Play store before checking for updates.
Stock, unrooted xt1540. Got the update notification this morning, so excited. After updating, it's boot looping and the M logo is the furthest it can go.
Tried to fastboot flash back to old 5.1.1 factory image, "image validation failed". Maybe because boot loader got updated and won't roll back?
All I can think of now is to wait for the 6.0 factory image and try that again, but I may end up waiting for it too long.
Any suggestions? Thanks!
What about the images at http://forum.xda-developers.com/2015-moto-g/general/ota-moto-g3-marshmallow-ota-links-t3284308
Try in fastboot clear the cache and data ...
have you tried using twrp to just install a cm rom or something similar?
worst case scenario you can use twrp to force the soak test images onto their respective partitions. if your bootloader was updated the soak test will run...even if it bootloops for any reason, then at least you've taken one step forward again.
MrTooPhone said:
What about the images at http://forum.xda-developers.com/2015-moto-g/general/ota-moto-g3-marshmallow-ota-links-t3284308
Click to expand...
Click to collapse
I wish I could resume the OTA, even manually, but right now I can only go to bootloader, not even the stock recovery....Thanks for the idea, though! Really appreciate it.
hp420 said:
have you tried using twrp to just install a cm rom or something similar?
worst case scenario you can use twrp to force the soak test images onto their respective partitions. if your bootloader was updated the soak test will run...even if it bootloops for any reason, then at least you've taken one step forward again.
Click to expand...
Click to collapse
I just tried flash in the twrp.img, got declined by bootloader again...
Now is there factory images for the soak test? Thanks!!
lexer98 said:
Try in fastboot clear the cache and data ...
Click to expand...
Click to collapse
clearing cache went through, but clearing data failed. Rebooting to bootloader mode and try returning to stock again, still no go...
In fastboot mode, I can flast logo, fsg, NON-HLOS, bootloader, recovery -- all from 5.1.1 factory image, but when I tried to flash boot or system chunks, it says:
D:\Desktop\g\Mfastboot>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (262141 KB)...
OKAY [ 10.573s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 11.042s
Is my only option to wait for the MM factory image....
alvin612 said:
I just tried flash in the twrp.img, got declined by bootloader again...
Now is there factory images for the soak test? Thanks!!
Click to expand...
Click to collapse
Well....yes and no.
http://forum.xda-developers.com/201...-devs-moto-g3-xt1540-soak-test-files-t3255643
The images all flash in fastboot except the system one, which requires using adb shell while booted to twrp. You have to use a dd command to force the system.img into the correct partition.
Earlier today I had to give up on this osprey because of limited bandwith for fix.
Thanks again for everyone's help!!
My phone got bricked after trying to downgrade from MM to LP
Hello, yesterday I was trying to downgrade from MM to LP using Fastboot and by mystake I flashed "fastboot flash partition gpt.bin" and it failed, the others commands failed as well, after that I was unable to turn on my device, it only let me access to Bootloader Mode and also shows the battery charging, cannot access to recovery, and it shows black screen when I try to turn it on.
My phone is completely stock, It has neve been rooted, stock recovery. Its a Moto G XT1540. the Bootloader is locked.
Is there a way to bring my phone back to life? What can I do?
JulesSDK said:
Hello, yesterday I was trying to downgrade from MM to LP using Fastboot and by mystake I flashed "fastboot flash partition gpt.bin" and it failed, the others commands failed as well, after that I was unable to turn on my device, it only let me access to Bootloader Mode and also shows the battery charging, cannot access to recovery, and it shows black screen when I try to turn it on.
My phone is completely stock, It has neve been rooted, stock recovery. Its a Moto G XT1540. the Bootloader is locked.
Is there a way to bring my phone back to life? What can I do?
Click to expand...
Click to collapse
I contacted Motorola. Warranty covers my situation. Going to ask for a replacement.
JulesSDK said:
Hello, yesterday I was trying to downgrade from MM to LP using Fastboot and by mystake I flashed "fastboot flash partition gpt.bin" and it failed, the others commands failed as well, after that I was unable to turn on my device, it only let me access to Bootloader Mode and also shows the battery charging, cannot access to recovery, and it shows black screen when I try to turn it on.
My phone is completely stock, It has neve been rooted, stock recovery. Its a Moto G XT1540. the Bootloader is locked.
Is there a way to bring my phone back to life? What can I do?
Click to expand...
Click to collapse
Unlock the bootloader and then try flashing. I was in a similar situation once, was getting failed messages when trying to flash official signed factory images. Unlocked the bootloader and then tried to flash and voila, everything flashed smoothly. No harm in trying unless you are worried about warranty.
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
sticktornado said:
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
Click to expand...
Click to collapse
I know, I flashed the correct number of system images that were in the zip file.
Thanks,
rent0n said:
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
Click to expand...
Click to collapse
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
rent0n said:
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
Click to expand...
Click to collapse
I tried that and it didn't work. When I try to go into recovery mode the phone keeps bootlooping.
One thing I noticed is that when I try to format cache or userdata I get this error:
Code:
$ fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.013s
I think there might be something wrong with the file system in my partitions. How can I manually format my partitions?
Thanks,
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
therealduff1 said:
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
Click to expand...
Click to collapse
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
rent0n said:
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
Click to expand...
Click to collapse
What os were you running when the phone screwed up ?
therealduff1 said:
What os were you running when the phone screwed up ?
Click to expand...
Click to collapse
I was running 5.1.1 when I got the notification for the 6.0 update.
I've noticed that trying to flash 5.1.1 firmware with fastboot gives me errors (preflash validation failed) while the 6.0 work "fine" (i.e.: I get OKAY after every step but then the phone is always stuck in a bootloop).
Thanks!
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
therealduff1 said:
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
Click to expand...
Click to collapse
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
rent0n said:
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
Click to expand...
Click to collapse
Have you gave this a try?
heavy_metal_man said:
Have you gave this a try?
Click to expand...
Click to collapse
Yes, no luck unfortunately.
I think I might have flashed the 5.1.1 bootloader after all - is there any way to recover from there?
Thanks,
Bump!
Does anyone have any other suggestion please?
Thanks,
Last bump
I'm going to sell this on eBay as non-working then unless someone comes up with a clever solution?
Thanks for your help!
Try flashing once more starting with the gpt.bin (that should hopefully take care of raw partition error) and skipping the bootloader altogether. Also, may be worthwhile to try mfastboot.exe instead of fastboot.exe.
I have this same issue, but I haven't flash 5.1.1 Files, I Only tried with 6.0 Brazil Retail.
I also tried to flash gpt to get rid of the "raw" partition, everything goes ok but still displaying that error. Anyone can help?
I got the same problem with my Moto E 2015... If I find a solution I will reply it in this topic..