Database Info

Installed twrp phone reboots to twrp

I installed twrp on my pixel on 7.1.1 it reboots to tarp again I got it to boot to the p.s. by clicking reboot / a on bottom left option but get error codes and can't open a lot of apps. I tried to install a tom and clear device cache and cause fails. Anyone know how I can fix this. I thought I used all the latest files

cgrimm9 said:
I installed twrp on my pixel on 7.1.1 it reboots to tarp again I got it to boot to the p.s. by clicking reboot / a on bottom left option but get error codes and can't open a lot of apps. I tried to install a tom and clear device cache and cause fails. Anyone know how I can fix this. I thought I used all the latest files
Click to expand...
Click to collapse
Did you fastboot boot into TWRP, then flash twrp-pixel-installer-sailfish-3.0.2-0-RC1.zip? Were you stock prior?

Installed img through pc then installed the zip file with twrp. I found a article here stating I need to flash stock ing to get back to normal

cgrimm9 said:
Installed img through pc then installed the zip file with twrp. I found a article here stating I need to flash stock ing to get back to normal
Click to expand...
Click to collapse
Yes, you are not supposed to install twrp, just boot into it. If you install it by mistake, you go back, flash stock boot.img, and do it again.
This is from Dees_Troy's post located here
https://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.

@Tulsadiver First off, thanks for the post on this. I installed TWRP to slot A by accident and am finding myself in this same predicament (though I found that I can boot by switching to slot B). I found another post online that mentioned what you commented on, specifically:
Tulsadiver said:
Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
Click to expand...
Click to collapse
Having previously downloaded Oreo 8.1 and setup root, I had loaded into TWRP, went to install, selected the TWRP zip, and installed (as per what you had suggested and what I read earlier). This is what led me to the current problem, making me realize that I'm missing something in the description. Now, I likely don't need to flash TWRP (I don't develop and used flashfire to do upgrades) but my last upgrade left me rootless and I felt having it installed would make life a little easier. I was hoping to ask for a clarification on the TWRP install.
Also, you mentioned flashing the stock img. Do you mean from the android OTA downloads? I was getting a corrupt file error when I tried flashing that to slot a...

alienjon said:
@Tulsadiver First off, thanks for the post on this. I installed TWRP to slot A by accident and am finding myself in this same predicament (though I found that I can boot by switching to slot B). I found another post online that mentioned what you commented on, specifically:
Having previously downloaded Oreo 8.1 and setup root, I had loaded into TWRP, went to install, selected the TWRP zip, and installed (as per what you had suggested and what I read earlier). This is what led me to the current problem, making me realize that I'm missing something in the description. Now, I likely don't need to flash TWRP (I don't develop and used flashfire to do upgrades) but my last upgrade left me rootless and I felt having it installed would make life a little easier. I was hoping to ask for a clarification on the TWRP install.
Also, you mentioned flashing the stock img. Do you mean from the android OTA downloads? I was getting a corrupt file error when I tried flashing that to slot a...
Click to expand...
Click to collapse
Things have changed with 8.1. you have to root with magisk. From slot b you cannot fastboot flash boot_a boot.img?
I believe the instructions now are to boot to TWRP, install TWRP pixel installer zip, then flash Magisk zip
Here is where TWRP files are here
https://dl.twrp.me/sailfish/

Tulsadiver said:
From slot b you cannot fastboot flash boot_a boot.img?
Click to expand...
Click to collapse
I hadn't tried yet. I was worried about messing things up further without asking for help online first. I'll give this a shot later. Does boot.img refer to the android image file? (ie: what I'd download from the OTA site?)

alienjon said:
I hadn't tried yet. I was worried about messing things up further without asking for help online first. I'll give this a shot later. Does boot.img refer to the android image file? (ie: what I'd download from the OTA site?)
Click to expand...
Click to collapse
Yes, the zip file that is located where the flash-all.bat is. Unzip it and flash the boot.img.
I bought a Pixel 2 on swappa. It had different bootloader's on slot a and slot b. I couldn't flash updates when on slot a. I thought I was hosed but from slot b I could flash to slot a so now I'm fine. Slot a had a preview bootloader.

Pixel 3 March 2019 Root

Okay. I'm late getting into the pixel 3 game because I got my pixel 2 late last year. But i've just purchased it recently and it's great. But iv'e been unable to root it & I've never had any trouble rooting any Google devices in the past, stretching back to the nexus 3. I've always been under the impression that Google encourages rooting, or at least, makes no attempt to stop it. So I'm surprised that I even feel the need to make this post. I can find plenty of people talking about rooting even up to February's security patch, but nothing for Google's current most recent security patch (March 2019). Nothing I do seems to make any difference, I've followed steps on several tutorial threads to the letter and still end up in a boot loop. I'm tempted to downgrade so I can root, but I'd like to avoid that if possible. Am I the only one having this issue? I'm not able to find a wealth of people complaining about it, which strikes me as weird. Has Google done something with this update to actively block Magisk, or what? I'm at a loss. Like I say, never have I ever encountered such a road block in rooting any device.
Anyways, hopefully someone can ease my frustrations by at least sharing in them. Thanks for any replies.

This assumes you have already unlocked the bootloader...
1. Fastboot boot TWRP.
2. If you don't want permanent TWRP, skip to step 5. Otherwise, go to step 3.
3. Flash TWRP zip.
4. Reboot to recovery.
5. Flash magisk zip.
6. Reboot to system
That's it. It's the same on every security patch.

This is exactly what I am doing. I've also tried manually patching the boot image and live booting it as well as flashing it, but none of these methods render any different result. I've done it so many times I don't need to follow instructions, I only looked at tutorials because it kept failing. I've definitely got the bootloader unlocked but every time I install Magisk I get boot looping.

You need to boot into system before flashing magisk.

watlingj said:
This is exactly what I am doing. I've also tried manually patching the boot image and live booting it as well as flashing it, but none of these methods render any different result. I've done it so many times I don't need to follow instructions, I only looked at tutorials because it kept failing. I've definitely got the bootloader unlocked but every time I install Magisk I get boot looping.
Click to expand...
Click to collapse
Maybe a shot in the dark, but, in twrp, after you flash the magisk zip, reboot to twrp, flash the magisk uninstaller, then flash magisk again. I had the same issue when I updated to 9.0 on my P2XL :good:

wangdaning said:
You need to boot into system before flashing magisk.
Click to expand...
Click to collapse
I've never had issues without booting back to system before flashing magisk.

Badger50 said:
Maybe a shot in the dark, but, in twrp, after you flash the magisk zip, reboot to twrp, flash the magisk uninstaller, then flash magisk again. I had the same issue when I updated to 9.0 on my P2XL :good:
Click to expand...
Click to collapse
Thanks for the suggestion but alas, still boot looping.

wangdaning said:
You need to boot into system before flashing magisk.
Click to expand...
Click to collapse
I've tried this, it didn't make a difference.

OK, try:
1) Flash factory image, remove -w if you want
2) Reboot system then reboot bootloader
3) Fastboot boot TWRP (if you flash install zip reboot system again, then back to recovery)
4) Flash magisk v18.1 (redownload it to eliminate bad dl as culprit)
Not sure what is causing your problems. The initial guide is the same as with the march update. I have done it several times without issue.

wangdaning said:
OK, try:
1) Flash factory image, remove -w if you want
2) Reboot system then reboot bootloader
3) Fastboot boot TWRP (if you flash install zip reboot system again, then back to recovery)
4) Flash magisk v18.1 (redownload it to eliminate bad dl as culprit)
Not sure what is causing your problems. The initial guide is the same as with the march update. I have done it several times without issue.
Click to expand...
Click to collapse
Sorry for the late reply, i actually ended up returning it to stock and swapping it for a different one, because my speaker was making a weird sound when i was calling and it was having bluetooth issues, this one rooted perfectly fine first try.'
Except, Magisk randomly can't detect it's self through it's own manager app, but all my installed modules are working.. but i can't... manage them..

Updated to 9.5.9 and now it reboots into TWRP over and over.

I followed the previously rooted guide to update to 9.5.9 and now when the phone reboots, it gets to the unlock screen and immediately tells me its shutting down and reboots back into twrp again. How do i fix this? Please help and thank you.

what method did you use (there are a million rooted guides)? did u get the correct OS OTA for you model phone? provide us more info please.

Looks like i forgot to turn off the magisk modules. I had to go into twrp and delete them all and re download the modules. silly me

I'm having a similar issue. I can't figure out what to do, but I i went and deleted all the zip files for magisk but after reinstalling magisk thru twrp, I get stuck booting to recovery everytime. I can someone help point me in the right direction?

jakemaxfield said:
I'm having a similar issue. I can't figure out what to do, but I i went and deleted all the zip files for magisk but after reinstalling magisk thru twrp, I get stuck booting to recovery everytime. I can someone help point me in the right direction?
Click to expand...
Click to collapse
I stuck at the same situation. Can you flashboot flash boot.img and then it can boot normally?

Same problem here.
Situation before flash: stock 9.5.8, Magisk, a number of Magisk modules
What I did:
* downloaded 9.5.9 with Oxygen Updater
* disabled Magisk modules
* rebooted
* installed 9.5.9 from the builtin System Update
* went to Magisk, installed it with After OTA
* rebooted to recovery
* installed TWRP and Magisk
* cleared Dalvik
* rebooted to system
The phone seems to start normally, but when it reaches the unlock screen it immediately goes to Power Off, then it reboots to TWRP (not power off). From TWRP I can decrypt data ok etc.
I tried reinstalling the boot loader, OTA image, TWRP, Magisk - same result. Rebooting to system from TWRP just goes back to Power Off then TWRP.

equlizer said:
I followed the previously rooted guide to update to 9.5.9 and now when the phone reboots, it gets to the unlock screen and immediately tells me its shutting down and reboots back into twrp again. How do i fix this? Please help and thank you.
Click to expand...
Click to collapse
If this is any help in the future, whilst I don't have twrp, I install the updates via local update in settings > system > updates and then before reboot I go to magisk manager, and install magisk to second slot and reboot. Never had a problem and I'm on 9.5.9 now. The only modules I disable, update, or remove are the magisk ROMs available here such as no limits, as they are usually version specific.

manor7777 said:
If this is any help in the future, whilst I don't have twrp, I install the updates via local update in settings > system > updates and then before reboot I go to magisk manager, and install magisk to second slot and reboot. Never had a problem and I'm on 9.5.9 now. The only modules I disable, update, or remove are the magisk ROMs available here such as no limits, as they are usually version specific.
Click to expand...
Click to collapse
That's exactly what I did. It landed me to the bootloop.

All you guys had to do is,
Install the full uddate zip in twrp,
Install the latest twrp zip,
Reboot recovery,
Install latest magisk,
Reboot system,
Hope this helps, cheers

Update: I can break out of the loop from TWRP > Advanced > Fix Recovery Bootloop. That lets me boot normally, but loses root. As soon as I reinstall Magisk I get back to the bootloop.

lcd047 said:
Update: I can break out of the loop from TWRP > Advanced > Fix Recovery Bootloop. That lets me boot normally, but loses root. As soon as I reinstall Magisk I get back to the bootloop.
Click to expand...
Click to collapse
I'm in the same boat.
My twrp doesn't offer to decrypt partition_b so I cannot manually install Magisk on the new partition.

This seems to be a common problem when updating rooted Oneplus 7 pro and I haven't found a update guide which actually works every time. Last update to 9.5.8 I had the same issue where I couldn't get into oxygen os because it turned itself off and when twrp opened I couldn't decrypt the data. I couldn't find a solution last time and I had to full wipe and start from scratch. Now I don't want the same to happen so I hope someone can post a guide how to do the update successfully.

sapalot said:
This seems to be a common problem when updating rooted Oneplus 7 pro and I haven't found a update guide which actually works every time. Last update to 9.5.8 I had the same issue where I couldn't get into oxygen os because it turned itself off and when twrp opened I couldn't decrypt the data. I couldn't find a solution last time and I had to full wipe and start from scratch. Now I don't want the same to happen so I hope someone can post a guide how to do the update successfully.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414.
Works every time, the same way I have been doing for both 6T and 7 Pro.

Sometimes you might be on the wrong active slot, you can change this by using fastboot set_active a or fastboot set_active b. TWRP seems to like changing your slot but will tell you when it does. If you're getting stuck try changing slot and booting.

schmeggy929 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414.
Works every time, the same way I have been doing for both 6T and 7 Pro.
Click to expand...
Click to collapse
It worked for me for 9.5.8, got the bootloop this time around. I guess this means I'm not the Chosen One.
---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------
djsubterrain said:
Sometimes you might be on the wrong active slot, you can change this by using fastboot set_active a or fastboot set_active b. TWRP seems to like changing your slot but will tell you when it does. If you're getting stuck try changing slot and booting.
Click to expand...
Click to collapse
I tried that too. When I switch to the other slot I get to a menu where I can only wipe data, reboot to boot loader, or reboot to recovery. Not particularly useful.

Hey guys!
I'm having the same problem. No matter how I try to update it will reboot to stock recovery.
I was wondering if any of you have /Data converted to f2fs? Maybe it could be culprit...

mkos86 said:
Hey guys!
I'm having the same problem. No matter how I try to update it will reboot to stock recovery.
I was wondering if any of you have /Data converted to f2fs? Maybe it could be culprit...
Click to expand...
Click to collapse
What I had to do here was go to fastboot mode and flash twrp img. Then in TWRP I flash the TWRP zip file and magisk and rebooted. All good

Alright so I fixed mine. I went and just removed all the modules while I was in twrp. To do that go to Advanced, then file manager or whatever it says, find the adb folder and from there look for a folder named Modules and just delete them all. From there just reinstall magisk through twrp and it should all work.

jakemaxfield said:
Alright so I fixed mine. I went and just removed all the modules while I was in twrp. To do that go to Advanced, then file manager or whatever it says, find the adb folder and from there look for a folder named Modules and just delete them all. From there just reinstall magisk through twrp and it should all work.
Click to expand...
Click to collapse
Thank you sir, this fixed it for me, too. So the missing link was that Magisk modules have to be removed completely, not just disabled, before upgrading. Removing all directories except .core from /data/adb/modules allows the phone to boot normally, with Magisk enabled.

schmeggy929 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414.
Works every time, the same way I have been doing for both 6T and 7 Pro.
Click to expand...
Click to collapse
Thats the way i tried that time and got stuck in bootloop.

Issues after installing latest update, keeps powering off?

Any help, I flashed magisk after latest update and I noticed it didnt reboot itself like it said it would. I clicked reboot myself and now I cant get back into my phone, just keeps saying powering off and takes me bootloader screen where I have enter my pin and it starts decrypting, then options to either reboot to recovery or fastboot. What can I do now?

Happened to me. My bet is you didn't delete all the magisk modules before running the update

mike710_0 said:
Happened to me. My bet is you didn't delete all the magisk modules before running the update
Click to expand...
Click to collapse
Never had to delete them before? What can I do now?

SysAdmNj said:
Never had to delete them before? What can I do now?
Click to expand...
Click to collapse
To be honest I don't know. All I do know is the problem gradually got worse. I ended up having to use that recovery software (can't remember the name of it)
Hopefully someone can shed some more light on what to do though

SysAdmNj said:
Never had to delete them before? What can I do now?
Click to expand...
Click to collapse
Boot into twrp of you have bootloader unlocked (fastboot boot whatever.img) and Flash magisk manager for recovery mode. You can use it to disable or remove modules in recovery

manor7777 said:
Boot into twrp of you have bootloader unlocked (fastboot boot whatever.img) and Flash magisk manager for recovery mode. You can use it to disable or remove modules in recovery
Click to expand...
Click to collapse
That will fix my issue? Never had to disable magisk modules before while doing an update, something changed?
UPDATE: Still need help but I was able to fastboot into twrp. I was able to reboot into Slot A and I was back in my phone ok. I was able to reboot and come back ok. I tried the update again, after it downloaded and installed. I opened magisk manager, went to install magisk, selected Install to Inactive Slot(After OTA) - I've been doing these steps all along - bu this time it failed again and put me in a bootloop. Luckily I know how to get back into Slot A but is something wrong with my other slot that the update isnt installing ok?
Only other weird thing I noticed was that after magisk finishes installing, it said it would force reboot my device but it doesn't. I have to manually push the reboot button and thats when I reboot into a boot loop. Any ideas?

Another thought, could it be that I bought this phone off oneplus but this is a verizon update 9.5.13 GM21AA? Although I do use a verizon sims card as a secondary line. Could this be causing the confusion? Maybe I"m just confused with this Slot A & B stuff :laugh:

SysAdmNj said:
Still need help but I was able to fastboot into twrp. I was able to reboot into Slot A and I was back in my phone ok. I was able to reboot and come back ok. I tried the update again, after it downloaded and installed. I opened magisk manager, went to install magisk, selected Install to Inactive Slot(After OTA) - I've been doing these steps all along - bu this time it failed again and put me in a bootloop. Luckily I know how to get back into Slot A but is something wrong with my other slot that the update isnt installing ok?
Click to expand...
Click to collapse
You need to flash Magisk to both slots. Also need to flash TWRP installer again (if you have been wondering why you can't get into TWRP, that is why).
---------- Post added at 11:59 AM ---------- Previous post was at 11:55 AM ----------
SysAdmNj said:
That will fix my issue? Never had to disable magisk modules before while doing an update, something changed?
Click to expand...
Click to collapse
This isn't new, it's been known for some time. But only a few modules are actually known to cause problem (Call Recording module is one).
I've used the following process successfully every time I've updated, since getting the 7 Pro shortly after it was released.
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414
The steps have mostly stayed the some. Not sure exactly when the part about removing Magisk modules was added, but it's been a while.

redpoint73 said:
You need to flash Magisk to both slots. Also need to flash TWRP installer again (if you have been wondering why you can't get into TWRP, that is why).
---------- Post added at 11:59 AM ---------- Previous post was at 11:55 AM ----------
This isn't new, it's been known for some time. But only a few modules are actually known to cause problem (Call Recording module is one).
I've used the following process successfully every time I've updated, since getting the 7 Pro shortly after it was released.
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414
The steps have mostly stayed the some. Not sure exactly when the part about removing Magisk modules was added, but it's been a while.
Click to expand...
Click to collapse
I dont usually flash twrp, I usually just fastboot into twrp. Its how I got out of bootloop this time, then in twrp I selected reboot into slot A.
So those steps are definitely a bit different than how I've been updating recently. I will try those steps. Before I would just download and install update, go into magisk manager and install into inactive slot and it would reboot automatically and that was it.

Can't reboot to Recovery after upgrade to Android 10

Hello everyone,
As I mentioned in the title, since I upgraded to Android 10, can't boot to recovery.
Dowloaded latest version of the Adb kit, and while issuing
adb reboot recovery
the phone reboots but goes to normal boot.
Tried manually (power + vol down etc.) and when choosing Recovery - same thing happens.
Needless to say that my laptop is authorized debug device and phone is in debug mode etc. - I have done this many times before Android 10 update.
All I try to do is to sideload the latest OTA as I did many times before because my phone is rooted and the updates do not install automatically.
Pixel (First generation)
Rooted with Magisk
Bootloader unlocked
Stock recovery (using TWRP without installing it when flashing Magisk)
Hope somebody can advise. Obviously there is something new in Android 10 which has to be set (like the need for debugging authorization for example, which I already did).
Thank you
John

Im getting a similar problem. I get stuck on th Google logo screen. I cant hard-reset, recovery mode or boot, the only things that works is th barcode.

Android 10 changed something in the ramdisk that you can't install TWRP directly on the phone. You have to boot it via PC using "fastboot boot <insert twrp image name>.img"

You can try installing twrp to ramdisk. Put twrp 3.3.1-0.img in your devices storage and then fastboot twrp 3.3.0-0 (disable pin etc first) then once it's booted go to advanced and select install to ramdisk and select the 3.3.1-0.img and it should install it. You may get a not enough storage error on 10/Q (I did) bit worth a punt. Make a back up first as usual, if no good flash a fresh factory.img and see if that cures it and then restore your apps/data etcfrom your Google back up (if you use it)
Good luck

junglism93 said:
You can try installing twrp to ramdisk. Put twrp 3.3.1-0.img in your devices storage and then fastboot twrp 3.3.0-0 (disable pin etc first) then once it's booted go to advanced and select install to ramdisk and select the 3.3.1-0.img and it should install it. You may get a not enough storage error on 10/Q (I did) bit worth a punt. Make a back up first as usual, if no good flash a fresh factory.img and see if that cures it and then restore your apps/data etcfrom your Google back up (if you use it)
Good luck
Click to expand...
Click to collapse
Thank you for the advice, however as I mentioned in my original post I don't want to install TWRP permanently , and the problem is that I cannot go to the stock recovery mode which has no connection to TWRP. There is something with Android 10 which changed since 9 and I'm interested to find what. Everything worked fine before the upgrade.
Also, the option to flash factory image and restore (I also have Titanium in addition to Google backup) is a too much of a hassle. I use this phone for real, not only to play with it.
Anyway, again thank you for your input.
John

Sorry mate, re read your OP. I just tried booting into the aosp recovery and got the same issue! My guess is its magisk as I could boot into the aosp recovery prior to installing it. Re flash or restore the previous boot.img or a stock boot.img and it should boot into aosp recovery again. Magisk must be installing to or patching the aosp recovery ramdisk and stopping it booting. Other than that just fastboot twrp and use that.
Edit: it's magisk, restored original images and it booted into aosp recovery first try.

I've had no problems installing TWRP 3.3.0.0 normally after using an *.img file to get TWRP started. EDIT: and booting into it.

junglism93 said:
Sorry mate, re read your OP. I just tried booting into the aosp recovery and got the same issue! My guess is its magisk as I could boot into the aosp recovery prior to installing it. Re flash or restore the previous boot.img or a stock boot.img and it should boot into aosp recovery again. Magisk must be installing to or patching the aosp recovery ramdisk and stopping it booting. Other than that just fastboot twrp and use that.
Edit: it's magisk, restored original images and it booted into aosp recovery first try.
Click to expand...
Click to collapse
You are right. I did open Magisk and from the uninstall options choosed "Restore images" (no need to do complete uninstall, which is the other option). After that I was able to boot in recovery etc. I guess this is what you meant in your PS. At the end re-flashed Magisk and all is back to normal.
I will alert the Magisk team about the issue (if they are not already aware).
Case closed.
Thanks again.
John

Master Cylinder said:
I've had no problems installing TWRP 3.3.0.0 normally after using an *.img file to get TWRP started. EDIT: and booting into it.
Click to expand...
Click to collapse
Please read my OP. I was clear that I DON'T want to install TWRP permanently and this was never the problem.
The problem is solved (kind of). See the other posts.
Thank you.
John

I thought TWRP wasn't compatible with Android 10 yet? I am seeing mixed things

aholeinthewor1d said:
I thought TWRP wasn't compatible with Android 10 yet? I am seeing mixed things
Click to expand...
Click to collapse
It works just fine.

Mzprx said:
It works just fine.
Click to expand...
Click to collapse
Are there steps for how to install somewhere? I keep reading that it's not working on the Pixel with Android 10. Thanks

aholeinthewor1d said:
Are there steps for how to install somewhere? I keep reading that it's not working on the Pixel with Android 10. Thanks
Click to expand...
Click to collapse
It is a mess. It works with Pixel (I have this one and can confirm) and supposedly Pixel 2. It won't work for brand new phones arriving with factory installed Android 10.
Read the following:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html#
After that, if you want to try, go to the page below to find instructions for your device. Note that the list is by manufacturer, so if you are looking for Pixel, it is under Google.
https://twrp.me/Devices/
Just in case - backup and have the factory image for your phone handy in case something goes wrong. For google phones you can download the image and see instructions here:
https://developers.google.com/android/images
Note that I never installed TWRP permanently, so I can't say if the permanent installation will work (I think it should, but not sure). Typically I just load TWRP and use it to flash pakages, but at the end I'm keeping the stock recovery.
Hope this helps. Good luck.
John

Mzprx said:
It is a mess. It works with Pixel (I have this one and can confirm) and supposedly Pixel 2. It won't work for brand new phones arriving with factory installed Android 10.
Read the following:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html#
After that, if you want to try, go to the page below to find instructions for your device. Note that the list is by manufacturer, so if you are looking for Pixel, it is under Google.
https://twrp.me/Devices/
Just in case - backup and have the factory image for your phone handy in case something goes wrong. For google phones you can download the image and see instructions here:
https://developers.google.com/android/images
Note that I never installed TWRP permanently, so I can't say if the permanent installation will work (I think it should, but not sure). Typically I just load TWRP and use it to flash pakages, but at the end I'm keeping the stock recovery.
Hope this helps. Good luck.
John
Click to expand...
Click to collapse
Thanks. Yea from what I can tell no one has had luck actually installing it on the Pixel with Android 10 yet. I'm familiar with how to fix everything if something goes wrong. I would try but others have already tried and failed. It won't install for them.

firstly, dont use whatever ****ty platform-tools you are using, get them from here.
secondly, you dont install recovery on android 10 yet, it doenst work. you have to just boot to twrp using `fastboot boot twrp.img` once you are in bootloader mode.