yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] brackett5:
well, I was stuck on twrp loop but it was taking me to the menu to the nightmare rom I was attempting to flash. so I hit the reset option which I believe was factory reset.....cant even flash twrp from adb, because I don't have anything in the root folder of my phone.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
hmmmm your wording is throwing me off...

if you were in a twrp "loop", then you probably wouldn't be able to get out of that unless you manually bypassed to the bootloader... so it confuses me that you were in this "twrp loop" but instead of looping, it was taking you to the Nightmare ROM menu...? That, in of itself, isn't a loop...

Also, when you hit this "reset option", was it in this "menu to the nightmare rom" or the reset option within TWRP?

In any case, it seems you have two options; 1) attempt to reinstall the Nightmare ROM -- which I have zero experience with so I'm not sure if you need to do option #2 beforehand as the rom may work in tandem to the stock rom and/or 2) reflash a taimen factory image. But if it is indeed true that you are missing or lost your /data folder, I regret to inform you that you most likely have lost (outside of the stock) all your apps and settings. Hopefully you have a backup somewhere. Speaking of which, if you have a NaNdroid backup, you can skip the previous advice and restore from there! **~It really is the best policy to make a NaNdroid and/or TB backup before flashing any/all ROMs~**

If you could get back to me/us on those clarification requests and/or how implementing the two given options, it would be most helpful...

Good luck and hope this helps...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] brackett5:
all I have now is bootloader screen. cant get into twrp. I made a titanium backup but I cant even get the system to load up.

don't have stock either. my titanium backup was on the phone.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
That's good to know, and I'm glad you resolved the touchscreen response issue from before as well...

While you might not be able to get into your embedded TWRP recovery, if you truly are in the "bootloader" screen, you should be able to fastboot into twrp. Once you are in TWRP, you might try reflashing the Nightmare ROM; that is, unless, Nightmare ROM requires stock partitions to be pre-installed. I'm not even sure if you flash the Nightmare ROM in TWRP. In case it doesn't, you should be able to re-install/re-falsh the ROM in "bootloader" mode -- if you truly are seeing the "bootloader" screen...

Try any of these and/or does all this make sense?

Good luck and hope this helps...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] brackett5:
but I not longer have the twrp zip or the tb backup on my phone. it was all wiped.

---------- Post added at 07:00 PM ---------- Previous post was at 06:55 PM ----------

ok, ive managed to get back into twrp. I have no files to flash however. Any ideas??
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
Well...while I can't say anything towards your tb backup and we can only hope that your /data/media and-or /sdcard is still intact... You don't need to have the twrp.zip on your phone to boot into TWRP using fastboot...

If you can try to recall that in order to first get into TWRP to install the custom recovery, you have to boot using the fastboot command pointing at the TWRP image file (.img), then you use the TWRP installation file (.zip) while inside TWRP to install it permanently into your boot partition. As long as you can access the bootloader, you can use fastboot to temporarily boot into image files (.img) as well as flash installation files (ROM files for instance)...

You can use either/both of these methods. Try 'em. If anything, it'll get you into TWRP if that's what you so choose, but it looks like you're gonna have to stay in the bootloader and flash either/both a factory image and/or ROM installation files/methods...

Good luck...

---------- Post added at 05:07 PM ---------- Previous post was at 05:03 PM ----------

It depends on what you want to do...

Do you wish to continue trying to install/flash Nightmare ROM, or Android P beta, or back to stock Oreo? What exactly do you wish to flash in which you need these .zip files you mention?(AFAIK, not much "flashing" within TWRP do you utilize in troubleshooting or re-installing partitions via images) Do you wish to attempt to search for folders/files that may still be intact? Switch slots? etc...?e
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] brackett5:
how do I flash rom files and custom kernels the bootloader method you have mentioned?? I'm willing to pay for the help.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
Hmmm...I'm curious as to how much research and preparation you did for flashing a non-stock ROM and the like... If you had done an adequate amount, you should already know the answer to that question...

In any case, most of what goes on here on XDA Forums is by and for the goodwill of it's experts and users; I don't need or require any payment (but there are donate buttons there for these type of reasons I imagine).

Also, in any case, you regrettably have ventured outside of the parameters of this specific thread as this is a TWRP thread. It seems you got into TWRP and are able to function through it.

As per your other inquiries, you most likely will have to go to their respective sections and threads to get support as to not get off-topic by those inquiries in this thread...

P.S. Or you can continue via PM, maybe...

I've gone some extra steps for you to attempt and point you into the right direction...

Try HERE for inquiries about what you can do in Bootloader Mode. A lot of what's in the guide correlates to what you do for flashing and running adb commands. HERE is also a great guide that covers a lot of pertinent information(if anything, you'll eventually need)

Try HERE for information on custom kernels; This one is Flash kernel, but I assume much/most of the steps and methods are similar or the same as with other custom kernels (if not the general picture).

And of course you can always inquire/appeal HERE for all of your ROM inquiries and questions...

In any case, I hope some (if not all) of this helps and gives you a good idea where to go from here...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Your TWRP recovery is not decrypting your internal memory. I have the same issue.

All you have to do is go back to the system go to security and remove your security pin, pattern or password. Then you can reboot back to TWRP and you will see all of your internal memory files.

After you finish your TWRP flashes, reboot to System and put back your security. You will need to do this until TWRP is updated.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
Yeah that's what I said too...but he states that after temporarily booting to TWRP (via fastboot command), he still doesn't see any of his internal memory files (or any folders at that). It doesn't even look like he has any security. In any case, he doesn't have access to the regular system just yet to remove any security (nor does it look like he had any security to begin with or that's he's mentioned).
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] brackett5:
I meant Nitrogen ROM sorry
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
Ahh...that makes more sense. If you return to the post you quoted (#2066), I've updated and adjusted the post to reflect most appropriately to that up-to-date change.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] brackett5:
I should still be able to flash the rom from the bootloader correct?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
I'm not 100% positive as I have no experience with that ROM; but in my humble opinion, that sounds correct that you flash ROMs from the Bootloader. I mean, I know one flashes the Factory Images from there (and they should be considered the stock ROM), so it can be reasonably assumed you flash from the Bootloader.

But, again, going about this any further is off-topic so I'll leave it at that. You can always refer to the threads/references I laid out in thread 2066 and/or rely on PMs...

Good luck
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] hanschke:
[MENTION=4618389]simplepinoi177[/MENTION]

Except that annoys your signature, I ask myself if you want to fool me because nothing of what you write only meets what you need!

I have the phone since December and of course have first opened the boot loader and all the other stuff.

Whether I am now on Februrar or on May or April has nothing to do with the fact that the change of Slot B on Slot A only when starting the phone, the TWRP Recovery appears and you can not change the slot because you in the Reovery not comes and via Fastboot the message appears that no slot is supported.

If I were on Slot B would yes Android P start which was installed via OTA.

I would not care about data loss, but you just will not get flashed on the phone!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
Wow....I apologize if my signature annoys you......? And that you believe I'm trying to make you "ask yourself if want to fool [you]..."?

Back to what I was suggesting... Why can't you change slots in TWRP? You say "...can not change the slot because you in the Recovery"; are you receiving an error when you attempt to change slots?

And what happened when you did any of the other things I advised; what happened when you attempted to re-install TWRP in attempt to fix your boot partition? what happened when you attempted to flash your original stock boot.img over your seemingly corrupted boot partition?

Speaking of which, I was merely making sure you flashed the correct stock boot image by month patch; I never said it had anything to do with changing to Slot A or Slot B or to imply that you are inexperienced with these matters (rooting, updating, flashing, "opening boot loader and other stuff," etc.).

I know you are simply trying to select a different Slot to be active on. As you have attempted doing so in TWRP and through the fastboot command, I don't believe there really is any other way in selecting an specific Slot to be active on. That's why I'm suggesting these other methods so it might correct the active slot issue adversely and indirectly -- reinstalling TWRP forces slot selection as TWRP flashes both slots, flashing & overwriting your seemingly corrupted boot partition might also force a specific correct slot selection as well.

I understand there is a language barrier here. I suggest using Google Translate if you are having extraordinary troubles. But please, I am trying to help you out of my own goodwill and free time; you are coming off as rather rude and I'm only trying to help. And if you truly believe that me and my signature is attempting to merely "ask [yourself] if [I'm] trying to fool you," then you are free to not take my advice and help then and can work it out yourself or with anyone else who is willing. Please keep this in mind...

In any case, good luck and hope this helps...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Samuel Holland:
Taimen_#1

Hello, here is a link (guide) with info for rooting, installing twrp, rom, etc. I hope this might can help you out if needed still.

https://xdaforums.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] techlogik:
Android P Beta 2, anybody having decryption issues when going into TWRP after putting a PIN and fingerprint on? Did I miss a bug on this, or not supported yet on Android P? Thought it worked fine on Beta 1...but that was awhile ago. Thanks
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] jasonstackhouse:
Android P is not yet supported, it most likely will not be until its out of beta. You can still use TWRP with Android P, however you just can not keep a lock screen set when you are booting into TWRP. As for TWRP working with Beta 1, it likely would have, but each new month rolls out a new security update that presents new decryption issues with TWRP.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] tarroyo:
Is twrp still being worked on? Or is it use as is???? Pixel 2 was released in October and were still on beta.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ridobe:
Maybe this helps.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
Well...I would say that since it was "...released in October," there have been 2 or 3 major updates because Google monthly patches messed up TWRP a good deal a number of times (the decryption debacle is probably the most notable) -- not to say anything bad about TWRP, they are awesome and are doing their best while

not even

being payed for it (necessarily, i'm certain there are still donations). As such, I doubt one can claim that TWRP for the Pixel 2 XL as it is now, with all the recent updates and changes it has to have gone through, can be claimed as so super stable that it "will" be viable "for sure" for the near and far future (at least 6+ months) -- which I'm under the impression would be the only reason to finally declare it not as a beta...

But, again referencing how many updates this "beta" has gone through (the first version here on taimen is 3.1.1-beta1 should show a clear indication how far it's come since its "...release[ed] in October") should certainly display that TWRP is

clearly

being worked on and shouldn't doubt the quality of the product and/or its developers.

Also I'd like to mention that Google Maps was on "beta" for years...didn't stop all of us from relying on it or doubting it's effectiveness or quality "as is..."

**~tiny clings & clangs~** [just the sounds of my 2 cents...]
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] clever_man:
I've installed latest factory image via fastboot than boot in twrp image, flash twrp zip and Magisk 16.4. After this I boot into flashed recovery and it doesn't respond to touches. What can I do?

TWRP v 3.2.1-2
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Trinaaa:
You need to flash a custom kernel after you booted twrp...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
You can also fastboot into twrp and/or disable screen lock security to acquire touch response if you want to stay on stock kernel. However, like Trinaaa said, custom kernel is much easier ??
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
To second [MENTION=3730810]Badger50[/MENTION] opinion, running Flash Kernel is the ticket. It's not like some older kernels of the past where all kinds of extras or experimental stuff is cooked in. The Creator of Flash [MENTION=6842057]nathanchance[/MENTION] strongly believes the people at Google know what they are doing and what defaults are best for the device. You can rest assured you are getting a quality product when you install his kernel. And of course you can then forget any the touch nonsense with TWRP too. Lol
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
While I'm not sure about the most current versions, when I was on Feb patch but refused (for my own reasons) to flash a custom kernel, even if I removed the lock screen (had no choice because updated beta wasn't out yet) still didn't get TWRP to respond...

just my experience...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] wtherrell:
Same here with the May release.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] clever_man:
Maybe you can advice kernel like stock with minimal editio just only for working touch in TWRP?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Here ya go :cool:

https://xdaforums.com/pixel-2-xl/development/taimen-flash-kernel-1-00-t3702057
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] jasonstackhouse:
I know a few people were asking about TWRP and its compatibility with Android P Beta. I did some testing and this is what works and what does not.

There is no decryption, TWRP does not have the ability to decrypt at all with Android P, so you you can not have a screen lock active when you boot into recovery. I did find an easy workaround to this, and it was to simply have all my files i wanted to access or flash on a jump drive and simply selected that storage option while in TWRP and you can flash away.

A major setback is that restores of any kind do not work. I have tried to restore everything together and individually (boot, system, vendor, data) without any success, you will just get a boot loop that eventually stops and loads the boot-loader screen. This is kind of weird too, because TWRP is able to generate backups without any issue and the backups are not corrupt.

I have had no issues using TWRP to flash kernels, magisk and other compatible zip files. However be careful, most any zip that you flash that writes to the system (for example adding a system application) will cause a soft brick and you will be stuck on the white splash screen with the "G". I was however successful in adding apps to the system by doing so manually, for example I made a folder, put the app in the folder and pasted the folder into system priv-apps, set the correct permissions and rebooted with the application working fine.

Since there is no current way to recover/load a backup in TWRP in Android P Beta, if you find your self soft bricked from something you installed/flashed, you can fix the issue in TWRP by locating the application or files you installed in the file manager folder. Its crucial however that before you flash or even install anything to your device that may not work in Android P Beta, make sure you take off your lock screen security. (If you end up in a soft brick situation and you have your security active you will have no way to delete applications or files via file manager.) For example, If you flashed a zip that installed to system/priv-apps lets say "NovaCompanion" you would locate the NovaCompanion folder in priv-apps, select the folder and delete the entire folder from the system. You will now be able to reboot your device without needing to flash the factory image.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
Awesome post and writeup [MENTION=4775019]jasonstackhouse[/MENTION]! I'm sure it will help many...

One thing I'd like to ask (and even request an experiment of if needed); In 8.1, files within the /data folder, or partition, was never encrypted -- thus TWRP could always process any files left within. For those who do not have access to a USB-C flash drive or something, would TWRP and P be able to correctly access a .zip or backup file (.win# file) if it resided in the /data folder, or partition, and/or it should be possible to adb push a .zip file to that folder and thus have access to it, correct?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] shindiggity:
I flashed June factory, fastbooted twrp img/flashed installer/flash kernel and Magisk. Booted to OS and all good, once I boot back into TWRP it just sits there and if I try and boot into OS it just boots back to TWRP.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Oh man, that's a weird one! Can you fastboot into twrp to get touch response back, and then try flashing your kernel and root again?? I did the same thing as you with one exception, I always fastboot the factory image with the -w removed to both slots.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] shindiggity:
The problem I was running Bryan's Magisk 16.5, flashed 16.4 and all good now ?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Kinda figured you'd get it fixed bruh. You know what's up :good::cool:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Reechings:
Damn I tried flashing 16.4 in twrp and it just started looping to twrp
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Did you ever get it resolved?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] HankMcCoyX:
The same thing happened to me and I reflashed Magisk 16.4 and it booted up fine.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Reechings:
Yeah I just tried again and it worked. On another note, what partitions do people backup and restore when doing nandroids?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Personally, I only backup boot, system, and data partitions. You could actually get away with only backing up data since twrp doesn't wipe system when you do a factory reset before you restore a backup :good:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Reechings:
Ok cool,so you haven't had any issues jumping back and forth just using those partitions? I know on my OG Pixel XL I used to restore system image and vendor image and boot and data.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Not thus far I haven't :good:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] profetia:
Hello everybody! I followed this guide to try to update to latest june update, it didn't work and then i installed magisk back to 2nd slot after ota and what happened is that now my phone wont start, it only boots into twrp, which is also locked and the touch screen give me no response. Im used to flashing roms kernels etc very easily on my oneplus one but it seems harder for me on the 2XL.. I have the factory image update and the platform-tools on the desktop of my Mac, but nothing happens when i try to ./fastboot-all.sh ( i removed -w) when inside fastboot mode. Please somebody give me a helping hand ??
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] KHold01:
Put your device into bootloader mode. Fastboot twrp.img. From twrp flash the twrp.zip, then flash magisk, then reboot to system. If you hang on the Google logo try a hard restart. If that does not work, install the factory image again -w. That should get you back into your system. Then, start at fastboot twrp.img process to get magisk.

Also, if you are not using a custom kernel then you will have touch response issues with twrp. If you choose to flash a kernel to fix the touch issue you will need to flash twrp.zip, flash kernel zip and finally magisk zip in that order.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] profetia:
Thanks for your fast respond!

It didn't happen anything when i tried to fast boost twrp.img , so i tried to copy the commands from fastboot-all.sh and ran them nothing happens, so i tried the "./fastboot flashing unlock_critical" & "./fastboot flashing unlock" which worked great, and then i ran all the commands from the installation file and suddenly it booted and yes, its wiped but I got it back to life which I was very afraid of.

So now when its back and running, Can I boot into fastboot and flash twrp, then kernel, then magisk, then xposed. Reboot and I should have a working twrp with screen response?

Thanks again!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] KHold01:
Yes. Also, double check and make sure you are typing all of your commands correctly. I'm on Windows and not familiar at all with Mac commands. Didn't catch that in your first post.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
....Just a side note I wanted to add....

If you use TWRP for nandroid backups, please be aware that (normally) it does

NOT

back up your internal storage or /sdcard. I mention "normally" because there is a way to get TWRP to include

ALL

of the data on the phone, but it requires a number of extra steps done in TWRP -- which is the method I employ. It's nice to have all data in one bunch/backup, but thank goodness for the compression because it ends up being a huge backup...

Also, if you intend to run custom ROMs, I've read of an issue coming up when restoring (somehow you end up accidentally backing up partitions that have missing data or something like that) -- if you are interested and intend on these, I can point you to the posts/direction where this was discussed as well as steps to backup the internal storage as well.