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! not sure if i hard bricked my phone

Hi everyone i flashed kings marshmallow hydrogen os but i didnt like it so i reverted back to my blisspop via nandroid backup. Unfortunately I am know stuck at the oneplus boot screen with the oneplus logo in the middle and the powered by android logo at the bottom. I am unable to boot into twrp. I was able to boot into fastboot mode and managed to flash twrp recovery however the phone will not load into recovery and goes to the oneplus boot screen. I think i softbriked or hard bricked phone because i went from kings hydrogen os which is marshamllow based to my nandroid backup which is blisspop 5.1. IDK what to do know
Bottom line i can boot into fastboot mode. device manager on my pc recognizes phone as android device- marshall london bootlooder interface any suggestions?

If you can Boot to Fastboot you have a softbrick. Somewhere around here is a thread for the recovery tool with the qualcom drivers. Read carefully and maybe give it a try.

Scherzengel said:
If you can Boot to Fastboot you have a softbrick. Somewhere around here is a thread for the recovery tool with the qualcom drivers. Read carefully and maybe give it a try.
Click to expand...
Click to collapse
Ok i thought that was for hardbrick. I will give it a try anyway

neal425 said:
Ok i thought that was for hardbrick. I will give it a try anyway
Click to expand...
Click to collapse
I installed the qualcom drivers and recovery tool, but the recovery tool doesnt do anything

neal425 said:
Hi everyone i flashed kings marshmallow hydrogen os but i didnt like it so i reverted back to my blisspop via nandroid backup. Unfortunately I am know stuck at the oneplus boot screen with the oneplus logo in the middle and the powered by android logo at the bottom. I am unable to boot into twrp. I was able to boot into fastboot mode and managed to flash twrp recovery however the phone will not load into recovery and goes to the oneplus boot screen. I think i softbriked or hard bricked phone because i went from kings hydrogen os which is marshamllow based to my nandroid backup which is blisspop 5.1. IDK what to do know
Bottom line i can boot into fastboot mode. device manager on my pc recognizes phone as android device- marshall london bootlooder interface any suggestions?
Click to expand...
Click to collapse
Do restore again. Flash 5.1.1 patch youre ok
Do you read OP.. Once you go MM you cannot go back without flashing the patch

lummujaj said:
Do restore again. Flash 5.1.1 patch youre ok
Do you read OP.. Once you go MM you cannot go back without flashing the patch
Click to expand...
Click to collapse
can you please elaborate. I have no way of getting into recovery how am i suppose to flash the patch?

Download twrp 3.0.0.0 (since you were MM ) flash it via adb... Reboot to recovery and flash the patch.. After flashin it automaticlly reboot. Than restore backup

lummujaj said:
Download twrp 3.0.0.0 (since you were MM ) flash it via adb... Reboot to recovery and flash the patch.. After flashin it automaticlly reboot. Than restore backup
Click to expand...
Click to collapse
I have done this already... the recovery will not load

lummujaj said:
Download twrp 3.0.0.0 (since you were MM ) flash it via adb... Reboot to recovery and flash the patch.. After flashin it automaticlly reboot. Than restore backup
Click to expand...
Click to collapse
i flash twrp 3.0 using fastboot flash recovery command.....
just so u know
if i type in adb devices nothing is recognized
if i type in fastboot devices my device is recognized

You cant use adb in fastboot mode.. Wtf
fastboot flash recovery recoveryname.img
fastboot boot recoveryname.img
In recovery flash the patch.. Than restore backup.. So simple. Why you complicate
Post cmd comands and results

lummujaj said:
You cant use adb in fastboot mode.. Wtf
fastboot flash recovery recoveryname.img
fastboot boot recoveryname.img
In recovery flash the patch.. Than restore backup.. So simple. Why you complicate
Post cmd comands and results
Click to expand...
Click to collapse
i did flash via fasboot after i flash it says sending recovery (okay) writing recovery (okay) than i reboot but. but when i try to reboot into recovery it does not reboot into RECOVERY it justs stuck at one plust boot screen.

Stucking 1+ logo is because having unsupported recovery from system... After you did restore did you got any error...
Get both recoveries and try command
fastboot boot recoveryname.img
One of them has to boot. Youre doing something wrong

lummujaj said:
Stucking 1+ logo is because having unsupported recovery from system... After you did restore did you got any error...
Get both recoveries and try command
fastboot boot recoveryname.img
One of them has to boot. Youre doing something wrong
Click to expand...
Click to collapse
after i did restore i did not get an error
ive tried to flash twrp 2.87 and twrp 3.0. i promise u i am flashing the recoveries correctly. each time i flash the recovery it says ok. it just wont boot into recovery after it is flashed

Did you try the coomant to boot automaticlly .. Try both recoveries
fastboot boot recoveryname.img

lummujaj said:
Did you try the coomant to boot automaticlly .. Try both recoveries
fastboot boot recoveryname.img
Click to expand...
Click to collapse
just tried that for both recoverie says downloading boot img okay. than it next thing it says remote: dtb not found

lummujaj said:
Did you try the coomant to boot automaticlly .. Try both recoveries
fastboot boot recoveryname.img
Click to expand...
Click to collapse
hey man i really appreciate you taking the time to help me out but i dont think its gonna work, im just gonna use the hardbrick method to restore my phone

Hope you will find a solution... Try firstaid from general section. I still insist about having bad recovery. Or go to op supoort site and back all to stock

Lost recovery, cant boot, only fastboot

Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode

You need to run the phone in Qualcomm mode on a PC and run the recovery tool to fix you bootloader.
I did the same and it was a royal ball ache trying to find out how to fix it

Don't do what rosswaa said

Why not?

What you should do is boot your phone into fastboot mode, connect it to your pc. Flash this modified TWRP recovery img to your phone https://www.androidfilehost.com/?fid=24459283995297945. After that you have to flash this modified SuperSU (through the new recovery) https://www.androidfilehost.com/?fid=24459283995297946.
The normal recovery doesn't work in OOS 3.0 (just like in HOS) and it's the SuperSU that gives you the soft brick. A dirty flash of the modified SuperSU should fix it.
I also had your problem and I did what rosswaa said which shouldn't be necessary (I lost all my data and backups).

I didn't lose anything, but I tried doing what you said and my bootloader was screwed so wouldn't take a flashed recovery or anything (yes the modified one)
Wish I hadnt been so excited and just flashed but all sorted now

Hmm okay, if it doesn't work with flashing the new recovery img then do what rosswaa said and after that follow this post https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/

Obviously try what green says first, if it works then happy days

first i am really glad that someone give some advices on me. But since i am a noob, how can i flash twrp in fastboot mode? using command? "fastboot flash recovery xxx.img"? thx

SPiCa39's said:
Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode
Click to expand...
Click to collapse
1 Install official TWRP 3.x via fastboot twrp.me/devices/oneplustwo.html
Reboot to recovery
2 install this modified version of TWRP
forum.xda-developers.com/oneplus-2/development/recovery-teamwin-recovery-project-3-0-0-t3310713
Reboot to recovery
3 install oos3 (And supersu)
Sorry i can't post link

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

(Moto G6 Plus) Cannot install twrp!

hello all, i cant install twrp in moto g6 plus, i get the error in cmd "(bootloader) Invalid partition name recovery ,(Failed) remote failure" after the command "fastboot flash recovery", but it works in command "fastboot flash boot" but this last dont works, the twrp delete my system, and android only boot in twrp, i have the drivers, bootloader unlocked, adb and fastboot, and various twrp.img for my device, please help me, i need to install twrp permanent!

Anonimo404 said:
hello all, i cant install twrp in moto g6 plus,........
Click to expand...
Click to collapse
I don't have this device but, your best bet is to take a look at the following thread and post your question within it that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3854240
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900T device.

Boot do not flash
Please do Not try installing TWRP as it is unsupported for now. Simply have to boot the TWRP.
Fastboot boot TWRP.img
I hope this changes but for now we need our pc.

ksk35695 said:
Please do Not try installing TWRP as it is unsupported for now. Simply have to boot the TWRP.
Fastboot boot TWRP.img
I hope this changes but for now we need our pc.
Click to expand...
Click to collapse
New to device:
do that mean.
we must not!
install the version 3.2.3.0
from the official TWRP homepage ??

No, no.. Reboot to bootloader and use this command. fastboot boot TWRP.img
We need a pc for this.
Our development still working on this. For now do not flash anything to the boot partition.

This device uses the a-b slots and does not have a recovery partition as before, the recovery is now part of the boot.
Use
fastboot boot twtp_every_xxx.img

You can install TWRP on this device and it's very simple!
First boot TWRP via fastboot boot twrp.img and then flash the TWRP-Installer.zip in TWRP. This overwrites the stock recovery which is within the boot.img now for A/B devices. After that you have to flash the magisk.zip and it's done!
Just use Google to find twrp-installer.zip/evert

segra246x said:
You can install TWRP on this device and it's very simple!
First boot TWRP via fastboot boot twrp.img and then flash the TWRP-Installer.zip in TWRP. This overwrites the stock recovery which is within the boot.img now for A/B devices. After that you have to flash the magisk.zip and it's done!
Just use Google to find twrp-installer.zip/evert
Click to expand...
Click to collapse
This installer has been around awhile and there is a reason the official twrps that are far newer cannot be installed yet. While it may seem like it works on the surface, this causes errors in the kernel itself if memory serves me right. This method is not advised! Hopefully, we are on the verge of a breakthrough on a proper official version that can install.