Develop Bugs

[GUIDE][ROOT][TWRP] Marshmallow(6.01) Sprint G920P root/TWRP using Magisk and Odin

I rooted my galaxy S6 a couple of days ago and wow was it totally worth tripping Knox, any way I am writing this because I could not find a thread that had a guide usng these methods. I had to figure out how to get past several errors in TWRP and Magisk and I thought some people might be curious how I did it. I did not make any of these programs used, credit to the original authors. I did this so I could play Pokemon Go with root.
WARNING: THIS WILL TRIP KNOX AND MAY BRICK YOUR PHONE. DO THIS AT YOUR OWN RISK I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS. MAKE SURE YOU HAVE A FULL BACKUP OF YOUR DEVICE BEFORE CONTINUING. THIS WILL ALSO DISABLE OTAS.
Prerequisites:
Odin (make sure its version 3.10.6 others may not work): https://androidmtk.com/download-odin-downloader-versions
Galaxy s6 (have not tested on edge)
TWRP in .tar format for your model: https://dl.twrp.me/zerofltespr/
Stock ROM in case you mess up
Windows PC
Magisk v11.1: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Magisk manager: https://play.google.com/store/apps/details?id=com.topjohnwu.magisk&hl=en
Installing TWRP:
1.) Download all the necessary files and extract Odin to your desk top.
2.) Go into developer mode on your phone and enable OEM unlocking and USB debugging.
3.) Turn off your phone and enter download mode by holding power button, home button and volume down until the screen comes up that says something along the lines of installing a custom OS is dangerous, push volume up to continue.
4.) Plug your phone into your computer and start Odin.exe.
5.) Make sure Odin says "added" in the text window.
6.) Click on AP and browse for the TWRP .tar that you downloaded in the beginning.. Check the box next to AP once TWRP is loaded, then click "Start".
A.) If TWRP fails to install go to "options" and un-check "auto reboot". If this is un-checked make sure to reboot into recovering when Odin says "reset" by first exiting download mode by repeating the steps used to get into it and then holding home, power button and volume up until the TWRP logo appears.
7.) Congratulations you have now installed TWRP!
Rooting and installing Magisk:
1.) This will not work unless you have followed my previous steps.
2.) Make sure your phone is in recovery mode by holding power button, home, and volume up until the TWRP logo appears.
3.) Make sure your PC recognizes the phone and copy the Magisk 11.1 .Zip you downloaded earlier.
4.) Tap install on TWRP and and browse for the Magisk 11.1 .Zip, swipe to install.
5.) When it is done installing tap reboot.
6.) When your phone is done rebooting install Magisk manager from the play store.
7.) When you open Magisk it should say rooted with MAGISKSU in the center box.
A.) If it does not say that flash Magisk 11.1 in TWRP again.
B.) If the above does not work re-flash to stock and repeat all steps again.
8.) You are now rooted.
A.) If you would like to use Magisk hide tap the first box where it says install Magisk and follow the onscreen instructions.
1.) You can try rebooting your phone when it asks you too, but it would not install this way for me.
B.) After you have installed Magisk Framework, go into to settings and enable the hide Magisk option.
C.) Go back to the status section and tap on safety net check, it should be a green check-mark
1.) If it is not green restart and install Magisk again, then go into settings and disable and re-enable Magisk hide.
2.) If it is not green after doing the above re-flash the stock ROM and start over.
9.) You will have to reinstall Magisk Framework every-time you reboot, your root should stay installed after a reboot though.

That is the wrong version of TWRP for a Sprint phone. The correct version is here: https://dl.twrp.me/zerofltespr/
There is a thread with links to the latest stock TAR files, correct version of TWRP for this phone and SuperSU here: https://forum.xda-developers.com/sp...uide-links-files-update-root-restore-t3366862

koop1955 said:
That is the wrong version of TWRP for a Sprint phone. The correct version is here: https://dl.twrp.me/zerofltespr/
There is a thread with links to the latest stock TAR files, correct version of TWRP for this phone and SuperSU here: https://forum.xda-developers.com/sp...uide-links-files-update-root-restore-t3366862
Click to expand...
Click to collapse
Thanks for pointing that out.

hmm, may I ask what advantages we get from this root method?
thank you.

You can hide your root and play Pokemon Go XD. I just think its more convientant having all my control apps super su and busy box in one place.
Sent from my SM-G920P using Tapatalk

Thank you for this.!!!!!!!!! 10/10

joej191 said:
Thank you for this.!!!!!!!!! 10/10
Click to expand...
Click to collapse
Your welcome. Glad I could help.
Sent from my SM-G920P using Tapatalk

Is magisk supposed to be installed after every reboot, or is that one of the many G920p specific issues?

I believe it is a GP20 specific issue because I have install mine after every reboot.

flett044 said:
I believe it is a GP20 specific issue because I have install mine after every reboot.
Click to expand...
Click to collapse
I just read this on the OP magisk thread: "magisk doesn't play well with Samsung devices. Try a custom kernel"
So i flashed the skyhigh kernel and now magisk is surviving restarts... the trouble is, Skyhigh auto intalls supersu and busybox.
Supersu isn't compatible with magisk, and i THINK that kind of busybox fails safetynet.
... so i used the busybox app to Uninstall busybox and the supersu app to do a full unroot and mount the stock boot image. (All to see if I could get magisk fully working) Then wipe davlik/cache, flashed the magisk.zip... booted up and opened the magisk manager, magisk was still installed, and magisksu was "properly installed"... but i fail safetynet attest now so i don't know what thats about.
Wondering if any of the veterans can chime in about any of this, since magisk indeed is pretty glitchy on the stock kernel.
Tl;dr: magisk doesn't work well with stock kernel, not sure how to get it working with custom kernel

I would also like to learn how to install magisk in sky high kernal.

Hey @tdhite do you have any input on this? I assume it would break synapse support to use magisk and magiskSu instead of supersu and the normal busybox, but worth it.
Quick recap: trying to run a magisk set-up with a custom kernel. Presumably using magiskSu.

still work?
@flett044,
Does this hidden root option still work with latest version of Pokemongo?
thanks

Yes it still works.

Nye-uhls said:
Hey @tdhite do you have any input on this? I assume it would break synapse support to use magisk and magiskSu instead of supersu and the normal busybox, but worth it.
Quick recap: trying to run a magisk set-up with a custom kernel. Presumably using magiskSu.
Click to expand...
Click to collapse
The boot routines currently use a policy tool specifically provided by SuperSu which is not available in Magisk. Access to files needed by various processes executed periodically (cortexbrain, cron jobs and others) may fail, but that would not be a critical failure, just a 'bummer' in the worst case. The startup routine is smart enough to check the policy tools and will cleanly boot even if SuperSu's tools aren't around.
Long story short, the kernel should work fine, you'll just miss out on certain things that try to run now and then to 'tune' the system.

How would I go about replacing supersu with Magisk?

tdhite said:
The boot routines currently use a policy tool specifically provided by SuperSu which is not available in Magisk. Access to files needed by various processes executed periodically (cortexbrain, cron jobs and others) may fail, but that would not be a critical failure, just a 'bummer' in the worst case. The startup routine is smart enough to check the policy tools and will cleanly boot even if SuperSu's tools aren't around.
Long story short, the kernel should work fine, you'll just miss out on certain things that try to run now and then to 'tune' the system.
Click to expand...
Click to collapse
That sounds like a pretty solid explanation for what happened when i tried running stock with skyhigh kernel and magisk.
Huge hit to battery life, and i still failed safetynet. Probably because the system showed i was using a custom kernel? I haven't been able to figure out a good way to mask that...
Anyways, good luck with implementing magisk like you said you would! I'm sure it won't be easy! You better have paypal links littered in the release post, you'll deserve it

What is the difference between Magisk and SuperSU?

JoeFCaputo113 said:
What is the difference between Magisk and SuperSU?
Click to expand...
Click to collapse
So I'm not super technical so i hope someone corrects me if i misrepresent this...
Magisk itself is basically a framework (think like xposed) except it functions from OUTSIDE of the system partition. Its only compatible with MagiskSU (a modified version of phh's superuser), magisksu is also not installed on the system partition...
Through magisk manager you can enable root, which as i understand, puts MagiskSU in the system partition in a sort of ghosted way, so its not really there? (As you can see I'm fuzzy on this part) And a step further, even with root still enabled, magisk can hide magisk and magiskSu's presence entirely from chosen apps (it automatically hides from play services so you pass safetynet)
So plain and simple, it theoretically works the same as supersu with the added benefit of being able to fully and effectively hide root...
There's still a lot of work to be done to reach it's full potential, especially in regards to compatibility with vendors and apps, but the dev believes magisk can do a lot eventually... including genuine multi-rom support.

https://www.xda-developers.com/magi...es-samsung-bugs-adds-core-only-mode-and-more/
Good news! Magisk update specifically for samsung devices! I can't wait to try this out!

[x Force] Installing Magisk Root & Universal Systemless Interface

Had issues installing the latest SuperSU, turns out an old version needs to be installed then updated
Found no mention of Magisk and the x Force so gave it a try. Works beautifully and just wanted to share
This is what I did for reference
Download:
Latest Magisk zip from here
Latest Clark TWRP from here
Have a clean boot, bootloader and system image see this guide here - Also follow this guide for obtaining adb/fastboot if you don't already have it
Copy the Magisk zip to your SDcard
reboot into fastboot either by holding the power button and volume down when booting or via adb
Code:
adb reboot fastboot
Temporarily boot into into TWRP
Code:
fastboot boot C:\twrp-3.0.2-0-clark.img
Select the install option, then navigate to the Magisk zip file. Swipe to install. Wait
Reboot
Install the Magisk app from the play store - official guide said there would be a stub app but i didn't encounter
Reboot again to get Super user access - Note: you can install modules like xposed at this point through the app.
Thankfully my banking app tap to pay works when used with Magisk Hide enabled on it so I am very pleased

JimyKK said:
Had issues installing the latest SuperSU, turns out an old version needs to be installed then updated
Found no mention of Magisk and the x Force so gave it a try. Works beautifully and just wanted to share
This is what I did for reference
Download:
Latest Magisk zip from here
Latest Clark TWRP from here
Have a clean boot, bootloader and system image see this guide here - Also follow this guide for obtaining adb/fastboot if you don't already have it
Copy the Magisk zip to your SDcard
reboot into fastboot either by holding the power button and volume down when booting or via adb
Temporarily boot into into TWRP
Select the install option, then navigate to the Magisk zip file. Swipe to install. Wait
Reboot
Install the Magisk app from the play store - official guide said there would be a stub app but i didn't encounter
Reboot again to get Super user access - Note: you can install modules like xposed at this point through the app.
Thankfully my banking app tap to pay works when used with Magisk Hide enabled on it so I am very pleased
Click to expand...
Click to collapse
Hi can I ask if using magisk to root will android pay then work because I have rooted in the normal way and root is detected on android pay app.

sam00561 said:
Hi can I ask if using magisk to root will android pay then work because I have rooted in the normal way and root is detected on android pay app.
Click to expand...
Click to collapse
Maybe™
My banking app uses google's inbuilt SafteyNet library to detect root and from my understanding that is also how android pay works as well. Magisk's hide function seams to bypass this detection even though on the main screen of Magisk management app the SafetyNet check fails.

For this procedure is necesary unlock the bootloader?

Cameronbrujah said:
For this procedure is necesary unlock the bootloader?
Click to expand...
Click to collapse
Absolutely it is !!!
You are rooting your phone.
BTW, I've been running Magisk on CrashXXLs ROMs since they first appeared last summer. There is a Magisk module available to allow the ROM to pass SafetyNET.

Yemble said:
Absolutely it is !!!
You are rooting your phone.
BTW, I've been running Magisk on CrashXXLs ROMs since they first appeared last summer. There is a Magisk module available to allow the ROM to pass SafetyNET.
Click to expand...
Click to collapse
Thanks a lot for your prompt response!!!
I'll do it.

Cameronbrujah said:
Thanks a lot for your prompt response!!!
I'll do it.
Click to expand...
Click to collapse
With the very latest CrashXXL ROM from a few days ago, Magisk 14.0 passes SafetyNET without the need for any additional modules, or at least it does on my EU xt1580 :good:
If you are coming from stock MM-6.01 on the X-Force, I can strongly recommend the CrashXXL 7.0 ROM as it is rock solid, works with TWRP and has auto-updating disabled (which is a good thing if you don't want to accidentally brick your rooted phone). Moto are not really supporting the X-Force, so there is absolutely no reason to stick with stock as there will be no official Oreo update.
Your other option is (unofficial) LineageOS, however, when I tried it a few weeks ago, I found it extremely unstable, particularly when running TomTom! Therefore, I cannot recommend LineageOS for the X-Force.

Yemble said:
With the very latest CrashXXL ROM from a few days ago, Magisk 14.0 passes SafetyNET without the need for any additional modules, or at least it does on my EU xt1580 :good:
If you are coming from stock MM-6.01 on the X-Force, I can strongly recommend the CrashXXL 7.0 ROM as it is rock solid, works with TWRP and has auto-updating disabled (which is a good thing if you don't want to accidentally brick your rooted phone). Moto are not really supporting the X-Force, so there is absolutely no reason to stick with stock as there will be no official Oreo update.
Your other option is (unofficial) LineageOS, however, when I tried it a few weeks ago, I found it extremely unstable, particularly when running TomTom! Therefore, I cannot recommend LineageOS for the X-Force.
Click to expand...
Click to collapse
actually I have Nougat 7.0 Official and only for the moment I will to root the phone. In a near future, of course I will change the ROM to the CrashXXL
Thanks a lot for all your help.
Regards from Mexico!

And how are we gonna unlock the bootloader?
Is there a way to do that?

Can't install SuperSU on Huawei Watch 1 "Patching sepolicy ---Failure, aborting"

Can't install SuperSU on Huawei Watch 1 "Patching sepolicy ---Failure, aborting"
I apologize if this is a noob question. I'm no stranger to modding Android devices; only new to modding Wear devices, and unfortunately information about rooting this watch is so sparse (understandably) and I couldn't find anyone with the same issue when searching. So like the title says, I can't get SuperSU installed on my Hwatch running AW 2.0. When I try to install SuperSU via TWRP, it gets stuck when trying to patch sepolicy.
Do I need a custom kernel for this? Is there one with no modifications other than the sepolicy? Or is there a way to change the sepolicy on the stock kernel. Between the guides I've read and WinDroid Toolkit, nothing has mentioned needing to do anything else to allow flashing SuperSU, but I can't think of what else would be the cause of the issue and I suppose things could have changed since those guides and Windroid were written.
I kind of want to avoid custom kernels as they almost always have issues in my experience with running them on phones (no offense to any kernel devs out there) and I can't deal with that on something simple as a watch. I just want this rooted mostly so I can test out underclocking and powersave governor when needing some extra battery time and so the next time I flash or upgrade my phone, I don't have to wipe the watch.
Any help will be greatly appreciated. And if I must install a custom kernel, I would love recommendations on the most reliable and/or closest to stock one.

For me, WinDroid Toolkit doesn't work for rooting Android Wear 2.0. I am on AW2.0 with the stock kernel and I have rooted the device using Magisk v13.2. Magisk Manager works on Android Wear (even though it may be hard to use on a round screen), but SuperSU (app) crashes when I launch the app. All you have to do to install Magisk is to flash the latest Magisk installer in TWRP and sideload the latest Magisk Manager using adb. You can download Magisk here. I have tried SuperSU, but I would get an every time I try to flash the latest SuperSU zip.

Tristan Phan said:
For me, WinDroid Toolkit doesn't work for rooting Android Wear 2.0. I am on AW2.0 with the stock kernel and I have rooted the device using Magisk v13.2. Magisk Manager works on Android Wear (even though it may be hard to use on a round screen), but SuperSU (app) crashes when I launch the app. All you have to do to install Magisk is to flash the latest Magisk installer in TWRP and sideload the latest Magisk Manager using adb. You can download Magisk here. I have tried SuperSU, but I would get an error every time I try to flash the latest SuperSU zip.
Click to expand...
Click to collapse
Thank you! Sounds like we encountered the same issue when flashing SuperSU. I had thought about trying Magisk, but wasn't sure if it would cause some issues on Wear. Thanks to your positive report, though, I'm going to try it out when I get home later. :good:

neonixxx said:
Thank you! Sounds like we encountered the same issue when flashing SuperSU. I had thought about trying Magisk, but wasn't sure if it would cause some issues on Wear. Thanks to your positive report, though, I'm going to try it out when I get home later. :good:
Click to expand...
Click to collapse
I'd like to know if it works for you. ?

Tristan Phan said:
I'd like to know if it works for you.
Click to expand...
Click to collapse
It worked! I was unable to sideload Magisk Manager, though, but that's fine. I'm just stuck on v5.0.5 which works just fine for handling root requests.

That's great! The only real difference between Magisk Manager v5.0.6 and v5.0.5 is that v5.0.6 fixes a crash when downloading modules from the repo, so you shouldn't be that affected. If you want any modules, you can just download them from XDA or something and flash it in TWRP.

Tristan Phan said:
That's great! The only real difference between Magisk Manager v5.0.6 and v5.0.5 is that v5.0.6 fixes a crash when downloading modules from the repo, so you shouldn't be that affected. If you want any modules, you can just download them from XDA or something and flash it in TWRP.
Click to expand...
Click to collapse
Yeah, that's why I'm not bothering with it. I don't feel a need for any modules on my watch at the moment Thanks again for tipping me off that Magisk would work.

neonixxx said:
Yeah, that's why I'm not bothering with it. I don't feel a need for any modules on my watch at the moment Thanks again for tipping me off that Magisk would work.
Click to expand...
Click to collapse
Just saying (sorry to bother), but Magisk v13.3 came out and fixed SafetyNet bypass. If you want, you can update by flashing Magisk-v13.3 by flashing it in TWRP without needing to uninstall the previous version. Installing this should also update Magisk Manager to v5.1.0.

Tristan Phan said:
Just saying (sorry to bother), but Magisk v13.3 came out and fixed SafetyNet bypass. If you want, you can update by flashing Magisk-v13.3 by flashing it in TWRP without needing to uninstall the previous version. Installing this should also update Magisk Manager to v5.1.0.
Click to expand...
Click to collapse
No worries, haha. Yeah I already updated on my phone. Thought about updating the watch, but too lazy at the moment :silly: since I don't really need to pass SafetyNet on my watch for anything. Probably will do it later on.

I'm thinking that the reason that you couldn't install Magisk Manager v5.0.6 was that it was already installed by the Magisk-v13.2 zip and ADB wasn't able to install over the existing APK, but I'm still a noob so I have no idea.

Tristan Phan said:
I'm thinking that the reason that you couldn't install Magisk Manager v5.0.6 was that it was already installed by the Magisk-v13.2 zip and ADB wasn't able to install over the existing APK, but I'm still a noob so I have no idea.
Click to expand...
Click to collapse
Check the adb install switches in adb help to solve that. Use the -r or -d switch.
Code:
adb install [-lrtsd] <file>
- push this package file to the device and install it
(-l: forward lock application)
(-r: replace existing application)
(-t: allow test packages)
(-s: install application on sdcard)
(-d: allow version code downgrade)

Switch to Magisk from supersu

Need your help guys. I am running beta 27 with super su V2. 82 SR 5....i heard now magisk is supported in beta 27...how to I unroot supersu, install magisk 14.5(1456) and still pass safety net... I tried searching for a solution everywhere but couldn't find a solution to this..... Please help... :crying:

uutsav said:
Need your help guys. I am running beta 27 with super su V2. 82 SR 5....i heard now magisk is supported in beta 27...how to I unroot supersu, install magisk 14.5(1456) and still pass safety net... I tried searching for a solution everywhere but couldn't find a solution to this..... Please help... :crying:
Click to expand...
Click to collapse
It's fairly simple. You will need unsu zip (from SuperSu official thread) and the Magisk zip downloaded where you can easily find it.
Boot to recovery
** create a Backup **
Flash unsu
(Assuming no errors) Flash Magisk
Again assuming no errors, reboot system
In your list of apps you should have a new"Magisk Manager" app and your "SuperSu" should be gone.
Thats it really. Took me a whole of 10 minutes, of which 7 minutes were backup [emoji6]

tropicanapure said:
It's fairly simple. You will need unsu zip (from SuperSu official thread) and the Magisk zip downloaded where you can easily find it.
Boot to recovery
** create a Backup **
Flash unsu
(Assuming no errors) Flash Magisk
Again assuming no errors, reboot system
In your list of apps you should have a new"Magisk Manager" app and your "SuperSu" should be gone.
Thats it really. Took me a whole of 10 minutes, of which 7 minutes were backup [emoji6]
Click to expand...
Click to collapse
And you passed safety net

uutsav said:
And you passed safety net
Click to expand...
Click to collapse
Yes! That was my main motivation for switching. That and SuperSu no longer being run by chainfire Trust me Magisk does a far better job than Super Su.
Also worth looking at this URL
https://android.gadgethacks.com/how-to/magisk-101-switch-from-supersu-magisk-pass-safetynet-0177578/
Forgot to mention you will need to uninstall xposed (can be reinstalled after). I don't use xposed.

tropicanapure said:
Yes! That was my main motivation for switching. That and SuperSu no longer being run by chainfire Trust me Magisk does a far better job than Super Su.
Also worth looking at this URL
https://android.gadgethacks.com/how-to/magisk-101-switch-from-supersu-magisk-pass-safetynet-0177578/
Forgot to mention you will need to uninstall xposed (can be reinstalled after). I don't use xposed.
Click to expand...
Click to collapse
I tried flashing unsu and it asked me to flash the stock boot image in TWRP.... Any ideas mate..
I am sorry to keep bugging.... But I am lost

Look for boot.img in the ROM zip and flash it.

I was just about to say that myself. See
https://forum.xda-developers.com/showpost.php?p=63615067
Like the previous post said, you need a pristine boot.img and your ROM zip is the ideal place to find it.

Dirty flash your Beta27 again and it should be clean, THEN reboot and then install Magisk

Now i flashed beta 28, flashed recovery and flashed magisk again... While I was able to flash it... But getting safety net error....
My life is finished...

If you were able to install magisk then you should take this to the official magisk support thread. You are more like to get a better variety of suggestions there.
Just saying.

[CLOSED] TWRP 3.3.1-1 for Pixel 3A [OFFICIAL]

Team 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]
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.
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 (Not Android 10), if not please file a request to the maintainer.
To follow up, 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.
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 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/googlepixel3a.html
XDA:DevDB Information
TWRP, Tool/Utility for the Google Pixel 3a
Contributors
ZVNexus, janjan
Source Code: https://github.com/TeamWin/android_device_google_bonito
Version Information
Status: Beta
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-15

Reserved

Incredible job thank you!

Thank you for all your guys hard work. I can't imagine the work involved

Congratulations and thank you for your time and effort.

This is awesome brother,,,if it werent for you we would not have a custom recovery! Thank you!

Thanks mate

Thank you!!!!!!!!
Shoud we allow Modifications or Keep Read Only when we boot for the first time?

WOOHOO!!! Thank you for this, it's so exciting!!!
Quick question: the instructions say there is also a zip to download but I didn't see it in anywhere. Do we really need it? TWRP did boot up temporarily just fine!

zombioptic said:
WOOHOO!!! Thank you for this, it's so exciting!!!
Quick question: the instructions say there is also a zip to download but I didn't see it in anywhere. Do we really need it? TWRP did boot up temporarily just fine!
Click to expand...
Click to collapse
Read the note

Fentadroid said:
Read the note
Click to expand...
Click to collapse
Ah yes... My bad!

Thank you for TWRP mate
Sent from my Pixel 3a using Tapatalk

Great job, now all we need is some proper rooting/with magisk, and everything will be golden!

jayyskittles said:
Great job, now all we need is some proper rooting/with magisk, and everything will be golden!
Click to expand...
Click to collapse
Magisk pushed a cannery build that roots for the Pixel 3s on Q4 last night.
Also, the Magisk dev has a Pixel 3 on Q4 (not 3a) that is his daily driver. So because of the similar file systems, it's good news for us on P3a.
Edit:
https://twitter.com/topjohnwu/status/1144159892430659584?s=09

12paq said:
Magisk pushed a cannery build that roots for the Pixel 3s on Q4 last night.
Also, the Magisk dev has a Pixel 3 on Q4 (not 3a) that is his daily driver. So because of the similar file systems, it's good news for us on P3a.
Edit:
https://twitter.com/topjohnwu/status/1144159892430659584?s=09
Click to expand...
Click to collapse
Does that canary build work for us?

jayyskittles said:
Does that canary build work for us?
Click to expand...
Click to collapse
Only if we get a Q compatible twrp. Or if someone can provide the Q beta 4 boot.img

jayyskittles said:
Does that canary build work for us?
Click to expand...
Click to collapse
For root It should even without TWRP. Pull the boot.img from the beta, modify it with Magisk Manager then Fastboot flash the modified boot image.
I have not tried it yet. I am still trying to spell canary correctly. :laugh:

Not sure how many of you have tested this thing out, but I can confirm it works on the stock rom. I had to root for a Titanium Backup, so I flashed Magisk through TWRP and rebooted just fine.

Finnaly!! Good work to OP who worked hard to get us this TWRP!

12paq said:
For root It should even without TWRP. Pull the boot.img from the beta, modify it with Magisk Manager then Fastboot flash the modified boot image.
I have not tried it yet. I am still trying to spell canary correctly. :laugh:
Click to expand...
Click to collapse
I wanted to try it tomorrow, but it seems ill better wait for a new update on the canary build:
https://github.com/topjohnwu/magisk_files/blob/master/canary_builds/notes.md
-> see the notes for the latest build. Afaik we need logical partition support or root will not work (correctly)
I'm also thinking if i can just pull boot.img via twrp backup (then extract if needed) or should i pull it via fastboot.
Really the userdata wipe holds me back (when OEM unlocking the device.)
Guess i will wait when root is successfully reported on P3 by topjohnwu, just to be sure.