I've gone through the posts trying to find an answer. seems like people are having similar issues, but either not exactly the same or no solution found.
I have flashed to stock 7.1.2 ( i know its old, but i want back button kill function). I can use the twrp image to fastboot into it. But when i try to flash the twrp zip (ive tried from 3.1-current), i get the encryption issue. I tried doing this with security passcode set and also with it turned off. same result.
And when twrp is encrypted, i can no longer boot into system. If i try to, it just boots back into twrp (which remains encrypted). I then have to use fastboot and twrp.img to open an unencrypted twrp. From there I can at least boot into android. But i lose root.
Could i potentially use fastboot to get into twrp, flash magisk and xposed and it would work? Yes, i wouldnt be able to boot into twrp without fastboot. But at this point im just trying to get things working any way i can.
Was going to try custom rom but when i tried to flash RR i couldnt get past the boot screen (left it going for at least 20-30 min before forcing a reboot).
Since I cant even get twrp to stick. dont want to go trying to flash roms.
cnoevl21 said:
Could i potentially use fastboot to get into twrp, flash magisk and xposed and it would work?.
Click to expand...
Click to collapse
yes, this should work. it's what i do. i fastboot boot the twrp image and then flash magisk. i don't used xposed and i don't flash the twrp zip anymore. if i need to use twrp, i'll just fastboot boot it.
Related
I'm having trouble installing TWRP on my Oneplus 3.
I can install it fine through Fastboot, it installs without problem.
But when I actually want to go to the recovery menu (by selecting it in the bootmenu), the screen flickers briefly and I'm returned to the bootmenu.
However, I have found a way to boot TWRP.
When I use the All in One Toolkit, there is the option "Flash TWRP AND Boot it".
This way I can get in TWRP, but as soon as I reboot, I'm having the same problem..
Has anyone experienced this before or know what to do?
Never experienced this problem. But are you sure that you use the correct version of TWRP for your ROM?
And did you try not to flash it via fastboot but just boot it? The command is
fastboot boot recovery twrp.img
Click to expand...
Click to collapse
yes even i had this issue once. i used to get a black screen when i try to enter recovery mode.but later i flashed modified twrp file. And its working fine now.
and try this while trying to enter recovery after installing through fastboot.
fastboot flash recovery twrp.img
fastboot boot recovery twrp.img
Click to expand...
Click to collapse
if you are unable to resolve the issue following this. you can head over to this link.
https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-1.439108/ .
the modified twrp also can be found here.
I've exactly the same problem...No solution at this moment...
EDIT: I found the solution: flash this recorvery:
http://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999
I solved my problem with.
I formated and reinstalled custom rom with gapps.
I can't get TWRP to install on my phone. I've tried manually fastbooting all three TWRP images that are available from the TWRP website. I tried installing TWRP using the Skipsoft Toolkit. Whatever I do I never get past the TWRP splash screen--no menus ever come up. Since no menus ever come up I can't install the TWRP zip or a custom ROM. I've been trying this for hours and it's driving me crazy. Is there a different procedure to boot into temporary TWRP if you are on the June bootloader? Is there another version of the TWRP image file that I'm missing? Am I supposed to let the TWRP sit there for a really long time? This is driving me completely batty.
Did you downgrade from O?
If that is the case you should flash the stock bootloader and boot.img into both slots on your device and try again
pcriz said:
Did you downgrade from O?
If that is the case you should flash the stock bootloader and boot.img into both slots on your device and try again
Click to expand...
Click to collapse
I did. Will give that a try. Thanks.
pcriz said:
Did you downgrade from O?
If that is the case you should flash the stock bootloader and boot.img into both slots on your device and try again
Click to expand...
Click to collapse
That did the trick! Thanks.
jhs39 said:
That did the trick! Thanks.
Click to expand...
Click to collapse
Np
It took way too long but I installed TWRP, flashed DU, installed ElementalEx, rooted with custom Magisk for Pixel and got the phone to pass Safety Net. Everything seems to be working. However, whenever I go into recovery TWRP doesn't seem to be there. I appear to get the stock recovery which I don't understand. I can still boot into temporary TWRP and flash the TWRP zip and flash other zips on my phone but I can't seem to boot directly into TWRP. Is this normal or did I do something wrong somewhere?
jhs39 said:
It took way too long but I installed TWRP, flashed DU, installed ElementalEx, rooted with custom Magisk for Pixel and got the phone to pass Safety Net. Everything seems to be working. However, whenever I go into recovery TWRP doesn't seem to be there. I appear to get the stock recovery which I don't understand. I can still boot into temporary TWRP and flash the TWRP zip and flash other zips on my phone but I can't seem to boot directly into TWRP. Is this normal or did I do something wrong somewhere?
Click to expand...
Click to collapse
If I recall correctly, after flashing any rom you have to flash twrp again before rebooting. Apparently roms flash an img to our recovery partition that looks similar to a modified CWM.
noidea24 said:
If I recall correctly, after flashing any rom you have to flash twrp again before rebooting. Apparently roms flash an img to our recovery partition that looks similar to a modified CWM.
Click to expand...
Click to collapse
I actually did that. Maybe I was supposed to boot into the rom once, then back into recovery to flash TWRP. There are a lot of different flashing instructions for this phone. It's hard to keep it all straight.
jhs39 said:
I actually did that. Maybe I was supposed to boot into the rom once, then back into recovery to flash TWRP. There are a lot of different flashing instructions for this phone. It's hard to keep it all straight.
Click to expand...
Click to collapse
Booting into the rom, going back into temp TWRP and flashing the TWRP zip seems to have worked --TWRP actually stuck this time and I can boot directly into it now. It's a shame Google made the Pixel XL such a headache to flash on.
I apologize if this is the wrong place to ask, but when I try to boot my phone (Mi 6) normally I end up seeing TWRP's OpenRecoveryScript running briefly before the phone shuts off and boots again. My phone started doing this last night without any apparent prompt while I had it charging and plugged into my computer. I think it might be because of the MIUI update I installed earlier that day. I can still boot the phone into the TWRP recovery screen with all its options, and into fastboot, but I can't boot it normally. How can I fix this without encrypting/deleting or otherwise messing up the data currently on my phone?
I was able to fix this problem by downloading the stock recovery .img file posted in this thread ( en.miui.com/thread-639221-1-1.html ) and flashing the recovery section using TWRP. I hope whatever caused my problem is fixed in future updates of TWRP.
If you want a advice, no worry about use TWRP for root or any other feature you can need, but don't flash it, only boot it. If you replace the Recovery, you will have problem with otas and other stuff. Instead:
fastboot flash recovery twrp.img
use
fastboot boot recovery twrp.img
Yes, you must use it everytime you want enter on twrp, but it by far, less problematic
Hey guys and gals,
Silly question.
For a few months now, I've had TWRP 3.1.0 RC2 installed and no matter what I do, I absolutely cannot reboot into recovery. If I choose reboot to recovery while the phone is running, it results in a ramdump and eventually boots to system. If I reboot into the bootloader and choose to boot into recovery mode from there, it just boots to system. It's incredibly annoying. Literally the only time I can get into recovery is when I connect my phone to a computer and fastboot boot into a temporary TWRP Img and install TWRP again. Once I boot into system, I can never boot into recovery again. This is extremely inconvenient on the go, like right now, because I want to flash V4A before I start playing music from my Bluetooth speaker. Guess I'll just listen to low quality music :'(
What am I doing wrong? This is stupid.
Alcolawl said:
Hey guys and gals,
Silly question.
For a few months now, I've had TWRP 3.1.0 RC2 installed and no matter what I do, I absolutely cannot reboot into recovery. If I choose reboot to recovery while the phone is running, it results in a ramdump and eventually boots to system. If I reboot into the bootloader and choose to boot into recovery mode from there, it just boots to system. It's incredibly annoying. Literally the only time I can get into recovery is when I connect my phone to a computer and fastboot boot into a temporary TWRP Img and install TWRP again. Once I boot into system, I can never boot into recovery again. This is extremely inconvenient on the go, like right now, because I want to flash V4A before I start playing music from my Bluetooth speaker. Guess I'll just listen to low quality music :'(
What am I doing wrong? This is stupid.
Click to expand...
Click to collapse
I had the same problem, then I got a twrp boot loop, ended up having to boot into slot b and reflash stock img through adb, beware...
I was JUST about to post this! Exact same problem to the tee (except using RC1)! Hopefully someone smarter can chime in lol
NYYFan325 said:
I was JUST about to post this! Exact same problem to the tee (except using RC1)! Hopefully someone smarter can chime in lol
Click to expand...
Click to collapse
I was on RC1 also
Anyone got some insight to this? Can't be that uncommon of a problem...
Try starting the process again.
Boot to bootloader
Fastboot boot 3.0.2 rc1
In twrp flash 3.1.0 r 2
Reboot recovery and check if it works
noidea24 said:
Try starting the process again.
Boot to bootloader
Fastboot boot 3.0.2 rc1
In twrp flash 3.1.0 r 2
Reboot recovery and check if it works
Click to expand...
Click to collapse
I never had TWRP stick unless I added another step to your instructions --boot completely into the rom once, go back into the bootloader, open temp TWRP and flash the TWRP zip again. If I didn't do this my recovery would always revert to stock but, strangely, even though I was running a custom rom the combination of the custom rom and stock recovery never bootlooped my phone and I was able to boot from the stock recovery to the custom rom with no problems. The only reason not being able to boot into TWRP was even an issue was that you can't flash any zips in recovery without it. Otherwise the phone ran so perfectly I didn't even realize at first that TWRP wasn't still the installed recovery.
Get the stock boot.img (this will remove root/kernel/twrp)
Boot into the bootloader
Fastboot flash boot boot.img
Fastboot --set-active=a or b (switch to the inactive slot)
Fastboot reboot bootloader
Fastboot flash boot boot.img
Fastboot --set-active=a or b (reload previous slot)
Fastboot reboot bootloader
Fastboot BOOT twrp.img
Flash TWRP in twrp..
If you can do that I would be interested in your results.
Also pointing out flashing rooms and certain zips here in the forums WILL revert you back to a stock recovery. Just my last bit of helpful information, hope someone gets it figured out, flashing is already a chore for those of us who like to experiment.
pcriz said:
Get the stock boot.img (this will remove root/kernel/twrp)
Boot into the bootloader
Fastboot flash boot boot.img
Fastboot --set-active=a or b (switch to the inactive slot)
Fastboot reboot bootloader
Fastboot flash boot boot.img
Fastboot --set-active=a or b (reload previous slot)
Fastboot reboot bootloader
Fastboot BOOT twrp.img
Flash TWRP in twrp..
If you can do that I would be interested in your results.
Click to expand...
Click to collapse
I was able to boot into recovery after doing this. Got a bootloop booting into system though, but flashing the ROM (and TWRP) fixed it.
Hello,
Try booting to TWRP 3.0.2 RC1 then flash TWRP 3.0.2 RC1 + SR1-SU v2.82SR1 + SU Pixel Fix (from Chains beta thread) one right after the other in the same TWRP session then reboot. Should fix your issue, give you recovery+root without ram dump.
Cheers
Everytime you flash a rom you need to flash twrp before rebooting or you'll lose twrp recovery.
Unfortunately I've had to get my Pixel XL replaced due to a defect and received a Verizon edition XL running 7.1.1. This is what I get for buying it from Best Buy Therefore I cannot unlock the bootloader and this problem no longer applies to me.
I'll keep this thread open for a bit in case it's useful for anyone else. I'll just sit here in all of my Stock-ness.
I couldn't get this to work. Tried flashing stock boot.img, then booting off of the TWRP images but I keep getting TWRP boot loop. Any suggestions? Tried flashing the entire stock image as well and no dice...
I wanted to install Lineage OS and was curious if I could install it without having TWRP flashed into recovery. I mean, I'll still use fastboot boot twrp, ill just won't have it in my recovery.
I'm asking because when I tried to do fastboot flash recovery twrp it said failed antirollback check. Would like some help if possible
Once you temporarily boot twrp, you can it flash twrp image from within it.
It would work without, but you won't be able to update LOS, unless you boot twrp again.
See: - https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
And don't downgrade MIUI firmware/rom.
corkiejp said:
Once you temporarily boot twrp, you can it flash twrp image from within it.
It would work without, but you won't be able to update LOS, unless you boot twrp again.
See: - https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
And don't downgrade MIUI firmware/rom.
Click to expand...
Click to collapse
Thanks for your help !
Anti rollback is such a pain in the ass.