Database Develop

TWRP 3.1.1-2 doesnt stick on reboot. [Lastest Open Beta]

Hi all.
i previous had TWRP installed and the latest open beta but temporarily went back to stock recovery to fix a dm-verity issue. Now, whenever i fast boot flash TWRP it doesn't stick. every time it boot into the OS it seems to revert to stock recovery.
after doing multiple flashes only 2 of them actually asked me if i wanted to change the read write permissions, the other times it just booted into TWRP without a promt.
any suggestions?
on a side note, if i was to get it to boot into TWRP then wipe and install Paranoid Android might that get it to stick?
Thankyou.

chowchillacharlie said:
Hi all.
i previous had TWRP installed and the latest open beta but temporarily went back to stock recovery to fix a dm-verity issue. Now, whenever i fast boot flash TWRP it doesn't stick. every time it boot into the OS it seems to revert to stock recovery.
after doing multiple flashes only 2 of them actually asked me if i wanted to change the read write permissions, the other times it just booted into TWRP without a promt.
any suggestions?
on a side note, if i was to get it to boot into TWRP then wipe and install Paranoid Android might that get it to stick?
Thankyou.
Click to expand...
Click to collapse
I had the same problem so I flashed it TWRP again then flashed another ROM and it stuck. I have no idea why it does that either.

chowchillacharlie said:
Hi all.
i previous had TWRP installed and the latest open beta but temporarily went back to stock recovery to fix a dm-verity issue. Now, whenever i fast boot flash TWRP it doesn't stick. every time it boot into the OS it seems to revert to stock recovery.
after doing multiple flashes only 2 of them actually asked me if i wanted to change the read write permissions, the other times it just booted into TWRP without a promt.
any suggestions?
on a side note, if i was to get it to boot into TWRP then wipe and install Paranoid Android might that get it to stick?
Thankyou.
Click to expand...
Click to collapse
Flash SuperSU or magisk before booting to system...and it Will stick...

[James] Moto E5 Play won't boot into Custom ROM(s)

Device variant: XT19121-2 James
Chipset: MSM8920
After repeated failed flashes I am on stock firmware using this guide. Phone boots and works normally right now, but I can't seem to flash any Custom ROMs on to my phone. I was using this post to flash Lineage OS 15.1, which worked successfully at first, but the WiFi wasn't working so I reflashed it. It still didn't work so I did it again, wiping Dalvik/Cache too. After the second flash attempt, my phone began to only flicker on and off. I made sure to always clean flash, factory resetting, wiping Cache and Dalvik, even formatting data, but no matter what I do it doesn't work. Also attempted other GSI images (arm, A-only) like AOSP, ResurrectionRemix and phhusson's Lineage OS 15.1 But they all failed too. I am using TWRP for James v 3.3.1 although I did also try other TWRP images like v 3.2.1 . But it makes no difference. Also used Magisk v19 like some guides suggested but whether I have Magisk or not, it doesn't work. Even made sure to push the fstab.qcom file to /vendor. Anytime a Custom ROM is flashed whether zip or GSI img it goes past the initial "bad key" or "N/A" screen and starts flickering on and off. Bootloader and TWRP works fine, but that's about it. Everytime a flash fails I go back to stock firmware (which always works) and try another ROM. I wonder why the first attempt worked but doesn't anymore even if I mirror the exact steps I took from stock. If anyone has any solutions I would be really grateful. Let me know if you need any more information.

have you taken any recent OTA updates?

mikeshutte said:
have you taken any recent OTA updates?
Click to expand...
Click to collapse
Nope. Still on the 8.0.0 version the stock firmware comes in.

tkhan7916 said:
Nope. Still on the 8.0.0 version the stock firmware comes in.
Click to expand...
Click to collapse
Okay give this a try, I'm assuming you have old root access and TWRP installed.
Download any Android 9 GSI of your liking, boot to TWRP.
Do a complete nandroid backup of the stock firmware.
Do a factory reset then wipe system partition.
Next flash your GSI that you downloaded to your system partition.
After flashing is complete of the GSI reboot to recovery.
After reboot completed flash your open Gapps zip. Then reflash Magisk.
if you get a error message when flashing g apps then you will need to use magic g apps with magisk as it will install them systemless. I have to do this on my device because the partition doesn't have enough space.
Give that a try and let me know how it goes if you have any questions feel free to ask.
---------- Post added at 10:09 PM ---------- Previous post was at 09:59 PM ----------
tkhan7916 said:
Nope. Still on the 8.0.0 version the stock firmware comes in.
Click to expand...
Click to collapse
mikeshutte said:
Okay give this a try, I'm assuming you have old root access and TWRP installed.
Download any Android 9 GSI of your liking, boot to TWRP.
Do a complete nandroid backup of the stock firmware.
Do a factory reset then wipe system partition.
Next flash your GSI that you downloaded to your system partition.
After flashing is complete of the GSI reboot to recovery.
After reboot completed flash your open Gapps zip. Then reflash Magisk.
if you get a error message when flashing g apps then you will need to use magic g apps with magisk as it will install them systemless. I have to do this on my device because the partition doesn't have enough space.
Give that a try and let me know how it goes if you have any questions feel free to ask.
Click to expand...
Click to collapse
I also just noticed you are using the latest version of TWRP 3.3.1. I'm not sure if you originally rooted and installed TWRP with the original patched version by Cody or not, but if so make sure with the new version that you format your data partition to f2fs. As this will ensure correct mounting of the data partition.

mikeshutte said:
Okay give this a try, I'm assuming you have old root access and TWRP installed.
Download any Android 9 GSI of your liking, boot to TWRP.
Do a complete nandroid backup of the stock firmware.
Do a factory reset then wipe system partition.
Next flash your GSI that you downloaded to your system partition.
After flashing is complete of the GSI reboot to recovery.
After reboot completed flash your open Gapps zip. Then reflash Magisk.
if you get a error message when flashing g apps then you will need to use magic g apps with magisk as it will install them systemless. I have to do this on my device because the partition doesn't have enough space.
Give that a try and let me know how it goes if you have any questions feel free to ask.
Click to expand...
Click to collapse
Followed these steps exactly, including formatting the data partition to f2fs, and the same problem still persists. Screen just keeps turning on and off in a loop without booting into the ROM. I downloaded the Lineage OS 16.0 GSI A-only Arm version for reference.

I am having the same issue
Using XT1921-1
Latest TWRP
Have tried LOS 15, LOS 16, AOSP 8.1, AOSP 9.0
Have tried flashing in fastboot and TWRP
Have tried every combo of wipe/factory reset/format data and magisk flash possible
have tried stock recovery, have tried no verity, have tried stock boot.img
nothing works. only able to produce powered on (black and blank) screen that turns on and off for a minute before returning to bootloader
PLEASE HELP
think i might need a 8.0 GSI but cant find one anywhere

I eventually got RR to boot on the james xt-1921-3 I installed XT1921-3_JAMES_T_MPCS_8.0.0_OCPS27.91-150-5-1-3_cid21 as a base, then used boot and vendor partitions from JAMES_T_OCP27.91-51-4_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC and it finally worked.

tkhan7916 said:
Followed these steps exactly, including formatting the data partition to f2fs, and the same problem still persists. Screen just keeps turning on and off in a loop without booting into the ROM. I downloaded the Lineage OS 16.0 GSI A-only Arm version for reference.
Click to expand...
Click to collapse
Message me, I'll host a TWRP backup for the XT-1921-3 that boots RR 6.1

Download the file from this post https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 , then using fastboot, flash the vendor and boot img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
then boot into recovery and flash the file from that post to disable dm-verity and force encrytion, after that flash magisk, then reboot to bootloader, at command prompt-
fastboot erase userdata
fastboot erase cache
fastboot reboot
that should get you booted - profit

mrbox23 said:
Message me, I'll host a TWRP backup for the XT-1921-3 that boots RR 6.1
Click to expand...
Click to collapse
Do you still have that back up by any chance and could ypu send it to me?

TWRP gets replaced by stock recovery

So I've used TWRP r16 and it throws an "Image not signed or corrupt" error as suggested by other users I ignored it, but everytime I reboot to system and try to get to recovery "no command" show's up meaning TWRP was replaced by stock recovery all help will be appreciated.
Thanks

Akash731 said:
So I've used TWRP r16 and it throws an "Image not signed or corrupt" error as suggested by other users I ignored it, but everytime I reboot to system and try to get to recovery "no command" show's up meaning TWRP was replaced by stock recovery all help will be appreciated.
Thanks
Click to expand...
Click to collapse
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed

pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
Hey thanks that worked.
But everytime I boot to system and boot to twrp the data gets encrypted and I can't access the files do you happen to know any solution for this?

Akash731 said:
Hey thanks that worked.
But everytime I boot to system and boot to twrp the data gets encrypted and I can't access the files do you happen to know any solution for this?
Click to expand...
Click to collapse
If you are on stock Rom, according to my knoweldge it is not possible to remove encryption, if you format your date in twrp for removing encryption then reboot to system you can see that the phone is again encrypted.
But in custom roms this doesnt happen.

pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
pradeeppk said:
If you are on stock Rom, according to my knoweldge it is not possible to remove encryption, if you format your date in twrp for removing encryption then reboot to system you can see that the phone is again encrypted.
But in custom roms this doesnt happen.
Click to expand...
Click to collapse
I don't want to try custom rom's as this is my main device guess I'm stuck with the encryption then thanks for your help. :good:
Edit:-
Tried TWRP r20 it decrypts fine thanks

pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
You don't have to flash Magisk after flashing TWRP. The two are unrelated.
After flashing TWRP you have to boot into recovery, not system. Once TWRP was started, you can reboot into system. No need for Magisk (unless you want Magisk anyway).

gewe said:
You don't have to flash Magisk after flashing TWRP. The two are unrelated.
After flashing TWRP you have to boot into recovery, not system. Once TWRP was started, you can reboot into system. No need for Magisk (unless you want Magisk anyway).
Click to expand...
Click to collapse
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867

pradeeppk said:
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
Click to expand...
Click to collapse
I am using stock ROM, and yes, also Magisk (installed later). IIRC Magisk is not needed for TWRP to work. When I receive the next OTA notification, I will test this.
The thread you are referring to is for a OnePlus 3T. For our device this is the thread: https://forum.xda-developers.com/moto-g5s-plus/development/recovery-twrp-3-1-1-r7-t3694910.
Since there is no official TWRP for the Moto G5S Plus, I took the following text from the TWRP page for the Moto G5S.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
Instead of that you can also use fastboot reboot-bootloader, and then from the bootloader start recovery.

pradeeppk said:
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
Click to expand...
Click to collapse
Two days ago I received a notification for an OTA update, containing the August 2019 security patches.
After going back to stock ROM, installing all the updates up to the latest, I installed TWRP. After booting into recovery, and then into system, and recovery again, TWRP was gone. Strange, I don't remember this happening before. Maybe I always installed Magisk before booting into system.
Bottom line: you were right, I was wrong. Thanks for pointing it out.

gewe said:
Two days ago I received a notification for an OTA update, containing the August 2019 security patches.
After going back to stock ROM, installing all the updates up to the latest, I installed TWRP. After booting into recovery, and then into system, and recovery again, TWRP was gone. Strange, I don't remember this happening before. Maybe I always installed Magisk before booting into system.
Bottom line: you were right, I was wrong. Thanks for pointing it out.
Click to expand...
Click to collapse
As like you said this is the first time in my life i need to flash magisk to stick twrp.
I usualy doesn't use root or custom roms, install twrp, remove unnecessary apps from stock system, replace host files with adaway hosts, replace or edit gps config files. and continue using stock.
This is the main routine from Android 1.5
(Samsung spica (i think it was the first Android phone from Samsung)).
It may be due to security reason stock kernel or system delete twrp.
When installing magisk it patch stock boot image, that may be the reason of twrp remains after flashing magisk.

Clearing up TWRP ambiguity versions + rooting MIUI pie

There is confusion over which recoveries to install for Redmi 6 (cereus).
Failure to install the correct TWRP will result in a hard brick with no chance of restoring the device without an authorised account or going to a Mi Service Centre.
If you are currently on the MIUI Oreo ROM:
You may ONLY use TWRP 3.3.0 OR 3.2.3-0 OR 3.2.3-1
The recovery by either TWRP or LR.Team is both ok.
If you are on the PIE rom:
You MUST use TWRP 3.3.1 or OrangeFox Recovery. R10.0-2 nocrypt Pie is confirmed to be working by me.
To root MIUI pie, follow the instructions in this post from 4PDA. This is because you will be unable to decrypt data.
You need to create an account to download the patched boot.img. You can either create one yourself or ask me or someone else to PM you with the boot.img. I will not attach it to this thread because it is not my work. The files have now been attached. See post below.
All credits go towards the respective recovery authors and 4pda

OK here are the boot files from 4pda
You MUST follow the instructions from this guide: http://4pda.ru/forum/index.php?showtopic=907017&st=5020#entry87853533
All files obtained from 4pda.ru - from a post by MCMXCII
Full credits go towards the authors of the respective .imgs

I did something wrong just don't know what
I tried with OrangeFox and when rebooted in recovery the phone would not turn on and just vibrates.
I was lucky because I just needed to open and remove the battery to get the phone back up.

So just to get it right (please correct me if i'm wrong):
Starting from unlocked MIUI stock with android 8.1 base:
0) Download patched boot image from OP
1)Download TWRP 3.3.0 OR 3.2.3-0 OR 3.2.3-1
2)Download Magisk 19.3 Stable (would the latest stable also work https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445?)
3)Download official Pie Rom: http://bigota.d.miui.com/V10.4.4.0.PCGMIXM/miui_HM6Global_V10.4.4.0.PCGMIXM_99304098f7_9.0.zip
4)Enter Fastboot -> Flash TWRP
5)Enter TWRP -> Flash the Pie Rom -> Flash patched boot.img -> flash Magisk
6)Boot into system -> Leave the device alone for 2-3 minutes and install Magisk Manager
7)Download -> TWRP 3.3.1 or OrangeFox Recovery. R10.0-2
8)Enter Fastboot -> Flash TWRP/OrangeFox
would this be the correct procedure?
cheers

snoerme said:
So just to get it right (please correct me if i'm wrong):
Starting from unlocked MIUI stock with android 8.1 base:
1)Download TWRP 3.3.0 OR 3.2.3-0 OR 3.2.3-1
2)Download Magisk 19.3 Stable (would the latest stable also work https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445?)
3)Download official Pie Rom: http://bigota.d.miui.com/V10.4.4.0.PCGMIXM/miui_HM6Global_V10.4.4.0.PCGMIXM_99304098f7_9.0.zip
4)Enter Fastboot -> Flash TWRP
5)Enter TWRP -> Flash the Pie Rom -> flash Magisk
6)Boot into system -> Leave the device alone for 2-3 minutes and install Magisk Manager
7)Download -> TWRP 3.3.1 or OrangeFox Recovery. R10.0-2
8)Enter Fastboot -> Flash TWRP/OrangeFox
cheers
Click to expand...
Click to collapse
?????????????????????
Why don't you skip steps 1-3 and just use XiaoMi Flash to install 10.4.4.0 via Fastboot by 'saving user data', then follow the instructions here? XiaoMiFlash will overwrite your recovery with the default so there is no risk of a brick. Then Flash TWRP Pie, flash boot img, flash magisk.
As I have said, you will brick your device. If you have TWRP Oreo, and then you install MIUI Pie, you will brick your device. You are doing EXACTLY what I told you not to do!

It didn't come out as clearly as you think. maybe it's my own deficiency.
btw whenever i flashed any update via TWRP the recovery got replaced by stock recovery as well.
(I don't tell this to call into question that your suggested way of doing was the most safe way.)
Is XiaoMi Flash available for linux as well?
edit: do you know if the latest magisk stable 20.0 would also work?

snoerme said:
It didn't come out as clearly as you think. maybe it's my own deficiency.
btw whenever i flashed any update via TWRP the recovery got replaced by stock recovery as well.
(I don't tell this to call into question that your suggested way of doing was the most safe way.)
Is XiaoMi Flash available for linux as well?
Click to expand...
Click to collapse
I'm not sure - I have never flashed any MIUI ROM in TWRP. It seems normal though - the updaterscript probably tells TWRP to overwrite itself.
https://forum.xda-developers.com/android/software/tool-miflash-linux-t3708847 It's a bit complicated

This work for me :
1 - Install Pie Rom https://bigota.d.miui.com/V10.4.4.0.PCGMIXM/miui_HM6Global_V10.4.4.0.PCGMIXM_99304098f7_9.0.zip with TWRP 3.3.1 https://mifirm.net/downloadtwrp/62 or with another method.
2 - Shut down the phone , go to fastboot (Vol - and power), plug to computer.
3 - From the computer fastboot flash boot boot_10.4.4.0_R6_mgsk_193.img (see the second post of this thread).
4 - fastboot flash recovery recovery-TWRP-3.3.1-0602-REDMI6-CN-wzsx150.img
5 - Recovery (Vol+ and power)
6 - Install Magisk 19.3
Reboot and enjoy

Hi, currently I'm on stable China mui v10.4.3.0. Do you have boot.img on that v10.4.3.0. Currently link only provide boot.img for v10.4.2.0 for the china version. If no how do I get those, can I just backup them from twrp, Then create patched boot img with those backup boot? Thanks

Che0063 said:
OK here are the boot files from 4pda
You MUST follow the instructions from this guide: http://4pda.ru/forum/index.php?showtopic=907017&st=5020#entry87853533
All files obtained from 4pda.ru - from a post by MCMXCII
Full credits go towards the authors of the respective .imgs
Click to expand...
Click to collapse
Thanx for boot_10.4.4.0_R6_mgsk_193.img :good:
ribou said:
This work for me :
1 - Install Pie Rom https://bigota.d.miui.com/V10.4.4.0.PCGMIXM/miui_HM6Global_V10.4.4.0.PCGMIXM_99304098f7_9.0.zip with TWRP 3.3.1 https://mifirm.net/downloadtwrp/62 or with another method.
2 - Shut down the phone , go to fastboot (Vol - and power), plug to computer.
3 - From the computer fastboot flash boot boot_10.4.4.0_R6_mgsk_193.img (see the second post of this thread).
4 - fastboot flash recovery recovery-TWRP-3.3.1-0602-REDMI6-CN-wzsx150.img
5 - Recovery (Vol+ and power)
6 - Install Magisk 19.3
Reboot an denjoy
Click to expand...
Click to collapse
ThanX ! ! !
This work for me :good:
EDIT:
The flashlight and the camera does not work after flash the boot boot_10.4.4.0_R6_mgsk_193.img [emoji848]
Does anyone else have a similar problem?
View attachment 4862683

I have the camera and flashlight problem too. Any fix?

Unfortunately, I didn't find any solution.
Currently, my phone does not start, has a black screen and vibrates all the time. I can't run it in any way
EDIT:
Hi.
I was able to bring the phone to life. Get instructions on how to get to the battery https://www.youtube.com/watch?v=L9FH88b16bc https://www.youtube.com/watch?v=fAflA4UKLLY. In orangeFox recovery I checked the flashlight, it works.

That makes us two. My phone is unusable at the moment. I thought the root was responsible for the camera bugs, I uninstalled magisk, the bug was still there. I tried to reinstall MIUI 10.4.4 ang got an error. I've wiped everything including vendor and system.

I clean dalvik and cache and for now the phone is working even, after flash the patch boot.img

ribou said:
This work for me :
1 - Install Pie Rom https://bigota.d.miui.com/V10.4.4.0.PCGMIXM/miui_HM6Global_V10.4.4.0.PCGMIXM_99304098f7_9.0.zip with TWRP 3.3.1 https://mifirm.net/downloadtwrp/62 or with another method.
2 - Shut down the phone , go to fastboot (Vol - and power), plug to computer.
3 - From the computer fastboot flash boot boot_10.4.4.0_R6_mgsk_193.img (see the second post of this thread).
4 - fastboot flash recovery recovery-TWRP-3.3.1-0602-REDMI6-CN-wzsx150.img
5 - Recovery (Vol+ and power)
6 - Install Magisk 19.3
Reboot an denjoy
Click to expand...
Click to collapse
Hello this is the steps i did but when rebooting to recovery i end up on blackcreen or mai i say powered off screen with the device unable to boot to recovery,any ideas what i did wrongly?

It seems there is something wrong with that boot patch. I followed a procedure on youtube and my phone is succesfully rooted without any bug

@ambyy
what guide did you use on YouTube?
Wysłane z mojego Redmi 6 przy użyciu Tapatalka

https://www.youtube.com/watch?v=I_4Zmco9R78&t=25s

Hard brick caused by flashing wrong TWRP is indeed able to get solved with unplugging the battery.

Miui v11 boot.img please

Can't access twrp 3.4.0.1, H870

Hello,
I've installed twrp 3.4.0.1 via fastboot, but after I select yes when i'm asked about erasing my data, the phone just boot up normally without deleting any of my data, but does not enter twrp either. Tried 3.4.0.0 too, no luck. Only 3.3.1.0 worked, but when I try to backup it says something like 'can't mount system partition' and some other errors. I think that version is too old for my rom, so I'm afraid to use it for backup/flash. My phone is LG G6 H870, Android 9, software version V30b. The phone is not rooted, the bootloader is unlocked. Tried to erase cache partition and install twrp 3.4.01 again, didn't work. I can't install Skyhawk or Orangefox becuase I can't use twrp.
Is anybody facing this problem too?
Thanks!

Bootloader unlocked?

Mendoo said:
Bootloader unlocked?
Click to expand...
Click to collapse
Yes

Thelock1 said:
Hello,
I've installed twrp 3.4.0.1 via fastboot, but after I select yes when i'm asked about erasing my data, the phone just boot up normally. Tried 3.4.0.0 too, no luck. Only 3.3.1.0 worked, but when I try to backup it says something like 'can't mount system partition', I think that version is too old for my rom. My phone is LG G6 H870, Android 9, software version V30b. My phone is not rooted.
Is anybody facing this problem too?
Thanks!
Click to expand...
Click to collapse
HI You need to use OrangeFox recovery or SkyHawk. If you plan to go to 10, then you need SkyHawk. And I think SkyHawk is maintained but OrangeFox not.
Links:
SkyHawk https://sourceforge.net/projects/pa-g6/files/Releases/SHRP/20.07.2020/H870/
OrangeFox https://forum.xda-developers.com/lg-g6/development/recovery-orangefox-recovery-project-t3943594

jis251 said:
HI You need to use OrangeFox recovery or SkyHawk. If you plan to go to 10, then you need SkyHawk. And I think SkyHawk is maintained but OrangeFox not.
Links:
SkyHawk https://sourceforge.net/projects/pa-g6/files/Releases/SHRP/20.07.2020/H870/
OrangeFox https://forum.xda-developers.com/lg-g6/development/recovery-orangefox-recovery-project-t3943594
Click to expand...
Click to collapse
So can I install SkyHawk via fastboot over stock recovery without installing twrp beforehand? I see there are multiple files in the shyhawk zip, should I only extract the recovery img and install it via fastboot? I'm kinda new to this, thanks!

Thelock1 said:
So can I install SkyHawk via fastboot over stock recovery without installing twrp beforehand? I see there are multiple files in the shyhawk zip, should I only extract the recovery img and install it via fastboot? I'm kinda new to this, thanks!
Click to expand...
Click to collapse
HI. It is made to flash in TWRP (same as OrangFox) So I really don't know if that recovery.img flashing through Fastboot works. Never tried, sorry.
Maybe someone knows though.

jis251 said:
HI. It is made to flash in TWRP (same as OrangFox) So I really don't know if that recovery.img flashing through Fastboot works. Never tried, sorry.
Maybe someone knows though.
Click to expand...
Click to collapse
Ok, thanks, I'll try to find a solution, or maybe I'll just wait for the next version of twrp.

You should try installing the recovery and immediately installing any custom rom, when i flashed twrp the first time i had to do it several times cause somehow it got "erased" every time i noot the stock OS.
Ig you don't want to install a custom rom try right after installing twrp and on the fastboot screen to reboot to recovery with (Volume - ) button and power.
I think the idea is not letting the Stock os boot
Also that error. i have the same problem, the only moment it doesn't appear is when you wipe all data with the "Format Data" option inside "Wipe" menu in twrp.
After you boot to the OS once and go back to recovery it will come again everytime you flash something.
Not sure if its a problem or not, because i've dirty installed some updates and also installed gapps and magisk even with that error.
Im currently in A10 using Havoc and NikGapps.
TWRP 3.2.3-0

AlejandroMota said:
You should try installing the recovery and immediately installing any custom rom, when i flashed twrp the first time i had to do it several times cause somehow it got "erased" every time i noot the stock OS.
Ig you don't want to install a custom rom try right after installing twrp and on the fastboot screen to reboot to recovery with (Volume - ) button and power.
I think the idea is not letting the Stock os boot
Also that error. i have the same problem, the only moment it doesn't appear is when you wipe all data with the "Format Data" option inside "Wipe" menu in twrp.
After you boot to the OS once and go back to recovery it will come again everytime you flash something.
Not sure if its a problem or not, because i've dirty installed some updates and also installed gapps and magisk even with that error.
Im currently in A10 using Havoc and NikGapps.
TWRP 3.2.3-0
Click to expand...
Click to collapse
Yes, I know I have to install twrp again every time I let the stock rom boot, but the only version of twrp working is 3.2.3 and I think that was released before the G6 received official Android 9 update, so that's why I'm not very confident using it. I've tried to enter recovery immediately after I've installed it, so I don't think that's the problem.

I have the same problem on the LG G6 H870. I won't get to TWRP. I tried several versions of TWRP and nothing.
Edit.
This twrp is functional:
https://androidfilehost.com/?w=files&flid=289997
After installation using fastboot, restart directly to twrp using power+vol. down.

Finally i've successfully flashed Skyhawk using TWRP 3.3.1, so thanks everyone for advice!
Still couldn't make official TWRP 3.4.0/3.4.0.1 work.

Update TWRP 3.1 to 3.4 problem
Thelock1 said:
Finally i've successfully flashed Skyhawk using TWRP 3.3.1, so thanks everyone for advice!
Still couldn't make official TWRP 3.4.0/3.4.0.1 work.
Click to expand...
Click to collapse
Hi, I don't know if this goes here, I hope you can help me, I update twrp from version 3.1 to 3.4 and now I can't access twrp, how can I fix it?
Hello again, I answer myself, and if it helps someone else, using adb fastboot with twrp 3.2 Melina solves it and twrp works perfectly again.