Database Info

Trying To Root Pixel 2

Ok I have the bootloader unlocked.
I was hoping then I could do the following
ADB Debugging on
adb reboot bootloader
fastboot boot twrp-3.1.1-1-fastboot-sailfish.img
But its not booting it. Pixel TWRP Image
So my question is can i modify the image to make the pixel 2 boot it?
Please advise?
Can I root without using TWRP?
Thanks,

bluh5d said:
Ok I have the bootloader unlocked.
I was hoping then I could do the following
ADB Debugging on
adb reboot bootloader
fastboot boot twrp-3.1.1-1-fastboot-sailfish.img
But its not booting it. Pixel TWRP Image
So my question is can i modify the image to make the pixel 2 boot it?
Please advise?
Can I root without using TWRP?
Thanks,
Click to expand...
Click to collapse
What makes you believe that TWRP for the original Pixel will work on the Pixel 2? Likely you'll have to wait for a recovery for the Pixel 2.

l7777 said:
What makes you believe that TWRP for the original Pixel will work on the Pixel 2? Likely you'll have to wait for a recovery for the Pixel 2.
Click to expand...
Click to collapse
Yeah I understand that. I was just hoping that since they are so similar it would work. Especially since I am not going to install it on my recovery just boot it to root and suhide.
I wanted to make sure I wasn't missing something or something I could change in the image to make it boot on a 2 .
Thanks though for your thoughts!

bluh5d said:
Yeah I understand that. I was just hoping that since they are so similar it would work. Especially since I am not going to install it on my recovery just boot it to root and suhide.
I wanted to make sure I wasn't missing something or something I could change in the image to make it boot on a 2 .
Thanks though for your thoughts!
Click to expand...
Click to collapse
The similarities are only on the surface my friend. When dealing with computers, similar and close is rarely good enough. You need exact.

bluh5d said:
Ok I have the bootloader unlocked.
I was hoping then I could do the following
ADB Debugging on
adb reboot bootloader
fastboot boot twrp-3.1.1-1-fastboot-sailfish.img
But its not booting it. Pixel TWRP Image
So my question is can i modify the image to make the pixel 2 boot it?
Please advise?
Can I root without using TWRP?
Thanks,
Click to expand...
Click to collapse
The MSM in them is totally different. Plus panel config, clock plan, power grid etc. Your original recovery kernel will not boot on Pixel2, so this is completely expected.

evilwombat said:
The MSM in them is totally different. Plus panel config, clock plan, power grid etc. Your original recovery kernel will not boot on Pixel2, so this is completely expected.
Click to expand...
Click to collapse
Can I root with latest supersu without recovery ?

Someone's bound to hose up their phone. Wondering where factory images are?

Born<ICs said:
Someone's bound to hose up their phone. Wondering where factory images are?
Click to expand...
Click to collapse
Yes. I agree. Might be me right. I wasn't planning on flashing recovery though just booting it.

If you are feeling adventurous (as it seems you already are!) you might try the twrp-3-1-pixel-bootable-mod.img located here: https://androidfilehost.com/?fid=745425885120753892 ? I used the instructions at https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-systemlessly-root-pixel-xl-t3660324 to root the 2016 Pixel (not xl) and if I upgrade to Pixel 2 might try that. You might just try fastbooting the twrp img referenced there and then flashing the supersu referenced there without the other modifications GroovinChip did. Again you are taking a risk trying this on "dissimilar" hardware.

If your bootloader is unlocked and you want root.
Try installing Chain fire's Supersu from the play store or install the apk.
I do not have my P2 yet to try.
Sent from my Nexus 5X using Tapatalk

me_droid said:
If you are feeling adventurous (as it seems you already are!) you might try the twrp-3-1-pixel-bootable-mod.img located here: https://androidfilehost.com/?fid=745425885120753892 ? I used the instructions at https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-systemlessly-root-pixel-xl-t3660324 to root the 2016 Pixel (not xl) and if I upgrade to Pixel 2 might try that. You might just try fastbooting the twrp img referenced there and then flashing the supersu referenced there without the other modifications GroovinChip did. Again you are taking a risk trying this on "dissimilar" hardware.
Click to expand...
Click to collapse
I think this may be a waste of time because it was modded to work on Oreo. They have already released a version that works on Oreo 3-1-1 that I already tried it wouldnt boot it. I will probably just wait even though i want to play. So i guess I can just say yep I have a pixel 2 with the bootloader unlocked and thats about it.

This can't come quickly enough - I always take my Ad Blocker for granted until it's not there anymore :'(

The_Fuzz22 said:
This can't come quickly enough - I always take my Ad Blocker for granted until it's not there anymore :'(
Click to expand...
Click to collapse
Yeah, I take having root completely for granted. I guess I've never bought a phone right at the moment of release before. If I didn't really need a new phone, I suppose I would have waited. Anyway, I figured out that you can block ads, without root, with apps that run all your traffic through a vpn (that's really only running locally on the phone). The best options after much research seem to me to be Netguard and AdGuard (though I haven't tried them yet). They both also include a firewall (Netguard is primarly a firewall), which I want.
https://github.com/M66B/NetGuard/blob/master/ADBLOCKING.md
https://adguard.com/en/adguard-android/overview.html
DNS66 also seems to be higly regarded, but it doesn't include a firewall. There are other firewall only apps, which work with the VPN method, but you can only run one VPN on Android at a time, so if you want both functions, without root, you need an app that does both.
https://forum.xda-developers.com/android/apps-games/app-dns66-source-host-ad-blocker-root-t3487497
Anyway, that's my plan until root comes along. Then I will go back to AdAway and AFWall+.

There is no kernel source released for the Pixel 2/XL yet. It is based on the 4.4 kernel, this should make development very smooth.

https://forum.xda-developers.com/pixel-2/development/psa-fastboot-booting-bad-image-confuse-t3692932

twrp for pixel 3a

The website below shows instructions on how to install twrp on the 3a. But when i go to the twrp website, they only have a recovery image for the xl. Are those recovery images interchangable?
MOD Edit:- Links Removed

Lol not even close. Don't try it. Or read ****ty articles like that, for that matter.

When the TWRP website has the builds up for the 3a (Sargo), that is when you download it and use it.

bigw34 said:
When the TWRP website has the builds up for the 3a (Sargo), that is when you download it and use it.
Click to expand...
Click to collapse
Or when I get it working lol. I've already booted TWRP on sargo but stuff won't mount. Close tho.

ZVNexus said:
Or when I get it working lol. I've already booted TWRP on sargo but stuff won't mount. Close tho.
Click to expand...
Click to collapse
Is it just /data that wont mount or everything?
I'm mulling rebuilding my env from scratch to simply build twrp without encryption support (low hanging fruit and all), if it's just due to the fact that /data is encrypted, I'd appreciate a copy as I'm only building twrp to be able to nandroid without encryption.

I know its too soon but I def miss having a custom recovery esp in cases when things do not flash correct and you have to undo them lol.

Trust me when TWRP is up for 3a you will definitely get a article on XDA/thread on 3a section. don't follow these spammy sites/blogs which does nothing but more of a click bait.

SacredDeviL666 said:
Trust me when TWRP is up for 3a you will definitely get a article on XDA/thread on 3a section. don't follow these spammy sites/blogs which does nothing but more of a click bait.
Click to expand...
Click to collapse
Sorry. I didn't really know. Thank you for the advice.

TheManii said:
Is it just /data that wont mount or everything?
I'm mulling rebuilding my env from scratch to simply build twrp without encryption support (low hanging fruit and all), if it's just due to the fact that /data is encrypted, I'd appreciate a copy as I'm only building twrp to be able to nandroid without encryption.
Click to expand...
Click to collapse
Literally everything besides the vendor image lol. At least that means I can load the kernel modules from touch as they are in the vendor image, but that's about it so for.
I decided to re base my trees and redo everything but this attempt doesn't even boot, or even get to the splash screen. Sad.

Heres hoping for some good news lol

Multirom?

For the sake of discussion, y'all ever see Tassadar's Multirom making a comeback ever? It was the absolute coolest thing ever!
That said, the new way Android works most likely killed this off entirely. A/B partitions that share userdata, and encryption that locks you out of your phone unless the security patch at least matches. Kinda hate the new way Android works to be honest.

If you remove encryption and AVB/Verity shouldnt it still work?

virtyx said:
If you remove encryption and AVB/Verity shouldnt it still work?
Click to expand...
Click to collapse
See now you got me thinking... Since Multirom mounts the userdata as system and then isolates the userdata for secondaries, it should right? Although people who have removed encryption on these newer devices have said you can't even have a screen lock or fingerprint at all with encryption gone, that's a big trade off. Hmm...

H4X0R46 said:
See now you got me thinking... Since Multirom mounts the userdata as system and then isolates the userdata for secondaries, it should right? Although people who have removed encryption on these newer devices have said you can't even have a screen lock or fingerprint at all with encryption gone, that's a big trade off. Hmm...
Click to expand...
Click to collapse
Hello, so what do you think is a good thing or a bad thing?
Personally, I'm a little afraid about that

H4X0R46 said:
See now you got me thinking... Since Multirom mounts the userdata as system and then isolates the userdata for secondaries, it should right? Although people who have removed encryption on these newer devices have said you can't even have a screen lock or fingerprint at all with encryption gone, that's a big trade off. Hmm...
Click to expand...
Click to collapse
On my pixel 3, removing encryption wouldn't let me use a pin or finger print to unlock, so no gpay.
On my 7 pro I tested out removing encryption and everything still worked perfectly, even removed Verity/ AVB too, fingerprint and pin worked fine.
I think the reason it didn't work on my pixel 3 is the Titan chip - but I'm unsure.

virtyx said:
On my pixel 3, removing encryption wouldn't let me use a pin or finger print to unlock, so no gpay.
On my 7 pro I tested out removing encryption and everything still worked perfectly, even removed Verity/ AVB too, fingerprint and pin worked fine.
I think the reason it didn't work on my pixel 3 is the Titan chip - but I'm unsure.
Click to expand...
Click to collapse
So you were able to keep your screen lock? That's neat! [emoji848] How do you remove encryption on these newer devices? I remember it used to just be a flag in the boot image, but has that changed?

H4X0R46 said:
So you were able to keep your screen lock? That's neat! [emoji848] How do you remove encryption on these newer devices? I remember it used to just be a flag in the boot image, but has that changed?
Click to expand...
Click to collapse
Firstly, you need to have twrp
Format data
Then
Make sure vendor is mounted
You need to pull the vendor/etc/fstab file to your PC
Rename "fileencryption" to "encryptable"
Then push it back to the vendor/etc location
I also make it a habit to do this before flashing magisk when unencrypted
Echo "KEEPVERITY" = false>>/data/.magisk
Echo "KEEPFORCEENCRYPT" =false>>/data/.magisk
Install magisk
And it's done.
To keep unencrypted between updates, you need to do the fstab move again in twrp and flash magisk again before first boot.
I suspect the pixels Titan chip prevents us from using a screen lock when decrypted
Which is silly, but I understand the security behind it.

virtyx said:
Firstly, you need to have twrp
Format data
Then
Make sure vendor is mounted
You need to pull the vendor/etc/fstab file to your PC
Rename "fileencryption" to "encryptable"
Then push it back to the vendor/etc location
I also make it a habit to do this before flashing magisk when unencrypted
Echo "KEEPVERITY" = false>>/data/.magisk
Echo "KEEPFORCEENCRYPT" =false>>/data/.magisk
Install magisk
And it's done.
To keep unencrypted between updates, you need to do the fstab move again in twrp and flash magisk again before first boot.
I suspect the pixels Titan chip prevents us from using a screen lock when decrypted
Which is silly, but I understand the security behind it.
Click to expand...
Click to collapse
Shoot I might just do this! I've always hated having to match the security patch when flashing a rom, or getting locked out of my phone, this might actually be better since Incan try roms and scrap em easily if I don't like em like I used to do in the older days of Android. Thanks so much! Gonna screenshot these steps and give it a go when I have time. Worst case, I restore a backup or use the MSM Tool, so no biggie! [emoji4]

H4X0R46 said:
Shoot I might just do this! I've always hated having to match the security patch when flashing a rom, or getting locked out of my phone, this might actually be better since Incan try roms and scrap em easily if I don't like em like I used to do in the older days of Android. Thanks so much! Gonna screenshot these steps and give it a go when I have time. Worst case, I restore a backup or use the MSM Tool, so no biggie! [emoji4]
Click to expand...
Click to collapse
No worries! Shoot me a PM if you have trouble
There is a noverity zip lying around somewhere but I prefer to do the steps manually gives me piece of mind.

virtyx said:
No worries! Shoot me a PM if you have trouble
There is a noverity zip lying around somewhere but I prefer to do the steps manually gives me piece of mind.
Click to expand...
Click to collapse
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
This is the zip you mentioned right? Since the change is made in the vendor partition, flashing a stock boot image wouldn't set it back to forced right? Or wrong?

H4X0R46 said:
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
This is the zip you mentioned right? Since the change is made in the vendor partition, flashing a stock boot image wouldn't set it back to forced right? Or wrong?
Click to expand...
Click to collapse
Right, but full rom zip will revert it back

Would this possibly mean multirom would be possible?

TWRP on the P4a?

I was wondering if anyone knew about the partition schemes and whether there is enough room on the boot image to install custom recovery on the P4a?
The Pixel 3A did not have enough room on the RAM disk on the boot image. So installing TWRP, even a stripped down version compressed, on the P3a was a no-go.
Custom recovery was not necessary on the P3a. Just having and unlocked bootloader and root via Magisk gives a lot of options including custom ROMs.
However, I'm still curious if custom recovery will ever come to the P4a?

12paq said:
I was wondering if anyone knew about the partition schemes and whether there is enough room on the boot image to install custom recovery on the P4a?
The Pixel 3A did not have enough room on the RAM disk on the boot image. So installing TWRP, even a stripped down version compressed, on the P3a was a no-go.
Custom recovery was not necessary on the P3a. Just having and unlocked bootloader and root via Magisk gives a lot of options including custom ROMs.
However, I'm still curious if custom recovery will ever come to the P4a?
Click to expand...
Click to collapse
LMAO. Give it up. We're going to be on 11. Good night

Golf c said:
LMAO. Give it up. We're going to be on 11. Good night
Click to expand...
Click to collapse
Not everyone will move to 11 right away if thet can get TWRP working on A10 first.

digger16309 said:
Not everyone will move to 11 right away if thet can get TWRP working on A10 first.
Click to expand...
Click to collapse
Good luck my friend. Stay on 10

We don't even have kernel source yet..

I don't think there was twrp for a pixel for a couple years was there? Pixel 2? And that didn't get past rc I don't think.

Golf c said:
LMAO. Give it up. We're going to be on 11. Good night
Click to expand...
Click to collapse
Thanks! As I said TWRP has not been needed and I was just curious.
However I did enjoy your insecure condescending attitude. It made me LMAO.
Again, thanks! ??

dmb219 said:
I don't think there was twrp for a pixel for a couple years was there? Pixel 2? And that didn't get past rc I don't think.
Click to expand...
Click to collapse
I know, it looks like TWRP has been doing a long slow death spiral.
We have TWRP on Android 10 for the Pixel C tablet. But of course among other things, there's no A/B partitions and Google abandoned support for the device a while ago.

Might be a while, pixel 3+ devices haven't had a 100% working TWRP for a long time.
They can still sideload ROMs and patch boot images with adb/fastboot
I'll miss this moving on from my 2xl. Nice to flash and update things without needing a PC

Golf c said:
Good luck my friend. Stay on 10
Click to expand...
Click to collapse
I will until there is EdXposed for 11 + module updates.

digger16309 said:
I will until there is EdXposed for 11 + module updates.
Click to expand...
Click to collapse
Yucky

Someone correct me if I am wrong but there are no factory images yet for the 4a so no rooting with Magisk until then?

Is it at least possible to unlock the bootloader right away? Is that just standard fastboot ADB procedure or is there something Pixel specific(first one)

dpaine88 said:
Is it at least possible to unlock the bootloader right away? Is that just standard fastboot ADB procedure or is there something Pixel specific(first one)
Click to expand...
Click to collapse
Just unlocked my Pixel4a using the standard ADB commands. Will say that OEM Unlocking stayed grayed out, until I connected to my WiFi (No SIM) and let the phone connect to the mother-ship.

Archangel said:
Someone correct me if I am wrong but there are no factory images yet for the 4a so no rooting with Magisk until then?
Click to expand...
Click to collapse
yea i believe you are correct, i think same steps for the pix4 can be applied on the 4a https://www.xda-developers.com/google-pixel-4-root-magisk/
im not sure if there are other ways to get the boot img but id rather just wait for the factory images to release & mess with it then. gonna make a cronjob script to watch / notify me once its up.

renzyyy said:
yea i believe you are correct, i think same steps for the pix4 can be applied on the 4a https://www.xda-developers.com/google-pixel-4-root-magisk/
im not sure if there are other ways to get the boot img but id rather just wait for the factory images to release & mess with it then. gonna make a cronjob script to watch / notify me once its up.
Click to expand...
Click to collapse
If I get around to it this weekend, I may just do a rom dump to extract the boot.img. Haven't done it in a while. I'm still waiting for some screen protectors to arrive before I mess with my phone.

Archangel said:
Someone correct me if I am wrong but there are no factory images yet for the 4a so no rooting with Magisk until then?
Click to expand...
Click to collapse
I can't find them either.

Isn't Android 11 going to make it more difficult to hide root anymore? I am tempted to root, but heard (or read) somewhere that with android 11 that it may not be worth it as any app (or something like that) will be able to see and not work.

This is the first phone I've owned that I think I'll be satisfied with stock. Ad guard does everything I need as ad away did. And it doesn't need root. Everything is fast! Now I don't have to hack Google pay.

edufur said:
This is the first phone I've owned that I think I'll be satisfied with stock. Ad guard does everything I need as ad away did. And it doesn't need root. Everything is fast! Now I don't have to hack Google pay.
Click to expand...
Click to collapse
Curious about adguard. I just tried it and won't install with chrome as browser.
Sent from my OnePlus 5T using XDA Labs

Twrp and magisk manager

What is the twrp for this rom. And how i can flash this twrp and install magisk manager.
Plz bro help me

There is no twrp for Android 11 right now.

JaymzTA said:
There is no twrp for Android 11 right now.
Click to expand...
Click to collapse
Is there twrp for android 11 at all for any device? If no, what is the main reason?

mzahs said:
Is there twrp for android 11 at all for any device? If no, what is the main reason?
Click to expand...
Click to collapse
Problem is decryption - it'a being worked on and there has been some limited success.

greyblue9 said:
Problem is decryption - it'a being worked on and there has been some limited success.
Click to expand...
Click to collapse
Does that mean more problems with future android versions?

mzahs said:
Does that mean more problems with future android versions?
Click to expand...
Click to collapse
I hate to say it, but I fear so. Also the change from physical partitions to dynamic--everything in "super" partition including system(/_a/_b) partition(s)--is another change that's makes the TeamWin guys' job harder. It means the Linux kernel can no longer even mount the filesystem, so it's a big adjustment. Wish I could put a positive spin on it. Makes one appreciate the options we *do* have more, at least!