Can't install twrp - Google Pixel 2 XL Questions & Answers

Hi,
Trying to boot twrp 3.2 from fastboot but it just causes the phone to reboot twice and boots back to android.
Using tmz12bb on latest security patch

UpwindManager18 said:
Hi,
Trying to boot twrp 3.2 from fastboot but it just causes the phone to reboot twice and boots back to android.
Using tmz12bb on latest security patch
Click to expand...
Click to collapse
Are you using the twrp.img with the correct command??...fastboot boot twrpxxx.img?

Badger50 said:
Are you using the twrp.img with the correct command??...fastboot boot twrpxxx.img?
Click to expand...
Click to collapse
I am

UpwindManager18 said:
I am
Click to expand...
Click to collapse
SDK platform-tools up to date?? That's really odd though. Maybe download again? ??

This happened to me too, just keep re-doing it until it finally works. That's what I did anyway and it eventually booted into TWRP lol

Related

twrp problem

Hi anyone can help me. Before i restart my device it automatically boots in bootloader mode. I manage to fix it via fastboot command "fastboot oem fb_mode_clear"
But after that my problem now is when i restart my device it boots on twrp recovery. When i reboot system it also goes back to twrp mode. What is this problem? Any fix for this? Thanks everyone.
Kdx10 said:
Hi anyone can help me. Before i restart my device it automatically boots in bootloader mode. I manage to fix it via fastboot command "fastboot oem fb_mode_clear"
But after that my problem now is when i restart my device it boots on twrp recovery. When i reboot system it also goes back to twrp mode. What is this problem? Any fix for this? Thanks everyone.
Click to expand...
Click to collapse
try hold power & -volume when logo appear hold again to buttons for 10 sec then check
hamad94 said:
try hold power & -volume when logo appear hold again to buttons for 10 sec then check
Click to expand...
Click to collapse
Tried it but it wot fix. Anyways thanks for reaching up bro
What version of TWRP are you using?
If you are on the latest one, try the version before.
https://www.androidfilehost.com/?w=files&flid=126925
Jimi Mack said:
What version of TWRP are you using?
If you are on the latest one, try the version before.
https://www.androidfilehost.com/?w=files&flid=126925
Click to expand...
Click to collapse
I have the latest v3.1.1-0
How can i flash the old one?
Edit. Tried it sir but no success :angel:
Kdx10 said:
I have the latest v3.1.1-0
How can i flash the old one?
Edit. Tried it sir but no success :angel:
Click to expand...
Click to collapse
To flash in TWRP you need to flash it as an image, the option is in there. It will allow you to flash an older or newer version when with in TWRP.
Jimi Mack said:
To flash in TWRP you need to flash it as an image, the option is in there. It will allow you to flash an older or newer version when with in TWRP.
Click to expand...
Click to collapse
Yes sir tried it but still not solved. Now i lost my hope in recovering my device :crying:
Kdx10 said:
Yes sir tried it but still not solved. Now i lost my hope in recovering my device :crying:
Click to expand...
Click to collapse
Just to double check, you have a rom installed right, you did not accidentally wipe that?
Jimi Mack said:
Just to double check, you have a rom installed right, you did not accidentally wipe that?
Click to expand...
Click to collapse
Yes sir. I have 4 different roms in my sd card. The aex, xperience, crdroid and aokp. Im in aex rom before everything is smooth no error when restarting. Until then i decided to try the aokp rom 05/21 nightly build, and after that i flash also a modified boot logo to get rid of the unlock bootloader warning iflash it using fastboot commamd but when i power it on and set up the aokp rom everything goes well but then i need to restart my phone then the problem now is appearing. It directly boot in twrp recovery.

flashing question

So do I really have to remove my password Everytime I flash something via twrp?..
egren58 said:
So do I really have to remove my password Everytime I flash something via twrp?..
Click to expand...
Click to collapse
Yes
Sent from my Pixel 2 XL using Tapatalk
browniegirl said:
Yes
Click to expand...
Click to collapse
Damm all I want is center clock that's it lol
egren58 said:
Damm all I want is center clock that's it lol
Click to expand...
Click to collapse
It sucks I know
Sent from my Pixel 2 XL using Tapatalk
Not anymore. TWRP just got updated.
rickysidhu_ said:
Not anymore. TWRP just got updated.
Click to expand...
Click to collapse
Where can I update?..
rickysidhu_ said:
Not anymore. TWRP just got updated.
Click to expand...
Click to collapse
Be cared if your wanting to flash roms or switch slots. There are reports that the new version is not working in that regard!!?
egren58 said:
Where can I update?..
Click to expand...
Click to collapse
Right about here ?
https://dl.twrp.me/taimen/
Badger50 said:
Be cared if your wanting to flash roms or switch slots. There are reports that the new version is not working in that regard!!?
Click to expand...
Click to collapse
I'm still on stock and stick to one slot so this new update is very welcome, now that it can finally decrypt! Appreciate the heads up regardless though =) :highfive:
rickysidhu_ said:
I'm still on stock and stick to one slot so this new update is very welcome, now that it can finally decrypt! Appreciate the heads up regardless though =) :highfive:
Click to expand...
Click to collapse
I'm stock room. And I have kernal installed am I safe flashing this I have no idea what slot I am though
egren58 said:
I'm stock room. And I have kernal installed am I safe flashing this I have no idea what slot I am though
Click to expand...
Click to collapse
You should be okay to flash that mod (I don't know which one it is exactly so don't hold me responsible); but I'm pretty sure you should be okay without worrying about slots, for this at least
rickysidhu_ said:
You should be okay to flash that mod (I don't know which one it is exactly so don't hold me responsible); but I'm pretty sure you should be okay without worrying about slots, for this at least
Click to expand...
Click to collapse
Sorry I meant I should be okay updating to the latest twrp. I've heard people locking up their phone in the thread.. lol
egren58 said:
Sorry I meant I should be okay updating to the latest twrp. I've heard people locking up their phone in the thread.. lol
Click to expand...
Click to collapse
Yes, if your still on 8.1, there's no trouble with it at all. Fastboot the new twrp.img, enter twrp, flash the twrp.zip, then kernel.zip, then magisk.zip. I would, for this new update, still remove your screen lock security just to be safe. Then add it back in, and you'll be fine :good:
Badger50 said:
Yes, if your still on 8.1, there's no trouble with it at all. Fastboot the new twrp.img, enter twrp, flash the twrp.zip, then kernel.zip, then magisk.zip. I would, for this new update, still remove your screen lock security just to be safe. Then add it back in, and you'll be fine :good:
Click to expand...
Click to collapse
+1
rickysidhu_ said:
+1
Click to expand...
Click to collapse
I already have twrp install couldn't it just be as flashing the updated TWRP?.
egren58 said:
I already have twrp install couldn't it just be as flashing the updated TWRP?.
Click to expand...
Click to collapse
Go ahead if you'd like. I Was merely pointing out the safe and tested method that I, and many others use to upgrade. The P2XL is a little bit of a finicky beast. I've read too many stories over the last 3 months with bootloops and soft bricks by others doing simple flashing procedures that worked fine on other nexus devices, but crap a brick on this thing. Therefore, I don't take chances
Badger50 said:
Go ahead if you'd like. I Was merely pointing out the safe and tested method that I, and many others use to upgrade. The P2XL is a little bit of a finicky beast. I've read too many stories over the last 3 months with bootloops and soft bricks by others doing simple flashing procedures that worked fine on other nexus devices, but crap a brick on this thing. Therefore, I don't take chances
Click to expand...
Click to collapse
So I have to boot into temporary recovery with adb and than flash the updated trwp img
egren58 said:
So I have to boot into temporary recovery with adb and than flash the updated trwp img
Click to expand...
Click to collapse
The procedure is as follows...
1. Put the new twrp.img in your platform-tools folder.
2. In bootloader/fastboot mode type fastboot boot twrpxxxx.img. That'll boot you into temp twrp .
3. In temp twrp, flash the new twrp.zip, then kernel.zip, then magisk.zip
4. Reboot, done :good:
Badger50 said:
The procedure is as follows...
1. Put the new twrp.img in your platform-tools folder.
2. In bootloader/fastboot mode type fastboot boot twrpxxxx.img. That'll boot you into temp twrp .
3. In temp twrp, flash the new twrp.zip, then kernel.zip, then magisk.zip
4. Reboot, done :good:
Click to expand...
Click to collapse
So I have to reflash the boot I'm and magisk too
egren58 said:
So I have to reflash the boot I'm and magisk too
Click to expand...
Click to collapse
Yes. There have been reported issues with bootloops if you don't flash your custom kernel and magisk at the end.
Badger50 said:
The procedure is as follows...
1. Put the new twrp.img in your platform-tools folder.
2. In bootloader/fastboot mode type fastboot boot twrpxxxx.img. That'll boot you into temp twrp .
3. In temp twrp, flash the new twrp.zip, then kernel.zip, then magisk.zip
4. Reboot, done :good:
Click to expand...
Click to collapse
So I have to reflash the boot I'm and magisk too?

December update breaks magisk?

Hi all,
I've updated my 3xl to the december update like usual, flash-all.bat without -w. Afterwards, it boots fine, and in settings it clearly states that I'm running the December security patch.
However, when I boot into twrp (not installed) and flash magisk, android boots to just before asking my SIM PIN, says "Shutting Down", then reboots and gives me the message "Can't load Android System. Your data may be corrupt." etc. inside stock recovery.
Did the December update somehow break magisk? Anyone gotten it to work? I'd rather not do a factory reset if it's not needed.
Works fine for me.
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Working fine for me as well.
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
mikepopo99 said:
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Click to expand...
Click to collapse
jd1639 said:
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
TonikJDK said:
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
Click to expand...
Click to collapse
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Flash the stock boot.img to both slots.
Reboot and check it.
Copy the Magisk zip to your phone.
Fastboot boot the TWRP img file, don't install it.
Use TWRP to install the Magisk zip, and you are done.
RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
RogerXIII said:
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
Click to expand...
Click to collapse
Good deal. That is why I always keep a copy of the Magisk uninstaller on the phone itself. As long as I can get to BL/temp TWRP .img, the worst I am out is the time it takes me to reconfigure Magisk.
RogerXIII said:
However, when I boot into twrp (not installed)
Click to expand...
Click to collapse
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Shaftamle said:
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Click to expand...
Click to collapse
The TWRP image from the official website, and then simply fastboot boot twrp.img
RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
Ok cool. Wasn't sure if there was an app like fashify or something.
Fire Hound 8.1
sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
you are godsend my friend.
Touz604 said:
you are godsend my friend.
Click to expand...
Click to collapse
Glad you got it figured out.
RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
You ca't yet.
bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
Thread is from 2018
I am gonna check the official TWRP website for the workable TWRP for my Pixel 3 till I see your post
wangdaning said:
Thread is from 2018
Click to expand...
Click to collapse

Bootloop back to twrp

Yesterday i sideloaded the December ota, today i decided im going to unlock the bootloader, root and install a custom kernel. I followed the instructions in the pined post in guides and well, now my pixel wont boot and its booting back to trwp.
What i did was boot twrp.img thru fastboot.
Once twrp booted i flashed the twrp zip, kernel and magisk beta zip.
How do i get out of this bootloop now?
welp, just tried to flash the factory image and got this:
error: failed to load 'image-crosshatch-pq1a.181205.006.zip': Not enough space
mac208x said:
Yesterday i sideloaded the December ota, today i decided im going to unlock the bootloader, root and install a custom kernel. I followed the instructions in the pined post in guides and well, now my pixel wont boot and its booting back to trwp.
What i did was boot twrp.img thru fastboot.
Once twrp booted i flashed the twrp zip, kernel and magisk beta zip.
How do i get out of this bootloop now?
Click to expand...
Click to collapse
fastboot flash boot --slot all boot.img
#6 in this guide.
Homeboy76 said:
fastboot flash boot --slot all boot.img
#6 in this guide.
Click to expand...
Click to collapse
Thank you! So would you know what i did wrong? Or what do i now to get root and custom kernel?
mac208x said:
Thank you! So would you know what i did wrong? Or what do i now to get root and custom kernel?
Click to expand...
Click to collapse
Pixel 3/Pixel 3 XL
- fastboot boot twrp-3.2.3-1...img
- install Magisk' uninstaller
- add more zips
- Edit: Kernel of your choice
- Add more zips
- magisk-17.3.zip
- reboot system
Homeboy76 said:
Pixel 3/Pixel 3 XL
- fastboot boot twrp-3.2.3-1...img
- install Magisk' uninstaller
- add more zips
- ElementalX 1.02.zip
- Add more zips
- magisk-17.3.zip
- reboot system
Click to expand...
Click to collapse
Did exactly that but instead of ElementalX kernel im trying to use Kirisakura now back to bootloop into recovery
mac208x said:
Did exactly that but instead of ElementalX kernel im trying to use Kirisakura now back to bootloop into recovery
Click to expand...
Click to collapse
After installing the TWRP.zip change slots in TWRP, reboot recovery and flash Magisk to the other slot, change slots back, then reboot.
airmaxx23 said:
Change slots in TWRP, reboot recovery and flash Magisk to the other slot, change slots back, then reboot.
Click to expand...
Click to collapse
Im so sorry but what do you mean by slot?
mac208x said:
Im so sorry but what do you mean by slot?
Click to expand...
Click to collapse
When you're in TWRP go to reboot, then switch from your current slot to the other.
airmaxx23 said:
When you're in TWRP go to reboot, then switch from your current slot to the other.
Click to expand...
Click to collapse
Alright this is becoming silly. Did exactly as you said and again, bootloop back too twrp....Should i use the twrp from dees_troy or it doesnt matter? I dont know what it can be
Edit: Nvm im using the right twrp
mac208x said:
Alright this is becoming silly. Did exactly as you said and again, bootloop back too twrp....Should i use the twrp from dees_troy or it doesnt matter? I dont know what it can be
Edit: Nvm im using the right twrp
Click to expand...
Click to collapse
Are you flashing Magisk in both slots?
airmaxx23 said:
Are you flashing Magisk in both slots?
Click to expand...
Click to collapse
No didn't do that.
Okay so fastboot boot twrp.img
Once it boots flash the twrp.zip and magisk
Change to slot b
Flash magisk
Reboot.
Right? What about kernel?
mac208x said:
No didn't do that.
Okay so fastboot boot twrp.img
Once it boots flash the twrp.zip and magisk
Change to slot b
Flash magisk
Reboot.
Right? What about kernel?
Click to expand...
Click to collapse
Try just that first and see if you can fully boot the phone.
airmaxx23 said:
Try just that first and see if you can fully boot the phone.
Click to expand...
Click to collapse
No bootloop back to trwp. Now its stuck on the white google logo screen wont go pass it
airmaxx23 said:
When you're in TWRP go to reboot, then switch from your current slot to the other.
Click to expand...
Click to collapse
Be careful with that. I did it bricked the device. It was like there was no system on that slot. I thought it was hard bricked but someone else did the same thing and eventually got it to boot.
Sent from my [device_name] using XDA-Developers Legacy app
I dont know what do now, wont boot, cant enter recovery, apparently there is no system image the only thing i can do is enter fastboot. Never had this much damn trouble with rooting and installing twrp on a device.
jd1639 said:
Be careful with that. I did it bricked the device. It was like there was no system on that slot. I thought it was hard bricked but someone else did the same thing and eventually got it to boot.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I've been doing it all along whenever I flash anything.
mac208x said:
I dont know what do now, wont boot, cant enter recovery, apparently there is no system image the only thing i can do is enter fastboot. Never had this much damn trouble with rooting and installing twrp on a device.
Click to expand...
Click to collapse
You'll have to flash back to stock in fastboot.
mac208x said:
I dont know what do now, wont boot, cant enter recovery, apparently there is no system image the only thing i can do is enter fastboot. Never had this much damn trouble with rooting and installing twrp on a device.
Click to expand...
Click to collapse
First, have you updated your sdk platform tools with the latest fastboot and adb? That's been causing a lot of people problems if they haven't updated them. If you have I would flash the stock boot image to boot slots.
fastboot flash boot_a boot.img. and
fastboot flash boot_b boot.img
If that's not enough then flash the system's image to boot slots.
Sent from my [device_name] using XDA-Developers Legacy app
airmaxx23 said:
I've been doing it all along whenever I flash anything.
You'll have to flash back to stock in fastboot.
Click to expand...
Click to collapse
jd1639 said:
First, have you updated your sdk platform tools with the latest fastboot and adb? That's been causing a lot of people problems if they haven't updated them. If you have I would flash the stock boot image to boot slots.
fastboot flash boot_a boot.img. and
fastboot flash boot_b boot.img
If that's not enough then flash the system's image to boot slots.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
How do i do this now? Flashing boot.img does nothing, phone still wont boot and hands on the boot logo. I cant enter recovery and apply from adb, nor flashing the factory image thru fastboot work, it keeps saying there isnt enough space for the .zip
mac208x said:
How do i do this now? Flashing boot.img does nothing, phone still wont boot and hands on the boot logo. I cant enter recovery and apply from adb, nor flashing the factory image thru fastboot work, it keeps saying there isnt enough space for the .zip
Click to expand...
Click to collapse
Do you have the latest sdk platform tools. If not Google that, download the zip and extract it. Replace what you do have. I create a folder c:adb and put everything in that. Then set an environment variable path in Windows so fastboot and adb are available no matter what folder I'm working in.
Sent from my [device_name] using XDA-Developers Legacy app

Touchscreen not working in TWRP

Im using official TWRP but the touchscreen does not work, how can i get around this?
Try to hold power button for 9-10 seconds
hogze94 said:
Im using official TWRP but the touchscreen does not work, how can i get around this?
Click to expand...
Click to collapse
same here, did you get any solution?
Same to me... help!
lupomarano said:
Same to me... help!
Click to expand...
Click to collapse
what screen do you have?
Sprut_name said:
what screen do you have?
Click to expand...
Click to collapse
I have a MI A2 lite,
reflash twrp .. i had the same issue yesterday ..
Connect the phone to the computer (fastboot mode)
Launch the command line and go to the folder where you put all the prerequisites (cd Folder_name)
Boot the recovery image: fastboot boot twrp-daisy-3.3.0-0-offain.img
You will see the recovery on your phone, prompting to enter the password. Choose "Cancel"
Click to expand...
Click to collapse
solved said:
reflash twrp .. i had the same issue yesterday ..
Click to expand...
Click to collapse
tried it over and over again. still having this issue.
TWRP loads up showing me the "Keep System Read only?" page. Touchscreen wont work.
using twrp-installer-3.3.0-dees_troy-daisy
flash a stock rom , then use offain 3.3.0-0 twrp
I have the same problem, this should help https://forum.xda-developers.com/mi-a2/how-to/guide-flashing-roms-twrp-black-screen-t3913052
Thats because u dont have OS, You need to flash OS with MiFlash, unlock bootloader and flash TWRP

Categories

Resources