trying to flash twrp; it just hangs!

[freddy0872]

Yes, I have tried fastboot to flash the TWRP img, as well as skipsofts toolkit. I guess I've been using the term "flash" for fastboot, as I haven't been able to use twrp yet.. I understand that you need to flash the TWRP img via pc and then flash the TWRP zip, then SuperSU or magisk, whatever your poison may be !

Okay just make sure that you have the .img file saved some where on your PC.
Also, save the twrp.zip file to your pixel
Then boot to bootloader
Once there run the following
fastboot boot "path/to/twrp.img"
(The path to twrp.img would be where ever you saved the img file.)

That should boot you to a "Temp TWRP" if you will. Once there you can proceed to install TWRP.zip as a normal zip file.
Just wanted to clarify your not flashing anything at the bootloader... your just booting the image from PC.

 

[mazubo]

Okay just make sure that you have the .img file saved some where on your PC.
Also, save the twrp.zip file to your pixel
Then boot to bootloader
Once there run the following
fastboot boot "path/to/twrp.img"
(The path to twrp.img would be where ever you saved the img file.)

That should boot you to a "Temp TWRP" if you will. Once there you can proceed to install TWRP.zip as a normal zip file.
Just wanted to clarify your not flashing anything at the bootloader... your just booting the image from PC.

Man, thanks for the detailed instructions, and sorry I was using the wrong terminology.. duly noted!

 

[freddy0872]

Man, thanks for the detailed instructions, and sorry I was using the wrong terminology.. duly noted!

No worries my friend!
Did that solve your issue?

 

[mazubo]

No worries my friend!
Did that solve your issue?

Haven't had time to get back to the PC. I'll let you know once all is done! Cheers, and thanks again!

 

[mikefnz]

No worries my friend!
Did that solve your issue?

Thanks for taking the time to ID a likely solution to this issue. I was stuck with the same issue.

I'm afraid I gave up. After years of rooting HTC and Samsung phones, this one tripped me up. I wasted too much time and had to stop.

This thread at least helped me get rid of the damn nav bar and get a full screen back: https://forum.xda-developers.com/pixel-xl/themes/how-to-enable-true-immersive-modes-t3554299/page3

I will have another attempt in a few weeks when I have more time. In the meantime, I will make do with Beta Andriod O.

Cheers

 

[ssingh819]

has anyone figured out how to use fastboot to boot twrp with the May 2017 android O update? (marlin-opp2.170420.019-factory-22308caf.zip)

 

[parakleet]

Hi all,
*I've unlocked bootloader
* Have tried fastboot boot TWRP.img, as well as tried flashing TWRP RC1 via the Skipsoft toolkit.

Every way I've tried the phone just sits at the TWRP boot screen and doesn't allow me to go any further..

Any help here would be truly appreciated!

Cheers,

3.1.0 RC2 doesnt work for me. I get bootloops and cannot flash anything, also has an issue with decryption. Probably user error.

3.0.2 RC1 works fine.

 

[jacobkuczynski]

I'm having this same issue. I've flashed the April and May updates today and still twrp gets stuck as soon as i fastboot twrp onto my phone. I have not had this issue in the past. In the past it just went straight into twrp and asked for my pin. Is there any resolution yet? I have scrolled through the comments and tried different suggestions and no luck so far

 

[jacobkuczynski]

I'm having this same issue. I've flashed the April and May updates today and still twrp gets stuck as soon as i fastboot twrp onto my phone. I have not had this issue in the past. In the past it just went straight into twrp and asked for my pin. Is there any resolution yet? I have scrolled through the comments and tried different suggestions and no luck so far

i just got this to work, i uninstalled find my device and i took android device manager off the access. I for s**ts and giggles decided to give it a try and sure enough twrp went through finally

 

[jacob5nights]

Still haven't found solution yet has anyone found a way to fix this issue?

 

[ByzLat]

No solution for me yet either.

 

[gubacsek]

has anyone figured out how to use fastboot to boot twrp with the May 2017 android O update? (marlin-opp2.170420.019-factory-22308caf.zip)

I was spending days to get this work.... From TWRP's log, it looks like google changed something on the encryption and TWRP fails to decrypt the data partition.
Also there is an entry about failing to find the DRM device (graphic card?). For me it hangs with a black screen (fastboot boot twrp.img), but at least there is a working adb, so I am trying to manually install supersu. With no success of course... (i modified and ran the update-script, and flashed the boot image, but nothing happens after boot, like if i didn't change anything...)
I also started a thread about this, but no dev is picking up the problem. I'm not a developer, just playing around with things. I can't even compile a working recovery image myself.... I gave it today and if i don't succeed, I'll go back to 7.1.2. Can't live without my sound mods


It seems I'm the only one in the world, who want's to have a working recovery and root on the pixel.
If this is not the case, I'm willing to offer my help, trying to add something, test something. I'm open to any suggestions, a guide, at least how to compile TWRP for the pixel (to have the fastboot bootable image and so i can modify it ,and test it out a bit...). Anyone, who can add something, please contact me!

 

[jhs39]

I'm sure a lot of people would like to have working TWRP on the Pixels. The problem is that the people who program official TWRP can't even seem to do it. Google seems determined to keep people on stock with this phone. If you want to install a custom recovery and flash custom ROMs then the Pixels have to be among the absolute worst phones to own

 

[chrisjgg]

Possible solution???

So I had this issue after attempting to Flash oreo and it botched. I flashed back to the Verizon Factory image (7.1.0 - image-marlin-nde63x) After Flashing I was not able to boot into TWRP after setting up my phone. In order to fix this I spent a lot of time searching for the same answer you all were. I found that (From Nexus 6p forum) that in order to get past the splash screen I needed to boot to bootloader and Fastboot format userdata. This allowed me to boot into the TWRP.img but presented another issue as I could not mount a USB OTG drive nor copy the file from my PC to my internal storage. I did find that I could sideload the TWRP.zip file to my phone and it installed perfectly fine boot to twrp, advanced, ADB Sideload. Connect to PC > adb.exe sideload /path/to/twrp-3.0.2-0-RC1.zip.

I hope this helps you all.

 

[michaelbsheldon]

So I had this issue after attempting to Flash oreo and it botched. I flashed back to the Verizon Factory image (7.1.0 - image-marlin-nde63x) After Flashing I was not able to boot into TWRP after setting up my phone. In order to fix this I spent a lot of time searching for the same answer you all were. I found that (From Nexus 6p forum) that in order to get past the splash screen I needed to boot to bootloader and Fastboot format userdata. This allowed me to boot into the TWRP.img but presented another issue as I could not mount a USB OTG drive nor copy the file from my PC to my internal storage. I did find that I could sideload the TWRP.zip file to my phone and it installed perfectly fine boot to twrp, advanced, ADB Sideload. Connect to PC > adb.exe sideload /path/to/twrp-3.0.2-0-RC1.zip.

I hope this helps you all.

After alot of screwing up my PixelXL and going back to 100% stock, one of the main TWRP lessons I've
learned is that you can't easily work with TWRP unless you have booted the rom and set a PIN in Security.
Not doing that creates issues...

 

[dbroer91884]

So I know this is an older thread but I had this issue last night and figured it out...

Basically, the issue was for me was that I had updated to Android O then wanted to go back to Nouget to get a Nouget ROM. When I went through the process of doing a flash-all.bat, I noticed that everything seemed like it was flashed to both slot a and slot b....except the bootloader. For me, that was only flashed to the active slot.

So, I did the the flash-all.bat from fastboot on the active slot, let the device boot up and ran through the setup, then I went back to fastboot, changed the active slot using the "fastboot --set-active=_a" (or b) and redid the flash-all.bat. I was able to boot directly to TWRP using this image and able to flash within TWRP this recovery.

Two things I'm not sure of
1) I had set a screen pin because I had heard that was important. Not sure if it helped.
2) I probably could have only flashed the bootloader with fastboot flash bootloader command but again, I read to just redo the flash-all.bat so I did.

 

[Zwitterion]

So I know this is an older thread but I had this issue last night and figured it out...

Basically, the issue was for me was that I had updated to Android O then wanted to go back to Nouget to get a Nouget ROM. When I went through the process of doing a flash-all.bat, I noticed that everything seemed like it was flashed to both slot a and slot b....except the bootloader. For me, that was only flashed to the active slot.

So, I did the the flash-all.bat from fastboot on the active slot, let the device boot up and ran through the setup, then I went back to fastboot, changed the active slot using the "fastboot --set-active=_a" (or b) and redid the flash-all.bat. I was able to boot directly to TWRP using this image and able to flash within TWRP this recovery.

Two things I'm not sure of
1) I had set a screen pin because I had heard that was important. Not sure if it helped.
2) I probably could have only flashed the bootloader with fastboot flash bootloader command but again, I read to just redo the flash-all.bat so I did.

This is very helpful. To clarify, you did the following:

1. Flashed the latest Nougat Factory image using the provided flash-all.bat
2. Booted up the ROM, set a PIN.
3. Rebooted into bootloader and then from your PC, ran ""fastboot --set-active=_a" (or is it b? you are unclear here).
4. Ran flash-all.bat again (though you say you think you could have just flashed the bootloader itself at this point since you've changed the active slot)
5. Then successfully booted to temporary TWRP via the RC1 Image and then actually flashed the RC2 zip once you were in TWRP

Some questions:
1. In 5 above, how did you get the RC2.zip onto the phone in order to flash it?
2. Have you flashed any ROMs successfully? If so, which one?
3. Have you rooted? If so, how?

I appreciate any and all guidance. I swapped my N6P for this phone and my regret is growing (despite knowing that the 6P was starting to fail). I had assumed a flourishing dev community around the Pixel, only to see that it's been a year and a proper TWRP (let alone a variety of ROMs) still doesn't seem to be available!

 

[dbroer91884]

This is very helpful. To clarify, you did the following:

1. Flashed the latest Nougat Factory image using the provided flash-all.bat
2. Booted up the ROM, set a PIN.
3. Rebooted into bootloader and then from your PC, ran ""fastboot --set-active=_a" (or is it b? you are unclear here).
4. Ran flash-all.bat again (though you say you think you could have just flashed the bootloader itself at this point since you've changed the active slot)
5. Then successfully booted to temporary TWRP via the RC1 Image and then actually flashed the RC2 zip once you were in TWRP

Some questions:
1. In 5 above, how did you get the RC2.zip onto the phone in order to flash it?
2. Have you flashed any ROMs successfully? If so, which one?
3. Have you rooted? If so, how?

I appreciate any and all guidance. I swapped my N6P for this phone and my regret is growing (despite knowing that the 6P was starting to fail). I had assumed a flourishing dev community around the Pixel, only to see that it's been a year and a proper TWRP (let alone a variety of ROMs) still doesn't seem to be available!

So trying to remember exactly what I did. Keep in mind I was running Android O, which means the bootloader was also updated to the Android O version.

1. Downloaded latest Android N image.
2. Booted phone into bootloader, noted that my current slot was slot b.
3. Did the flash-all.bat on with latest Android N version.
4. Let phone then completely boot and go through setup (albeit I didn't input anything, I was just making sure I had a bootable slot)
5. Went back to bootloader use the "adb reboot bootloader" command (had to enable in developer options)
6. Since I was still on slot b, I switched to slot a using "fastboot --set-active=a".
7. From there, I ran the flash-all.bat command again. My thinking here was that even though slot a had the Android N information, slot b is still on Android O. Given that we know that TWRP isn't working great yet with Android O, I thought I should change both of them.
8. Let the phone boot up again.
9. This time I set a pin lock since I was going to now flash TWRP. I also connected it to the internet so I could download what I needed to.
10. Downloaded the TWRP RC1.img file and but that in my fastboot folder on my computer.
11. On my phone downloaded the TWRP RC2.zip.
12. Went back to bootloader using adb reboot bootloader
13. ran fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img This temporary boot twrp. Since I had set a PIN, it asked for that, which seemed important because it was need to decrypt the data
14. In TWRP, flashed the TWRP RC2.zip.
15. Rebooted the phone and it stuck without issues.

As far as other ROMS I've used, I am using the PureNexus ROM on it. I don't have Root because I don't use it often. I did try to flash Magisk V14 and that failed, but I've not put any effort into figuring that out yet.

 

[Zwitterion]

So trying to remember exactly what I did. Keep in mind I was running Android O, which means the bootloader was also updated to the Android O version.

1. Downloaded latest Android N image.
2. Booted phone into bootloader, noted that my current slot was slot b.
3. Did the flash-all.bat on with latest Android N version.
4. Let phone then completely boot and go through setup (albeit I didn't input anything, I was just making sure I had a bootable slot)
5. Went back to bootloader use the "adb reboot bootloader" command (had to enable in developer options)
6. Since I was still on slot b, I switched to slot a using "fastboot --set-active=a".
7. From there, I ran the flash-all.bat command again. My thinking here was that even though slot a had the Android N information, slot b is still on Android O. Given that we know that TWRP isn't working great yet with Android O, I thought I should change both of them.
8. Let the phone boot up again.
9. This time I set a pin lock since I was going to now flash TWRP. I also connected it to the internet so I could download what I needed to.
10. Downloaded the TWRP RC1.img file and but that in my fastboot folder on my computer.
11. On my phone downloaded the TWRP RC2.zip.
12. Went back to bootloader using adb reboot bootloader
13. ran fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img This temporary boot twrp. Since I had set a PIN, it asked for that, which seemed important because it was need to decrypt the data
14. In TWRP, flashed the TWRP RC2.zip.
15. Rebooted the phone and it stuck without issues.

As far as other ROMS I've used, I am using the PureNexus ROM on it. I don't have Root because I don't use it often. I did try to flash Magisk V14 and that failed, but I've not put any effort into figuring that out yet.

This is superbly helpful - thank you so much for taking the time to go back through it! I am also on Oreo as it asked to update as soon as I booted the new phone and said what the heck. I will try this out and report back. It may be a day or two. I'll see if I can get root, which is most important for me as I want to run Franco Kernel to stop this horrible battery life!

 

[dbroer91884]

This is superbly helpful - thank you so much for taking the time to go back through it! I am also on Oreo as it asked to update as soon as I booted the new phone and said what the heck. I will try this out and report back. It may be a day or two. I'll see if I can get root, which is most important for me as I want to run Franco Kernel to stop this horrible battery life!

So did this help?