Database Info

[Q] Can't boot, recovery keeps dissapearing

I have searched and tried different things but I'm getting nowhere. I have been running Purity rom on this for a while but when I woke up this morning, I found my screen black and only being able to boot to the bootloader and and google screen (which quickly goes away and goes black again). When I tried to go to recovery at first I believe it was just shutting off. Now it goes to a light black screen.
The first thing I did was flashed the factory image .bat file and everything seemed to go ok but when trying to go to recovery after it went to the light black screen. I turned it off and it booted to the Google screen then off again. Then it booted to the google screen and it froze that way. I can always get it back to the bootloader screen and got it to recovery once by flashing TWRP again using ADB.
TWRP opened once and I tried to do a factory reset but it couldn't find anything and couldn't mount to anything. I got it back to the bootloader again but the recovery has disappeared again. I tried to flash the factory image again but it definitely failed this time.
Please help.

aburn95 said:
I have searched and tried different things but I'm getting nowhere. I have been running Purity rom on this for a while but when I woke up this morning, I found my screen black and only being able to boot to the bootloader and and google screen (which quickly goes away and goes black again). When I tried to go to recovery at first I believe it was just shutting off. Now it goes to a light black screen.
The first thing I did was flashed the factory image .bat file and everything seemed to go ok but when trying to go to recovery after it went to the light black screen. I turned it off and it booted to the Google screen then off again. Then it booted to the google screen and it froze that way. I can always get it back to the bootloader screen and got it to recovery once by flashing TWRP again using ADB.
TWRP opened once and I tried to do a factory reset but it couldn't find anything and couldn't mount to anything. I got it back to the bootloader again but the recovery has disappeared again. I tried to flash the factory image again but it definitely failed this time.
Please help.
Click to expand...
Click to collapse
@bitdomo might be able to help you lol
Might be bad eMMC or something?

when youre flashing recovery, which command are you using.. fastboot boot recovery recoveryname.img or fastboot flash recovery recoveryname.img?

aburn95 said:
I have searched and tried different things but I'm getting nowhere. I have been running Purity rom on this for a while but when I woke up this morning, I found my screen black and only being able to boot to the bootloader and and google screen (which quickly goes away and goes black again). When I tried to go to recovery at first I believe it was just shutting off. Now it goes to a light black screen.
The first thing I did was flashed the factory image .bat file and everything seemed to go ok but when trying to go to recovery after it went to the light black screen. I turned it off and it booted to the Google screen then off again. Then it booted to the google screen and it froze that way. I can always get it back to the bootloader screen and got it to recovery once by flashing TWRP again using ADB.
TWRP opened once and I tried to do a factory reset but it couldn't find anything and couldn't mount to anything. I got it back to the bootloader again but the recovery has disappeared again. I tried to flash the factory image again but it definitely failed this time.
Please help.
Click to expand...
Click to collapse
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress

simms22 said:
when youre flashing recovery, which command are you using.. fastboot boot recovery recoveryname.img or fastboot flash recovery recoveryname.img?
Click to expand...
Click to collapse
Hey I'm using "fastboot flash recovery recovery.img" and that's what I've used in the past. I've had a fully functioning rom with fully functioning recovery for a while until yesterday.

bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Ok thanks I'll try this and check the text in fastboot after work today. Thanks for the responses guys.
After reading some more last night I'm afraid it's an emmc problem but I like to be proven wrong sometimes.

Maybe also try this?
http://forum.xda-developers.com/showthread.php?t=2577447

beekay201 said:
Maybe also try this?
http://forum.xda-developers.com/showthread.php?t=2577447
Click to expand...
Click to collapse
I actually have that thread open on my computer. It was my next attempt of repair before starting the thread late last night. Thanks for the suggestion I will certainly try it.
Update: I tried pushing Philz recovery to the phone which seemed to work fine until I selected go to recovery mode. It just went back to that barely light black screen. I'll try again when I get home. Going to try Bitdomo's advice about locking bootloader first.

bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Out of curiosity what's the reason for using two brands, or were they just available so they were used?

bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Bitdomo I'm trying the Flashtool but it's staying at 0% on the firmware update and nothing is popping up on computer or in Device Manager. Had no connection issues prior to the brick or with adb/fastboot. My Ports aren't evening showing at all in DM even if I select show hidden devices.

aburn95 said:
How do I lock the bootloader without being able to put the .zip on my internal memory?
Click to expand...
Click to collapse
In fastboot type
fastboot oem lock
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
In fastboot type
fastboot oem lock
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I honestly wanted to do that but it seemed too easy. I was trying to lock it like I did before when i had to send original back to T-Mobile. Sorry and thanks.

bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Ok so it stayed locked so that's a start. I'm back in download mode again but it's staying at 0% and nothing on computer.

I tried to re-download the factory images and flash again using adb. It failed again. Here's a picture of what happened:

Unzip the zip and use manual flash commands. Clikc the link in my signature and read my "adb and fastboot. What is it?" thread of you're unsure of the commands.
Sent from my Nexus 5 using Tapatalk

aburn95 said:
I tried to re-download the factory images and flash again using adb. It failed again. Here's a picture of what happened:
Click to expand...
Click to collapse
You have "remote: flash write failure" error. It means your emmc (internal storage) is broken and you cannot modify the data on it. You have to rma your device.
Just for matter of research can you enter to fastboot and post the variable line here?
Mine is: hammerhead D821(H) 16GB

bitdomo said:
You have "remote: flash write failure" error. It means your emmc (internal storage) is broken and you cannot modify the data on it. You have to rma your device.
Just for matter of research can you enter to fastboot and post the variable line here?
Mine is: hammerhead D821(H) 16GB
Click to expand...
Click to collapse
Sorry I meant to tell you yesterday... D820H 16GB. Should I still be able to toggle the tamper tag so they will take it back with no problems? Or am I screwed?

aburn95 said:
Sorry I meant to tell you yesterday... 820H. Should I still be able to toggle the tamper so they will take it back with no problems? Or am I screwed?
Click to expand...
Click to collapse
You should be able to if you managed to lock the bootloader. The name of the zip does not came into my mind which you have to flash, but you have to do it with the adb sideload command because you cant copy anything to your phone, or use adb push command to push it to the "/" folder because it is mounted to the ram which you can write not like your storage . If you bought your phone from google it does not matter you have tamper flag set to 1.

bitdomo said:
You should be able to if you managed to lock the bootloader. The name of the zip does not came into my mind which you have to flash, but you have to do it with the adb sideload command because you cant copy anything to your phone, or use adb push command to push it to the "/" folder because it is mounted to the ram which you can write not like your storage . If you bought your phone from google it does not matter you have tamper flag set to 1.
Click to expand...
Click to collapse
Ok thanks. I haven't quite figured out the adb sideload function yet. I tried doing it through TWRP but it just sits there and does nothing after selecting. Maybe I'm trying the wrong thing. I got my phone from T-Mobile so I'll need to solve this. Thanks for the help.

This phone is being a real a-hole. I'm trying to boot to stock recovery but it just sits on a screen with a really big android with wiggling antennae. I pressed up+power many times but it stayed that way. So I tried booting to TWRP again and it did but went immediately to an "OpenRecoveryScript," had a little bar at the bottom for a while with some other stuff on the screen, then turned off.
I tried stock recovery again and it went to the little dead android this time but still nothing when I press up+power.

Troubleshooting eMMC with fastboot or adb.

Hi guys,
My Nexus 5 (hammerhead D821 (E) ) died on me two day ago. It's showing the google logo without any progress and then restarts itself.
I can boot into bootloader from the device. If I issue <adb devices> command it won't show any devices however when using <fastboot devices> it finds the device's ID.
My devices was running the latest official marshmallow 6 when it happened (it was working just fine for more than a week).
Currently my device is in <lock state - Locked> I tried issuing <fastboot oem unlock> command without any success. The phone would run the command shows the <lock state - Unlocked> then it shows <erasing...> (I left the phone for 10Hours, no change) .
It won't finish nor respond unless I reboot the device into bootloader again.
I'm using the google USB drivers and universal drivers for my phone, they seem to be working, showing as android bootloader interface in my system (win7). I can't boot into recovery mod from the bootloader it will just show a black screen until I restart the phone.
I'm suspecting my eMMC is dead, my knowledge with adb and fastboot is limited, I would appreciate to hear your feedback regarding the issue.
Is there are way I can run some low level diagnostics commands to understand if its dead?
Can I revive my phone in anyway as I can't flash anything at the moment while the device is in <lock state - Locked> .
Waiting to hear from the experts =) thanks in advance guys!
Alex

Fish7 said:
Hi guys,
My Nexus 5 (hammerhead D821 (E) ) died on me two day ago. It's showing the google logo without any progress and then restarts itself.
I can boot into bootloader from the device. If I issue <adb devices> command it won't show any devices however when using <fastboot devices> it finds the device's ID.
My devices was running the latest official marshmallow 6 when it happened (it was working just fine for more than a week).
Currently my device is in <lock state - Locked> I tried issuing <fastboot oem unlock> command without any success. The phone would run the command shows the <lock state - Unlocked> then it shows <erasing...> (I left the phone for 10Hours, no change) .
It won't finish nor respond unless I reboot the device into bootloader again.
I'm using the google USB drivers and universal drivers for my phone, they seem to be working, showing as android bootloader interface in my system (win7). I can't boot into recovery mod from the bootloader it will just show a black screen until I restart the phone.
I'm suspecting my eMMC is dead, my knowledge with adb and fastboot is limited, I would appreciate to hear your feedback regarding the issue.
Is there are way I can run some low level diagnostics commands to understand if its dead?
Can I revive my phone in anyway as I can't flash anything at the moment while the device is in <lock state - Locked> .
Waiting to hear from the experts =) thanks in advance guys!
Alex
Click to expand...
Click to collapse
Sounds like it (eMMC) died.

beekay201 said:
Sounds like it (eMMC) died.
Click to expand...
Click to collapse
Thanks for the feedback beekay201. I hope someone will know if this can be confirmed with some sort of test etc...

I think my emmc is dead too because my n5 does the same thing in fastboot - unlocked, locked, unlocked. Also, I can't mount partitions or perform a factory wipe in stock recovery. Also tried flashing TWRP right after unlocking the bootloader. Fastboot says recovery was successfully flash but, when I immediately boot to recovery, I still have stock recovery.
Time for me to find a n5 with a smashed screen

audit13 said:
I think my emmc is dead too because my n5 does the same thing in fastboot - unlocked, locked, unlocked. Also, I can't mount partitions or perform a factory wipe in stock recovery. Also tried flashing TWRP right after unlocking the bootloader. Fastboot says recovery was successfully flash but, when I immediately boot to recovery, I still have stock recovery.
Time for me to find a n5 with a smashed screen
Click to expand...
Click to collapse
Hi audit13,
My Nexus is locked. I can't unlock it at all. It's stuck in "erasing" if I run <fastboot oem unlock> command.

[HELP] Nexus 5 stuck on bootloop + bootloader locked + can't access recovery

Hi,
I have come here seeking help for repairing my Nexus 5 which is stuck in bootloop. The phone wasn't rooted with possibly no custom recovery and it's bootloader is locked. And I am not sure which firmware was on it. And I also don't know what was done to it for it to become "bricked" as it was given to me in that state.
I can access the Bootloader Mode (a.k.a. Fastboot) but when I try to enter the Recovery Menu it gives me an Android logo with the red triangle with "No Command." written underneath it. And since the bootloader is locked, I am unable to flash a Stock ROM on the phone.
I have somehow managed to "temporarily" unlock the bootloader by entering the following command.
Code:
fastboot oem unlock
But, as mentioned, it is temporary as whenever the phone is rebooted it automatically gets locked again.
So I tried entering that command then I immediately entered the following commands to flash the stock 6.0.1 recovery.img
Code:
fastboot erase flash
fastboot flash recovery recovery.img
But in vain, as it still gives me the "No Command." Android logo when I run the Recovery Mode. I have also tried the same procedure with the TWRP recovery.img but with the same results.
I have also tried launching the flash-all.bat from the stock 6.0.1 right after running the bootloader unlock command mentionned previously. But it fails as i guess the flash-all.bat is programmed to reboot the bootloader before flashing. Thus re-locking the bootloader right before attempting to flash it.
I have come here seeking for help as I believe XDA is the most active Android community online.
If my post is somehow against any forum rules here, please be indulgent as this is my first time posting on XDA.
Thanks in advance.

At first, fastboot erase flash is not a working fastboot command. It is used to erase a partition: boot, cache, data...
Is your bootloader relocked after typing this?
fastboot oem unlock
fastboot reboot-bootloader
In the stock Android, press Volume up when you see "No Command".

NexusUser5 said:
But, as mentioned, it is temporary as whenever the phone is rebooted it automatically gets locked again.
Click to expand...
Click to collapse
Sounds like the EMMC is dying. http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301 you can try using the tool here, test the EMMC and RAM, it'll pretty much confirm it.

Primokorn said:
Is your bootloader relocked after typing this?
fastboot oem unlock
fastboot reboot-bootloader
In the stock Android, press Volume up when you see "No Command".
Click to expand...
Click to collapse
Yes the bootloader gets re-locked. And pressing Volume Up doesn't work either.
JonesL said:
Sounds like the EMMC is dying. http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301 you can try using the tool here, test the EMMC and RAM, it'll pretty much confirm it.
Click to expand...
Click to collapse
I've tried the tool and I can't get it to work properly as it gives me an error saying "partition.txt does not exist. Please extract the file from the total binary image."
UPDATE: I just got it to work. The SDRAM test passed but EMMC test failed. So that means it's hard-bricked right? And is changing the motherboard the only way to fix it?

I have a phone that does exactly the same thing. Swapped out only the motherboard and everything is fine again.

audit13 said:
I have a phone that does exactly the same thing. Swapped out only the motherboard and everything is fine again.
Click to expand...
Click to collapse
I suspect a hard-brick, so I am strongly considering it. Would you know if motherboards are carrier specific? Meaning if I get a motherboard from another carrier's Nexus, would it end up changing the carrier of my phone?

Any motherboard from any carrier will work as long as the model numbers match. In Canada, every N5 carried by all carriers is the d820.

audit13 said:
Any motherboard from any carrier will work as long as the model numbers match. In Canada, every N5 carried by all carriers is the d820.
Click to expand...
Click to collapse
Thanks a lot for your help, very much appreciated.

i bricked my honor, is there anything i can do?

So I had an unlocked H8 with LOS. As I wanted to install EMUI, I put the proper restore Update.app into the dload folder and started Huawei's recovery. Everything went well, I formated data and wanted to install the EMUI 4.1 ROM using the same method.
Unfortunately my H8 is bootlooping and there is now way into erecovery nor any other recovery. It simply reboots on every single known vol up or down key pressing combination. The only thing I can go to is fastboot mode when holding down vol down and plugging in usb wire. But, it says frd locked and I can't install nor boot twrp. It's simply gone and reboots all the time.
Any hints? I can't even turn it off.

I wanted to give away that phone that's the reason. Last time I did it this way, I could flash the EMUI 4.1 since it's signed. But not this time.
Interesting part is, that although fastboot says frd locked, I still get the "phone unlocked" warning on every reboot. dload method isn't working, as it simply keeps rebooting.
It's my hardest brick so far I ever encountered

the same thing happened to me.....on my phone lock/unlocked frp and bootloader were tweaked for some reason(I mean that what was written wasn't the reality) so how did I fix it? I kept on to flash rollback package many times and I tried to unlock/relock bootloader again, at the end the phone let me to flash the firmware, I didn't know how but the phone allowed me to flash things throw recovery(using dload method). At the begin I only could access to erecovery and fastboot. I suppose that I broke system and data partition and while I looked/unlocked the bootloader, the wipe fixed the partition table. Sorry I'm tired and I know that my English sucks, I hope you understand what I have written.

How did you enter erecovery as this isn't working for me.... What did you flash over fastboot?

Have you tried flashing the firmware separately using adb on computer?
For this you just need to extract the Update.app using the firmware extractor for huawei. Then flash them individually using adb commands in cmd.

I can't access any state that would allow to do adb.

faeArai said:
How did you enter erecovery as this isn't working for me.... What did you flash over fastboot?
Click to expand...
Click to collapse
sorry. I'll try to explain better, however on Huawei/honor devices there are not one but two recoveries, so one is the normal recovery flashed in recovery partition, the second one is the Huawei recovery that is flashed in recovery2 partition, so if you didn't touch recovery2 partition, your erecovery is still there, now, if you press VOL+ VOL- and POWER it will reboot to recovery2 and it starts to flash something from dload in your sd card, so in my opinion you should do this things, first try this method to flash rollback package(this is the transition package from 7 to 6 and you will find it on honor site) if this is still not working try locking and unlocking again your bootloader(I hope this fix partitions of your device) then try to enter recovery and do a wipe and then boot your device, if this doesn't work flash rollback package(now it would work) and then flash an emui 4 full firmware image, always using dload method. trust me... I did the same... and it worked for me. let me know if it works for you :good:

faeArai said:
So I had an unlocked H8 with LOS. As I wanted to install EMUI, I put the proper restore Update.app into the dload folder and started Huawei's recovery. Everything went well, I formated data and wanted to install the EMUI 4.1 ROM using the same method.
Unfortunately my H8 is bootlooping and there is now way into erecovery nor any other recovery. It simply reboots on every single known vol up or down key pressing combination. The only thing I can go to is fastboot mode when holding down vol down and plugging in usb wire. But, it says frd locked and I can't install nor boot twrp. It's simply gone and reboots all the time.
Any hints? I can't even turn it off.
Click to expand...
Click to collapse
I ran into this issue not that long ago. What you have to do is relock your bootloader using ADB. The ADB commands and instructions can be found in this thread.
Just a FYI, do not use the links to the software listed in that thread as it is a little outdated. The method still works but the software will probably not work. Just be sure to get the most recent/appropriate version of SuperSU and TWRP via their official threads (This is if you want to re-root). There are Honor 8 specific TWRP files if I remember correctly, so be sure to check around the Honor 8 forums for the correct files.
A quick summary of what I did:
1) Power your phone off and then boot into fastboot by holding Vol down + Power; as soon as it boots up, plug your phone into your combuter via your usb cord.
2) With ADB running, type:
Code:
fastboot oem relock [COLOR="LightBlue"]################[/COLOR]
NOTE: The '#' should be replaced with your unique unlock code that you obtained to unlock your bootloader.
3) Wait for it to format and reset your phone and go through the setup. BE SURE TO BYPASS all google registration; skip everything you can to get into the phone itself. If you do register, it will reactivate FRP and you'll have to start over again.
4) Turn on USB Debugging and every other setting that enables developer administrative navigation and control just to be safe. USB Debugging being the most important one, though.
5) Restart your phone and boot into fastboot again using Vol down + Power.
6) Unlock your phone again with:
Code:
fastboot oem unlock [COLOR="LightBlue"]################[/COLOR]
7) Once the command is entered, it'll reset your phone once more and - as stated before - bypass/skip all google (FRP) registration.
8) Enable developer options and USB debugging again and make sure that OEM Unlocked is checked and grayed out.
9) Reboot into fastboot mode to confirm that FRP is disabled and you should be able to install TWRP now via ADB.

@Numerics thanks. The thing is, that I can't boot anything. I can't even go into eRecovery. Nor can I flash a stock EMUI 4.1. It just boot loops all the time and I can only access fastboot.

If you can flash twrp..........Install los or other Rom ..................Go back to stock.......you must flash b360 ober adb...... because los is 7.1...............if you on b360 you can usw the rollback for emui 4.1........,..............sry for bad english

I can easily go to fastboot. But I can't flash anything. I extracted the img from the update.app but can't flash. It simply says that it's not permitted.

faeArai said:
I can easily go to fastboot. But I can't flash anything. I extracted the img from the update.app but can't flash. It simply says that it's not permitted.
Click to expand...
Click to collapse
With my method, you don't need to flash anything. Just relock your bootloader via adb in fastboot mode and let it reset. Unless I'm not understanding your issue entirely.

@Numerics as I said, in won't boot anything as it is constantly boot looping. There is no way to access any kind of recovery nor erecovery. There is no boot into Android. The only thing accessible right now is fast boot (which is not ADB). But even in fast boot I can't do anything als operations are not permitted.
after boot looping and starting fast boot mode, I can see a "Android reboot reason" section saying:
AP_S_PANIC
data is invalid
There is still a lineageos installed on system as firmware but as I tried to get rid of it by going back to stock EMUI, I guess Huawei's rollback did something wrong and killed recovery (although I did it in the past successfully).
I tried to run HiSuite to recover my phone, but it just says, that my phone is not supported.
Speaking of this, Huawei messed up with that whole fastboot locking bull****.

faeArai said:
@Numerics as I said, in won't boot anything as it is constantly boot looping. There is no way to access any kind of recovery nor erecovery. There is no boot into Android. The only thing accessible right now is fast boot (which is not ADB). But even in fast boot I can't do anything als operations are not permitted.
after boot looping and starting fast boot mode, I can see a "Android reboot reason" section saying:
AP_S_PANIC
data is invalid
There is still a lineageos installed on system as firmware but as I tried to get rid of it by going back to stock EMUI, I guess Huawei's rollback did something wrong and killed recovery (although I did it in the past successfully).
I tried to run HiSuite to recover my phone, but it just says, that my phone is not supported.
Speaking of this, Huawei messed up with that whole fastboot locking bull****.
Click to expand...
Click to collapse
No, I know ADB isn't Fastboot. What I'm trying to say is that you should be able to still run ADB via CMD on Windows when you're in fastboot mode to relock your bootloader with the directions I gave in my previous post. It'll force-restore your phone to a non-bricked/vanilla state. At least that is how I fixed mine.
Like... You can't even try using the 'fastboot oem relock ################' function via the ADB console while in fastboot?

yes boy trust us, you haven't a working OS so it is a normal thing that your phone reboot, you cannot access to recovery because some partitions are corrupted (data partition) , so these are the steps that could help you:
1) using fastboot, relock your boot loader
2)using fastboot, unlock your boot loader (partition table would be ok now, and you would be able to use load method to flash things trow stock recovery)
4)put inside your sd card \dload\update.app(use rollback package)
3) press all the buttons while your device is rebooting(do this before the blue screen logo appear), your phone is now looking for something inside your sd card
5) if the next step doesn't work do a factory reset from recovery that now would be working
6) put inside your sd card a full android 6 (emus 4) update.app and pressing all buttons it will install the firmware
7) your device now is locked and back to stock, maybe without cust partition or maybe in test mode but it is certainly alive
8) do a factory reset and reinstall the firmware
9) your phone is now ok

You don't lock the bootloader via ADB but via fastboot.
As I said, northing was restored and nothing is booting and I can't unlock my bootloader again. As I said, recovery is not working so the file in dload is not loaded and used. Which is strange.
Locking bootloader didn't do anything besides locking the bootloader. Device is still dead and I still can only access fastboot.

faeArai said:
You don't lock the bootloader via ADB but via fastboot.
As I said, northing was restored and nothing is booting and I can't unlock my bootloader again. As I said, recovery is not working so the file in dload is not loaded and used. Which is strange.
Locking bootloader didn't do anything besides locking the bootloader. Device is still dead and I still can only access fastboot.
Click to expand...
Click to collapse
Which model do u own?
Sent from my Honor 8 using XDA Labs

The European one.

faeArai said:
You don't lock the bootloader via ADB but via fastboot.
As I said, northing was restored and nothing is booting and I can't unlock my bootloader again. As I said, recovery is not working so the file in dload is not loaded and used. Which is strange.
Locking bootloader didn't do anything besides locking the bootloader. Device is still dead and I still can only access fastboot.
Click to expand...
Click to collapse
This is not the truth.....locking bootloader will erase all your data and fix partitions....and with fixed partition you can access to recovery ......trust me the only thing that you can do is to lock your bootloader......you can't flash anything from fastboot and boot recovery or system now...... lock your bootloader and then unlock it again, try using "fastboot OEM lock *****" or "fastboot OEM relock *******" (try cmd runned as admin, people say that this makes the difference) then unlock your device again and .....magic your recovery will boot......the same thing happened to me and I fixed my phone using this trick, however, even if you had frp unlocked it would say you that isn't possible to write anything because you broke some partition, and that's the reason why you can't boot recovery, wait one second and think: why doesn't my recovery boot?

It has nothing to do with trust. I did it and device is still a full stone brick. Nothing changed by locking the bootloader besides that now I can't unlock the bootloader anymore.

Phone boots into fastboot, system files corrupted

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!