Develop Bugs

Problem with access in Twrp

Hello guys,
I decided to install Twrp 2.7.01 in order to flash custom rom. So, i do that :
C:\Fastboot>fastboot flash recovery recovery.img
It work and send me Okay.
But, when i want to go in twrp, it start loading with writting "enterring recovery", and finaly my M8 reboot and restart the phone. So, i can't access to my recovery in order to root it and flash custom.
If someone can help me it's cool.
Erratum : I flash Twrp 7.0.2.0 and it's working

What version of bootloader are you using, e.g. 3.16.0000?

TWRP 2.7; here, first turn your phone on fastboot mode,
in terminal/cmd type in:
fastboot erase cache
then flash this recovery: (GSM ONLY, NOT CDMA)
http://www.mediafire.com/download/6dtgx3w3kpid1ce/openrecovery-twrp-2.8.5.0-m8_3.img
(That's the official TWRP recovery, turns out that TWRPS site is kinda slow...)
let me know how it turns out.

i4GS said:
TWRP 2.7; here, first turn your phone on fastboot mode,
in terminal/cmd type in:
fastboot erase cache
then flash this recovery: (GSM ONLY, NOT CDMA)
http://www.mediafire.com/download/6dtgx3w3kpid1ce/openrecovery-twrp-2.8.5.0-m8_3.img
(That's the official TWRP recovery, turns out that TWRPS site is kinda slow...)
let me know how it turns out.
Click to expand...
Click to collapse
The OP has already flash TWRP using the right commands, but if they're using an old version on a new HBOOT (or new version on old HBOOT) it might not load, hence me asking what bootloader they're using

Help, possibly bricked phone

Hello, I am currently rooted and on stock on pixel xl. I am trying to flash the pure nexus rom. I downloaded through the link in the op, factory reset and flashed through twrp (3.0.2rc1). When I went to reboot, it said OS not installed. Can anyone offer any assistance with this? Needless to say, I didn't reboot with that. I did however do a backup (of stock) prior to this. I decided to restore my backup but when it rebooted it said something about the vender image is not right with this system and to flash the correct image. This is exactly what its saying : Your vendor image does not match the system. Please flash the NOF27C vendor image for your device. I have managed to move the correct image file to the internal storage but from what i read, can only install through twrp.
And when it finished rebooting, now 90% of my apps are crashing, no fingerprint hardware, developer options are not available and I had to reboot back into recovery but its like twrp is gone, it looks like the stock recovery. Somehow it appears there are parts of my stock rom and pure nexus rom combined which is understandbly causing my issues. Right now I am trying to get back to having twrp but am stuck.
I have since tried to reinstall twrp but when I plug my xl into my pc, the pc recognizes it but no storage. I cant move a file from pc to xl because its saying disconnected or not responding. Tried to get a command prompt and when I shift/right click, there is no option. I don't know what else to do.
If anyone has any suggestions, please help. I am freaking over this. Can't use my phone in the state its in.

Sounds far from bricked.
Just entirely screwed up.
FASTboot the latest factory image and then refrain from tinkering for the weekend.
These are the steps i use.
I think a new ADB/FastBoot package was released yesterday you might want to install that.
Execute fastboot commands (assuming the bin is on your PATH)
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot
To add TWRP and Root:
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip

TWRP not persistent

Hi guys,
I've just updated to newest OOS firmware wich is 5.1.2 and I'm facing a weird problem.
Every time I flash codeworks TWRP and reboot to system, the next time i try to boot to recovery it boots to the original recovery.
It's like when I flash TWRP it doesn't remain persistent. When i flash it through fastboot and straightly boot from fastboot to recoverry I succeed to get in TWRP but as soon as I reboot to system and try to boot to recovery I reach the original OnePlus recovery.
Is anyone facing the same problem ?
And also do you have any idea about what i could do to solve this problem ?
Thanks in advance for your answers !

If you don't have root or custom kernel its normal, plus you should use blu spark's twrp, its newer and more reliable.

Adnan008 said:
If you don't have root or custom kernel its normal, plus you should use blu spark's twrp, its newer and more reliable.
Click to expand...
Click to collapse
Indeed, I just needed to flash magisk to get it persistent. I'll try blu spark's one as you suggested.
Thank you very much for your answer !
Cheers !

Nothing to do with recoveries or kernel. After you do the fastboot flash recovery TWRP in fastboot, do this: "fastboot boot TWRP". I believe that's the right command. Basically after you flash it, manually boot to recovery through fastboot one time. After that it'll work from inside the phone or with the button combination with the phone off.

Jesus people are lazy these days.
First off there are official twrp versions for a reason!
Download the latest version: https://dl.twrp.me/dumpling/
Reboot into flash boot with the following command from your rom: adb reboot bootloader
With phone in fastboot mode: fastboot flash recovery 'twrp.img'
(You don't need to type out the entire file path you can just drag the file into the terminal and it'll insert the file location)
The reason you're not getting back into that recovery is because you're not booting into the recovery before you reboot into your ROM.
There is an option to boot straight into the recovery from the fastboot mode

pinnekeshaar said:
Jesus people are lazy these days.
First off there are official twrp versions for a reason!
Download the latest version: https://dl.twrp.me/dumpling/
Reboot into flash boot with the following command from your rom: adb reboot bootloader
With phone in fastboot mode: fastboot flash recovery 'twrp.img'
(You don't need to type out the entire file path you can just drag the file into the terminal and it'll insert the file location)
The reason you're not getting back into that recovery is because you're not booting into the recovery before you reboot into your ROM.
There is an option to boot straight into the recovery from the fastboot mode
Click to expand...
Click to collapse
Actually not that lazy because I used to do what you mentionned.
The thing is that a flash of Magik is needed to patch twrp. That's the step I forgot in the procedure and explained here.
So before being unpleasant, please know what you're talking about...
Cheers !

My Mi Max 3 is dead

Hi, yesterday I was flashing a rom with flash tool. It finished, reboot but it didn't start anymore. No fastboot nor recovery. Seems to be dead.
Is there a way to start it?
Thanks,
Andrés

Does this help?
Please report back.

Hi! thanks, it worked. Now I'm having a different issue with TWRP.
I install TWRP via fastboot, but i can't access the data inside the phone nor do the wipes. It shows errors.
When I boot the TWRP i don't enter any password or something like that.
Any ideas? It is a TWRP issue?
Thanks

andres88_ said:
Hi! thanks, it worked. Now I'm having a different issue with TWRP.
I install TWRP via fastboot, but i can't access the data inside the phone nor do the wipes. It shows errors.
When I boot the TWRP i don't enter any password or something like that.
Any ideas? It is a TWRP issue?
Thanks
Click to expand...
Click to collapse
Glad to hear your device is back from the dead.
Are all TWRP functions available? And all info gibberish?
Before installing TWRP, you can also see if it works without installing it by just booting it.
Code:
fastboot [B]boot[/B] recovery TWRP.img
See if folders are readable now, then extract data. Try different TWRP's. There are a few for Mi Max 3. Keep trying, TWRP does have some rare and occasional hiccups with password and decrypting. Also for me. Just reboot and try again until it works. Try to boot Orange Fox in recovery if needed.
Second, if nothing works, you may try and download the ROM you used before updating. Extract boot.img, recovery.img and system.img from old ROM and flash with fastboot:
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
This will restore the 3 .img's. Boot into recovery and see if you can pull data.
Let me kow if it helps because maybe otherwise you have to worry about flashing full ROM and lose data.
Addendum: if you run into trouble when flashing you can use Xiaomi ADB/ Fastboot Tools. Install Java first though. Also, please be aware of Xiaomi's ARB feature.

Question installing custom recovery when device has AOSP recovery

So I installed a A13 AOSP rom (Evolution x) via orangefox and when I rebooted to recovery orangfox was gone and now I'm on AOSP recovery. I tried to "fastboot boot" TWRP but the phone restarts on black screen for several seconds then restarts again to system. and when I enter fastboot thro AOSP recovery and try to boot TWRP it just fails (says unrecognized command boot). how can I flash custom recovery? i was thinking of trying sideload but with fastboot not working properly, I dont want guessing and rather ask someone with more knowledge with AOSP recovery and what could be causing fastboot not working properly
PS/ AOSP recovery is not detecting otg, and when choosing apply updates from internal storage it says it cant mount /data

Aserar said:
So I installed a A13 AOSP rom (Evolution x) via orangefox and when I rebooted to recovery orangfox was gone and now I'm on AOSP recovery. I tried to "fastboot boot" TWRP but the phone restarts on black screen for several seconds then restarts again to system. and when I enter fastboot thro AOSP recovery and try to boot TWRP it just fails (says unrecognized command boot). how can I flash custom recovery? i was thinking of trying sideload but with fastboot not working properly, I dont want guessing and rather ask someone with more knowledge with AOSP recovery and what could be causing fastboot not working properly
PS/ AOSP recovery is not detecting otg, and when choosing apply updates from internal storage it says it cant mount /data
Click to expand...
Click to collapse
What is the code name of your device?

NOSS8 said:
What is the code name of your device?
Click to expand...
Click to collapse
Its alioth poco f3

Aserar said:
Its alioth poco f3
Click to expand...
Click to collapse
Seems that in official no TWRP A13
https://androidfilehost.com/?w=files&flid=322193
Here boot version A12(more recent).
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
https://dl.akr-developers.com/?dir=skkk/TWRP/A12/v5.6_A12
https://forum.xda-developers.com/t/recovery-12-official-teamwin-recovery-project.4272625/

Aserar said:
So I installed a A13 AOSP rom (Evolution x) via orangefox and when I rebooted to recovery orangfox was gone and now I'm on AOSP recovery. I tried to "fastboot boot" TWRP but the phone restarts on black screen for several seconds then restarts again to system. and when I enter fastboot thro AOSP recovery and try to boot TWRP it just fails (says unrecognized command boot). how can I flash custom recovery? i was thinking of trying sideload but with fastboot not working properly, I dont want guessing and rather ask someone with more knowledge with AOSP recovery and what could be causing fastboot not working properly
PS/ AOSP recovery is not detecting otg, and when choosing apply updates from internal storage it says it cant mount /data
Click to expand...
Click to collapse
It is because flashing rom also flash the recovery packed along with the rom, and it will replace your old recovery. To prevent it you need to also tick on the reflash ofox option when you flash a rom, which is too late in your case.
So, if you want to reflash ofox recovery, download and extract the zip file, locate the recovery.img in the extracted folder, reboot to bootloader and issue this command:
Code:
fastboot boot /path/to/recovery.img
then reboot to recovery with the command:
Code:
fastboot reboot recovery
and your device will temporarily boot into ofox recovery
The last step is to flash the recovery to ramdisk to make it permanently, you can find this option in ofox settings.

NOSS8 said:
Seems that in official no TWRP A13
https://androidfilehost.com/?w=files&flid=322193
Here boot version A12(more recent).
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
https://dl.akr-developers.com/?dir=skkk/TWRP/A12/v5.6_A12
https://forum.xda-developers.com/t/recovery-12-official-teamwin-recovery-project.4272625/
Click to expand...
Click to collapse
This is what I did befor posting but but TWRP wouldnt boot through fastboot. it just gives me blackscreen for a few seconds then it boots to system. but the problem was solved with ofx. thank you for your help

disconmair said:
It is because flashing rom also flash the recovery packed along with the rom, and it will replace your old recovery. To prevent it you need to also tick on the reflash ofox option when you flash a rom, which is too late in your case.
So, if you want to reflash ofox recovery, download and extract the zip file, locate the recovery.img in the extracted folder, reboot to bootloader and issue this command:
Code:
fastboot boot /path/to/recovery.img
then reboot to recovery with the command:
Code:
fastboot reboot recovery
and your device will temporarily boot into ofox recovery
The last step is to flash the recovery to ramdisk to make it permanently, you can find this option in ofox settings.
Click to expand...
Click to collapse
Thank you mf this worked! Booting twrp through fastbood just gave me black screen so I didnt think that booting Ofox would be any different but it actually booted Ofox recovery and I flashed it no problem. If anyone's going to attempt this make sure to backup your data before cause you'll need to format data