[CLOSED]TWRP 3.3.1-1 for Pixel 3A XL [OFFICIAL]
- Thread starter ZVNexus
- Start date
- Status
Followed this exactly but still having problems. On the first reboot to system it proceeds to where I can begin setting up the system. At that time, I shut off the phone and rebooted into twrp, pushed magisk 19.3 to the phone and then flashed from twrp. By the way, I am using ElementalX-P3A-1.05 kernel. Are you on the same version or should I try another one?
Rebooted, the Google logo shows, up and stays on screen for quite some time whereafter the phone reboots into recovery.
I will now try to reflash the factory image PD3Q and repeat the above.
Hmm, tried flashing PQ3B from 190705 but could not install it since it complained about "invalid zip file format", the same for PD2A from 190115.
Did anyone else see this?
By the way, which version of Elemental kernel?
Lol. You don't flash factory images. You extract them and use the flash all script. Also look at Edwins updating monthly bits guide.
Ah, OK, did that and then installed Elemental 1.05 and the twrp installer. But, is your phone rooted wth Magisk 19.3? That is when I run into problems - which I did again and the phone rebooted into twrp recovery.
Perhaps there is some incompatibility between Elemental 1.05 and Magisk 19.3??
I
There isn't a compatibility issue. Are you pushing the same 19.3 file each time? Perhaps your download is corrupt.
Yes, all files have been checksummed after downloading with the exception of Magisk where I cannot find a checksum to match.
Maybe redownload magisk then and try again. I'm rooted with the latest stock update with twrp and ElementalX 1.05 kernel installed.
If you haven't redownloaded magisk after the first time it didn't boot I'd try downloading it again.
I did, no difference. I also tried installing Magisk 19.4 with no change, still bootlooping.
I can share that when I installed Magisk 19.2 it worked fine and I have root. Thus, there must be a bug in 19.3 and 19.4.
---------- Post added at 05:23 PM ---------- Previous post was at 05:18 PM ----------
Should one go back to the Settings and turn OEMunlock off after TWRP, appropriate kernel and Magisk root have been installed?
NO. Do not do that unless you go completely back to stock.
FWIW, magisk 19.3 works great for me.
Ok, thanks for the info on the OEM unlock. Not sure why 19.3 did not work for me...
Can anyone help? I am kinda stuck.
1) OEM Unlock enabled.
2) Wiped phone.
3) Booted TWRP using fastboot boot.
4) It boots up.
5) I try to flash TWRP .zip... and nothing. It just boots into normal system, cannot boot it no matter how hard I try.
What am I missing?
1) OEM Unlock enabled.
2) Wiped phone.
3) Booted TWRP using fastboot boot.
4) It boots up.
5) I try to flash TWRP .zip... and nothing. It just boots into normal system, cannot boot it no matter how hard I try.
What am I missing?
I did help, your solution is within the second paragraph... I literally put it within the first couple paragraphs so people would see it because it's extremely important. Unfortunately people don't seem to read.
"Note: You cannot install this on stock without a kernel with LZMA compression support."
Hey folks,
I am on a factory stock, I used 'fastboot boot path/to/twrp.img' to temporarily boot TWRP on my device and flash the patches I need. Each time I plan to flash anything new, I will do the temporary boot. LoL, it sounds silly but works fine. Hope you guys can enjoy it.
Again, all my thanks go to ZVNexus who did this voluntarily.
Thanks
---------- Post added at 09:17 PM ---------- Previous post was at 09:15 PM ----------
I am on a factory stock, I used 'fastboot boot path/to/twrp.img' to temporarily boot TWRP on my device and flash the patches I need. Each time I plan to flash anything new, I will do the temporary boot. LoL, it sounds silly but works fine. Hope you guys can enjoy it.
Again, all my thanks go to ZVNexus who did this voluntarily.
Thanks
---------- Post added at 09:17 PM ---------- Previous post was at 09:15 PM ----------
Last edited:
Correct. Can't decrypt Q so you basically can't do anything with it. Do the other root method for Q where you extract boot.img and patch it in Magisk, then flash it back to the phone.
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
32Team Win Recovery Project 3.x, or TWRP3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:[I]#include <std_disclaimer.h> /* * Your warranty is not void. * * We are not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this recovery * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at us for messing up your device, we will laugh at you. * */[/I]
Note: Please be aware that you cannot install this without a kernel with LZMA compression support, I believe most ROMs have included my commit for this so you should be good for all custom ROMs and kernels. If not please file a request to the maintainer.
In addition, please be aware that TWRP is currently not compatible with Android 10. If you would like to use TWRP you will need to go back to Android 9. If you would like more information you can read at the link here.
Not a huge problem, stock users can just temporarily boot TWRP if you have access to a PC.
Not compatible with Android Q.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. Use ADB or MTP to transfer the zip onto your device.
Go to install and browse to the zip and install the zip. The zip will install TWRP to both boot slots. Installing TWRP at this time will remove root if you are currently rooted.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
Changelog:
[BETA]
3.3.1-0: Initial release for Pixel 3A XL devices
3.3.1-1: Fixed having to manually change slots before rebooting.
3.3.1-2: Updated to July blobs!
3.3.1-3: Can now install TWRP to boot image. ADB, MTP, LOGD, Repack Tools and Logcat have all been removed to save the necessary space for this to work. You can grab stuff while in the OS, then flash it in TWRP (Keep in mind I have only tested this on stock as of now, feel free to test it on whatever ROM you use. It should work, but let me know if it doesn't).
3.3.1-4: Changed back to LZMA compression, also added back all the features besides ADB/Logcat. As long as your kernel supports LZMA you will be able to take advantage of installing it permanently without having to worry about space restrictions.
3.3.1-5:
Add persist entry to fstab
* To allow TWRP to store a backup settings file on /persist
and also to be used as QCOM time fix source during early boot.
Revert "Don't include logcat."
Revert "Don't include repack tools."
3.3.1-6:
Revert "Revert "Don't include repack tools.""
Add haptics firmware.
* This obviously on it's own isn't enough to get haptics working for the 3A in TWRP, but its a start.
Don't include a precompiled update_engine_sideload
* This should fix the issue of flashing officials for StatiXOS
[STABLE]
3.3.1-0: Initial official release!
Download:
https://twrp.me/google/googlepixel3axl.html
XDA:DevDB Information
TWRP, Tool/Utility for the Google Pixel 3a XL
Contributors
ZVNexus, janjan
Source Code: https://github.com/TeamWin/android_device_google_bonito
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-07-17
Current Beta Version: 3.3.1-6
Beta Release Date: 2019-06-27
Created 2019-06-27
Last Updated 2019-11-1593.3.1-3: Can now install TWRP to boot image. ADB, MTP, LOGD, Repack Tools and Logcat have all been removed to save the necessary space for this to work. You can grab stuff while in the OS, then flash it in TWRP (Keep in mind I have only tested this on stock as of now, feel free to test it on whatever ROM you use. It should work, but let me know if it doesn't).
3.3.1-4: Changed back to LZMA compression, also added back all the features besides ADB/Logcat. As long as your kernel supports LZMA you will be able to take advantage of installing it permanently without having to worry about space restrictions.
3.3.1-5:
Add persist entry to fstab
* To allow TWRP to store a backup settings file on /persist
and also to be used as QCOM time fix source during early boot.
Revert "Don't include logcat."
Revert "Don't include repack tools."8
