Develop Bugs

[NOT WORKING] ReLock bootloader for ZE551ML

After some research on internet and xda i decided to try to relock my bootloader with the information provided by RealYoti, and this is how i did without causing a war conflict a Cthulhu evocation or a burning Zenfone
Anyway follow this guide at your own risk, turn on your brain and everything will be fine (hopefully)
Download these files
AFT: https://mega.nz/#!LcwhXDLZ!PN1jzQ0hD...QyvMzN8VK4fVBU
RAW: https://mega.nz/#!7cA3nTZC!NiHOzVoVP...axpE2es7lrwGpI
Install the Asus flash tool
Reboot your zenfone to bootloader
Open the asusflash tool
Select your model in the drop-down menu (under the button settings)
Choose if you want to keep the data or to wipe it all (i wiped)
Click on the box and the select the raw file you just downloaded
Connect your phone to the pc with the original usb cable
Now you should see your phone in the device list, check if all is ok and then start the flash clicking the green button on the top
Wait for 6-7 minutes and your phone should boot to android but now is recognized as ZE550ML, we have to fix this
Reboot to bootloader
Download from here (thanks to Shaka Huang) the last recovery set for the ze551ml (recovery.img droidboot.img boot.img)
Flash it from cmd:
Code:
fastboot flash fastboot droidboot.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash boot boot.img
Now we are ready to flash the ZE551ML firmware download the last one from the asus support site
From the bootloader enter in the recovery
Apply update from adb/sideload
From the pc CMD type
Code:
adb sideload thezipyoujustdownloaded.zip
Wait
Wipe data/cache factory restore
Reboot
Enjoy your warranty
Let me now if there is any unclear passage
Thanks to:
RealYoti
Shakalaca
I Tried to flash twrp after this procedure and it worked so the bootloader even with this method remains unlocked, it only reverts to stock

this is awesome in case you need to regain warranty!!

I Updated the first post, the bootloader after a deeper research remains unlocked, so the method with the raw file reverts only to stock
Inviato dal mio ASUS_Z00AD utilizzando Tapatalk

Very strange

To be frank, i didn't even gave a thought that it will work

In this way can I return to stock rom ?
I cant download the files from mega.
Waiting for an other method for relock the bootloader.

LG G3 Bricked / No ADB / No download mode / No recovery

Hi,
Since the rom ( http://forum.xda-developers.com/lg-g3/development/rom-resurrection-remix-lp-v5-5-5-t3198675 ) of my phone crashed. After reboot, the phone is blocked on LG logo. Now, i can't enter in recovery mode (or in the download mode) and when I start my phone, it's fixed on the LG for 5 to 10 minutes, and after that it goes to a terminal (started fastboot mode).
I have read several tutorials to use fastboot to flash the recovery to reinstall a rom, but i have a error when i tried to erase or flash the recovery partition.
I look on my phone, and this error appear : "failed to send erase grp start address".
what can i do to fix this error ?
Thanks.

up please

Use the "boot" command instead of "flash" and it should boot up into recovery or downloadmode, depending on which file you use

I tried but i am stucked on teamwin logo.
Which file do i use for download mode ?

Hard to tell, there are some laf.img files floating around on xda and google or even better, extract the laf.img from the stock kdz depending on your android version (for instance you flashed 6.0 you pick the 30b kdz and extract it with the firmware extraction tool)
I would suggest you to and try to use the boot command with them..
Be carefull, do not use the flash command until you found one that boots into downloadmode properly or you can loose your fastboot mode aswell
From then on you should be able to boot into the downloadmode and flash a new firmware via the lg flashtool

I need help please. What can i do to re install a rom ?

Does your PC recognise the port.?
I found tutorial under bender_007 signature. People seemed happy with tool.
http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-g2-all-variants/
Doesn't hurt to read and ask some questions.

no i can't connect my phone with port. I think, i nned to correct the error with fastboot. (remote : failed to erase partition)

th0was said:
no i can't connect my phone with port. I think, i nned to correct the error with fastboot. (remote : failed to erase partition)
Click to expand...
Click to collapse
Can you elaborate, how exactly your phone crashed, it is very unlikely that it will mess all the partitions just by crashing the rom?

The rom crushed twice, and now i can not access to recovery to install a new rom. I only have access to the fastboot command. Adb not working.
I tried to boot on recovery.img, but it's not working.
Thank for your help.
Regards,

Help please ?

Today i can connected to my phone with ADB when i tape this fastboot command : fastboot boot ./recovery.img.
I can too go into my phone as root with adb command : adb shell.
i tried to push flash_image on my phone and use it, but it donesn't work.
how can i flash my phone with adb command ?

[551ml] flashboot FAILD (remote: flash_cmds error!) Im stuck in fastboot

HW_Version -
Bootloader Version - unknown
IFWI Version - 0094 - 1069
Serial Number - my #
Signing - ?
Secure_boot - ?
RESULT: FAILD (remote: flash_cmds error!)
Thats what my bootloader looks like. What happened was I tried to update from Stock .184 to the new MM build. I downloaded the file and got prompted the update in my phone. It installed or did something and when it rebooted I was stuck in a bootloop with no screen.
I ended up using xFSTK Downloader everything went fine, my phone turned on with 4 colored bars and brought me in to the bootloader. I proceed to use Asus Flash Tool to flash the raw file of .194 and that's where my problem started.
It was taking soo long so I took my dog out for a good 15-20 min walk came back and the flash tool was still doing its thing and the green bar was still moving and on my phone it said RESULT OKAY.
I ended up closing the Flash Tool because it was taking soo long. I rebooted my phone then it goes in a bootloop with the 4 colored bars on the screen. Then I just keep repeating these steps and can't get anywhere.
When I am able to get in the bootloader after using xFSTK Downloader I cant use some flashboot commands. I cant flash twrp because I get FAILD (remote: flash_cmds error!) .
I was going by this guide here. http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
EDIT: I just noticed that my phone doesnt come up as MOOREFIELD in device manager. when it turns on and goes in to the bootloader it shows for a second and goes away.
I'm very thankful for anyone that responds. Thx for reading.

I just had this problem after a bad flash~
The instructions of unbricking the phone was lacking some infos.
So I tried a lot of experiments just to unbrick this piece of crap XD
If you are successful on xFSTK procedure you'll end up on "fastboot" mode.
Then you'll proceed with the flashing tool. According to your description everything is just normal my mate~
Now this is the REAL DEAL.
You may notice an ENDLESS "Flash Image" on your flash tool.
Now look on your phone in the Fastboot mode. If you see that the "RESULT: OKAY" seems got stuck, its ok my friend its normal (it will take about 10-30mins depending on your PC).
• Unplug your phone, re-plug it in
• Close AFT
• End process "a500cgfastboot.exe" in the task manager"
Then do the FASTBOOT commands:
• fastboot flash splashimage splashimage.img
• fastboot fastboot flash droidboot.img
• fastboot flash boot boot.img
• fastboot flash recovery recovery.img
AND! you can now proceed on your recovery menu.
You may ADB Sideload the stock firmware by doing
• adb sideload UL-Z00A-WW-X.XX.XX.XX-user.zip (replace the "X" of what file version you want to flash)
And wait for it to reboot. I really hope this helps you mate~
#cheers!

Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.

Just so you know why it happened. You HAVE to be at version 194 before you update to MM! Otherwise... Boom
Sent from my ASUS_Z00A using Tapatalk

This is not so, I sideloaded MM fine straight on .184
No problem sideloading

kenbo111 said:
Just so you know why it happened. You HAVE to be at version 194 before you update to MM! Otherwise... Boom
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
I wish they said that in the steps for updating on their site

Chrodechild said:
I just had this problem after a bad flash~
The instructions of unbricking the phone was lacking some infos.
So I tried a lot of experiments just to unbrick this piece of crap XD
If you are successful on xFSTK procedure you'll end up on "fastboot" mode.
Then you'll proceed with the flashing tool. According to your description everything is just normal my mate~
Now this is the REAL DEAL.
You may notice an ENDLESS "Flash Image" on your flash tool.
Now look on your phone in the Fastboot mode. If you see that the "RESULT: OKAY" seems got stuck, its ok my friend its normal (it will take about 10-30mins depending on your PC).
• Unplug your phone, re-plug it in
• Close AFT
• End process "a500cgfastboot.exe" in the task manager"
Then do the FASTBOOT commands:
• fastboot flash splashimage splashimage.img
• fastboot fastboot flash droidboot.img
• fastboot flash boot boot.img
• fastboot flash recovery recovery.img
AND! you can now proceed on your recovery menu.
You may ADB Sideload the stock firmware by doing
• adb sideload UL-Z00A-WW-X.XX.XX.XX-user.zip (replace the "X" of what file version you want to flash)
And wait for it to reboot. I really hope this helps you mate~
#cheers!
Click to expand...
Click to collapse
im gonna get some breakfest in my belly and have another go at it.. couldnt use have my phone at all yesterday and I tried fixing it for atleast 8-10 hour.. it sucks lol.

timbernot said:
Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
Click to expand...
Click to collapse
Ill watch you video and see if it helps. the instructions on the unbrick I was using was kinda hard to understand for the most part.

timbernot said:
This is not so, I sideloaded MM fine straight on .184
No problem sideloading
Click to expand...
Click to collapse
After a long day yesterday and the flsah process getting stuck, I uninstalled everything and reinstalled everything required for this process. When I finish with xfstk then move on to the flash tool it starts to flash then it stops says Flash image failure[FAILD [wrong image format]]
Im getting so fusturated with this phone its crazy.. I just got in a month ago too.

So now it seems I can use xFSTK and now im in the bootloader with the 4 color bars. But when I goto flash using the Flash tool my phone just sits on FASTBOOT CMD WAITING and the flash tool fails with FLASH IMAGE Failure[FAILED[wrong image format]]
I need some serious help :[

quarterbreed said:
After a long day yesterday and the flsah process getting stuck, I uninstalled everything and reinstalled everything required for this process. When I finish with xfstk then move on to the flash tool it starts to flash then it stops says Flash image failure[FAILD [wrong image format]]
Im getting so fusturated with this phone its crazy.. I just got in a month ago too.
Click to expand...
Click to collapse
well lot of people facing problem. as you told that you are able to get into fastboot after xFSTK process. and you are unable to flash raw firmware file!!!! well perform xFSTK again. get into fastboot and perform following steps:
very first of all. rename .raw firmware file to .zip file and extract all files in there.. now place all files in adb and fastboot folder. open command window here. ( where you places files from raw firmware and adb and fast boot tool folder) perform the following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem erase_token
4. fastboot oem start_partitioning
5. fastboot flash /tmp/partition.tbl partition.tbl
6. fastboot oem partition /tmp/partition.tbl
7. fastboot erase system
8. fastboot erase cache
9. fastboot erase data
10. fastboot erase APD
11. fastboot erase ADF
12. fastboot oem wipe splashscreen
13. fastboot oem stop_partitioning
14. fastboot flash fastboot droidboot_sign.bin
15. fastboot flash token PROD_BOM_Full.bin
16. fastboot flash ifwi ifwi-prod.bin
17. fastboot flash splashscreen splash_sign.bin
18. fastboot flash boot boot_sign.bin
19. fastboot flash recovery recovery_sign.bin
20. fastboot flash APD APD.img
21. fastboot flash system system.img
22. fastboot reboot
hope it will work fine. hit thanks if helped. if any further question please post.

sukhwant717 said:
well lot of people facing problem. as you told that you are able to get into fastboot after xFSTK process. and you are unable to flash raw firmware file!!!! well perform xFSTK again. get into fastboot and perform following steps:
very first of all. rename .raw firmware file to .zip file and extract all files in there.. now place all files in adb and fastboot folder. open command window here. ( where you places files from raw firmware and adb and fast boot tool folder) perform the following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem erase_token
4. fastboot oem start_partitioning
5. fastboot flash /tmp/partition.tbl partition.tbl
6. fastboot oem partition /tmp/partition.tbl
7. fastboot erase system
8. fastboot erase cache
9. fastboot erase data
10. fastboot erase APD
11. fastboot erase ADF
12. fastboot oem wipe splashscreen
13. fastboot oem stop_partitioning
14. fastboot flash fastboot droidboot_sign.bin
15. fastboot flash token PROD_BOM_Full.bin
16. fastboot flash ifwi ifwi-prod.bin
17. fastboot flash splashscreen splash_sign.bin
18. fastboot flash boot boot_sign.bin
19. fastboot flash recovery recovery_sign.bin
20. fastboot flash APD APD.img
21. fastboot flash system system.img
22. fastboot reboot
hope it will work fine. hit thanks if helped. if any further question please post.
Click to expand...
Click to collapse
Thx for the detailed post.. I got in to my phone finally after messing with it all day yesterday and I close to throwing it against the wall lol. It worked like a charm.. I wonder why the flash tool wouldnt work.
Now how would I go about side loading .194 and installing a recovery like twrp again so I can back this thing up once i get to mm.

quarterbreed said:
Thx for the detailed post.. I got in to my phone finally after messing with it all day yesterday and I close to throwing it against the wall lol. It worked like a charm.. I wonder why the flash tool wouldnt work.
Now how would I go about side loading .194 and installing a recovery like twrp again so I can back this thing up once i get to mm.
Click to expand...
Click to collapse
you can side load 194... works well... after 194 you can also install latest official marshmallow. but do not install custom recovery if you want to install lates MM. first install 194 then latest MM. then custom recovery

sukhwant717 said:
you can side load 194... works well... after 194 you can also install latest official marshmallow. but do not install custom recovery if you want to install lates MM. first install 194 then latest MM. then custom recovery
Click to expand...
Click to collapse
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.

quarterbreed said:
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.
Click to expand...
Click to collapse
posting new thread. do not update to official MM if you have custom recovery or you have rooted phone. though after install MM you can install custom Recovery afterwards. not tried but i think will not cause any issue
yes cause of brick is custom recovery

sukhwant717 said:
posting new thread. do not update to official MM if you have custom recovery or you have rooted phone. though after install MM you can install custom Recovery afterwards. not tried but i think will not cause any issue
yes cause of brick is custom recovery
Click to expand...
Click to collapse
I have no recovery installed I tried to get to bootloader with adb and it showed the android guy with a error. How do I go about flashing the new MM build. I really dont want to mess up my phone again lol. Only thing I have on its is .194 atm.
Is it ok to put the MM build on my internal storage and apply the system update from there?

quarterbreed said:
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.
Click to expand...
Click to collapse
quarterbreed said:
I have no recovery installed I tried to get to bootloader with adb and it showed the android guy with a error. How do I go about flashing the new MM build. I really dont want to mess up my phone again lol. Only thing I have on its is .194 atm.
Click to expand...
Click to collapse
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery

sukhwant717 said:
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery
Click to expand...
Click to collapse
I didnt do a factory restore after installing .194 I'll do that now.

sukhwant717 said:
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery
Click to expand...
Click to collapse
Im sure what you mean sorry. I have .194 on my phone with the help of your steps in fastboot. It booted and im in my phone and its updating all my apps and stuff..
Do you mean factory restore in bootloader? If so I tried adb reboot recovery the phone restarts and goes to a screen with https://i.ytimg.com/vi/wuixmZ11Kyc/maxresdefault.jpg Im guessing if i cant get in to recovery I cant do a factory restore?
in fastboot my bootloader doesnt have a version number it just says unknown
EDIT when the picture above showed up I held the power button and vol + to get into recovery and its performing a factory reset atm.

Anyone else bricked ?
Unbrick and into system with correct serial and imei numbers in 20 mins ..see my signature for zubes ..
PS, save yourself days of pain , after xfstk , flash an earlier raw ..
PMSL
---------- Post added at 08:22 AM ---------- Previous post was at 08:18 AM ----------
timbernot said:
Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
Click to expand...
Click to collapse
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.

(Bricked - Solution) Works for MATE SE BND-L34 8.0.0.330(C567)

Due to an update bricking my phone hardcore I found this solution. Please keep in mind my phone's state of function.
BootLoop into erecovery
TWRP was not working
*Have access to FASTBOOT with Bootloader=Unlocked and FRP=Unlocked
1. You must have access to FASTBOOT with Bootloader and FRP Unlocked.
To get to FASTBOOT you need to have a USB cable hooked up to a Windows PC and at the ready.
Turn off the phone and make sure it is disconnected from the charging cable.
Now turn on the phone by holding down the Volume (-) and Power Button Simultaneously.
*Important* As soon as you feel the phone vibrate you must put in the USB cable attached to the PC.
At this point you should be at the FASTBOOT screen.
2. Download the following File and extract it to a folder on the Desktop. 1.2GB in size.
https://mega.nz/#!rAlSBQ7B!zI21XTb_0IrYsD3hBGdn8cYhjK9oh-WXecWuDbkJxl8
3. Now start up the Terminal in Windows (start, Run, then type "CMD" ).
Now change your directory so that your inside the fold you just created from unzipping the downloaded file.
4. Execute the following commands one at a time.
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash ramdisk RAMDISK.img
fastboot flash kernel KERNEL.img
fastboot flash recovery_ramdisk Twrp_p10_lite_0.5_Pretoriano8.img
fastboot reboot
This should fix the issue.

Can you put the file into google doc? hard for me to download from mega.

When I get back to the computer I'll Google drive it for you.

Still getting bootlooped to erecovery. Not sure if I am missing any step or my phone just bricked AF.
I am using BND-L34/Huawei SE bought from Amazon US.
Update(12/24):
So I finally got my Mate SE working after 3 month of bricked mode and countless of tries to get it un-bricked. I bricked my phone by rooting it/flashing RROS Rom then attempting to go back to EMUI.
Method:
Flash TWRP to recovery,
Follow these two guides,
https://forum.xda-developers.com/hu...ide-manual-update-p20-pro-hurupdater-t3816283
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
before you attempt those two guide, wipe everything on phone except for the external storage(this was the method that really worked for me)

Here is the Google drive link for the zip file.
https://drive.google.com/file/d/1BstLuj0WHrHLWQ2tjen9xtdtdkzYQNVL/view?usp=drivesdk

Bricked BND-L34 8.0.0.362(C567)
Hi,
This is my situation, my Mate SE is bricked, stuck in Huawei Logo. It's a mystery because I don't know what cause it (no root, never flashed, etc.)
Firmware version: BND-L34 8.0.0.362(C567)
Device name: BND-L34
OEMInfo: hw/usaA
Serial N: 4AV7N18A12005478
Bootloader state: Locked
Phone: Locked
FRP: Locked
Could you help me?
Any ideas?
Thanks in advance

peatonurbano said:
Hi,
This is my situation, my Mate SE is bricked, stuck in Huawei Logo. It's a mystery because I don't know what cause it (no root, never flashed, etc.)
Firmware version: BND-L34 8.0.0.362(C567)
Device name: BND-L34
OEMInfo: hw/usaA
Serial N: 4AV7N18A12005478
Bootloader state: Locked
Phone: Locked
FRP: Locked
Could you help me?
Any ideas?
Thanks in advance
Click to expand...
Click to collapse
Have you tried any of the guides here?

No OS is installed. Moreover recovery cannot be accessed. Nor can flash it via adb.

Previously I was using Ressurection Remix treble rom which is based on android 9 pie. I went to TWRP and wiped the OS. Then I tried to install a new rom called Dot OS. But it showed error 7. So I flashed Vendortofactory zip within twrp and without rebooting again into TWRP I flashed a new TWRP image within TWRP by selecting Recovery mode. After that I cant boot into TWRP and as already my OS is gone I also cannot boot into any system. Moreover my device is not getting detected in my PC. I cannot install TWRP by writing commands in cmd, while the phone is in fastboot mode as the device is not getting detected in my pc. Really it is urgent. I will be glad if someone helps me. Thanks in advance.

What is the present booted state of your device? Are you in twrp, or bootloader. Most of the time you can keep on pressing the power button. When it boots into a message about unlocked bootloader, press volume button to select recovery and it will boot into twrp

You should be able to boot in fastboot mode without recovery nor os, maybe your drivers are not working on windows? Try different usb ports, check if the display says "bootloader" or something. If nothing works try the usb shunt, this device is literally 'unbrickable' if it's working properly.

Watch this video(https://www.youtube.com/watch?v=DexLELi04XY) and then you will be able to detect your phone in your pc in qcom 9008 mode , then use qfil to flash ZUI firmware ,there are plenty of tutorials on the internet for that ,then follow the proper procedure mentioned in DotOs thread for flashing the new rom .
Hope it helped .

If you don't want to flash the firmware and all long process just follow the following steps
Enter in to the boot loader make sure you installed all the drivers in to pc then open cmd windows in adb fastboot folder and enters the following cmd into the cmd
Fastboot -i 0x2b4c devices this will detect your device
After that enter
Fastboot -i0x2b4c flash recovery recovery name.img
And boom you are good to go flash the rom of your choice and enjoy
For this process you need following files
Adb and fastboot devices
Drivers of zuk z2
Latest recovery and place revovery image file into the adb and fastboot folder if you are confused about anything pm me i am not the expert but i faced simillar problem and solved by this method

yashpatel1221 said:
If you don't want to flash the firmware and all long process just follow the following steps
Enter in to the boot loader make sure you installed all the drivers in to pc then open cmd windows in adb fastboot folder and enters the following cmd into the cmd
Fastboot -i 0x2b4c devices this will detect your device
After that enter
Fastboot -i0x2b4c flash recovery recovery name.img
And boom you are good to go flash the rom of your choice and enjoy
For this process you need following files
Adb and fastboot devices
Drivers of zuk z2
Latest recovery and place revovery image file into the adb and fastboot folder if you are confused about anything pm me i am not the expert but i faced simillar problem and solved by this method
Click to expand...
Click to collapse
This assumes u have upgraded bootloader to 4.4 kernal.
U can still boot into twrp.. When the phone is booting up press vol up key and select recovery.. From there boot into twrp. There select f2v or v2f .. Then flash twrp which u want to flash.. Reboot to recovery.. U will get promp no os installed.. Ignore and reboot to recovery . Then again d9 f2v or v2f depending on what rom to install.. Again reboot to recovery... Then flash rom of ur choice.
This procedure is needed when changing from vendor to factory and vice versa.

sanjay.2704 said:
This assumes u have upgraded bootloader to 4.4 kernal.
U can still boot into twrp.. When the phone is booting up press vol up key and select recovery.. From there boot into twrp. There select f2v or v2f .. Then flash twrp which u want to flash.. Reboot to recovery.. U will get promp no os installed.. Ignore and reboot to recovery . Then again d9 f2v or v2f depending on what rom to install.. Again reboot to recovery... Then flash rom of ur choice.
This procedure is needed when changing from vendor to factory and vice versa.
Click to expand...
Click to collapse
I don't understand what you are talking about as i say i am not some kind of technical expert i am here help regarding this i faced similar situation where i am not able to enter into recovery and also not able to enter into the os and when i restart the phone it automatically boot into fast boot mode what ever option i select and i solved my problem by this method