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.
Related
OTA softbricked? the device of my friend
Although the bootloader is unlocked, I was able to flash new firmware with fastboot with succes!! The device is now booting 4.1.1 (10.4.2.20)again
So, I tried to flash TWRP through fastboot (it's still responding to fastboot), but that fails:
Code:
FAILED <remote: <InvalidState>>
Thinking it is because the bootloader is locked, installed unlocking tool. Run it, at the last step, where you have to click the -normally- bar with image of locked lock to unlock, I get the dreaded network error, more importantly: the lock image is UNlocked
What could be the case now?
n/m http://forum.xda-developers.com/showthread.php?t=2037266
fastboot is available, flashing is not
Hi
I have soft-bricked my Moto G 4G, as the title says. I decided to use the nandroid backup from my working Moto G 4G & flashed it to the one which has now since bricked. (kinda lazy XD)
Its also locked too -_- So i can flash signed motorolla img's but unsigned do not work. I have tried to find official 4.4.4 images but I've had no luck in flashing them. So now i get constant error messages when trying to flash the same system images, or boot.img to the system.
I have access to Fastboot & only Fastboot. The issues i have are:
When booting into fasboot i get:
Fastboot Reason: UTAG "bootmode" configured as fastboot.
When trying to unlock the bootloader, however i can get the unlock token by doing "fastboot oem get_unlock_data then paste that on the motorolla site.
But as soon as i type in fastboot oem unlock i get the following message:
fastboot <bootloader> oem unlock disabled!
I also get:
Invalid PIV signed system image
hab check failed for system
I can flash the following successfully:
gpt.bin
motoboot.img
logo logo.bin
fsg.mbn
NON-HLOS.bin
Because I've flashed the other system's rom to this phone, ALL the information under "Barcodes" is identical to that of my working phone. Even the fastboot code thats identical too. So even when i request a unlock token, sure it works, but the site thinks that its a call from my working phone so it gives out the incorrect unlock code, so thats why i think the unlock is disabled. Either way this is a really irritating situation, which i am having trouble trying to solve.
I wonder if I'm going to have to flash a blank flash to get it back to working state.
Hopefully if i can get the bootloader unlocked, id be back in business. :fingers-crossed:
Any help would be greatly appreciated.
Thanks
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.
I'm unable to flash stock rom on my moto g turbo xt1557, with the fastboot method,
the actual problem is when i try to flash gpt.bin in the command getting the error
preflash validation failed remote failure.
since i've flashed this rom earlier it was succesfull at that time then i have installed twrp to try lineage os.
as now i want to revert back to stock , im unable due to the following error.
i'm trying the latest version of the stock rom which is availables\ still getting the error.
Please help.:crying :crying::crying:
Thanks :good::good::good:
vishal4950 said:
I'm unable to flash stock rom on my moto g turbo xt1557, with the fastboot method,
the actual problem is when i try to flash gpt.bin in the command getting the error
preflash validation failed remote failure.
since i've flashed this rom earlier it was succesfull at that time then i have installed twrp to try lineage os.
as now i want to revert back to stock , im unable due to the following error.
i'm trying the latest version of the stock rom which is availables\ still getting the error.
Please help.:crying :crying::crying:
Thanks :good::good::good:
Click to expand...
Click to collapse
Just skip that and do all commands,
Ojas25.8 said:
Just skip that and do all commands,
Click to expand...
Click to collapse
Dude. You mean to skip the flashing of gpt.bin
I have tried that too. Skipping the gpt.bin makes firmware flashing successful.
But after that problem is that phone get stuck on boot logo. Waited untill 30mins still no response.
vishal4950 said:
Dude. You mean to skip the flashing of gpt.bin
I have tried that too. Skipping the gpt.bin makes firmware flashing successful.
But after that problem is that phone get stuck on boot logo. Waited untill 30mins still no response.
Click to expand...
Click to collapse
Did you factory reset in stock recovery first? It's essential...