it was in version 5.0.2, with the unlocked bootloader and the camera does not opened, thus did the restoration with fastboot to the same version more displays an error after the restoration process "failed to validate system image - Fasboot Reason: Fail- through from the normal boot mode "not out of this error and not start the system, what do I do?
Downloaded the ROM in this site filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=2
I am Brazilian and smartphone model Moto G xt1033 16GB
Could you tell, what error you are receiving and what system Installation you are trying. are you upgrading to 5.0.2??
bgeke said:
Could you tell, what error you are receiving and what system Installation you are trying. are you upgrading to 5.0.2??
Click to expand...
Click to collapse
it was in version 5.0.2, with the unlocked bootloader and the camera does not opened, thus did the restoration with fastboot to the same version more displays an error after the restoration process "failed to validate system image - Fasboot Reason: Fail- through from the normal boot mode "not out of this error and not start the system, what do I do?
Downloaded the ROM in this site filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=2
I am Brazilian and smartphone model Moto G xt1033 16GB
restaurapc said:
it was in version 5.0.2, with the unlocked bootloader and the camera does not opened, thus did the restoration with fastboot to the same version more displays an error after the restoration process "failed to validate system image - Fasboot Reason: Fail- through from the normal boot mode "not out of this error and not start the system, what do I do?
Downloaded the ROM in this site filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=2
I am Brazilian and smartphone model Moto G xt1033 16GB
Click to expand...
Click to collapse
Not sure
So phone is not booting up now??
Download your Complete firmware and Follow the steps given here http://forum.xda-developers.com/showthread.php?t=2700502. If your firmware have different files, command will vary. Search in xda or google.
This is known issue and I think no exact solution is found. I'm not responsible for any damage. If you get it to work. then post it here. But give more details about your situation.
bgeke said:
Not sure
So phone is not booting up now??
Download your Complete firmware and Follow the steps given here http://forum.xda-developers.com/showthread.php?t=2700502. If your firmware have different files, command will vary. Search in xda or google.
This is known issue and I think no exact solution is found. I'm not responsible for any damage. If you get it to work. then post it here. But give more details about your situation.
Click to expand...
Click to collapse
device is locked status code 2 , as for the unlock code 3 ?
restaurapc said:
device is locked status code 2 , as for the unlock code 3 ?
Click to expand...
Click to collapse
It means bootloader is locked.
bgeke said:
It means bootloader is locked.
Click to expand...
Click to collapse
you need to unlock to install system?
restaurapc said:
you need to unlock to install system?
Click to expand...
Click to collapse
Not required to unlock bootloader for flashing stock ROM. Just try to flash the whole firmware with mfastboot.
bgeke said:
Not required to unlock bootloader for flashing stock ROM. Just try to flash the whole firmware with mfastboot.
Click to expand...
Click to collapse
I'm downloading the rom ASIARETAIL_XT1033_5.0.2_LXB22.46-28_cid7_CFC.xml.zip, if not go right setup with the fastboot is possible to do using the TWRP recovery?
soon put the result of the installation of fastboot
Related
[HELP] Black Screen Even after Restoring to stock firmware & Cannot relock Bootloader
My phone - Moto G XT1033 Asia Dual Sim
I updated my phone to 5.0.2 official via OTA.. And then unlocked by bootloader...
Everything was working fine, after few days, phone suddenly stopped working.
I restarted my phone and after that, every time after moto boot animation, it always gets stuck at a black screen, showing nothing
I tried all the tutorial of Reverting back to stock firmware.. I tried flashing following files via both fastboot and mfastboot... Everything gets flashed successfully without any error.
First I tried 5.1. file named - XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml
Then 5.0.2, ASIARETAIL_XT1033_5.0.2_LXB22.46-28_cid7_CFC.xml
Then 4.4, ASIA-DS_4.4.4_KXB21.14-L1.40_34_cid7_CFC_1FF.xml
Still same problem persists.. Phone does not starts after moto boot animation and stucks at a black screen..
I tried to downgrade to 4.3, tried to flash this file fastboot_falcon_asia_ds_user_4.3_14.10.0Q3.X-84-7-LCG-4_4_release-keys-cid7-AsiaRetail_03.tar, but it always show prevalidation of firmware failed.
Screenshots of my bootloader and the blackscreen have been included....
Also I tried relocking my bootloader several times.. But after flashing a stock firmware, there comes a screen where is it written locked and when I reboot to the bootloader, it still shows unlocked..
This is how my bootloader looks right now http://postimg.org/image/4w8zrwgrp/
Bootloader Unlocked Warning http://postimg.org/image/o76nd4qux/
Moto boot animation works perfectly http://postimg.org/image/m3w85gr21/
And then this black screen comes and phone stucks here. http://postimg.org/image/5775d1ji1/
Fastboot results in Cmd after flashing Stock 5.0.2 http://postimg.org/image/a6ksy5nyv/
http://postimg.org/image/uf86jvn9z/
http://postimg.org/image/5zzyitod3/
Please please please help me now... I have been asking since a long time.. And have described my problem clearly this time..
Is there anyone who can help me
Somebody please help me
Not getting an answer is usually a sign that you didn't provide enough information. Most people who could probably help you will ignore your question if it's incomplete.
happiy91 said:
Today I tried restoring to the stock firmware 5.1.1 ( Moto g XT1033 Asia Retail, which my phone had before going dead). I flashed all the files correctly with mfastboot... Everything went right...
Click to expand...
Click to collapse
Post a full console log of your fastboot commands and the corresponding output.
happiy91 said:
I have unloacked bootloader.. And I think since before going dead usb debugging was not on,, I am unable to flash custom recoveries.
Click to expand...
Click to collapse
USB debugging affects only Android and is not required for flashing custom recoveries.
Finally. Somebody replied.. Thanks a lot..
I will just upload the console output and other things in detail tomorow morning..
_that said:
Not getting an answer is usually a sign that you didn't provide enough information. Most people who could probably help you will ignore your question if it's incomplete.
Post a full console log of your fastboot commands and the corresponding output.
USB debugging affects only Android and is not required for flashing custom recoveries.
Click to expand...
Click to collapse
I have updated the details.. PLease check it now.. And help me please
Sorry, I don't know how to fix your black screen issue. However I've seen others reporting a similar problem (but didn't read the threads). And I've read that downgrading your bootloader can brick your device. You also said that flashing the ROMs worked without errors, but you didn't provide a log of your fastboot commands and the output that you got.
_that said:
Not getting an answer is usually a sign that you didn't provide enough information. Most people who could probably help you will ignore your question if it's incomplete.
Post a full console log of your fastboot commands and the corresponding output.
USB debugging affects only Android and is not required for flashing custom recoveries.
Click to expand...
Click to collapse
_that said:
Sorry, I don't know how to fix your black screen issue. However I've seen others reporting a similar problem (but didn't read the threads). And I've read that downgrading your bootloader can brick your device. You also said that flashing the ROMs worked without errors, but you didn't provide a log of your fastboot commands and the output that you got.
Click to expand...
Click to collapse
My phone is not bricked... Output of fastboot commmands in Command prompt have been already included in the post.. I have included the screenshots..
flash custom recoery and rom
if you by any chance downgraded the bootloader (fastboot flash motobot......) in your previous flash attempts there is a chance you have hard bricked your device.
and there is no point locking/unlocking bootloader (fastboot oem unlock/lock) once its unlocked. the only reason you are able to flash stuff you have is because the bootloader is unlocked. and i'm not sure how well you can lock a bootloader thats unlocked.
incase you have hard bricked your device refer; https://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788
hello
i've bought used moto g 2015 from spain.
the problem is that the device is locked with status code 0.
i've been trying to unlock it, but with no luck.
everything gives the error failed(remote failure)
recently i've used windroid toolkit to unlock bootloader and install twrp like in some tutorials, the app says it's done, but after i enter a recovery the phone hangs and boots again to fastboot.
any help will be appreciated
EDIT:
invoking "mfastboot flash partition gpt.bin" command gives the error too so i am unable of installing stock firmware too
EDIT2:
i've successfully installed stock package but there is still a problem - boot loop.
you need to flash stock rom to remove boot loop.
here is the link
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
sachin09 said:
you need to flash stock rom to remove boot loop.
here is the link
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Click to expand...
Click to collapse
I have already flashed the rom but now i think it could be a bad package. My phone is from spain and i installed before:
XT1541_OSPREY_ORAES_6.0_MPI24.65-33_cid7_subsidy-DEFAULT_CFC.xml
now i'm downloading
XT1541_OSPREY_RETES_6.0_MPI24.65-33_cid7_subsidy-DEFAULT_CFC.xml.zip
is there any way to find out which package should i use for sure?
the last package i mentioned doesnt change anything. phone boots to bootloader not to system.
any news i have the same thing with my device everything was flashed but i get boot faillure ??
nothing... i'll get my money back i guess
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
spacezork said:
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
Click to expand...
Click to collapse
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
the ljubich said:
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
Click to expand...
Click to collapse
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
spacezork said:
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
Click to expand...
Click to collapse
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
the ljubich said:
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
Click to expand...
Click to collapse
Sorry for my confusion with adb/sideload - from what I understand I need both to be able to connect to my device (correct me if im wrong). In the bootloader menu I see "flashing_unlocked" which I believe confirms my bootloader being unlocked, but then at the top of the text right under the dead android guy I see "AP Fastboot Flash Mode (Secure)" could that be an issue?
I can retry downloading the recovery from the TWRP site, but I know I'm downloading the official one already, just can't put my finger on why I'm getting that error message if others are doing it successfully.
thanks for helping :good:
Do you have the Verizon model?
samwathegreat said:
Do you have the Verizon model?
Click to expand...
Click to collapse
I have the canadian BELL model XT1650-03
spacezork said:
I have the canadian BELL model XT1650-03
Click to expand...
Click to collapse
You're at the bootloader, it says Flashing Unlock so yes your bootloader is unlocked and you should be able to flash TWRP no problem.
Did you recently install this .45 firmware? Are you sure that TWRP wasnt actually flashed? I see lots of errors like this from the bootloader and its usually just rubbish.
The twrp does not show the actual memory value of my cell phone and does not let me paste ROM backup, from insufficient memory? how to support it?
I updated my phone to .45 when I bought the phone I believe 1-2 weeks ago, it's definitely NOT flashed as the flashing process runs for 0.2 seconds and fails. I can even boot in the stock recovery afterwards confirming that nothing flashed. I wish I knew what I was doing wrong? possibility of drivers not installed properly?
Before I try and flash recovery I check USB debugging, OEM is unlocked, don't verify ADB files and accept Unknown sources. Is there anything I'm missing?
What if fastboot boot twrpname.img
It's really weird anyway...
enetec said:
What if fastboot boot twrpname.img
It's really weird anyway...
Click to expand...
Click to collapse
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
spacezork said:
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
Click to expand...
Click to collapse
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
enetec said:
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
Click to expand...
Click to collapse
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
spacezork said:
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
Click to expand...
Click to collapse
Right, bootloader screen. Enter on it by key-comb... not by command...
Even the real flash take same time... Sending seems to work, is something on verify that doesn't "like" it...
Try to download again recovery and/or check its MD5...
if reading correctly (and what I told you yesterday) command is
fastboot flash recovery recovery.img
and not
fastboot flash recovery.img
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Troll amiga said:
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Click to expand...
Click to collapse
try following this instructions: http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
and download eu rom from here: https://mirrors.lolinet.com/firmware/moto/griffin/official/RETEU/
i don't know from which ROM you are coming, don't know if downgrading works, but this was onl RETEU ROM i could find.
I have the exact same phone and I've upgraded to Nougat but I got my TWRP working. You need an unlocked bootloader and after upgrading to nougat, the option "unlock OEM" need to be enabled again.
I've used this TWRP : https://dl.twrp.me/griffin/twrp-3.0.2-0-griffin.img.html
Also I tried to only boot on it at first with the command fastboot boot twrp.img then I saw it was working, I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
cilk said:
...I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
Click to expand...
Click to collapse
Yeessss... I don't know how could I forgot it!!! :silly:
The message (I forgot I received too...) is *only* to indicate that recovery is not signed! But before there is a clear "Done" confirming the flash!
Just boot on it!
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Nixonkai417 said:
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Click to expand...
Click to collapse
Give the all required information like Brand, model number in your post first.
Huawei honor 5x kiwi L24, I can't really acces the phone so finding some information is impossible. My main issue is when I boot it's failing to verify the Boot.img , recovery.img and system.img . I don't exactly know what all information I can give you
Nixonkai417 said:
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Click to expand...
Click to collapse
First open the tool
Select the update.app file
Then press Ctrl and select the imgs you want
And then right click and click extract selected
Like in here
https://up.harajgulf.com/imagef-149893652739431-png.html
-Hope- said:
First open the tool
Select the update.app file
Then press Ctrl and select the imgs you want
And then right click and click extract selected
Like in here
https://up.harajgulf.com/imagef-149893652739431-png.html
Click to expand...
Click to collapse
I have already done that, I've tried flashing it via SP flash tool but nothing, it won't show up. I've downloaded correct drivers and done what I could but my phone shows up as Lemobile android adb interface. It sometimes shows as a disk drive as well.
When I run CMD command (fastboot flash oem info) it shows everything but the recovery.img system.img and boot.img need verification how can I verify them without the debugging bridge active on the phone.
Nixonkai417 said:
I have already done that, I've tried flashing it via SP flash tool but nothing, it won't show up. I've downloaded correct drivers and done what I could but my phone shows up as Lemobile android adb interface. It sometimes shows as a disk drive as well.
When I run CMD command (fastboot flash oem info) it shows everything but the recovery.img system.img and boot.img need verification how can I verify them without the debugging bridge active on the phone.
Click to expand...
Click to collapse
What do you mean sir
Imgs are already verified cause they are official
And you don't need USB debug in fastboot mode
Your device is not has mtk processor so it won't work
-Hope- said:
What do you mean sir
Imgs are already verified cause they are official
And you don't need USB debug in fastboot mode
Your device is not has mtk processor so it won't work
Click to expand...
Click to collapse
I rooted my phone and was running xenon HD on my Huawei honor 5x, in the midst of switching ROMs I accidently targeted a TWRP recovery.img with the ROM and Gapps.
So what my phone dose now is when it powers on it an all green screen with a red box and a blue box. After a second it come up with " recovery image verify failed, please update to verified images." I can enter fastboot&rescue mode and a Huawei erecovery, but when i do try to download the recovery via WIFI it says package failure.
Nixonkai417 said:
I rooted my phone and was running xenon HD on my Huawei honor 5x, in the midst of switching ROMs I accidently targeted a TWRP recovery.img with the ROM and Gapps.
So what my phone dose now is when it powers on it an all green screen with a red box and a blue box. After a second it come up with " recovery image verify failed, please update to verified images." I can enter fastboot&rescue mode and a Huawei erecovery, but when i do try to download the recovery via WIFI it says package failure.
Click to expand...
Click to collapse
What happens when you try flashing through fastboot
Assuming that your bootloader is unlocked have you tried reflashing twrp?
-Hope- said:
What happens when you try flashing through fastboot
Assuming that your bootloader is unlocked have you tried reflashing twrp?
Click to expand...
Click to collapse
I had unlocked my bootloader but some research I was doing says, when you accidently flash wrong images it can relock the bootloader. I lost the original bootloader code and i don't exactly have the box anymore, so getting a new code will be difficult.
Nixonkai417 said:
I had unlocked my bootloader but some research I was doing says, when you accidently flash wrong images it can relock the bootloader. I lost the original bootloader code and i don't exactly have the box anymore, so getting a new code will be difficult.
Click to expand...
Click to collapse
As long as the bootloader says 'phone is unlocked' then its ok
-Hope- said:
As long as the bootloader says 'phone is unlocked' then its ok
Click to expand...
Click to collapse
I'm my case the bootloader has relocked, so in green it say phone status: locked.
Nixonkai417 said:
I'm my case the bootloader has relocked, so in green it say phone status: locked.
Click to expand...
Click to collapse
I've reread your previous post and you didn't mentioned what happens in the cmd window when trying to flash the files?
-Hope- said:
I've reread your previous post and you didn't mentioned what happens in the cmd window when trying to flash the files?
Click to expand...
Click to collapse
(REMOTE: command not allowed)
I have already sent an email to Huawei support, just waiting on a response to see if they can give me another unlock code. If I'm unable to unlock the boot loader again with the codes, what's my options for unlocling the boot loader without Huawei's help.
Hi! My old phone is booting into fastboot mode, when I try to boot normally I get a black screen, the "Power off" button appears when I hold the power button. The bootloader is not unlocked and the phone was never rooted. Wiping the user partition does not help. It is visible in fastboot mode and I can enter stock recovery, though trying to adb sideload a stock rom returns an error (footer is wrong; signature verification failed). Trying to fastboot boot twrp or recovery.img doesn't work either. I've ran out of ideas, what should I do to get this phone to work?
Try flashing the stock ROM with fastboot. I'm pretty sure ADB doesn't let you flash onto your phone because using your phone with ADB means that it's still powered on - which can cause some issues. You can also try and unlock your bootloader through fastboot, and then flash a recovery and custom ROM.
Both failed. I attached the errors I recieved.
crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try "fastboot bootloader unlock", maybe. Also: Is there a flashall.bat in the stock ROM folder? If there is: Connect your device while in fastboot, and double-click it.
crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try this maybe. I know you can't wipe through the stock ROM, so, try the command: "fastboot -w". That'll wipe everything off the device.
[INDEX][Osprey][Merlin] Moto G Factory Firmware Images
Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own. Moto G (3rd Gen) Factory Firmware Images - Provided by Firmware TEAM - Please report broken links. New Mirrors welcome...
forum.xda-developers.com
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
crepper4454 said:
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
Click to expand...
Click to collapse
Try this: https://forum.xda-developers.com/t/guide-osprey-fastboot-flashing-factory-firmware-images.3187750/
It says there that the "preflash validation failed" error occurs when the firmware being flashed is older than the one already installed. I will try downloading a newer version and flashing it. Will update here.
Update: I have dowloaded a newer rom and tried to flash it. This time got different errors (picture attached, this went for every sparsechunk). I think I know the reason but I do not know how to solve it. This might not be the exact stock rom of this phone so I cannot flash it with a locked bootloader. Could someone help me finding the correct rom or suggest a different solution?
Yooooo. I have the Moto e5 Cruise and so does my wife. We bought them in 2018 from Cricket and last night hers went to emmc failure, also known scientifically as 'no worky' mode.
The phone would only load in fastboot and had tried to use my Moto RSD tool to reflash but the phone would not detect in anything but fastboot mode.. Here's where it gets interesting....
There is a piece of software called the Lenovo (which now owns Moto) Rescue and Smart Assistant that can reflash your phone back to factory, no matter your sub-variant (cricket, metro, etc). Without having a fresh backup on hand, you're going to be beholden to the last cloud sync or manual backup you have because all data will be wiped in the below process.
BTW: Just run the assistant as it seems to be the easiest 'back-to-stock/working' tool I can find. Going to fastboot alone yielded weird errors since i didn't have the unlock code for the 'fastboot oem unlock [code goes here]' command.
**RESTORATION PROCESS**
This will apply to multiple Lenovo/Moto Mobility devices. Unknown at this time how many have been impacted by this seemingly pre-planned failure on Lenovo's part.
If your phone is stuck in fastboot mode where MTK download mode does not load, nor does adb, follow these simple steps:
(NOTE: BACKUP YOUR FILES IF POSSIBLE)
1. Click the link above to be directed to the Lenovo software download page and run the installer on your PC (Sorry Mac users :'().
2. The software, once installed, will require you to sign up for OR link a google, fb, g+, etc account to it for purposes of creating a Lenovo ID. Once signed in, click on 'Rescue Now'.
3. With your phone in fastboot mode, allow the software to download the firmware for your phone.
4. Once the firmware has finished downloading and validating, click on 'Rescue Now' once again. Your phone will begin the reflashing process.
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
crepper4454 said:
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
Click to expand...
Click to collapse
No problemo! Glad it worked!