yashsingh1/xdaforums huggingface dataset:
[Google Pixel Themes, Apps, and Mods] Tulsadiver:
Everything is done through TWRP. This is not a module though after flashing the Magisk zip it will show up in magisk manager as a module so you can disable it like a module.

There is a base that has clock on the right, 4 column QS, one that is the same but wifi-data has up-down arrows, one that is stock like with left hand clock and 3 column QS, one that is the same but has up-down arrows.
[Google Pixel Themes, Apps, and Mods] Arju:
It works now. Thank you! :)
[Google Pixel Themes, Apps, and Mods] LoeWn:
Maybe a stupid question, but what about gapps? included? or need openGapps 8.1?
[Google Pixel Themes, Apps, and Mods] Arju:
this is not a rom. this is a mod that you flash on top of Android P dp2 and it will give you the option to add those features mentioned in the first post. so make sure you're on android P dp2 before you flash this.
[Google Pixel Themes, Apps, and Mods] Tulsadiver:
DP3 is up. Magisk version will come later.
[Google Pixel Themes, Apps, and Mods] Myo Thu Htet:
This is for stock rom. So , dun need gapps
[Google Pixel Themes, Apps, and Mods] Tulsadiver:
I'm unable to download the system image of for because I'm at the lake but if someone can upload the systemUIGoogle.apk and framework-res.apk I can get started on it.
[Google Pixel Themes, Apps, and Mods] Kanuk:
Will this work on p Aug release?
[Google Pixel Themes, Apps, and Mods] Tulsadiver:
The other Pixels have but I haven't tested this one.
[Google Pixel Themes, Apps, and Mods] Kanuk:
Works great,thanks
[Google Pixel Themes, Apps, and Mods] Tulsadiver:
Uploaded new Aroma's
[Google Pixel Themes, Apps, and Mods] selw0nk:
How would I go about flashing this? Do I start by flashing the aroma installer, then the included Magisk? Does that mean I can't use the latest Magisk?
[Google Pixel Themes, Apps, and Mods] nolawardana:
changelog ???
[Google Pixel Themes, Apps, and Mods] Tulsadiver:
Bug fixes
[Google Pixel Themes, Apps, and Mods] Tulsadiver:
If you are using Magisk manager and modules, use the Magisk version. After the aroma installer is done and while still in TWRP, find the magisk.zip file in the Magisk folder on your internal sdcard and flash that.
[Google Pixel Themes, Apps, and Mods] post-mortem:
The 8/23 version didn't work for me. It would show the wallpaper, then reboot into recovery. I had to uninstall then reinstall Magisk, then use your 8/16 version.
[Google Pixel Themes, Apps, and Mods] Tulsadiver:
Working on mine. Which aroma did you flash and what in the aroma did you flash?
[Google Pixel Themes, Apps, and Mods] post-mortem:
I flashed the Magisk version. I think I used the like-stock framework & stock UI, then I added clock right, throughput center, and power button mod. I didn't change any colors.
[Google Pixel Themes, Apps, and Mods] Tulsadiver:
I flashed those and it installed just fine. That being said, the updater script has an error and it flashed framework base for gray qs WiFi data icons also.

Do you have any other modules installed?

I uploaded a new one though it won't fix your problem.
[Google Pixel Themes, Apps, and Mods] post-mortem:
I have 2 Magisk modules installed: Yours and YouTube Vanced black themed, from the repo.
[Google Pixel Themes, Apps, and Mods] Tulsadiver:
Mine isn't actually a module though it shows up as one after flashing. I don't know why you are having problems. It is flashing fine on mine.

You are flashing in TWRP, right?
[Google Pixel Themes, Apps, and Mods] post-mortem:
Yes, flashing in TWRP.
[Google Pixel Themes, Apps, and Mods] selw0nk:
WIll this include security updates in the future?
[Google Pixel Themes, Apps, and Mods] Tulsadiver:
It has gone all the way from dp2 to pie so I would say yes, at least as needed. Does it work for you? Have you flashed it?
[Google Pixel Themes, Apps, and Mods] selw0nk:
I have not flashed it yet. I will have to backup some stuff first.
[Google Pixel Themes, Apps, and Mods] post-mortem:
So the 8/24 Magisk version did work for me, but to make sure it would on my first attempt, I went through the following drawn-out process:

Remove security settings

Reboot to TWRP

Uninstall Magisk

Reboot to TWRP

Install Magisk

Reboot to TWRP

Install Tusladiver mod Aroma package

Flash /magisk/magisk.zip

Reboot system

Enable security settings
[Google Pixel Themes, Apps, and Mods] post-mortem:
I upgraded Magisk to v17.1 from within the Magisk manager app today. I didn't even have to reinstall your mod; everything stuck.

:good:
[Google Pixel Themes, Apps, and Mods] -Happy Feet-:
How can I install this mod. I have try it but nothing changed after reboot ?
[Google Pixel Themes, Apps, and Mods] Tulsadiver:
Are you using magisk manager? Do you have any other modules installed? If not, use the regular Aroma.
[Google Pixel Themes, Apps, and Mods] -Happy Feet-:
Yes
[Google Pixel Themes, Apps, and Mods] post-mortem:
If by "yes" you mean that you're using Magisk, then the Magisk version of the Tusladiver mod doesn't actually make any changes. It modifies the Magisk image and puts it into /magisk/magisk.zip. You have to flash that file in TWRP to enable the changes you selected in the Aroma installer.
[Google Pixel Themes, Apps, and Mods] kpmohamedhussain:
Can this be installed on any device running pie??
[Google Pixel Themes, Apps, and Mods] post-mortem:
Each version of the Tulsadiver mod is device-specific.

On which device are you looking to install this?
[Google Pixel Themes, Apps, and Mods] Tulsadiver:
Appreciate the help.

Uploaded new Aroma's including one for modding Pixel Launcher.
[Google Pixel Themes, Apps, and Mods] orpamoc:
has anyone gotten error magisk is not installed/magisk is required for this mod! when flashing the magisk.zip file it creates? I most certainly have magisk installed but cannot get passed this error. Am I missing a step? thanks in advance.
[Google Pixel Themes, Apps, and Mods] Tulsadiver:
Are you flashing in TWRP? Are you on magisk 16.3 or later?
[Google Pixel Themes, Apps, and Mods] orpamoc:
Hey thanks for the response.

Yes I'm fastbooting into twrp 3.2.3 then flashing the mod which then creates the zip file to flash thereafter. Running magisk v17.1 and everything has been running great except for the error I receive when flashing the zip created by the mod. I do not have twrp permanently installed if that matters. Running the stock PPR2 factory image. Thanks for any help in getting this working for me. Had the last few mods you made installed in the past and I absolutely love it.
[Google Pixel Themes, Apps, and Mods] Tulsadiver:
Try this one.

https://mega.nz/#!gdRnmKAS!JWNvAk0TU0TMen8GTCn8zHyOttsgqGGPfhXSPff2VSs
[Google Pixel Themes, Apps, and Mods] orpamoc:
Perfect will try this after work and will let you know if any issues much appreciated [emoji1666]
[Google Pixel Themes, Apps, and Mods] orpamoc:
Able to confirm this now works for me on PPR2. Thanks Tulsadiver much appreciated.
[Google Pixel Themes, Apps, and Mods] post-mortem:
I installed the October 5 security update today, and the magisk.zip file previously created with your Aroma mod works just fine.

:good:
[Google Pixel Themes, Apps, and Mods] kerryh420:
Apologies if this is the wrong thread to ask this but I am trying to flash Android P so that I can flash these mod's but when I'm doing the flash-all command with the factory image the flashing goes fine until it hit a stump and errors out with a: "slotb can't find/doesn't exist" or something very similar. I don't see anyway to switch to a slot b, though I have heard of it I've dealt with it before....Does anyone know what my issue is and/or how to fix it, please? Any help would be appreciated!
[Google Pixel Themes, Apps, and Mods] post-mortem:
Try installing the newest stock ROM here. If you want to save your user data, edit the flash-all script to remove the "-w" switch, prior to executing the script.

If that doesn't fix it, you'll get better help (and more visibility) if you start a new thread to ask for help with your specific issue.
[Google Pixel Themes, Apps, and Mods] Tulsadiver:
Try using deuces flash bat. It is really for pixel 2 and Pixel 2 XL but I use it on my pixel. You have to unzip the factory image zip and also put your bootloader and radio images in along with everything else.

Here is my version tweaked for Pixel. Use at your own risk but I use it. Unzip the bat file, put it in with all the other files and run it.

https://xdaforums.com/pixel-2-xl/development/tool-deuces-bootloop-recovery-flashing-t3704761
[Google Pixel Themes, Apps, and Mods] kerryh420:
DL the zip file. Unzipped it. Copied the .bat file and moved it up a level to where all of the rest of the unzipped factory image files were at along with the req'd fastboot/adb files for flashing. Performed flash-all and got same error as before, no surprise. Flashed the deuces flash-all bat file, it flashed and flashed and while it appeared to work when I rebooted to system the setup screen appeared so I did the required set up and assigning a pin etc and when I went to about phone I am still on 8.1. Disheartened I booted back to recovery to restore my nandroid backup and low and behold it displays a bunch of gibberish file names. Pressing the restore key in TWRP does not take me to the backup folder. When I use file manager to look for the backup there is no longer a TWRP folder under sdcard or storage where it should be.

It deuces file appeared to work but the only thing it did was erase all data - even though I told it no when asked during flashing - and delete my nandroids...Never had this happen before. I did however notice that while in TWRP I did see the option to boot to A or B which bootb was not able to be found causing the original flash-all fail to begin with. Beyond confused now. What exactly was the deuces flash supposed to do anyways?
[Google Pixel Themes, Apps, and Mods] Tulsadiver:
Flash everything to both A and B partitions.

I've seen those gibberish files before. TWRP wasn't able to decript your files.

Maybe your download of your system images is bad. Are you flashing the OTA or full factory images from here? It says bullhead but all pixel images are here also.

Did you install TWRP or boot to TWRP?

You could try a factory reset in TWRP after flashing your factory images again. It doesn't wipe data but you have to set your phone up again.

To select boot b partition in fastboot

fastboot --set-active=b

Run flash-all from b, then select a partition and run flash-all again.

https://developers.google.com/android/images#bullhead
[Google Pixel Themes, Apps, and Mods] kerryh420:
Edit to my previous reply to you - when I connect pixel to pc using explorer I can see the TWRP files and all the other files, including my nandroid, just like I am supposed to. Talk about really confused now.

Alright I'll try your most recent suggestion. You know sometimes when you have than "feeling"...? Well it does seem like this is very close so it's just a mater of figuring out what it is I'm not doing properly or in the right sequence...I'm close, and I thank you for your help and patience...much oblige!
[Google Pixel Themes, Apps, and Mods] Tulsadiver:
No problem. I did edit my post and added a couple of things.

Edit:. Here is a better flash-all bat than the one I tweaked earlier. This one uses the native update cmd but automatically runs it on both A/B partitions leaving it on A when finished. No need to unzip the image zip ( in fact, if you have already, you should delete that folder before running this). Just extract the bat file from this zip and put it where the native flash-all.bat is and run it.
[Google Pixel Themes, Apps, and Mods] post-mortem:
As Tulsadiver said, it looks like TWRP was unable to decrypt your device. Make sure you are using the latest version of TWRP!
[Google Pixel Themes, Apps, and Mods] Tulsadiver:
Uploaded new Aromas, a couple of fix's and some new backgrounds.
[Google Pixel Themes, Apps, and Mods] kerryh420:
Sorry for the long absence, thanks for the reply, I didn't try your zip file I first wanted to get the latest TWRP on there. That is not flashing for some reason. Getting "recovery partition doesn't exist" error. When I try to switch over to A slot when I enter "fastboot --set-active=b" I get "could not get suffixes" error. I've tried flash both the img and the zip and neither worked. I just can't get twrp to flash the updated version. Thanks anyways for the help.
[Google Pixel Themes, Apps, and Mods] Tulsadiver:
Pixels don't have a recovery partition. You cannot install it like other phones. You need to install system images again. Reboot. After that place the TWRP image on your PC, the TWRP zip on your phone.

Boot to fastboot then do this.

fastboot boot twrp-3.2.2-1-sailfish.img

(or whatever the image is named.)

Once booted to TWRP, flash the TWRP zip, this will install TWRP. Right after flashing TWRP zip, flash magisk 17.1 zip and reboot.

You should have TWRP and be rooted.
[Google Pixel Themes, Apps, and Mods] kerryh420:
1) Run which one? flash-all.bat or tulsadiver-flash-all.bat?

2) and delete which folder?

3) No need to unzip what image zip?

Sorry for not understanding there are too many zip's, img's and files in general to keep it all straight. I know it makes sense to you guys, you are the ones who know what you are doing.

---------- Post added at 12:45 AM ---------- Previous post was at 12:29 AM ----------

I got the updated twrp to flash and am now on twrp 3.2.3-1.

tried flashing the october 9.0 factory image in fastboot, got same error msg after what I thought was going to be a successful flash: "boot slotb doesn't exist".

tried flashing tulsadiver-flash-all-v1.bat and got same result as duece flash-all and factory image flash-all "no suffixes found". Why? I have update twrp. I have done everything that's been suggested. fastboot --set-active=b returns no suffixes found. I've made absolutely no progress at all. **** I hate being stupid
[Google Pixel Themes, Apps, and Mods] Tulsadiver:
Your folder should look like the enclosed picture. Run the tulsadiver bat file. Follow instructions. Don't format data, (last option when flashing is done), just reboot. You might have to format data at some point if this doesn't work.
[Google Pixel Themes, Apps, and Mods] kerryh420:
I've been flashing ROM's for over five years and had my share of bad flashes and quite a number of soft bricks but it looks like I have finally done it! My phone is now hard bricked. Having lost patience with trying to flash the factory image and your flash all script (I'm not blaming you at all, just pointing out how spectacularly f^^^ing God damn stupid I am) I went and successfully flashed pixeldust ROM (with pie update) I booted into system and it sat on the google welcome screen for a long long time. Figuring it was a bad flash after all I rebooted to recovery and proceeded to restore my only nandroid, because the 32GB model can only store one nandroid due to file size. Restored that successfully, or at least according to TWRP, but then I booted into system and here I am right back at the google welcome screen. It is not even trying to boot. No splash screen or anything. Thanks for your help. Sorry I have wasted so much of your time.

---------- Post added at 03:05 AM ---------- Previous post was at 02:53 AM ----------

When you have unzipped the factory image and are left with the bootloader and radio .img and the image-sailfish-ppr2.1810005.003.zip (and of course the flash-all.bat, flash-all.sh, and flash-base.sh), do you have to further unzip the image-sailfish.ppr2....zip? I unzipped that and there is like 20 .img files in there including the system, boot, ,etc... do those need to be brought up to be with the flash-all.bat and other files? (when I was flashing I saw that the flash was looking for them and they were "missing". Is this my problem?

---------- Post added at 03:14 AM ---------- Previous post was at 03:05 AM ----------

My folder looks like yours except it has twrp 3.2.3-1 instead of 3.2.2-0

---------- Post added at 03:56 AM ---------- Previous post was at 03:14 AM ----------

flash twrp 3.2.2-0 so everything is exactly like your folder. Followed instructions just as you said. I got the exact same errors. No difference at all. What I really don't understand is while I'm sitting here bricked in bootloader mode I can see that BL has the correct version numbers as does the base band (same numbers as in the file names in your/my folder). So something flashed correctly, didn't it? I'm so FRUSTRATED right now! What the hell is it with the damned boot slots? Why are they ****ing up my phone? Are you sure the command is correct "fastboot --set-active=b" or a or whatever it is, maybe a typo? You know what, I'm sorry. I'm just so far beyond frustrated I have lost my cool. It's not like I don't need my phone for pretty much everything like anyone else. Probably has something to do with it. And my one fail safe has ****ed me too, my nandroid won't restore. Thank you for the help thus far - I do appreciate it, you're a good guy. Sorry I lost my cool. Don't blame you for giving up on me. As I said earlier, I hate being so stupid.
[Google Pixel Themes, Apps, and Mods] Tulsadiver:
Nobody's given up. I went to bed. If you can get to fastboot you are not hard bricked.

Boot into TWRP and do a factory reset from TWRP.

Are you saying that nothing is flashing or just nothing is flashing to boot_b?

Have you tried this tool? It saved me once. I couldn't get adb to recognize my device. Somehow this tool got it to work. It also installs system images. Give it a try.

https://xdaforums.com/pixel/development/tool-skipsoft-android-toolkit-google-t3482761
[Google Pixel Themes, Apps, and Mods] kerryh420:
I can flash custom ROM's in recovery. I can flash the google factory image as well as your tulsdiver-flash-all zip in fastboot. When I do that however is when I get the bootb partition failure, always towards the end of the script. When fastboot flashing tulsadiver zip it goes through the script and periodically I will see "can't find suffix's" errors - this is from the "fastboot --set-service=b" (maybe service isn't the right word, I can't look it up right now). It's like the entire problem lies around the inability to flash the slot (whether its A or B). I don't know what you mean about flashing to both slots, I can't the script errors out and I can't do anything beyond that point.

Still, the strangest thing I am observing is the fact that in fastboot/bootloader screen I can see that the bootloader and the radio have the current versions from the most recent google system image file. And let me back up a second....I forgot to mention that I did successfully flash the pixeldust ROM (from XDA) but upon booting to asystem after the flash I was stuck in a bootloop but it wasn't a bootloop, it was just the white google screen you see after the "please lock your bootloader" warning. The flashing instructions didn't say anything about needing to flash a vendor file or gapps or anything...It was the first time I've seen that behaviour before. Tried to do a nandroid restore and after a "successful" restore (according to twrp) it goes back to the white google screen - no splash screen or anything.

Theoretically shouldn't I be able to take the most recent non-OTA factory image from google and flash-all that and the phone should work fine, right? The factory image has all of the partitions exactly as they should be since it's not like building a ROM where you are altering the partitions slightly and then zipping them back up for the flash. Factory images are from the mfg and are precisely the way the phone should be, correct?

Thanks for helping again I was so tired and frustrated last night...
[Google Pixel Themes, Apps, and Mods] h0mer_:
Mate, I was where you are now last week. Except I was attempting to root an 8.1 vanilla Pixel. I spent a whole day getting similar errors in the flashing process as what you are getting.

In the end, I changed computers and then all the magic just started to happen as it should.

Not another single error at all. So from all that, I put it down to a dodgey USB driver on the PC that I was using somehow corrupting the data transfer of some of the data files.

For me, this post was definitive in finding a solution to the hole I was in last week. I note that it is a similar set of commands that are included in the batch scripts posted in this thread that you have already tried.

https://xdaforums.com/showpost.php?p=73699257&postcount=5

As for bricking the phone, by all accounts they are pretty bulletproof up until the point where someone attempts to relock the bootloader (because of that silly nagscreen at startup) and that doesn't end nice in most circumstances.

Could be a good idea to explicity state that if the unlock/critical unlock options are used then the phone is going to be reset completely and all and any user data will be deleted as a result of either of these steps?

IIRC, there isn't a reminder of this being the outcome at stage of the script running.

:chooseunlock
set /P c= Unlock Bootloader[Y/N]?
if /I "%c%" EQU "Y" goto :yesunlock
if /I "%c%" EQU "N" goto :nounlock
goto :chooseformat
:yesunlock
echo Running Unlock
echo Look at your device,
echo press up arrow and Power to confirm
fastboot flashing unlock
echo This will say "failed" if already unlocked - ignore
ping -n 5 127.0.0.1 >nul
echo Running Unlock_critical
echo Look at your device,
echo press up arrow and Power to confirm
fastboot flashing unlock_critical
echo This will say "failed" if already unlocked - ignore
ping -n 5 127.0.0.1 >nul
[Google Pixel Themes, Apps, and Mods] post-mortem:
If you don't have access to another computer, you could also try a different USB port on your computer, in particular if you have both USB 2 & 3 ports. If you've been trying all this while plugged into a USB 3 port, switch to a USB 2 port. They use different controller chips. Sometimes things will work on one, but not the other.

You should also definitely try another USB cable.
[Google Pixel Themes, Apps, and Mods] Tulsadiver:
Try this, unzip the image zip that is in with the bootloader and radio images, the big one, a gb or so. It will have the boot.img inside. Open a cmd window in that folder and run this:

fastboot flash boot_b boot.img

fastboot flash system_b system_other.img

If that works try booting to slot b again

fastboot --set-active=b

It is possible your bootloader in slot b was changed but nothing else so now it doesn't recognize slot b because the boot.img failed to install to boot_b
[Google Pixel Themes, Apps, and Mods] h0mer_:
I've also experienced this as well. Flashing xyz simply doesn't work until changing the USB port to another one. And then, same as when I changed computers, the issues disappear and the flash sticks.

It can definitely be hair-pulling for those of us who only do this on the odd occasion, sometimes with a year or 3 slipping between efforts. What you vaguely remember from previous efforts is all for nort because the whole environment has moved on :(
[Google Pixel Themes, Apps, and Mods] kerryh420:
Thanks everyone for your support and help. It was as simple as switching to my laptop. I am beside myself in disbelief.

I'm still not out of the woods yet though, but very very close. So coming out of the flash of the factory image, as expected I am left with stock recovery and no root. Idea is to flash magisk in recovery but I can't flash the recovery. Tried "fastboot flash recovery twrp-3.2.3-1.zip" and "FAILED, zip not support in BL. Please go to download mode"...

What's that? and how to get there? I see lots of references to it on XDA but how to enter the mode? When I scroll through the options in fastboot I don't see a "download mode". Got something called barcodes, which I've never seen before....
[Google Pixel Themes, Apps, and Mods] Tulsadiver:
Pixel doesn't have a recovery partition and you cannot flash it to recovery. You put the twrp image on your PC, the twrp zip and magisk zip in your phone. You boot into TWRP, not install it.

fastboot boot twrp-3.2.2-1-sailfish.img

Once in TWRP, flash TWRP zip, flash magisk 17.1, reboot.

You should have root.