Develop Bugs

TWRP install on G4 H815 20A mm, doesn't stick (unlocked bootloader by LG official)

Hi,
I get TWRP running on phone , but when I boot into recovery , I always get the Standard Recovery, only option being a factory reset. Have opted for this factory reset and that is exactly what I get, no TWRP :crying:
Thanks

Also if you reboot to recovery through TWRP itself, it won't stick? If not: Is rooting an option for you? If yes: Try Flashify and flash it through this nifty little app .

MickyFoley said:
If not: Is rooting an option for you? If yes: Try Flashify and flash it through this nifty little app .
Click to expand...
Click to collapse
Thanks,
Yes rooting is where I want to go by means of TWRP and flashing these
Marshmallow custom kernel for root — Link | File: STOCK-20a-ROOTED.zip (16.5 MB)
Click to expand...
Click to collapse
I did have Twrp running on this phone but had to reinstall the full 6.00kdz to get out of a bootloop and since then TWRP won't sick.
thanks

More than one way to skin a cat. went HERE chainfire Systemless Root 2.61 using Running TWRP from PC
Update on getting TWRP to stick. ......... I had success using following
adb reboot bootloader
Click to expand...
Click to collapse
fastboot flash recovery twrp-2.8.7.0-h815.img
Click to expand...
Click to collapse
When done, execute “fastboot reboot”
Click to expand...
Click to collapse

This happened to me, too. Here is what i did:
Boot your device into fastboot mode via adb, straight up boot to recovery ("fastboot boot twrp-2.8.7.0-h815.img"), transfer the recovery image to your device, then flash it from within TWRP (there is an option for that within the normal install menu, its called "install image" or something like that). Hope this helps, it did for me.
Edit: Just realized you already found a solution. Never mind.

Ive the same problem. I unlocked the bootloader by the official procedure. Then i tried to flash twrp but it doesnt install truly. It always appear the stock recovery. I tried also clockrecovery but nothing. No recovery wants to get installed. Pls help me i want a custom rom on my g4

use twrp v2.8.7.0 on 20A mm....... adb reboot bootloader, fastboot boot twrp-2.8.7.0-h815.img, and to double check you have recovery,adb reboot recovery and then flash STOCK-20a-ROOTED

chester2011 said:
use twrp v2.8.7.0 on 20A mm....... adb reboot bootloader, fastboot boot twrp-2.8.7.0-h815.img, and to double check you have recovery,adb reboot recovery
Click to expand...
Click to collapse
Ok the one i tried is the newest. Ill gonna try the one u told me. But the line u wrote wont install twrp it will only boot it

setaf said:
Ok the one i tried is the newest. Ill gonna try the one u told me. But the line u wrote wont install twrp it will only boot it
Click to expand...
Click to collapse
sorry, fastboot flash recovery twrp-2.8.7.0-h815.img, instead of fastboot boot twrp-2.8.7.0-h815.img worked for me after hours and hours of boot loops and restoring

chester2011 said:
sorry, fastboot flash recovery twrp-2.8.7.0-h815.img, instead of fastboot boot twrp-2.8.7.0-h815.img worked for me after hours and hours of boot loops and restoring
Click to expand...
Click to collapse
Also u had problem with the 3.0 ? Ill update you later

setaf said:
Also u had problem with the 3.0 ? Ill update you later
Click to expand...
Click to collapse
yep.. but currently running with xposed and g4 tweaksbox (paid version) nicely

ok update:
finaly i got twrp 2.8.7.0 on my g4 (thanx chester) but i still cannot flash cyanogen.
when i try to do it by recovery i get the error message 7 then when i start the system im in damn bootloop
what i can do ?

flash twrp version 3.0.2.0

setaf said:
ok update:
finaly i got twrp 2.8.7.0 on my g4 (thanx chester) but i still cannot flash cyanogen.
when i try to do it by recovery i get the error message 7 then when i start the system im in damn bootloop
what i can do ?
Click to expand...
Click to collapse
you can upgrade twrp with the twrp manager from playstore (once youve got twrp and root of course)

TWRP bootloops

I've seen this problem mentioned in a few threads but not seen any definitive fix.
My current install :
Stock NPD35K system, vendor, bootloader
Xceede's v8.01 kernel
TWRP 3.02 v6.0
Encrypted data partition
I currently get bootloops every time I boot into TWRP. After using TWRP and attempting to reboot it will then bootloop into recovery refusing to boot the system.
I have found it can be fixed by rebooting into fastboot and the "fastboot reboot" command. But this is frustrating if I don't have a laptop handy.
This happens every time I need to boot into recovery to install or update via TWRP. Is anyone else getting the same bootloops and has anyone found a permanent fix?
Thanks guys.
Sent from my Nexus 6P using Tapatalk

Hi Jake,
I had exactly the same issue since NPD35K except the fastboot reboot solution did not work for me.
What i could find was that if you flash the default vendor, recovery and cache partition via fastboot and then put off the tablet, it should after all of this boot correctly to the system.
Cheers,
Mathieu

You are not alone ..
I had the recovery bootloop once myself.
I did the "fastboot reboot" command and since then the Pixel C is booting fine again.
Did several installations afterwards .. no problems anymore.
Just once ..
But if you get it every reboot this a real problem.
Right now I am not able to help you .. just don't know the root cause and how to fix it.
As it looks like, it helps if you go back to stock recovery, like mentioned above.
I can not confirm this .. as I don't have the problem.
Good luck !

Thanks for the advice guys.
As I said it only bootloops immediately after boating into TWRP (even if I don't install anything), if I reboot from system it's fine.
At the moment I prefer to keep TWRP installed and reboot from fastboot if I need to use TWRP. I don't see an advantage to installing the stock recovery. It would be great to pinpoint what's causing this though.
Sent from my Pixel C using Tapatalk

I'm still getting this TWRP bootloop. I've tried several versions - 3.0.0, 3.0.21, 3.0.23. I've tried numerous times re-flashing stock using NRT and then flashing the recovery again. I've also tried fastboot-reboot.
I'm on stock 7.1.1 - NMF26H. If i need to install a different version for this to work I can do that.
Is there perhaps some particular version of TWRP that everyone but me is using? Or are there some specific versions of other files that I also need to flash along with TWRP? From what I've read if I get past this once that's probably it.
Thanks

badwiring said:
I'm still getting this TWRP bootloop. I've tried several versions - 3.0.0, 3.0.21, 3.0.23. I've tried numerous times re-flashing stock using NRT and then flashing the recovery again. I've also tried fastboot-reboot.
I'm on stock 7.1.1 - NMF26H. If i need to install a different version for this to work I can do that.
Is there perhaps some particular version of TWRP that everyone but me is using? Or are there some specific versions of other files that I also need to flash along with TWRP? From what I've read if I get past this once that's probably it.
Thanks
Click to expand...
Click to collapse
Pls install latest bootloader and latest factory image via fastboot, manually.
Pls use latest fastboot binaries from Google.
Pls install 3.0.2-23 via fastboot as well.
Reboot directly into TWRP and not into system in between.
Install SuperSu.zip v2.79 in TWRP.
Reboot into system.
The first time the system will boot twice .. it's normal.

followmsi said:
Pls install latest bootloader and latest factory image via fastboot, manually.
Pls use latest fastboot binaries from Google.
Pls install 3.0.2-23 via fastboot as well..
Click to expand...
Click to collapse
Thank you. I'll try this today. If I use s tool like NRT to flash "stock" to the device, does that cover what's described in the first step - latest bootloader and latest factory image - or is there something else I need to flash at that step?
Thanks

badwiring said:
Thank you. I'll try this today. If I use s tool like NRT to flash "stock" to the device, does that cover what's described in the first step - latest bootloader and latest factory image - or is there something else I need to flash at that step?
Thanks
Click to expand...
Click to collapse
Maybe your problem is related to the tool itself
For this reason I recommend to use the official google fastboot tool for complete flashing of factory image including bootloader.
To have a proper base to continue ..
Good luck !
EDIT: .. no need to wipe data here. Just a fresh system, vendor, cache and boot image from factory image.

followmsi said:
Maybe your problem is related to the tool itself
For this reason I recommend to use the official google fastboot tool for complete flashing of factory image including bootloader.
To have a proper base to continue ..
Good luck !
Click to expand...
Click to collapse
I think that answers my question - the original factory image including the bootloader.
I'll try it in a few hours. Thank you very much!

That worked! I was currently on stock 7.1.1 so I tried it first without re-flashing, although I was prepared to go back to that step if it didn't work.
First I downloaded SuperSU 2.79 and copied the ZIP to my device.
I used Minimal ADB and Fastboot (which I think is taken from the official Google source) and flashed recovery-twrp-3.0.2.23.followmsi-ryu.img.
Then I rebooted into recovery - not system - and flashed SuperSU.
Finally I rebooted into system.
The Google logo appeared for a moment and then it booted again (exactly as you said.) Then it booted normally.
Finally! Thank you very much! Hopefully this will help someone else too. It can be the smallest detail we miss that makes the difference.

badwiring said:
That worked! I was currently on stock 7.1.1 so I tried it first without re-flashing, although I was prepared to go back to that step if it didn't work.
First I downloaded SuperSU 2.79 and copied the ZIP to my device.
I used Minimal ADB and Fastboot (which I think is taken from the official Google source) and flashed recovery-twrp-3.0.2.23.followmsi-ryu.img.
Then I rebooted into recovery - not system - and flashed SuperSU.
Finally I rebooted into system.
The Google logo appeared for a moment and then it booted again (exactly as you said.) Then it booted normally.
Finally! Thank you very much! Hopefully this will help someone else too. It can be the smallest detail we miss that makes the difference.
Click to expand...
Click to collapse
You are welcome ..

``

tried numerous times to flash TWRP to my Pixel C 8.0.0 (OPR1.170623.032, Nov 2017) every time with bootloop in to recovery...
most recently hoping twrp-3.2.0-0-dragon would work
---------- Post added at 07:44 PM ---------- Previous post was at 07:29 PM ----------
tried to reflash ryu-opr1.170623.032-factory-020f1cf9's boot.img and it still bootlooped.
Tried to flash the recovery and now its bootlooping into stock recovery. Any ideas?
for a stock google device, this things a nightmare to work with compared to my nexus devices

Assistance regarding a possible bricked op3

Hi guys, I searched around the forum before posting this so I apologize but I recently installed a new rom and possibly a wrong kernel with it. Afterwards, if I try to turn it on, it just shows the logo and then turns right off. I can't even go into recovery since it does the same. The only thing I can do is boot it into fastboot but I'm not sure where to go from here. I tried using a guide with no success.
Any words of wisdom?

reflash your recovery via fastboot, then boot into recovery and do a clean install
fastboot flash [recovery].img

I tried reflashing recovery but all it does is show the old rom logo that was used and then shuts down.

Hi,
Read carefully and try this guide:
forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700

which rom did you flash? You need the correct twrp file for your bootloader.

That's the first place I tried. Anytime I hook-up my phone to the PC it shows up as OnePlus Android bootloader interface under Android phone and I can't seem to update the drivers..

matze19999 said:
which rom did you flash? You need the correct twrp file for your bootloader.
Click to expand...
Click to collapse
I used the Freedom Rom 2.0

Arken2121 said:
I used the Freedom Rom 2.0
Click to expand...
Click to collapse
you need this twrp file:
https://forum.xda-developers.com/devdb/project/dl/?id=21835

matze19999 said:
you need this twrp file:
https://forum.xda-developers.com/devdb/project/dl/?id=21835
Click to expand...
Click to collapse
Thank you so much, I guess I installed the wrong TWRP and I can FINALLY get into recovery. Thank you so much.

Moto G5 automatically boots into TWRP

Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?

I have the same problem, it comes back to recovery all the time and we can tell you about it, some help please
---------- Post added at 09:59 PM ---------- Previous post was at 09:43 PM ----------
Hi, I've come back, hahaha, I installed resurrection remix 7.1, previous all the wipes and reboot in bootloader I gave start and started, great.

I had this problem trying to install the rom ViperOS. I solved it with one of these steps:
- Boot into Fastboot, select "Start" with volume Keys.
- Flash "boot.img" directly from the zip that is ROM, do this using a PC.
- If you're using stock rom, reflash boot.img
Greetings

CypherPotato said:
I had this problem trying to install the rom ViperOS. I solved it with one of these steps:
- Boot into Fastboot, select "Start" with volume Keys.
- Flash "boot.img" directly from the zip that is ROM, do this using a PC.
- If you're using stock rom, reflash boot.img
Greetings
Click to expand...
Click to collapse
Does not work for me.
I have flash boot.ini Atomic-OS-1.5 and OCT-N-WEEKLY ...
My phone boot always in recovery
regards
Sry for my bad english.

SuperUtilisateur said:
Does not work for me.
I have flash boot.ini Atomic-OS-1.5 and OCT-N-WEEKLY ...
My phone boot always in recovery
regards
Sry for my bad english.
Click to expand...
Click to collapse
Have you tried to boot from Fastboot?

Yes, it works once...
But if I have to restart it (or turn off and start with the power button), the phone boot always in recovery.
It is then necessary to restart fastboot then press "start".

Haxorkat said:
Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?
Click to expand...
Click to collapse
Try do a full reset through fastboot and then try installing whatever you need through fastboot and recovery. Much more reliable han ota installs/updates

Haxorkat said:
Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?
Click to expand...
Click to collapse
install resurrection remix and lock with the update of the security patch as we know, then install via fastboot the original firmware, after rebooting install resurrection and now bootea normalmally greetings

grosobart said:
install resurrection remix and lock with the update of the security patch as we know, then install via fastboot the original firmware, after rebooting install resurrection and now bootea normalmally greetings
Click to expand...
Click to collapse
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--

SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
It always says that
As long as it says at the end
Write OK
It flashed successfully

OK,
After flash,
boots automatically into recovery ...
--
I tried with various boot.img. (linéage, AOSP, OctOS, ... )
Does not work ..
I started (into fastboot), I was errors. (Process stopped)
I just restored my phone ( https://mirrors.lolinet.com/firmware/moto/cedric/official/RETAIL/ )
... boot correctly.
Never mind ...
thank you all

SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
https://forum.xda-developers.com/g5/how-to/fyi-recovered-g5-xt-1676-to-stock-t3626088
try this first, regards

SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
you should flash the correct firmware on your device and it should work, I did it several times and it works perfect

Moto G5 boots to TWRP
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??

Noel Carson said:
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??
Click to expand...
Click to collapse
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup

rajibahmed said:
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup
Click to expand...
Click to collapse
Backing up Gigs of data is a huge pain. Even if I have to copy to my pc. So, just something that's less cumbersome.

Noel Carson said:
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??
Click to expand...
Click to collapse
rajibahmed said:
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup
Click to expand...
Click to collapse
Read the faq section (2nd post) - answer is there
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737

grosobart said:
you should flash the correct firmware on your device and it should work, I did it several times and it works perfect
Click to expand...
Click to collapse
Anyone get the stock for 16gb/2gb version?

Question stuck on boot logo (fixed)

booting to fastboot after flashing with mtk, finally unlocked the bootloader so it's easier... what do i do?
i have: orangefox recovery from another xda thread here (best recovery ever)
i dont have: a stock super img because i also wanted to flash a gsi
Edit: fixed but its now stuck on boot logo
2nd Edit: fixed by installing miui 13.0.2 (IM EXCITED)

itayalush said:
booting to fastboot after flashing with mtk, finally unlocked the bootloader so it's easier... what do i do?
i have: orangefox recovery from another xda thread here (best recovery ever)
i dont have: a stock super img because i also wanted to flash a gsi
Click to expand...
Click to collapse
What do you want to do?

SubwayChamp said:
What do you want to do?
Click to expand...
Click to collapse
to get miui work again

oh wait i fixed this but now its stuck on the logo and after a few hundred years it turns off + i really want someone to make a custom rom for this device

itayalush said:
to get miui work again
Click to expand...
Click to collapse
Flash the stock ROM

I know what happened
He flashed orangefox to boot but orange fox can't flash to boot because then you can't boot the os I had the same problem

You have to copy orange fox and original boot.img to your phone. Flash the original boot.img and then flash orangefox recovery ramdisk however I don't know because I only know how to install TWRP this way

SubwayChamp said:
Flash the stock ROM
Click to expand...
Click to collapse
i did, like a million times

Stephanizgo said:
I know what happened
He flashed orangefox to boot but orange fox can't flash to boot because then you can't boot the os I had the same problem
Click to expand...
Click to collapse
i also tried with stock boot... result: still stuck on boot logo

pls anyone help

i wiped cache partition so maybe it will finally work... pls give me other solutions while it's booting

itayalush said:
i wiped cache partition so maybe it will finally work... pls give me other solutions while it's booting
Click to expand...
Click to collapse
Format data

Stephanizgo said:
Format data
Click to expand...
Click to collapse
tried a million times before

itayalush said:
i did, like a million times
Click to expand...
Click to collapse
Tell me exactly, so, I can help you.
When you unlocked bootloader, which other partitions you formatted? You said, you used "mtk", I assume you used ,mtk-client, and in the scripts of this tool, also is recommended to delete other partitions.
When you say, you flashed back the stock ROM, which method did you use?, which tool?, and what message you got from that tool, I mean, it was success, etc?

I recommend replacing Orange Fox with TWRP.
I just had this issue on a different Xiaomi phone. I replaced Orange Fox with TWRP and was able to flash LOS and fix the problem.

SubwayChamp said:
Tell me exactly, so, I can help you.
When you unlocked bootloader, which other partitions you formatted? You said, you used "mtk", I assume you used ,mtk-client, and in the scripts of this tool, also is recommended to delete other partitions.
When you say, you flashed back the stock ROM, which method did you use?, which tool?, and what message you got from that tool, I mean, it was success, etc?
Click to expand...
Click to collapse
i flashed my stock rom after finally unlocking my phone after millions of tries with the "Unknown Error -1", i finally found a modified unlock tool that fixes it. still stuck on boot logo
if you want my unlock tool, this is the file (u can publish it wherever you want)

Oh... nevermind... I just installed MIUI 13.0.2 and it's back to its normal state (Just without the data because I wiped it a way before I unlocked the bootloader)

itayalush said:
Oh... nevermind... I just installed MIUI 13.0.2 and it's back to its normal state (Just without the data because I wiped it a way before I unlocked the bootloader)
Click to expand...
Click to collapse
So you were trying to boot Xiaomi on unverified software on locked bl the mtkflash bypassed bl and installed by itself how is that possible

You can now install my TWRP lol

Stephanizgo said:
So you were trying to boot Xiaomi on unverified software on locked bl the mtkflash bypassed bl and installed by itself how is that possible
Click to expand...
Click to collapse
No, they unlocked the bootloader, as it said in the first post.
SPFT and mtk-client tools can flash even to locked devices.