Database Info

Phone bricked (Piv validation failed)-rsdlite flashing fiemware)

After using rsdlite to flash telstra Australia over FR jellybean leak, my phone is now bricked because it says at 16/19: no valid PIV block in SP for system. Piv validation failed (system).*So I tried to re flash the FR Vodafone ica stock through rsd and then it fails at 16/19 and says phone read failed.*Now my phone can't get into recovery, and is stuck at fast boot..*What can I do??

The PIV error means the image you tried to flash wasn't properly marked and signed (not sure about the details, but there is some magic header missing I'm the file...), you may need an unlocked bootloader and/or fastboot instead of rsdlite, or something else, to flash that.
If you can get into fastboot mode, you should be able to unbrick it, with a properly signed image, like the one coming from a leak or official fastboot.
Make sure you're not running rsd lite from a virtual machine like virtual box, as that will fail. I had virtual box with win xp running on my macbook and it won't work, I had to use a real windows machine, or fastboot.
If you're comfortable with the command line, get the system image out of the zip file and try with fastboot instead:
fastboot flash system system.img.ext4
If you still get errors, with either rsdlite or fastboot, post the exact error then we'll see.
Sent from my XT907 using xda app-developers app

tried flashing the system_signed with the fastboot command from official telstra stock ics, (flashed the firmware (which got the error at 16/19 system - phone read failed error), then took out the system_signed and tried to flash that.
error is bootloader prevalidation failed when trying to write in the cmd window
error on fastboot mode is :invalid entry hash for system:index=0
EDIT: ok i changed the system_signed (to system)signed.ex4 and flashed it with the ex4 extension, and wierdly it started working and finished writing system with an OKAY!
but now its just stuck at motorola logo, and not loading, just seems to be stuck at the M logo..
i guess it means 16/19 flash step is over, so what is 17/19? do i fast boot the rest, and if so, which files are they?

royalbloodvi said:
tried flashing the system_signed with the fastboot command from official telstra stock ics, (flashed the firmware (which got the error at 16/19 system - phone read failed error), then took out the system_signed and tried to flash that.
error is bootloader prevalidation failed when trying to write in the cmd window
error on fastboot mode is :invalid entry hash for system:index=0
EDIT: ok i changed the system_signed (to system)signed.ex4 and flashed it with the ex4 extension, and wierdly it started working and finished writing system with an OKAY!
but now its just stuck at motorola logo, and not loading, just seems to be stuck at the M logo..
i guess it means 16/19 flash step is over, so what is 17/19? do i fast boot the rest, and if so, which files are they?
Click to expand...
Click to collapse
I'm not sure exactly which firmware/zip file you are using, but there should be a .xml file in it. Unzip the whole thing into some folder, then open the .xml file with your favorite text editor (yeah, even wordpad ... but not notepad please), there you'll see all the steps, so you can search for "system" and see what's after ... in fact you can edit that file, remove the steps you don't want, then open it and run it in rsdlite
I'm not really sure, but since you managed to flash system manually, you could try removing the system line from that .xml file, then flash the whole thing with rsd lite, that should flash everything else.
Edit: are you bootloader unlocked by chance? You shouldn't need it to restore your phone, but, for example, an unlocked bootloader will let you flash garbage on system, while the locked one won't, so if you are locked and system flashed with an OKAY, you're pretty sure it's good

aslomagic said:
I'm not sure exactly which firmware/zip file you are using, but there should be a .xml file in it. Unzip the whole thing into some folder, then open the .xml file with your favorite text editor (yeah, even wordpad ... but not notepad please), there you'll see all the steps, so you can search for "system" and see what's after ... in fact you can edit that file, remove the steps you don't want, then open it and run it in rsdlite
I'm not really sure, but since you managed to flash system manually, you could try removing the system line from that .xml file, then flash the whole thing with rsd lite, that should flash everything else.
Edit: are you bootloader unlocked by chance? You shouldn't need it to restore your phone, but, for example, an unlocked bootloader will let you flash garbage on system, while the locked one won't, so if you are locked and system flashed with an OKAY, you're pretty sure it's good
Click to expand...
Click to collapse
ok so i managed to flash the system_signed manually, edited out system_signed from the xml file, and all went well.
and went to reboot. flash complete.
now when it loads up, all went back to step 1.
and ends up being fastboot reason: sticky bit factory_fastboot
do u happen to have the boot.img of stock ics? maybe thats the reason..
&
same error, PIV validation failed... i even went to morola service engineer. he said i killed the motherboard and its $300 replacement... is this true?

royalbloodvi said:
ok so i managed to flash the system_signed manually, edited out system_signed from the xml file, and all went well.
and went to reboot. flash complete.
now when it loads up, all went back to step 1.
same error, PIV validation failed... i even went to morola service engineer. he said i killed the motherboard and its $300 replacement... is this true?
Click to expand...
Click to collapse
So, what do you mean "back to step 1" .. does the phone boot at all? Does it get past bootloader/fastboot mode?
Again, is your bootloader locked or unlocked?
I doubt you killed the motherboard, but who knows ... if you still get fastboot mode you should be able to flash it, you just need to flash something that works.
Was the jellybean leak working? maybe just reflash that for now, so you confirm that it still works, and at least you won't have a brick ...

aslomagic said:
So, what do you mean "back to step 1" .. does the phone boot at all? Does it get past bootloader/fastboot mode?
Again, is your bootloader locked or unlocked?
I doubt you killed the motherboard, but who knows ... if you still get fastboot mode you should be able to flash it, you just need to flash something that works.
Was the jellybean leak working? maybe just reflash that for now, so you confirm that it still works, and at least you won't have a brick ...
Click to expand...
Click to collapse
back to step 1, as in after going through the rsd lite process and removing system from the xml, it completes the flashing process. but it gets to the motorola, stock recovery, and when it looks liek it was success, it goes back to the initial error piv validation failed..
Now I cant even try go back to jelly bean leak, cause when flashing it fails at step 1. it seems like my phone is even more screwed up now.
error is : 1/17 flash partition ''partition_signed"" -> phone returned FAIL..
as a side note: i accidentally flashed the CWM backup boot.img to my phone in my other post: http://forum.xda-developers.com/showthread.php?p=35045589#post35045589
is this the reason it keeps failing now when it should not? i flashed this command halfway during the rsd lite process..

royalbloodvi said:
back to step 1, as in after going through the rsd lite process and removing system from the xml, it completes the flashing process. but it gets to the motorola, stock recovery, and when it looks liek it was success, it goes back to the initial error piv validation failed..
Now I cant even try go back to jelly bean leak, cause when flashing it fails at step 1. it seems like my phone is even more screwed up now.
error is : 1/17 flash partition ''partition_signed"" -> phone returned FAIL..
Click to expand...
Click to collapse
Hmm, maybe somebody with more knowledge can help you better at this point, but let's see ...
If you can, look in the actual system file you are trying to flash (system_signed I guess) with a hex editor (or heck, again, even wordpad), and see if you see anything that says MOT_PIV ... if not, well, yeah, it will probably fail with that error.
I just seen you said you flashed a boot.img from something completely unrelated ... are you able to flash back a sane boot.img from jellybean/telstra/something that is known working with fastboot (I'd say forget rsdlite here, but it's a matter of preference)?
Also, let's assume your bootloader is unlocked, cause you keep not saying. Try to re-lock it, then flash. If you get an error when before you were getting success, as assuming the things you are flashing are supposed to be signed, then it means it's not really flashing it right. At least, it'll tell you what is not flashed right...
Other than that, I'd try flashing things manually with fastboot (I like it better than rsdlite), especially partition, then boot and/or system, maybe from jellybean, and see if the phone gets a little further in booting ...

aslomagic said:
Hmm, maybe somebody with more knowledge can help you better at this point, but let's see ...
If you can, look in the actual system file you are trying to flash (system_signed I guess) with a hex editor (or heck, again, even wordpad), and see if you see anything that says MOT_PIV ... if not, well, yeah, it will probably fail with that error.
I just seen you said you flashed a boot.img from something completely unrelated ... are you able to flash back a sane boot.img from jellybean/telstra/something that is known working with fastboot (I'd say forget rsdlite here, but it's a matter of preference)?
Also, let's assume your bootloader is unlocked, cause you keep not saying. Try to re-lock it, then flash. If you get an error when before you were getting success, as assuming the things you are flashing are supposed to be signed, then it means it's not really flashing it right. At least, it'll tell you what is not flashed right...
Other than that, I'd try flashing things manually with fastboot (I like it better than rsdlite), especially partition, then boot and/or system, maybe from jellybean, and see if the phone gets a little further in booting ...
Click to expand...
Click to collapse
sorry it is a locked bootloader.
so what do i do if i do see mot_piv?

royalbloodvi said:
sorry it is a locked bootloader.
so what do i do if i do see mot_piv?
Click to expand...
Click to collapse
Nothing, if you see that you know it's (probably) a legitimate, signed image and not garbage, or in another format
Not sure if the file name actually matters, but yeah, name it system.img.ext4 and flash it (not ex4, ext4).
Try to flash boot from a known good firmware (i.e. from jellybean, it was working, right?)
fastboot flash boot boot.img
Then check if it boots, it should at least show the motorola logo (but that's not enough of course).
If it doesn't, flash the corresponding system, again with fastboot, see what happens ... worst case, can you unlock the bootloader and flash CWM or something, like madmonkey57 was suggesting in the other thread (i.e. is your bootloader unlockable)?

aslomagic said:
Nothing, if you see that you know it's (probably) a legitimate, signed image and not garbage, or in another format
Not sure if the file name actually matters, but yeah, name it system.img.ext4 and flash it (not ex4, ext4).
Try to flash boot from a known good firmware (i.e. from jellybean, it was working, right?)
fastboot flash boot boot.img
Then check if it boots, it should at least show the motorola logo (but that's not enough of course).
If it doesn't, flash the corresponding system, again with fastboot, see what happens ... worst case, can you unlock the bootloader and flash CWM or something, like madmonkey57 was suggesting in the other thread (i.e. is your bootloader unlockable)?
Click to expand...
Click to collapse
unfortunately its not dev edition, device is locked.. =(
but i will try the JB method and see what happens now

royalbloodvi said:
sorry it is a locked bootloader.
Click to expand...
Click to collapse
Sorry, I just realized ... yours is a XT925 right? You kept talking about Telstra, is yours the australian version?
I'm pretty sure you can unlock the bootloader, get the code from motorola. You need dev edition only for verizon model, all others should be unlockable even if retail. Yes you'll lose the warranty, but if the alternative is a paperweight ...

aslomagic said:
Sorry, I just realized ... yours is a XT925 right? You kept talking about Telstra, is yours the australian version?
I'm pretty sure you can unlock the bootloader, get the code from motorola. You need dev edition only for verizon model, all others should be unlockable even if retail. Yes you'll lose the warranty, but if the alternative is a paperweight ...
Click to expand...
Click to collapse
ive tried to unlock the bootloader, got the code, but it just doesnt seem to unlock when doing the fastboot oem unlock command..
also, after writing system into it, everything works, motorola logo boots. but nothing happens and just stays like that,
when trying to enter recvery, comes up with errors :
e:\ cannot mount cache/recovery/command
e:\ cannot open cache/recovery/caller
and similar cache/recovery errors

royalbloodvi said:
ive tried to unlock the bootloader, got the code, but it just doesnt seem to unlock when doing the fastboot oem unlock command..
also, after writing system into it, everything works, motorola logo boots. but nothing happens and just stays like that,
when trying to enter recvery, comes up with errors :
e:\ cannot mount cache/recovery/command
e:\ cannot open cache/recovery/caller
and similar cache/recovery errors
Click to expand...
Click to collapse
I am in the exact same boat as you... No success and I have tried everything!

royalbloodvi said:
ive tried to unlock the bootloader, got the code, but it just doesnt seem to unlock when doing the fastboot oem unlock command..
also, after writing system into it, everything works, motorola logo boots. but nothing happens and just stays like that,
when trying to enter recvery, comes up with errors :
e:\ cannot mount cache/recovery/command
e:\ cannot open cache/recovery/caller
and similar cache/recovery errors
Click to expand...
Click to collapse
Well, at this point, I really don't know ... if it happened to me, I'd be in "trial and error mode" now
Have you tried wiping the cache partition (fastboot erase cache, I think)?
Also, you didn't say if you managed to flash back a known-good boot.img, as well ...

I unbricked my phone, had to mix and match system files between telstra and Vodafone fr, and get it to boot up to the Motorola logo.
If you so manage to get to logo, it can be re stored just take it to Motorola service centre and they will flash their software and Walah.. Costed me 55$ but but better than a expensive junk
Sent from my XT925 using xda app-developers app

Paying is not an option. I'm currently fixing my Atrix HD. Not that hard once you find the right file. Mine failed in RSDlite on step 1/23 and I just hit it again and it went through all the way. You should've tried that. Next time, because there WILL be a next time, just send through the xml file again through rsdlite.
My phone just finished booting up as I typed this.

Soft bricked shield tablet PLEASE HELP!

So I bought my shield tablet back in March, used it until about may I think. Was browsing the internet then it suddenly crashed and got stuck on the Nvidia boot screen. tried to reboot several times. Nothing. So I forgot about it and thought I would just google the reset option later when I had time. Now since June I have tried everything! From factory reset to fast boot and adb my pc won't even recognize my tablet. Also I never turned on usb dbugging cause I didn't even know what that was. I even gave it to the IT guys at work and they couldn't fix it. Now after reading everything there is to read on this problem and trying to fix it myself I'm stuck on the no command screen with the dead android robot. And now I hear there is a recall do to the battery, I can't even check what type I have. So if someone can please help me I would be much appreciative. Also this happened after updating to the latest OS.

okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?

Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Can you flash twrp and boot to it?

Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Hello,
Did you use "Fastboot flash recovery.img" as your command line??
I believe it is "Fastboot flash recovery recovery.img"
If you were able to unlock bootloader you're on the right track.
Sent from a Locked Bootloader

Yes I used "fastboot flash recovery recovery.img" but every command after that keeps telling me "failed to write file"

danjull said:
Can you flash twrp and boot to it?
Click to expand...
Click to collapse
I'm a complete noob when it comes to this stuff, what is twrp? Haha

Ace0169 said:
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Click to expand...
Click to collapse
TWRP (Team Win Recovery Project) is a custom recovery that you can flash on your device. You can flash it like the stock recovery over fastboot. With TWRP you can make full system backups, installing roms or other stuff, wipe partitions and more. Keep trying to install the drivers on your pc. Try to use another usb slot or boot your pc into test mode to install the driver. If you can still access the bootloader, you have really good chances to rescue your device.

Okay will try that. Thanks man.

Ace0169 said:
Okay will try that. Thanks man.
Click to expand...
Click to collapse
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5

Mojar7070 said:
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Click to expand...
Click to collapse
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?

Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader

Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
Those official nVidia recovery images come with smaller .img files such as recovery.img, system.img, etc. You'll need to flash those one by one ("fastboot flash recovery recovery.img", then run "fastboot flash system system.img", etc. etc.) or you can just run the flashall script that I think is included in the nVidia images.
Otherwise, if you want to flash TWRP, you'll need to download the TWRP recovery (you can rename it to "twrp-recovery.zip"). Then you'll need to "fastboot flash twrp-recovery.zip" in order to flash the twrp recovery to your tablet.

Mojar7070 said:
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Click to expand...
Click to collapse
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.

Ace0169 said:
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Click to expand...
Click to collapse
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5

Mojar7070 said:
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Click to expand...
Click to collapse
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?

Ace0169 said:
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Click to expand...
Click to collapse
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.

koop1955 said:
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
Click to expand...
Click to collapse
Select "fastboot protocol"? Is that correct?

Ace0169 said:
Select "fastboot protocol"? Is that correct?
Click to expand...
Click to collapse
So i selected "fastboot protocol" it blipped for a second then brought me back to the bootloader. tried flashing again and once i reached the fastboot flash system system.img it said write failed again. did it not engage the "fastboot protocol"?

Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.

koop1955 said:
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
Click to expand...
Click to collapse
@Ace0169 Same, not sure what else to tell you. Sorry sir.
Sent from a Locked Bootloader

Trying to root, can't boot into recovery

This is my fourth failed attempt to do anything custom with an android phone (yes, 4 different phones). Why is it so hard?
I'm following some nice instructions from teamandroid.com, but I can't get into recovery. Either I get "no command", or if I flash and go into recovery right away while connected, I get "Error: failed to load kernel!"
I wasn't able to flash TWRP ("Image size exeeded partition limits") but clockwork-6.0.4.7-falcon seemed to work. Just can't boot into it. I don't know what else to try, I don't know why it doesn't work.
Can anyone help me? Just trying to root my Moto G 2015 for development purposes. thanks so much.

rmp251 said:
This is my fourth failed attempt to do anything custom with an android phone (yes, 4 different phones). Why is it so hard?
I'm following some nice instructions from teamandroid.com, but I can't get into recovery. Either I get "no command", or if I flash and go into recovery right away while connected, I get "Error: failed to load kernel!"
I wasn't able to flash TWRP ("Image size exeeded partition limits") but clockwork-6.0.4.7-falcon seemed to work. Just can't boot into it. I don't know what else to try, I don't know why it doesn't work.
Can anyone help me? Just trying to root my Moto G 2015 for development purposes. thanks so much.
Click to expand...
Click to collapse
I assume your talking about this guide: http://www.teamandroid.com/2015/10/02/root-moto-g-2015-on-android-5-1-lollipop-with-supersu/
It is an OK guide, but you really have to read the details... did you unlock via the Motorola Bootloader Unlock page? Nothing will work properly until you do.

Yes that's the guide (xda didn't let me post the link). Yes I did unlock that way. I'm trying to follow all of the details and I don't think I've missed anything (hence my frustration).

http://forum.xda-developers.com/showthread.php?t=3188850

Thank you hp420! This is what worked for me:
fastboot boot twrp-osprey-2.8.7-test1.img

What helps you ... Can u please explain that... I have a same issue with moto g4 plus... Failed to load kernel....

Vishaly634 said:
What helps you ... Can u please explain that... I have a same issue with moto g4 plus... Failed to load kernel....
Click to expand...
Click to collapse
Kind of digging up an old thread here, what is the problem you are having and what process are you using? TBH, this is pretty simple but you need the TWRP specific to your device and just flash Magisk.

Moto g4 plus root problem..,
After installing twrp.img with mfastboot while I enter in recovery mode after few seconds it shows u need software repair assistant and final shows failed to load kernel.... Can u help me with this....I m totally confused: I Hove no idea what to do now...
..In red ....It shows..
Start up failed:
Your device didn't start up successfully.
Use the software repair assistant on computer
To repair your device.
Connect your device to your computer to get the software repair assistant.
IN RED - AP Fastboot flash mode (secure)
In green - Fastboot reason: volume down key pressed
USB connected
.....
......
In red - failed to load kernel !
Boot up failed
This is what shows up after I enter into recovery mode
...Please help me to root my devices...And reply fast

Vishaly634 said:
After installing twrp.img with mfastboot while I enter in recovery mode after few seconds it shows u need software repair assistant and final shows failed to load kernel.... Can u help me with this....I m totally confused: I Hove no idea what to do now...
..In red ....It shows..
Start up failed:
Your device didn't start up successfully.
Use the software repair assistant on computer
To repair your device.
Connect your device to your computer to get the software repair assistant.
IN RED - AP Fastboot flash mode (secure)
In green - Fastboot reason: volume down key pressed
USB connected
.....
......
In red - failed to load kernel !
Boot up failed
This is what shows up after I enter into recovery mode
...Please help me to root my devices...And reply fast
Click to expand...
Click to collapse
Flash the factory image... There are threads for the software and how to do it.

How to flash the factory image.... Can you please tell me in detail...Which thread ??? How to do it..

Vishaly634 said:
How to flash the factory image.... Can you please tell me in detail...Which thread ??? How to do it..
Click to expand...
Click to collapse
There is literally two threads in general... One is for factory firmware images, and one is how to flash factory firmware images. I am not going to spoon-feed you the answer just because you won't look. Find the threads, read a bit, and try it, if you have issues post in the appropriate thread.

Flashing new TWRP 3.1.1 lead me to no recovery

Hi guys.
My issue: I had TWRP 3.0.2.1 on my honor and decided to update to latest version. Big error.
I have the TWRP app installed and I followed the procedure to flash recovery with that app. It seemed everything was fine, because it said ""recovery flashed".
Now when I try to enter recovery, my phone gets stuck at logo "your device is booting now".
I have to reboot in EMUI recovery to go out from that stuck page and to load normally the phone.
So I decided to flash recovery in the old ADB fashioned way: now when I get to "fastboot flash recovery twrp.img", the phone tells me "FAILED (remote: Command not allowed)"
Practically now I have no TWRP and I do not know how to proceed.
Some good Samaritan out there?
Thanks.

My firmware is latest Nougat (BLN-L21C432B360).
I tried to flash TRWP 3.1.1. Before this try, I had version 3.0.2-1 as written above. I flashed twrp when I still had Android 6 with EMUI 4.
Regarding the way to enter TWRP, yes, I know the method and I do it.
The problem is my phone don't enter twrp but remain stuck at logo.
It seems that the recovery is not present or has problems.
I've tried even to reflash the old recovery, just in case. Nothing.

Try this-
flash stock recovery for your model.
boot normally.
flash TWRP latest.

Now I try and post later.
What a mess. I should leave the old 3.0.2 which was working good...

I was already on nougat and the 3.0.2 was still working perfectly. I had flashed that twrp when I was still on 6.0 and after the update with firmware finder it was still working.
Moreover I used the official TWRP app to update and it failed miserably even if it said flash successful at the end of operation....

Then I used the classic way with ADB and still nothing.
I can see on the Windows shell "failed: command not allowed"

Rommco05 said:
Frp in fastboot is unlocked?
Click to expand...
Click to collapse
AFAIK, Factory Reset Protection is linked to account protection in case someone steals the phone. In this way it should be more difficult to wipe completely the phone and use it.
Anyway, just checked in fastboot and no, FRP is locked. I just had a look in developer options and I noticed that "Enable OEM unlocked" is greyed out. But it should not have nothing to do with flashing the recovery.
Or not?

Let's see

Diamantes said:
Hi guys.
My issue: I had TWRP 3.0.2.1 on my honor and decided to update to latest version. Big error.
I have the TWRP app installed and I followed the procedure to flash recovery with that app. It seemed everything was fine, because it said ""recovery flashed".
Now when I try to enter recovery, my phone gets stuck at logo "your device is booting now".
I have to reboot in EMUI recovery to go out from that stuck page and to load normally the phone.
So I decided to flash recovery in the old ADB fashioned way: now when I get to "fastboot flash recovery twrp.img", the phone tells me "FAILED (remote: Command not allowed)"
Practically now I have no TWRP and I do not know how to proceed.
Some good Samaritan out there?
Thanks.
Click to expand...
Click to collapse
Unlock your boot loader

Bootloader is unlocked.
For some reason, my "OEM unlocked" option turned greyed out, and FRP is locked again.
I will try this eve to lock bootloader again and restart the unlocking operation from scratch.
Will see

Diamantes said:
Bootloader is unlocked.
For some reason, my "OEM unlocked" option turned greyed out, and FRP is locked again.
I will try this eve to lock bootloader again and restart the unlocking operation from scratch.
Will see
Click to expand...
Click to collapse
In emui 5 OEM unlock option is not there and can only be found in MM or Emui 4.x

you mean that even if I can't access TWRP, this should be still there and I cannot lock bootloader?
And you advice to do a factory reset first.
If this doesn't work? Then?

shashank1320 said:
In emui 5 OEM unlock option is not there and can only be found in MM or Emui 4.x
Click to expand...
Click to collapse
You mean that I couldn't even see the option?
I have nougat and emui 5, the option is present but greyed out

Diamantes said:
You mean that I couldn't even see the option?
I have nougat and emui 5, the option is present but greyed out
Click to expand...
Click to collapse
Yeah exactly. See SS
This was there till emui 4

So how can I solve the problem?
Someone told me the only way is to lock bootloader in order to have again this option available to be turned on... And so start the process again.
At the moment I cannot access TWRP nor flash it through ADB. Practically even if bootloader is unlocked, I have a rooted phone with no possibility to do anything else... Regarding flashing of course.

Thank you for your replies.
Anyway I really know now that I cannot buy honor for flashing.
I just tried a factory reset from advanced options.
After all the pin request etc, the phone rebooted and get stuck on the initial window (your phone has been unlocked and cannot be trusted-your phone is booting now...).
So I had to press usual buttons to enter in emui recovery, the only way I can get the rebooting option from this state.
Of course the phone is not reset.
I give up. This crappy phone is taking too much time of my life.
I will keep it like this. And I'm not sure at all I will get future OTA update.
I never EVER had these issues with Samsung phones or HTC, and believe me that I was flashaholic... I flashed tens and tens of ROMs, I rooted and unlocked all my previous phones with no glitches or whatever..,
This time I tried honor for the price.
Never again for flashing or playing around.
Just for normal, classic phone use, hoping it will last some other month before I purchase another brand.
Thank you all.

Of course my thoughts about this ****ty phone were all right.
I received the ota update for version b365, downloaded and OF COURSE STUCK at boot logo after automatic restart...
I will never be able to install anything else because the recovery is corrupted.
I am condemned to stay with b360 until this cursed phone will die for natural causes...
No comment

Diamantes said:
Of course my thoughts about this ****ty phone were all right.
I received the ota update for version b365, downloaded and OF COURSE STUCK at boot logo after automatic restart...
I will never be able to install anything else because the recovery is corrupted.
I am condemned to stay with b360 until this cursed phone will die for natural causes...
No comment
Click to expand...
Click to collapse
But recovery can be changed mate. Try twrp with new thread in my signature and follow steps, it won't be a trouble. Try once in free time as i know you already are frustrated with trying all ways.

The TWRP on official TWRP site sadly won't work for our berlin devices, i neither know why it is still there sincerely. Personally i can't recommend the usage of TWRP official app for our phone as it downloads a wrong version... you have to get the OpenKirin edition from here https://forum.xda-developers.com/honor-6x/development/twrp-t3583413 and flash that via adb fastboot. Be sure to have "USB debug" on by developer options menu, and to have installed HiSuite (just to have all the functional drivers)

I thank you all for your patience and replies.
But as Shashank said, I'm really frustrated because I tried everything in the past.
Now I'm rooted (luckily) but with FRP locked. It seems the reason why I cannot flash nothing.
In any case I will try again the suggestion of redskull. The last hope!
Thanks.

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!