Can't install TWRP - Google Pixel XL Questions & Answers

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.

Related

I can't reflash stock recovery

Hi, yestarday I flashed CM 14 with TWRP to try it, and today I have tried to return to stock rom & recovery but I can't do it. At the beginning I have tried to flash stock recovery that I have downloaded from op.net with fastboot and I couldn't do it and after I have tried to do the same process but this time flash it with TWRP and also this time I couldn't able to fix it. In fine I have installed the stock ROM via TWRP and I managed to install it but now the problem is that I still can not install the stock recovery and accordingly I can't install op3 update.
An another problem is that I have tried to re-lock OEM from fastboot and when I try to turn on the phone, is asks me a pin to enable it and I don't know that pin because I haven't set no one
ICosmin said:
Hi, yestarday I flashed CM 14 with TWRP to try it, and today I have tried to return to stock rom & recovery but I can't do it. At the beginning I have tried to flash stock recovery that I have downloaded from op.net with fastboot and I couldn't do it and after I have tried to do the same process but this time flash it with TWRP and also this time I couldn't able to fix it. In fine I have installed the stock ROM via TWRP and I managed to install it but now the problem is that I still can not install the stock recovery and accordingly I can't install op3 update.
An another problem is that I have tried to re-lock OEM from fastboot and when I try to turn on the phone, is asks me a pin to enable it and I don't know that pin because I haven't set no one
Click to expand...
Click to collapse
Need to download custom twrp http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Then use flashify to flash recovery
cbendixe84 said:
Need to download custom twrp http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Then use flashify to flash recovery
Click to expand...
Click to collapse
i have already flashed twrp 3.0.2.2 but now I would flash stock recovery but when I try to install it and turn into it op3 show me only op logo and after a few seconds the screen become black.
your phone is bricked I'm assuming. there is a thread for that. that should work for you!
sahed01 said:
your phone is bricked I'm assuming. there is a thread for that. that should work for you!
Click to expand...
Click to collapse
No it isn't. Because I managed to put stock ROM into it via adb with push command and after I have installed it from twrp that works. My only problem is that i can't flash stock recovery.
i have the same issue. Tried many times but i'm getting a black screen after one plus logo for both stck recovery and unmodified twrp. only moidified twrp is working. please let me know if u find a way to resolve this.
thanks in advance
varmasagiraju said:
i have the same issue. Tried many times but i'm getting a black screen after one plus logo for both stck recovery and unmodified twrp. only moidified twrp is working. please let me know if u find a way to resolve this.
thanks in advance
Click to expand...
Click to collapse
I downloaded the stock rom and inside it(stock rom.zip) i put the stock recovery after I reflashed the stock rom via adb from twrp and in fine I locked bootloader.
ICosmin said:
I downloaded the stock rom and inside it(stock rom.zip) i put the stock recovery after I reflashed the stock rom via adb from twrp and in fine I locked bootloader.
Click to expand...
Click to collapse
you can reboot in to stock recovery without any issues?? I think I should give it a try. And you are saying the bootloader is locked again ?
varmasagiraju said:
you can reboot in to stock recovery without any issues?? I think I should give it a try. And you are saying the bootloader is locked again ?
Click to expand...
Click to collapse
Yes, I manage to reboot into stock recovery and i relocked bootloader(you needn't relock bootloader if you do not want)
ICosmin said:
Yes, I manage to reboot into stock recovery and i relocked bootloader(you needn't relock bootloader if you do not want)
Click to expand...
Click to collapse
Great. Can I place the file in beta8 rom .zip file and flash it using adb ??
If this procedure doesn't you can download an older version of oxygen os and update it via ota. At the first attempt when you will try it will give you an error and at the second attempt It will download all the ROM again and it will reflash by itself
varmasagiraju said:
Great. Can I place the file in beta8 rom .zip file and flash it using adb ??
Click to expand...
Click to collapse
I suggest you to try at the beginning with the beta 7 because if that procedure not work for you, you can't downgrade to beta 7.
ICosmin said:
I suggest you to try at the beginning with the beta 7 because if that procedure not work for you, you can't downgrade to beta 7.
Click to expand...
Click to collapse
Thank you.
Will let you know if it worked.
I had that problem.
Solution as follows, worked everytime for me: (I have not tried this method with the newest beta 8)
1. Flash OOS 3.2.6 firmware in twrp.
2. Reboot to fastboot and flash official oxygen os recovery downloaded from the OnePlus website. (This is still the old version for some reason, thus why it won't work)
3. Side load community build with oxygen os recovery, this will flash the new firmware back and update the recovery to be community build compatible.
4. Before rebooting erase everything (factory restore)
5. Reboot to OOS, finish setting up.
6. Turn on advance reboot in developer settings.
7. Reboot to recovery via the reboot menu. First time boot into the recovery may take sometime, but it has always worked for me.
8. After everything looks good, go ahead and OEM lock in fastboot, recovery should work as usual this time and format your phone
OP did you find a solution to this?? Im on the same boat as you

When i install TWRP in my oneplus 3 and i reboot to system still stock recovery again

Step to expose what happens to me:
after brick my oneplus 3 by flash a wrong zip I got back to the stock rom, but when I try to install twrp only stays 1 time. When I reboot the system and try again to enter TWRP it appears the stock recovery of oneplus. Any idea why this happens and how to fix it?
BlackDeath XVI said:
Step to expose what happens to me:
after brick my oneplus 3 by flash a wrong zip I got back to the stock rom, but when I try to install twrp only stays 1 time. When I reboot the system and try again to enter TWRP it appears the stock recovery of oneplus. Any idea why this happens and how to fix it?
Click to expand...
Click to collapse
Flash the recovery by adb. This should make it stick.
zelendel said:
Flash the recovery by adb. This should make it stick.
Click to expand...
Click to collapse
I flash it with adb 3 times and still stock when i reboot the phone
BlackDeath XVI said:
I flash it with adb 3 times and still stock when i reboot the phone
Click to expand...
Click to collapse
Immediately after flashing TWRP, without booting, flash SuperSu or Magisk and then boot to system.
tnsmani said:
Immediately after flashing TWRP, without booting, flash SuperSu or Magisk and then boot to system.
Click to expand...
Click to collapse
What is the diference for do twrp permanently installing magisk?? Ty very much for you help
BlackDeath XVI said:
What is the diference for do twrp permanently installing magisk?? Ty very much for you help
Click to expand...
Click to collapse
Your question is not very clear. If you are asking how TWRP stays permanent if Magisk is flashed, I think that since Magisk modifies the boot image, it prevents the ROM from overwriting TWRP with stock recovery.
tnsmani said:
Your question is not very clear. If you are asking how TWRP stays permanent if Magisk is flashed, I think that since Magisk modifies the boot image, it prevents the ROM from overwriting TWRP with stock recovery.
Click to expand...
Click to collapse
ty yes that my question jajaja

Rooting went fine Flashing rom almost bricked me due to directions??

I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Sent from my [device_name] using XDA-Developers Legacy app
androidddaaron said:
I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Click to expand...
Click to collapse
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list out what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
I know it's a typo but condom kernel cracked me up. Does it automatically boot you to safe mode?
Sent from my Pixel 2 XL using XDA Labs
androidddaaron said:
I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Click to expand...
Click to collapse
What?
I never flashed a custom ROM on this device, but it should be fairly easy. Turn off security settings on stock ROM, flash permanent twrp. Wipe system, dalvik/ cache and data and install RR. Boot and wait a few minutes, it sometimes takes some time. I don't know how the gapps situation is, so you might need to flash gapps. Also make sure to make a backup since you will wipe all data. Should be fairly easy of you followed the steps correctly
Vinnipinni said:
What?
I never flashed a custom ROM on this device, but it should be fairly easy. Turn off security settings on stock ROM, flash permanent twrp. Wipe system, dalvik/ cache and data and install RR. Boot and wait a few minutes, it sometimes takes some time. I don't know how the gapps situation is, so you might need to flash gapps. Also make sure to make a backup since you will wipe all data. Should be fairly easy of you followed the steps correctly
Click to expand...
Click to collapse
What I' did to flash the rom was separate from rooting procedures . The phone been unlocked for months.
I did both separate times
I fastboot booted twrp.img then I installed magisk zip. I did not permanent flash twrp zip after . I only flashed the perm twrp zip after I wiped and flsahed the RR Rom . So another words I was on twrp temp boot only when I flashed the rom then I flashed twrp zip per the rom Dev instructions . But I can't make sense why you have to flash twrp after you flash a rom install .
I'm assuming it goes like this
Install latest magisk apk.
Fastboot boot twrp .img
Then perm flash twrp .zip
Then flash magisk .zip
Reboot into the O.S and check for root
Reboot into (permanent Twrp) swipe to allow modifications .
wipe stock rom with the swipe only method??
Install Rom of choice and reboot !
Or is it install Rom /flash twrp.zip for a second time then reboot
Sent from my [device_name] using XDA-Developers Legacy app
CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
I want to flash a rom but I'm not understanding how the pixel 2 xl works with twrp vs other devices .
If I reboot without first flashing a kernel then maybe that's the dilemma?
I just don't get why you need to flash permanent twrp .zip after you install Rom If you already had twrp permanent installed to begin with .
I' went over what I did in this thread and what I'm guessing I did wrong. So do I need special kernel for each and every rom listed . I never had to flash a kernel to get a rom to boot on any device and I've been flashing for years with T-Mobile phones on Galaxy devices and unlocked Google based phones.
Sent from my [device_name] using XDA-Developers Legacy app
I don't get why you would need to flash magisk before.
0. Make Backups and turn off security settings. Also make sure you're on the newest OTA
1. Boot into TWRP
2. Do a factory reset in Wipe settings.
3. Flash ROM
4. Flash TWRP of you want, not required but recommended
5. Reboot and set it up
6. Install magisk Manager and reboot to TWRP
7. Flash magisk and reboot
That's it.
CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
Hey let me ask you something, I just got the Pixel 2 XL but I always do a lot of research. Something I wasn't prepared for is the touch issue in TWRP. It works fine when initially installed, works fine sometimes after a reboot, but always ends up not working because touch isnt working. You're saying I can install a custom kernel and that should be fixed? I've always rocked Elemental or Franco's but am on rooted stock and since I've never stayed stock before I'm not even sure if I can flash another kernel without changing ROMs. If I can, or even if I have to change ROMs, you're saying that most custom kernels have the touch in TWRP working?
nein7three said:
Hey let me ask you something, I just got the Pixel 2 XL but I always do a lot of research. Something I wasn't prepared for is the touch issue in TWRP. It works fine when initially installed, works fine sometimes after a reboot, but always ends up not working because touch isnt working. You're saying I can install a custom kernel and that should be fixed? I've always rocked Elemental or Franco's but am on rooted stock and since I've never stayed stock before I'm not even sure if I can flash another kernel without changing ROMs. If I can, or even if I have to change ROMs, you're saying that most custom kernels have the touch in TWRP working?
Click to expand...
Click to collapse
All the custom kernels fix the twrp touch issue. You can flash them anytime you want on stock rom via twrp. Just disable screen lock(just initially for safety) boot into twrp, flash your kernel then magisk, reboot and done
Badger50 said:
All the custom kernels fix the twrp touch issue. You can flash them anytime you want on stock rom via twrp. Just disable screen lock(just initially for safety) boot into twrp, flash your kernel then magisk, reboot and done
Click to expand...
Click to collapse
Thanks a lot. Does changing kernels remove magisk?
nein7three said:
Thanks a lot. Does changing kernels remove magisk?
Click to expand...
Click to collapse
Some do, some don't. That's why you flash magisk after the kernel. But that's changing as well :good:

Question about TWRP.

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.

Rooting issues

I have a Pixel 3 XL and I was following this Guide to root it.
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
When I get to part 2-10 (The part to install Magisk) my phone wont boot into the OS. Instead I end up back at TWRP. If I reinstall TWRP from my download folder or restore a back up I can get back into the OS. I still have TWRP installed but no root. I know I'm doing something wrong but I'm not sure. Like I've said TWRP is install but not Magisk.
What Android version; Pie or Q, stock or custom? What Magisk version? Are you booting to TWRP (fastboot boot twrp.img) or did you flash twrp to the device?
ktmom said:
What Android version; Pie or Q, stock or custom? What Magisk version? Are you booting to TWRP (fastboot boot twrp.img) or did you flash twrp to the device?
Click to expand...
Click to collapse
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.
Potatochip400 said:
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.
Click to expand...
Click to collapse
Try clean fastboot flashing the stock boot.img back onto the phone. You can get it from the fastboot factory img. Then just boot TWRP to flash the Magisk zip. The Magisk zip will need to be on the device for the booted TWRP to find it just like if you were running TWRP installed on the device.
An alternative is to use Magisk manager to patch the stock boot.img and then fastboot flash that patched img to the device.
ktmom said:
Try clean fastboot flashing the stock boot.img back onto the phone. You can get it from the fastboot factory img. Then just boot TWRP to flash the Magisk zip. The Magisk zip will need to be on the device for the booted TWRP to find it just like if you were running TWRP installed on the device.
An alternative is to use Magisk manager to patch the stock boot.img and then fastboot flash that patched img to the device.
Click to expand...
Click to collapse
I tried the easiest method first, which was installing the Magik app and flashing the zip, I got the following error,
Device platform: arm64-v8a
copying image to cache
Unpacking boot image
! Unsupported/Unkown image format
! Installation failed
I'll try flashing the stock image, but should I flash twrp again after the image? I've done this before in the past because some phones require it as part of the rooting instructions. Does this order sound right, flash stock image, reboot, flash twrp reboot, then Magisk?
Potatochip400 said:
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.
Click to expand...
Click to collapse
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL
Eudeferrer said:
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Just tried the beta version (19.4) and I'm stuck in a standard bootloop. I'll try and get it into recovery.
No worries, I forgot to mention that I restored a back up
Eudeferrer said:
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Surely not on Pie. I'm using 19.3 on the last Pie.
ktmom said:
Surely not on Pie. I'm using 19.3 on the last Pie.
Click to expand...
Click to collapse
I'm on pie, but your first suggestion was the fix. I had to flash the factory img before doing everything else. I just had to put a little more time a side and not be lazy.

Categories

Resources