Try opening your command prompt directly on your platform-tools folder. The command is...fastboot boot twrp-xxxxxx.img :good:
* * * [Pixel 2 XL] - UPDATE Monthly Factory Image / UPGRADE To New OS * * *
- Thread starter Az Biker
- Start date
I'm not trying to be insulting here, but you are trying to install the twrp 3.2.2-0.ZIP file from within TWRP after fastbooting in using the twrp 3.2.2-0.IMG file, correct?
No, I'm trying to flash the TWRP img within the platform folder. I find I have to enter ./ first before the command but I just can not flash the img with fastboot command.
So your running a Mac, correct? What error message does it throw at you?
No, I'm running windows 10. It states something like bad command or command doesn't exist. I had no problems when I was using Win 7 but 10 is a new beast.
Cant we just do the flash-all.bat (remove the -w) then fastboot boot twrp, then install twrp then kernel then magisk? Why do we need to uninstall magisk? I'm still on 3.2.1-2, so can't i just install 3.2.2 over top?
Last edited:
I've attempted to follow this tutorial many times, including reflashing the factory image multiple times, flashing the magisk uninstaller multiple times, and attempting it on both slots. Every time I try it, my phone ends up stuck on the Google logo and progress bar until eventually rebooting into TWRP.
---------- Post added at 07:09 AM ---------- Previous post was at 06:42 AM ----------
---------- Post added at 07:09 AM ---------- Previous post was at 06:42 AM ----------
It turns out I'm just stupid. I was using TWRP 3.2.3. Once I used 3.2.2, it worked flawlessly.
A couple of updates
1) TWRP 3.2.3.0 has been released. I used this and was able to install zips from my local storage, just like in the good old days -- no need to use an external drive anymore.
2) The reason that there is confusion about the need to "Critical Unlock" on the Pixel 2 XL, and why some people do and some don't need to do it was CLEARLY explained on the Android Developer's page (https://developers.google.com/android/images). There it says:
1) TWRP 3.2.3.0 has been released. I used this and was able to install zips from my local storage, just like in the good old days -- no need to use an external drive anymore.
2) The reason that there is confusion about the need to "Critical Unlock" on the Pixel 2 XL, and why some people do and some don't need to do it was CLEARLY explained on the Android Developer's page (https://developers.google.com/android/images). There it says:
So - if you're already on a bootloader later than TMZ20a (like if you joined the 9.0 beta program) you don't need to do it...
[/COLOR]
Exact same thing for me. I couldn't figure out why this was occurring or how to fix it either. If anyone has an idea it would be appreciated. Thanks
Same for me. I had to reboot into system and disable screen lock.
For everyone who followed OP's instructions but was bootlooping into TWRP with Magisk installed. Redo the whole procedure without installing the TWRP zip file.
Tried countless times on my phone with TWRP installed and kept getting stuck at the "G" screen for a few minutes before looping back into TWRP recovery.
First try with a dirty flash without TWRP installed, just booting it through a PC and uninstalling magisk and installing 3.0 kernel and magisk again without even rebooting in between and I have Android 9 with root finally.
Tried countless times on my phone with TWRP installed and kept getting stuck at the "G" screen for a few minutes before looping back into TWRP recovery.
First try with a dirty flash without TWRP installed, just booting it through a PC and uninstalling magisk and installing 3.0 kernel and magisk again without even rebooting in between and I have Android 9 with root finally.
Last edited:
I second that - have done numerous monthly updates on Oreo and now this update to 9 Pie (full flash -w) without installing TWRP and have never had a glitch. I also have never flashed kernel.
Thank you for all the good info in this thread.
The module didn't work for me. It would activate after turning it on but then it would quickly shut off with an error message.
So I uninstalled the module, then I did the build.prop edit my root file explorer:
3 - Edit build.prop
adb shell
su
**(grant permission if phone asks)**
mount -o rw,remount /system
echo "net.tethering.noprovisioning=true" >> /system/build.prop
reboot
(that was in case you didn't know about it or how to do it.).
It's working now. No problems.
A couple questions/comments
1) Thanks for the guide, basically working flawlessly
2) TWRP 3.2.3.0 is now out. This guide talks about 3.2.2.0. Someone earlier in the thread mentioned that they had issues when using 3.2.3.0, and when they went back to 3.2.2.0, all worked fine. Someone else, however, mentioned that whey they used 3.2.3.0, it fixed some issues for them. What is recommended? 3.2.2.0 still, or now 3.2.3.0? (Note: I used 3.2.3.0)
2) I'm not using Flash Kernel whatsoever, so I just skipped steps 9 & 10 (after I flashed the magisk uninstaller, I rebooted into android system, let it settle, then installed magisk apk)
3) When I went back into recovery after installing the magisk APK (so I could flash the 1674 magisk zip), i had no touch responses working whatsoever. Eventually, the screen turned off of course. When i hit the power button to wake it up, i couldn't "unlock" it by swiping because, again, touch responses weren't working. I held down power until the phone rebooted, went back into the system, and then did an "adb reboot recovery" to try again. Upon going BACK into recovery, this time, touch was responding fine, and I was able to flash 1674. At first i was thinking I shouldn't use 3.2.3.0 and was going to try to re-flash 3.2.2.0, however now, all seems to be good and working, and I'm up and running.
TL;DR -- Can/should we use 3.2.3.0, and any idea why my touch responses stopped that one time?
On a side note (or, maybe, same note?) now in Magisk, after flashing 1674, Safetynet is giving me a "the response is invalid'.... so i may have done something wrong here?
1) Thanks for the guide, basically working flawlessly
2) TWRP 3.2.3.0 is now out. This guide talks about 3.2.2.0. Someone earlier in the thread mentioned that they had issues when using 3.2.3.0, and when they went back to 3.2.2.0, all worked fine. Someone else, however, mentioned that whey they used 3.2.3.0, it fixed some issues for them. What is recommended? 3.2.2.0 still, or now 3.2.3.0? (Note: I used 3.2.3.0)
2) I'm not using Flash Kernel whatsoever, so I just skipped steps 9 & 10 (after I flashed the magisk uninstaller, I rebooted into android system, let it settle, then installed magisk apk)
3) When I went back into recovery after installing the magisk APK (so I could flash the 1674 magisk zip), i had no touch responses working whatsoever. Eventually, the screen turned off of course. When i hit the power button to wake it up, i couldn't "unlock" it by swiping because, again, touch responses weren't working. I held down power until the phone rebooted, went back into the system, and then did an "adb reboot recovery" to try again. Upon going BACK into recovery, this time, touch was responding fine, and I was able to flash 1674. At first i was thinking I shouldn't use 3.2.3.0 and was going to try to re-flash 3.2.2.0, however now, all seems to be good and working, and I'm up and running.
TL;DR -- Can/should we use 3.2.3.0, and any idea why my touch responses stopped that one time?
On a side note (or, maybe, same note?) now in Magisk, after flashing 1674, Safetynet is giving me a "the response is invalid'.... so i may have done something wrong here?
I'm pretty sure if you flashed the latest kernel it would help with twrp not being responsive.
But my recommendation for the future to just update via a booted twrp or patched boot image through magisk. Flashing the twrp 3.2.2 or 3.2.3 zip has only caused me issues lately.
Thank you, I'm glad the guide worked for you.
I've not run 3.2.3-0 yet, but I'd say make a back up of what you have running now, try to upgrade to the new TWRP, and add a cust kernel as well, and see how it goes. If it's borked, restore wait until things are fixed.
I too have the "response is invalid" in Magisk 16.7 (1674) but I don't require Safety Net to pass since I don't use my device for that purpose.
Other than the above issue, 3.2.2-0 hasn't given me a single issue.
I took the Pie OTA update after flashing stock image after having a rooted Oreo version. Do I still need to use magisk uninstaller before trying to root Pie?
HI guys , just wondering if i installed the latest android pie factory image , does that mean i cannot revert back to the latest (july) oreo factory image if i wanted to ? or im i stuck on PIe 9.0 ?
hi guys, just curious..
what is the different just flashing unlock & flashing unlock_critical ?
so if i only flashing unlock i not able to flash custom rom and custom kernel ?
what is the different just flashing unlock & flashing unlock_critical ?
so if i only flashing unlock i not able to flash custom rom and custom kernel ?
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone