Database Users

Flashed TWRP as boot.img / Now it only goes to recovery HELP ME!!!

Hi people...
Everything was going so smoothly... bootloader unlock... root... some nice root apps... free paid games... and my p8 lite was just feeling so good... until... I flashed twrp with flashify under the name of boot.img... Am I stupid or what?! Now I can only get 2 scenarios... when i turn on the phone it goes directly to twrp. In twrp i get the option to go the bootloader screen... If I choose system it goes back to twrp... I can't get it to start. I downloaded the official tar.gz from emui site but I dont know how can I install it. PLEASE HELP... What should I do in this case?! I miss my baby...
Thanks in advance

You have to restore stock recovery in fastboot mode.

arviit said:
You have to restore stock recovery in fastboot mode.
Click to expand...
Click to collapse
How do I do that?! If I wanted to wipe my phone completely and re-install the OS would be better to do it using twrp or stock recovery?
Thank you very much

Sorry, i misunderstood. If you flashed twrp as boot.img, reflash stock boot in fastboot mode.

flash stock boot.img in fastboot mode
and then flash twrp as recovery
will be like this
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery TWRP.img
fastboot reboot
use the boot.img from stock rom and twrp image you downloaded

Oh no!
Now I made some serious **** to my baby... guess now i'll have to send it to huawei to fix it. I made a full wipe like if it was format c: in computers... everything is gone (i didnt had any personal data) it doesnt have OS even. But when I still had twrp i tried to flash boot.img and recovery.img and now when i start it goes directly to bootloader screen but saying "please update system again" and where it used to say phone unlocked it now says (in red letters):
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
I was able to get to eRecovery with usb connected but when i choose to download e install the new version it gives me the message "wifi starting failed".
It also does not get any instuction with fastboot. but hi suite starts when I connect it. Strange?!
What do you think? Should I send it to huawei? Or is it possible for me to make it work again?
Also tried UPDATE.APP function and all give me fail message.
I'm going crazy!!!! But I love to mess around with android... To me this is the android essence. Fortunately I have a lumia for when my baby doesnt work.loooool
Thank you all

I don't understand why you don't use fastboot. Everybody told you to use it. In our phone situation, without custom kernel or rom, twrp is for experimentation and you cannot mix things.

arviit said:
I don't understand why you don't use fastboot. Everybody told you to use it. In our phone situation, without custom kernel or rom, twrp is for experimentation and you cannot mix things.
Click to expand...
Click to collapse
Well, you warned me... but sometimes i do these kind of *****... So, in this situation you think it's better to send it or is there way to fix this.
By the way, when I enter huawei eRecovery and I get the option to download the firmware through wifi and it says wifi starting failed, is there any way to make this work? And to fastboot do we need to open cmd as administrator to make it work? Because if Hi suite detects the phone I should also be able to fastboot it right?
Thanks for your patience

Just use fastboot aand flash everything
Recovery
Boot
Systme
Cust

jabonloco said:
flash stock boot.img in fastboot mode
and then flash twrp as recovery
will be like this
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery TWRP.img
fastboot reboot
use the boot.img from stock rom and twrp image you downloaded
Click to expand...
Click to collapse
hello I have p8 lite unlocked and rooted, yesterday I wanted to install the TWRP 2.8.7. but I was wrong and I installed twrp for the p8 and not p8 lite.
When I go into recovery mode my phone locks that read huawey, I tried with fastboot command to delete the wrong recovery and install the right of the p8 lite but the result does not change, my phone locks that read huawey
i think The commands that you wrote and that I have quoted are also fine for my case, it's' true?
i have version firmware b133 which boot.img from stock rom?

Try to reflash stock boot.img too.

arviit said:
Try to reflash stock boot.img too.
Click to expand...
Click to collapse
but Ido the extraction of the boot.img from the update version b133?

Hi everyone!!
First of all, thanks to everybody who helped me with this situation.
I now am using my baby again as if it was new. I wiped him completely as i stated before and it was as easy as finding the right firmware (136a) and using the vol down + vol up + power button technique. I put the UPDATE.APP file inside a folder named dload in sdcard using other phone (with my p8 was impossible). After that rebooted the device, pressed those 3 buttons and the instalation started successfully.
I just cant explain how happy i was. I stayed 3 days without it.
After that I have been messing with fastboot so thanks to everyone who made me realize that i didnt need to do all of this, but well, A full wipe is always welcome.
Is there any custom kernel on the way for overclock my baby?

Please explain to me how do I put SOLVED in this thread as my problem is already solved...
Thanks

siul_lasc said:
Hi everyone!!
First of all, thanks to everybody who helped me with this situation.
I now am using my baby again as if it was new. I wiped him completely as i stated before and it was as easy as finding the right firmware (136a) and using the vol down + vol up + power button technique. I put the UPDATE.APP file inside a folder named dload in sdcard using other phone (with my p8 was impossible). After that rebooted the device, pressed those 3 buttons and the instalation started successfully.
I just cant explain how happy i was. I stayed 3 days without it.
After that I have been messing with fastboot so thanks to everyone who made me realize that i didnt need to do all of this, but well, A full wipe is always welcome.
Is there any custom kernel on the way for overclock my baby?
Click to expand...
Click to collapse
I also have same problem. Now i am going to try this. thank you very much.
---------- Post added at 02:22 PM ---------- Previous post was at 01:53 PM ----------
siul_lasc said:
Hi everyone!!
First of all, thanks to everybody who helped me with this situation.
I now am using my baby again as if it was new. I wiped him completely as i stated before and it was as easy as finding the right firmware (136a) and using the vol down + vol up + power button technique. I put the UPDATE.APP file inside a folder named dload in sdcard using other phone (with my p8 was impossible). After that rebooted the device, pressed those 3 buttons and the instalation started successfully.
I just cant explain how happy i was. I stayed 3 days without it.
After that I have been messing with fastboot so thanks to everyone who made me realize that i didnt need to do all of this, but well, A full wipe is always welcome.
Is there any custom kernel on the way for overclock my baby?
Click to expand...
Click to collapse
Yeah finally my phone is working now thanks to you I searched many treads and forums but i cant find a solution. But finally i got an easy solution Thank you again bro.. Good Luck !!!:good::good::good::good::good::good::good:

Just download your firmware version, use huawei extractor to extract boot.img,cust.img,recovery.img and system.img
After that,download mininal adb fastboot copy you files into fastboot folder , enter fastboot mode on your phone and from fastboot folder,open cmd and type these commands:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
After this your phone will boot normally. Once you've done this, copy update.app to your sdcard or internal and install it by local update. Once you've done all this,your phone is fine.

May I know how do you wipe your internal storage? and what if after wiping, im unable to get into recovery mode? does it mean phone is not usable anymore?

SOLUTION
Hello. I'm the bigest mess on androids but i know that flashing stock recovery can remove any TWRP/CWR. If its too powerfull flash stock boot and run fastboot -w.(fastboot -w erases all PERSONAL data)

Guys Help me in this
guys help me
http://forum.xda-developers.com/honor-7/help/stock-emui-recovery-image-lost-twrp-t3442021

thank you !!
VladHD said:
Just download your firmware version, use huawei extractor to extract boot.img,cust.img,recovery.img and system.img
After that,download mininal adb fastboot copy you files into fastboot folder , enter fastboot mode on your phone and from fastboot folder,open cmd and type these commands:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
After this your phone will boot normally. Once you've done this, copy update.app to your sdcard or internal and install it by local update. Once you've done all this,your phone is fine.
Click to expand...
Click to collapse
After days of searching the internet i couldnt find any working solution. then i tried the local update without flashing al those .img's. ( didnt work )
Now after flashing al those .img's my phone works again but its a whole different phone. Only problem is when i try to update him with the update.app file it won't go any further then 5%.
If you know why this happens let me know
Further i wanna thank you one last time .. thank you

Help help help with a hard bricked 6P

Hello guys,
I had my phone rooted with latest twrp. I flashed stock+ rom with Franco Kernel 25r and the A.R.I.S.E file for better sound. I've done the same set up minus the ARISE file and never had an issue.
well to my luck it kept bootlooping and I wasn't able to get back into my custom recovery. When I got home and got my hands on a pc I did a factory reset by manually flashing stock google img . I even used a couple tools since I ran out of ideas and still no luck.
I'm able to do anything through fastboot but I can't seem to get into my recovery at all.
Any ideas or tips of where I should go next?

Not a Hardbrick
As long as you can get to the bootloader mode, you haven't hard bricked your device. Hardbricking is a point where you cant boot your device and in to bootloader so there is no way to flash your device to a useable state.
Now as you can boot to the bootloader, just fastboot boot twrp.img and if you have a factory image zip, copy it in your device internal storage and flash it. Its that simple, provided you are already using an unencrypted boot.img in your current setup. Or else the next step is to flash an decrypted boot.img(you will loose all your userdata and internal storage data.). There are ways to mount the the encrypted filesystem if you are using a pin or password combo with your fingerprint. But without it its a bit more trickier so just for ease and if you dont have any inseparable data in your device now just flash a decrypted boot.img and then you can easily mount your internal storage to your pc and copy the factory image and the rest you already know..

At this point, I'd recommend a full reset.
Flash all the images in the latest Android M factory image (don't flash DP5 or similar N based ROMs): Recovery, Boot, System, Bootloader, Radio, everything.
Once you get stabilized and back into a working phone, then start rooting and messing around with kernels and what not.
To be completely honest, I've flashed nearly every ROM for the 6p, as well as my other Nexus devices, Galaxy phones, Sony phones, and no-name brands and none of those ultra modified kernels did any noticeable change. I tried the F2FS, NTFS, etc file system changes, tweaks to the governors and IO's, all of that, and found the stock kernel was the best. If a kernel with a different IO Scheduler worked even 10% better than the current implementation, and was just as stable, don't you think the Google/Android Engineers would've pushed that to live?
Currently running Pure Nexus July 23rd Update, everything stock that comes with it, Systemless Root/XPosed, and Viper4Android and have never had a performance or stability issue. I'd recommend you do the same.

leninmon said:
As long as you can get to the bootloader mode, you haven't hard bricked your device. Hardbricking is a point where you cant boot your device and in to bootloader so there is no way to flash your device to a useable state.
Now as you can boot to the bootloader, just fastboot boot twrp.img and if you have a factory image zip, copy it in your device internal storage and flash it. Its that simple, provided you are already using an unencrypted boot.img in your current setup. Or else the next step is to flash an decrypted boot.img(you will loose all your userdata and internal storage data.). There are ways to mount the the encrypted filesystem if you are using a pin or password combo with your fingerprint. But without it its a bit more trickier so just for ease and if you dont have any inseparable data in your device now just flash a decrypted boot.img and then you can easily mount your internal storage to your pc and copy the factory image and the rest you already know..
Click to expand...
Click to collapse
First of all thank you for the response.
I've tried flashing the most current twrp and it seems to go through fine on fast boot but when I actually try to get into recovery from the device it will boot loop and just keep doing that.
How can I get into the phones storage through fastboot?
Where can I get the factory zip?
it feels as if everything seems to go good through fastboot but when I actually try to boot the phone nothing seems to work.

Wiltron said:
At this point, I'd recommend a full reset.
Flash all the images in the latest Android M factory image (don't flash DP5 or similar N based ROMs): Recovery, Boot, System, Bootloader, Radio, everything.
Once you get stabilized and back into a working phone, then start rooting and messing around with kernels and what not.
To be completely honest, I've flashed nearly every ROM for the 6p, as well as my other Nexus devices, Galaxy phones, Sony phones, and no-name brands and none of those ultra modified kernels did any noticeable change. I tried the F2FS, NTFS, etc file system changes, tweaks to the governors and IO's, all of that, and found the stock kernel was the best. If a kernel with a different IO Scheduler worked even 10% better than the current implementation, and was just as stable, don't you think the Google/Android Engineers would've pushed that to live?
Currently running Pure Nexus July 23rd Update, everything stock that comes with it, Systemless Root/XPosed, and Viper4Android and have never had a performance or stability issue. I'd recommend you do the same.
Click to expand...
Click to collapse
Thanks for the reply.
I've done the manual flashing already and flashed everything single item the most current factory image. Everything seemed to have gone through okay but when I rebooted the phone it was back to 0.
I'm actually considering getting rid of the phone now since it is my daily =/

Format each partition before flashing.
fastboot format <partition>
wait until it's done, then
fastboot flash <partition> <image>
Some partitions can't be formatted, which there are ways around, but try this first.

Just get to bootloader mode and try booting the twrp.img
fastboot boot twrp.img
From the twrp ui, go to advanced wipe and format your storage.
To mount the internal storage on your PC, enable mtp from twrp screen.
If U are using a decrypted boot.img, it will easily mount ur internal storage. Or try flashing a decrypted boot.img
fastboot flash boot boot.img
Then try the above again..

leninmon said:
Just get to bootloader mode and try booting the twrp.img
fastboot boot twrp.img
From the twrp ui, go to advanced wipe and format your storage.
To mount the internal storage on your PC, enable mtp from twrp screen.
If U are using a decrypted boot.img, it will easily mount ur internal storage. Or try flashing a decrypted boot.img
fastboot flash boot boot.img
Then try the above again..
Click to expand...
Click to collapse
I flashed the twrp.img and it went through successfully at least on the computer it did but when the phone actually tries to get into recovery (twrp) it will start to boot loop and keep on doing that. I tried both an encrypted and decrypted boot img but it still made no difference.
I'm really going crazy over this

Wiltron said:
Format each partition before flashing.
fastboot format <partition>
wait until it's done, then
fastboot flash <partition> <image>
Some partitions can't be formatted, which there are ways around, but try this first.
Click to expand...
Click to collapse
I just tried this and had no luck =/....the phone wont get past the google boot screen

You need to explain more on what you actually tried here.
Just download the latest factory image and try to flash the latest bootloader using fastboot.
Then boot to the bootloader and try formating the device. Not wiping
Then you have to
fastboot boot twrp.img
I believe you have only tried wiping not formating. I faced similar issue before. But once I flashed a decrypted boot.img, it cleared the user data and then I was able to get to twrp.
Maybe your twrp img is corrupted if this didn't work.

leninmon said:
You need to explain more on what you actually tried here.
Just download the latest factory image and try to flash the latest bootloader using fastboot.
Then boot to the bootloader and try formating the device. Not wiping
Then you have to
fastboot boot twrp.img
I believe you have only tried wiping not formating. I faced similar issue before. But once I flashed a decrypted boot.img, it cleared the user data and then I was able to get to twrp.
Maybe your twrp img is corrupted if this didn't work.
Click to expand...
Click to collapse
i just flashed the latest bootloader from the most recent factory image and i did the command format user data and then tried the fastboot boot twrp and the phone will then try to get into recovery, the google logo comes up lasts a couple seconds and boot loops all over to where is says my phone cant be check for corruption
By now i should have been able to get into recovery and it wont go through

edgarted said:
i just flashed the latest bootloader from the most recent factory image and i did the command format user data and then tried the fastboot boot twrp and the phone will then try to get into recovery, the google logo comes up lasts a couple seconds and boot loops all over to where is says my phone cant be check for corruption
By now i should have been able to get into recovery and it wont go through
Click to expand...
Click to collapse
download a factory image and run the flash all file...... it should reboot your phone after 5 minutes and the issue should be resolved.. a hard brick would be a device that does nothing.... in this case i believe that you just didnt do something right.

Then download the latest factory image and extract it
fastboot flash radio.img
fastboot flash bootloader.img
& do a fastboot update the rest archive file as it is
This will flash the rom via fastboot& U don't have to rely on TWRP or CWM

i42o said:
download a factory image and run the flash all file...... it should reboot your phone after 5 minutes and the issue should be resolved.. a hard brick would be a device that does nothing.... in this case i believe that you just didnt do something right.
Click to expand...
Click to collapse
I was really really hoping this would help. I erase/formated everything before flashing anything. I then ran the flash-all file and it took a couple of minutes and it said finished on the command box and my phone restarted and went into the white google logo and rebooted again with a bootloop. I waited around 15 minutes hoping it would start but it didn't.
It honestly feels as if the phone is not processing the full commands but on the pc it seems to go through successfully
is there a way to force an install of a rom and see if maybe a dirty flash over the stock one will allow it to start up?

leninmon said:
Then download the latest factory image and extract it
fastboot flash radio.img
fastboot flash bootloader.img
& do a fastboot update the rest archive file as it is
This will flash the rom via fastboot& U don't have to rely on TWRP or CWM
Click to expand...
Click to collapse
i know how to flash the radio and bootloader but how do i do a fastboot update?

edgarted said:
i know how to flash the radio and bootloader but how do i do a fastboot update?
Click to expand...
Click to collapse
Just unzip the factory image and there U can see the flash shell script files too. Open them in a text editor & U could see the exact command. In a factory img, they also do the same thing via script files. Flashing the radio & bootloader & updating the rest archive

so this is what I've done
I've manually flashed every file needed for the factory image from google.
I also tried wugfresh tool kit which is great but didn't help me much. I flashed stock recovery and treid to boot into to and nothing. I flashed a customer recovery and nothing.
It always does the same thing
the screen that says my phone can't be checked for corruption and then the google sign comes up stays on for a couple seconds and then it bootloops to the can't be checked for corruption.
I try to get into recovery using fastboot commands and the phone does the same exact thing.
I was even able to lock and relock the bootloader and I was able to successfully flash everything at least that is what it showed on the computer
so ive read almost every thread that had to do with bricking and I feel like an expert now but im starting to think it is done =/

edgarted said:
so this is what I've done
I've manually flashed every file needed for the factory image from google.
I also tried wugfresh tool kit which is great but didn't help me much. I flashed stock recovery and treid to boot into to and nothing. I flashed a customer recovery and nothing.
It always does the same thing
the screen that says my phone can't be checked for corruption and then the google sign comes up stays on for a couple seconds and then it bootloops to the can't be checked for corruption.
I try to get into recovery using fastboot commands and the phone does the same exact thing.
I was even able to lock and relock the bootloader and I was able to successfully flash everything at least that is what it showed on the computer
so ive read almost every thread that had to do with bricking and I feel like an expert now but im starting to think it is done =/
Click to expand...
Click to collapse
Hey there. First off make sure to unlock again your bootloader. Then you may follow post # 10 of @Heisenberg 's flashing guide for our device.
First images to flash would be bootloader and radio. First flash bootloader, then make sure to issue the command adb reboot-bootloader. Then afterwards once the phone has rebooted back to bootloader, flash radio, then again do the adb reboot-bootloader again.
Once the phone is again back to bootloader flash the rest of the images except userdata. For the boot.img and recovery.img, flash the stock ones-don't use the decrypted boot.img and don't flash the twrp.img yet. Once all necessary images have been flashed issue the reboot-booloater command one more time, then on the bootloader screen choose the reboot option. Wait anywhere from 3-10 minutes for the phone to load. Let us know how it goes for you.

blitzkriegger said:
Hey there. First off make sure to unlock again your bootloader. Then you may follow post # 10 of @Heisenberg 's flashing guide for our device.
First images to flash would be bootloader and radio. First flash bootloader, then make sure to issue the command adb reboot-bootloader. Then afterwards once the phone has rebooted back to bootloader, flash radio, then again do the adb reboot-bootloader again.
Once the phone is again back to bootloader flash the rest of the images except userdata. For the boot.img and recovery.img, flash the stock ones-don't use the decrypted boot.img and don't flash the twrp.img yet. Once all necessary images have been flashed issue the reboot-booloater command one more time, then on the bootloader screen choose the reboot option. Wait anywhere from 3-10 minutes for the phone to load. Let us know how it goes for you.
Click to expand...
Click to collapse
Hello and thank you for helping.
I tried this method a couple of minutes ago. I flashed them this same way
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
It does the same exact thing it will try and restart the phone, the message that says it can't be checked for corruption the google logo comes up and it repeats it self non stop.
This is what doesn't make sense to me.
This is the file that I had flashed through twrp when it was working fine
Leviticus 1.3 - http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709

edgarted said:
Hello and thank you for helping.
I tried this method a couple of minutes ago. I flashed them this same way
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
It does the same exact thing it will try and restart the phone, the message that says it can't be checked for corruption the google logo comes up and it repeats it self non stop.
This is what doesn't make sense to me.
This is the file that I had flashed through twrp when it was working fine
Leviticus 1.3 - http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
Click to expand...
Click to collapse
This is weird. What version of the stock factory images did you flash? I've been using leviticus 1.3 since it came out and when i was still on stock rom. I switched over to cm builds and have been flashing every nightly since the 7/24th build, and in the process repeatesly reflashing the aound mod along, and i've had zero issues with the phone booting afterwards.

Boot from SD card. EMMC memory is dead

I have the wt86047(HM2014813,HM2XTDPro) and I have dead emmc on my phone. The internal /data /system and /cache partitions are unmountable. So I decided that I try to boot from sdcard.
I have used this tutorial Dual boot to partition my sdcard and modify the recovery and the rom(Lineage 14.1) to look for the system, data and cache partitions on sdcard.
But when I try to boot up the phone is stuck at the MI logo and I see my device in fastboot. To be able to boot to my device I need in fastboot to execute fastboot boot modifiedboot.img. This is not too much convenient as I need pc to turn my phone on. I also can only boot recovery and not to get to the recovery mode. I can however flash the image to the /recovery partition. I suspect that my /boot partition is also corrupted. I tried to manualy flash boot also with no succes. Any ideas how to boot the phone without need to use fastboot?

I have the exact same issue with the same phone.
You have modified only the fstab file ?

nings008 said:
I have the exact same issue with the same phone.
You have modified only the fstab file ?
Click to expand...
Click to collapse
In boot.img yes(fstab.qcom), in TWRP the etc/recovery.fstab and in the updater script any mention of /system and /data.
The phone boots with the fastboot boot, but it is quite slow as I have quite cheap sd card in it. I would buy a better one If I would be able to boot the phone without computer.
EDIT: Camera is also not working for some reason

Try folding the fastboot ROM.
Same thing happened to me. I tried and flashed the fastboot image. It worked. This happened to me a long time ago. Don't worry about bootloader if you can see the fastboot screen with the mi man on your phone .
http://bigota.d.miui.com/V8.0.1.0.K...DG_20160805.0000.29_4.4_global_daca6227c0.tgz
This is the link for the fastboot file for Redmi 2 aka wt88047 or any other version of the Redmi 2.
Just use the following method to flash using ADB and should be successful.
Steps to Flash MIUI Fasboot ROM Without Using Mi Flash Tool {Using Command Prompt}
We would like to suggest that Please use the Official Flashing method through Mi Flash Tool if that method didn’t work for you then try this method.
Below is the overall method to Flash MIUI 8/9 Using Command Prompt. The commands use in this method are pretty common. For most of the users are familiar with this Commands.
Quick Requirments:
Download Fastboot ROM of your device.
Xiaomi USB Driver & ADB Driver of your device.
Try Mi PC Suite if above USB Driver doesn’t work for you.
Flash MIUI Fastboot ROM Using Command Prompt
1. Download the Fastboot ROM you want to flash from the above download link. Extract the Downloaded Fastboot ROM in your Windows PC.
2. Enter into Download Folder. You will see some Files & Folder out there. Again go to Images Folder.
3. Boot your device into Fastboot Mode. To do this Switch off your phone. Now, Press Power Button + Volume Down button to boot your device into Fastboot Mode.
4.In that folder “Open Command Window” by Holding Shift Button + Right Click button of the mouse. You will see Command Prompt will open there.
5.Type following Command to check whether your device is connected or not.
fastboot devices
6. Below the command, If it shows the device then you are ready to flash. Now, Execute following commands one by one to flash the whole ROM.
fastboot flash system system.img
Press Enter to Continue
fastboot flash boot boot.img
Press Enter to Continue
fastboot flash recovery recovery.img
Press Enter to Continue
fastboot flash cache cache.img
Press Enter to Continue
Want Complete erase of data? All Data will be deleted it will be like new device. Then type this following commands.
fastboot erase userdata
Press Enter to Continue
fastboot flash userdata userdata.img
Press Enter to Continue
All Flashing process in complete. Now, Type the following code & hit enter button to Reboot your device normally.
fastboot reboot
That’s it! Congratulation! You have successfully Installed Latest MIUI Fastboot ROM. Your device bootloader is locked now & You device is unrooted. Please let me know if it helped.

d2211basu said:
Same thing happened to me. I tried and flashed the fastboot image. It worked. This happened to me a long time ago. Don't worry about bootloader if you can see the fastboot screen with the mi man on your phone .
Click to expand...
Click to collapse
This won't help. This is the hardware issue. The storage chip on the motherboard is dead. You can not write anything to it. It is possible to replace that chip but it is a quite difficult operation.

tulen_kobi said:
Any ideas how to boot the phone without need to use fastboot?
Click to expand...
Click to collapse
Looking for the same.
https://forum.xda-developers.com/android/help/how-to-boot-sd-card-qmobile-z8-bricked-t3712171

Redmi 2 Hard Bricked or Boot Dead Repair
tulen_kobi said:
I have the wt86047(HM2014813,HM2XTDPro) and I have dead emmc on my phone. The internal /data /system and /cache partitions are unmountable. So I decided that I try to boot from sdcard.
I have used this tutorial Dual boot to partition my sdcard and modify the recovery and the rom(Lineage 14.1) to look for the system, data and cache partitions on sdcard.
But when I try to boot up the phone is stuck at the MI logo and I see my device in fastboot. To be able to boot to my device I need in fastboot to execute fastboot boot modifiedboot.img. This is not too much convenient as I need pc to turn my phone on. I also can only boot recovery and not to get to the recovery mode. I can however flash the image to the /recovery partition. I suspect that my /boot partition is also corrupted. I tried to manualy flash boot also with no succes. Any ideas how to boot the phone without need to use fastboot?
Click to expand...
Click to collapse
Follow This Link
https://globaltech2u.com/how-to-bring-a-boot-dead-or-hard-bricked-redmi-2-back-to-life

Help me Recover my files from no more booting Redmi 4 Prime. I will pay for success

Hi there,
after a normal shutdown, my xiaomi redmi 4 prime is not booting anymore.
it is stuck on MI Logo. I can enter fastboot and download mode. Phone is NOT rooted and Bootloader seems to be locked, but fastboot flash recovery seems to work. But all my hope to get a twrp started failed until now. I REALLY need the files from that phone. If somebody can help me, i will pay you money if you SUCCESSFULLY help me recover the files.
Beside, adb mode does not more work, after trying to fastboot flash a twrp image. But in ADB Mode i was in sideload mode, where no commands like pull did work. Oh and i never turned od developer mode i think. I will not stop believing there must be some person on this planet who can rescue my data.
thanks for any help.

I believe adb and developer mode are irrelevant since they work from within the system. One option is to make twrp recovery boot and copy files from it, but since you tried and failed you could try something else, but as last resort since I don't remember if it saved my data.
Since your bootloader is locked you cannot flash boot partition, but you can flash every other which cold fix your system. You should find EXACT same rom you had and extract partitions you want to flash (you have tutorials online, I don't remember, think you just extract them). If you try to flash complete rom with locked partition, process will fail.
fastboot flash system
fastboot flash recovery
fastboot flash data?!or whatever (or not data if your files are there)
Hope I gave you another perspective..

Fastboot Failed (data transfer failure(unknown error)

Hello and thanks for inteterest to help. (My phone Redmi 2 Prime)
So to the point, i have my phone installed custom ROM. And today when i try to reset factory, it stuck in the MI Logo (Show and then turned off). So i forgot to flashing the twrp again last time, so i left it without any recovery. The only way is repairing it with Fastboot and installing TWRP. So i start installing all driver and flashing. But, when i want to flash twrp to my phone, it keep showing me this
fastboot flash recovery recovery.img
flashing 'recovery.img'
FAILED (Data Transfer Failure(unknown error)
DONE! 5.8 sec
But it doesnt installing any recovery. I have installing MiFlash driver. Is there any driver that i should install again? Or anything that i can do? Also my PC doesnt read my phone storage at all, it doesnt show in the explorer, but can read "my phone" and my phone model. And I'm using USB 2.0. I also have try USB 3.0 but it doesnt work too.
Any help would be appreciated. Sorry for the long post, eh?

Try to temporarily boot into recovery by this command
"fastboot boot recovery.img"
(If it boots to recovery then you can flash any zip)

dabakale said:
Try to temporarily boot into recovery by this command
"fastboot boot recovery.img"
(If it boots to recovery then you can flash any zip)
Click to expand...
Click to collapse
Thank you for replying
So i've try it, but why its stuck at 'downloading boot.img' for 2 hours?
Can i download the boot.img manually? If yes, what should i download?

Can you share a photo of error.
Or you can try miflash to flash stock rom. Then you try to flash twrp. I suspect there would be something wrong with your recovery partition.(i also had similar problem while flashing different roms.)

Ok, so when i flash stock rom on miflash, at average 70%, it show me "fastboot.exe has stopped working" and show me error 0x80004005('Error flash system.img')
Why, godness? Is it because my laptop is only having 2GB Ram?
Or is there any ways to flash TWRP with fastboot without UBL?

Egalito Rieans said:
Ok, so when i flash stock rom on miflash, at average 70%, it show me "fastboot.exe has stopped working" and show me error 0x80004005('Error flash system.img')
Why, godness? Is it because my laptop is only having 2GB Ram?
Or is there any ways to flash TWRP with fastboot without UBL?
Click to expand...
Click to collapse
Try this method
[No More Errors] [Fastboot Rom Flashing] [Direct Method]
Hi all, Yesterday i flashed miui LP on my Redmi 2 Prime. In the evening i tried to flash the miui KK with fastboot rom. But ended up with unspecified error ;). I tried many things but no luck. Then i followed direct method and that worked...
forum.xda-developers.com