yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Haslo41:
Hi iv recently got my pixel 3 from being an lg g6 user.

Ive tried rooting it and it shows thats its rooted but when i install a module from magisk its successful but upon reboot the module doesnt show up. I have tried different modules none of then show up.

Googke pixel 3 nov build blue line.

Here is what iv done.

Unlocked bootloader

Transfered magisk Zip 17.3 to downloads folder

Reboot in bootloader

Temp boot to twrp

Installed magisk via twrp it automatically installed to slot b

Rebooted and it was stuck in bootloader

Then patch ed the orginal boot.img from the orginal firmware to boot phone

Phone boots up and root checker confirms phone is rooted
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] chowhoundb:
Thanks, Josh. I will give that a shot.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] georgs_town:
All the trouble you guys describe made me a bit hesitant, whether I should give it a shot and root my Pixel 3. I can finally get it from the store tomorrow, so getting really excited. And I want root in order to remap the squeeze-function.

So for everybody, who's not too experienced with rooting, this is a great video:

[YOUTUBE]https://www.youtube.com/watch?v=x1Lg04XAYlU[/YOUTUBE]

The guy does need a second attempt here and there, but seeing every step "live" is a big help for me and I'll give it a go first thing, when I get the phone...
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jerseymk2:
well, i'm in a bind. I unlocked no problem, I booted twrp no problem, I flashed magisk... now I have a problem lol phone was stuck in boot loop. I can get to recovery, and I can get to fastboot. The problem is that I can't get the phone to communicate in fastboot. I can communicate in recovery with adb commands, but fastboot commands i get left hanging with "waiting for any device" I downloaded the factory images and when I try to adb sideload, I am getting E:footer is wrong, E:signature verification failed, E:error 21.... any ideas?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] chowhoundb:
Are you issuing the fastboot commands with the phone in the bootloader, or recovery?

Also make sure you have the latest google adb drivers installed on your PC as well as the latest version of fastboot.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Slomies:
Unplug and replug your phone in when you're at the bootloader screen and then try fastboot commands. My phone does the same thing if I don't do that.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] geremye:
My Pixel 3 is stuck in Fastboot.

I haven't rooted a device in over a year, I got a Pixel 3 and then screwed up somewhere and I need help.

https://www.xda-developers.com/googl...r-root-magisk/ i was using these instructions.

I unlocked bootloader, booted into TWRP, installed Magisk and rebooted. Then I got stuck in the google screen for forever. It seems like I was really close, but after reading and troubleshooting a few things I fear I have made it worse.

I have tried to going thru it again, but now I am stuck in Fastboot. I can't get into the bootloader screen, if I restart bootloader it just stays in fastboot. Reason says reboot bootloader. I can boot into twrp again by using fastboot boot twrp-3.2.3-0-blueline.img, but then I just end up back at the fastboot screen.

I tried changing the slots, but then at fastboot page it says error booting boot.img.

After reading I was going to try flashing the factory image and start over, i downloaded and extracted it into my adb folder on my PC, but I can't get into the bootloader. Or unsure what to do next. Please help.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jsauder2:
If you're at the fastboot screen, you are in the bootloader. Just unpack the factory image you downloaded and get the stock boot.img. Then from fastboot, run the command "fastboot flash boot boot.img". That will flash the stock boot image and you should be back to normal and be able to boot into the system.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] geremye:
I didnt realized the extracted the factory image was in a subfolder. I moved them into platform tools and ran flash-all and it started to run.

now it says fastboot: error: device doesn't have required partition product! press any key to exit
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jsauder2:
Can you extract the second zip to get the boot.img and try the command I mentioned earlier to just flash the boot.img? If all you've done is try to flash twrp and magisk, you likely don't need to do anything other than that to get things working again.

If you really want to flash the entire image, you need to extract the downloaded zip to the folder where your fastboot and adb is and run the flash-all script. You don't need to extract the second zip, the script takes care of that for you.

Should probably move this to the "questions answers" forum since it's not really a twrp issue. Also, feel free to PM me if you need more help.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] sirebral123:
Has anyone completed a full restore successfully? I haven't had any luck with my attempts. May be my lack of knowledge on A/B phones, yet my restores won't boot.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] adhusky:
I was trying to install the magisk 17.3 and then reboot the system. then I am getting the Android Recovery as it says cannot load the android system. your data may be corrupt . try again or factory reset will keep coming back to that android recovery black screen. Somehow i use power + hold down to flash the twrp to wipe the cache and reset the factory. If I installed the twrp and then installed the magisk 17.3, I am getting the twrp loop.

Thanks in advance,

Adrian

Update:

I've got it working.. I had to do OTA after I downloaded the latest adb from 1.0.31 to 1.0.36 and then do the steps again and I installed both slots and was not able to reboot on slot a and then tried to rebtoot on slot b which is working. Thanks! :)
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Archangel:
Yeah I tried once and it failed like it was cool. I only use TWRP to flash Magisk.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] sirebral123:
I use them for peace of mind, just in case anything gets screwed up. I've used TWRP for years with several phones and restores always worked. I think we're in real need of an update where Nandroid backups and restores actually function.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Archangel:
I am sure they will fix it,,,I am just glad to have a semi-working recovery and dont have to go through the trouble of patching the boot.img for Magisk.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] AquilaDroid:
Anyone have an issue with the TWRP date and time? I wasn't able to set the time correctly in the settings and the backup shows the date and time as Mar 03, 1970 00 02 PM (should have been 1530 or 3:30Pm)
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] NYCHitman1:
Time is broken in TWRP.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] mrnovanova:
When I reboot after flashing TWRP or just from TWRP I boot back into TWRP. I keep having to flash boot to boot into my phone. Any idea why that is?

---------- Post added at 10:57 AM ---------- Previous post was at 10:40 AM ----------

Things just keep getting better and better...Restored back up and now it won't even boot. Nothing. Tried flashing boot from fastboot and now I get

FAILED (remote: Error calling AvbLoadAndVerifyBootImages Load Error)

finished. total time: 0.374s

WOW

Good times

Sigh

Edit: Was able to fix it.

Downloaded latest SDK. I think that was the issue
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] moldovanos:
I tried installing it two times and both times it ended up messed up. First it just got stuck on the Google logo, the second attempt (after flashing stock image) it said something about, that there is nothing to boot
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] NYCHitman1:
You messed up then. That's not the TWRP team's fault.

fastboot boot filename.img

flash the twrp installer zip when booted in.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] tulipyan:
Can someone help me?

After I unlocked the bootloader,

fastboot boot twrp.img and install Magisk 17.1.zip, but after reboot, I can't enter the system.

And can't boot in twrp.img,The screen can only display this screen. I don't know if anyone can help?

Best regards
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jemeljsh:
It seems to me you skipped one step (booting into system with unlocked bootloader). Did you boot into twrp right after you unlocked the device in fastboot without booting the system? Did you boot into the system after unlocking the bootloader (system/data wipe) to re-enable Developer Options/USB Debugging/OEM unlock?

From my understanding and how I have done it with various pixels is that you only apply magisk zip in temp. or permanent T WRP recovery only after you have booted the system after succesfull bootloader unlock and re-enabled the mentioned settings..
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] tulipyan:
I have rebooting into system to re-enable usb debugging, but the OEM unlock is locked and cannot be changed.

I think because I use the wrong version of magisk v17.1.

After using magisk v17.3 but still stuck in the start animation, a G has no next step.

I don't know how to deal with it.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jemeljsh:
Very odd, because I just did it. Got my Pixel 3 this morning. I initially was installing Magisk 17.1 and on first boot system got stuck on Google logo with the meter running from side to side same as you describe with 17.3.

Re-flashed stock image in fastboot and did all the steps again with Magisk 17.3 this time and it booted instantly.

Here’s how I did it after I was stuck with that Google logo:

1.	Re-flashed whole system image in fastboot through flash-all.bat;

2.	Booted into system enabled USB debugging and authorized the device (adb / adb devices / check mark in phone;

3.	Booted into fastboot -> adb reboot bootloader;

4.	From fastboot booted into temporally TWRP -> fastboot boot ___(name of TWRP image).img

5.	Installed TWRP zip file for TWRP to stay intact always;

6.	Installed 17.3 magisk zip and booted into system.

7.	Done.

Maybe you try also to all the steps from the very beginning with installing factory image for pixel 3/blueline (https://developers.google.com/android/images#blueline) on unlocked phone through fastboot..

p.s. not sure if it matters but I noticed that magisk 17.1 was flashing into boot B slot while 17.3 flashed in A ;)
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] tulipyan:
Thank you, after flash-all, I have completed the magisk after the steps!
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] sliding_billy:
Has anyone fully installed TWRP on the Pixel 3 (non-XL)? The touch screen was only broken on the XL in the 3.2.3-0/November OS and not the small 3. I rooted my wife's 3 last night but only used the TWRP fastboot boot .img for now and kept stock recovery. I can put the custom kernel on my 3 XL to get TWRP touch working, but if I don't need to (to get touch) on the regular 3 I won't.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] VerneVerne:
At least in my case, i did need to have a custom kernel to get recovery touch to work. I used flash-all to update, fastbooted the recovery image, flashed recovery zip and then rebooted to recovery. Touch did not work. I then fastbooted the recovery image, flashed the custom kernel and now touch works.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] sliding_billy:
I appreciate it. I had a feeling that whatever they did that broke it on the 3 XL probably happened on the 3 this time too. I guess it's custom kernels for all unless the TWRP team gets a new version out before I get home from work.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] rczrider:
I've got a brand new Pixel 3 that arrived today and of course I unlocked the bootloader first thing. Problem is that I'm stuck in a TWRP bootloop and the only way I can get out of it is to flash back to stock boot image AND system zip (but minus the "-w" flag, so it doesn't erase userdata). I'm not new to this whole thing, but it's been a few years. Still, I'm not sure what simple thing I'm missing here, and so any suggestions are appreciated. Here's what I've done:

1.) Unlock the bootloader

2.) Boot back into the system to enable USB Debugging and authorize my PC

3.) Used fastboot to boot into TWRP (made system writable)

4.) Flashed the TWRP zip

5.) Flashed the Magisk 17.3 Beta zip (pretty sure 17.1 doesn't work with the Pixel 3)

6.) Wiped cache/dalvik

7.) Rebooted into System via TWRP

At this point it looks like it's booting up, but it just goes back into TWRP where I have to put in my pattern to decrypt. Flashing the stock bootloader image via fastboot doesn't get me anywhere; it leaves me hanging at the white boot screen with "G" on it for a while, then reboots itself into TWRP. If I flash all of the stock boot and system (latest/December), I'm back to square one (it boots up, though).

What dumb thing am I missing? I'm fully updated (December security updates). I'm using Windows 10 and as a result, using PowerShell instead of the command prompt, but that shouldn't make any difference other than using ".\fastboot" instead of just "fastboot". Could it have something to do with the different Slots A/B (this is new to me)?

With the exception of unlocking the bootloader, installing TWRP, and flashing Magisk, I haven't done anything else. Thoughts?

EDIT: Of course after posting, I make some progress. I tried again but didn't install TWRP at all, just booted into it temporarily to install Magisk. That did the trick. Is the inability to permanently replace stock recovery with TWRP an obvious and known issue that I just totally missed?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Chezbel:
I have similar issues

- If I do not install Magisk I am able to install permanent TWRP and there is no problem

- If I use temp TWRP to install Magisk and do not install permanent TWRP there is no problem

- If I try to have both permanent TWRP and Magisk it just never boots.

- I tried Magisk 17.3 and canary version 17.4-ec472309-17317
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Rumsfield:
Anyone else not getting an accurate clock/time? Even with the correct timezone and daylight savings enabled I am seeing 12:43PM and its 5:48AM
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] AquilaDroid:
See posts 67 & 68. It's a known issue.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Rumsfield:
Gotcha, looks like time is broken in TWRP for us at the moment.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] robocuff:
Did you reboot recovery after installing the twrp.zip? You need to do that before you install Magisk. Also, you say flashing the stock boot image doesn't get you out of it. Unless I'm misunderstanding, you must be doing something wrong when you flash it because you say it boots back into TWRP after you flash the stock boot image. If you flashed it correctly, TWRP should be gone and if it happened to still bootloop after flashing the stock boot image it should boot into the stock recovery, not TWRP.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] ryanstfl:
Anyone have issues accessing the USB storage while connected to PC while in TWRP? It worked for my OG Pixel but not the 3
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] frewys:
Mtp does not work yet
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] ken_ac:
Pixel 3, December 2018 build, rooted

Thanks for all the tips. I encountered my share of bootloops and boot failures before I followed several of the tips given above. I list those I found especially important (mandatory!):

Lock the phone using a numerical or alphanumerical password.

Download the TWRP zip and the Magisk zip (see below for version number) to some directory under "sdcard" ("download" works well) on the phone.

Reboot to bootloader, then boot the TWRP image file.

Install the TWRP zip using the live booted TWRP program.

Reboot!

Install Magisk v17.4. To get this version I had to go to the Magisk "canary" builds (the build number I used is v17.4-08cd5b81). (It is possible v17.3 would work, but this one

did

work.)

Reboot. You should be rooted at this point. Look for Magisk in the app drawer.

Thank you one and all for the trials and tribulations leading up to successful rooting of this new and powerful smartphone.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Chezbel:
Thank you for mentioning step #1. In my previous attempts I did not set up a pin, my plan was to get TWRP and Magisk working and then set everything up. Just in case anyone else is wondering, I did the above steps without having my sim card installed (it's still in the old phone).
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] devsk:
I created a PIN for the phone unlock, backed up /data using TWRP, got replacement phone, booted up TWRP and can't restore my older Pixel /data backup. It does not prompt me for password during initial boot into TWRP. I think its trying to restore without the encryption password and failing.

The error is: extractTarFork() process ended with ERROR: 255

Any ideas on how I can restore my /data backup?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] sliding_billy:
Anyone know why the Pixel 3 did not get an update to 3.2.3-2 like the 3XL did? I have a 3XL, but my wife has he smaller 3. The 3 never needed updated to 3.2.3-1 since touch always worked (on both .img and .zip), but others have mentioned that touch is broken on the 3 now as of the December update (.zip version, but .img is still working fine). I am probably just going to keep using the .img and stock recovery on both, but I still wonder.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] NYCHitman1:
Different people working on the device(s).
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] sliding_billy:
Good point.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] devsk:
I did a factory reset and did the whole thing again. This time it asked for the password, it decrypted fine like last time. And it restored fine as well. I have no idea where the mess happened. But this error did give me jitters...:)
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Tulsadiver:
[MENTION=912474]Dees_Troy[/MENTION], aromas are not working for the Pixel 3 devices. Here is a question posed and answered on Aroma thread:

Quote:

Originally Posted by JEANRIVERA

let me explain a little bit deeper of what is exactly happening for my device HTC U12+, once I select the zip in TWRP the zip looks like it is going to start but the interface just freezes without even showing the usually aroma zips splash, then I noticed I could press the buttons and get feedback from them so it is not completely frozen I said then I started to press random combinations of buttons and the aroma installer finalized without issues, so the problem is I do not get any graphics from the aroma installer but it is actually running in the background, i'll attach some logs but I think they are useless no to much information in them. thanks for your time & reply

PD. I guess the same exact thing is happening in OP6 , I can't confirm because I do not own the device, but the similarities between HTC U12+ & OP6 are that both are SD845 and both are Official Treble A/B devices I look around for other Official Treble A/B devices with SD845 but I couldn't find any flashable zip that contains aroma installer on them to test

--------------------

The problem is that your device/TWRP is using DRM graphics (hardware accelerated) instead of framebuffer (traditional SW rendering). Aroma doesn't understand how to use your graphics "driver".

Unless you can get a build of TWRP (and kernel) with classic framebuffer rendering, it can't be fixed. Not sure how likely or even possible that is.

Is it possible do you think or even worth trying?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Dees_Troy:
Aroma hasn't been updated in years. We don't support Aroma either. If it works, great. If not, it's still not a TWRP problem; it's an Aroma problem. While it may be possible to compile a kernel with framebuffer graphics support, but TWRP will still use DRM graphics first which may still conflict with Aroma trying to use the framebuffer. Further, recovery shares the boot image kernel, so you would need to install a custom kernel with the framebuffer support and keep it installed to be able to try to use TWRP with Aroma.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Tulsadiver:
Thanks!

Just to clarify, I don't think it was meant as being a TWRP problem, but rather the hope for a fix would need to be a TWRP solution.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] mauronofrio:
Adb is working where you are in TWRP or not?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Chezbel:
Yes, adb is working for me when I'm booted to TWRP
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] mauronofrio:
Thanks for the answer

[MENTION=3507415]Chezbel[/MENTION] which twrp are you using? bluline 3.2.3-0 or crosshatch 3.2.3-2?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Chezbel:
blueline-3.2.3.0

I'm using the latest version of adb: 1.0.40

and the latest version of fastboot : 28.0.1-4986621
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] rczrider:
I agree that flashing boot over TWRP should leave in a good place, but the fact is that (for me) it does not. It's bizarre.

Doesn't matter, though; you were right in that I needed to install the TWRP zip and reboot. I wasn't doing that, I was just flashing the TWRP and Magisk zips in the same session.

Thanks!
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] slartibartfast42:
Yea, I tried that, doesn't work. I needed to factory reset. Do it separately.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Tayden21:
Anyone had any luck with the Verizon variant of the Pixel 3? Like how you even unlocked the bootloader?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Badger50:
You can't unlock the bootloader on the Verizon variant devices.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Debizzle:
Question guys if I did a "system-read only" back up a while back, will twrp restore with "system read only" ? Im trying to take the latest ota.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jd1639:
Why don't you just download the factory image and use the flash-all batch file with the -w removed? I haven't been very successful restoring the system image in twrp.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] AquilaDroid:
I had a problem a couple days ago when trying to restore a (TWRP) nandroid backup. I had to hold the volume down and power buttons down for over 30 seconds before I could get back into fastboot mode to re-install the January system image, etc.. After reading about the Pixel A&B slot architecture I never was able to determine that I'd done something wrong (like indicating which slot I wanted to restore to). Does anyone have more advice?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jd1639:
I haven't successfully restored a complete nandriod. If you try only backup and restore the boot, system image, and data. My work around is to flash a factory image or rom and then restore only the data partition from the nandriod.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Debizzle:
Sure I can do that. Will that allow me to take the OTAs at that point?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jd1639:
If you're are 100% stock, yes. But if you're rooted or have any other changes, kernels, etc, then no.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Debizzle:
Does this method allow u to get OTAs???