[ROM][Pixel 4 XL][10_r41] PixelDust Android 10 for coral [05 August 2020]

[GROOVYJOSHCLARK]

Thanks for the detailed reply. I ended up giving up on 11 because I found bugs like the dialer not hanging up a call. That was enough for me to get rid of it as unreliable. I then tried to install 10 again by first flashing the Aug 20 stock firmware and then installed PD10 using the links at the start of this thread.

I had exactly the same issue as the first time I tried to install. The install got halfway through and then gave an error. I can't remember the exact error that was shown in the command window. I should have written it down. The phone definitely wouldn't boot. At that point I gave up for now and flashed stock and rooted it with Magisk no problem.

I'd like to give PD 10 another try because I really like the look of what I saw when I had PD 11 running. Unless I've done something wrong when installing 10 I'm not sure how to get it installed, given that my previous 2 attempts failed in exactly the same way.

Should I be flashing the Aug 2020 stock image and then using the links to the rom zip and boot image at the start of the thread as I have done on my previous 2 attempts?

Edit: It wasn't a slot problem because.....
fastboot --set-active=a or fastboot --set-active=b didn't help it to boot.

The easiest way to know what firmware to use (assuming its not in the OP), is to open the ROM zip, go to META-INF\com\android and read this line"

post-build=google/coral/coral:10/QQ3A.200805.001/6578210:user/release-keys

I highlighted the important lines, then go to the official Google firmware page for the device, and find the matching firmware. This corelates to:

10.0.0 (QQ3A.200805.001, Aug 2020)

I dont think thats your issue though, I think its either kernel related, or you are not patching the boot.img from the same OS you are using, with the same MAGISK installed in the OS. That's the only time I get bootloops, when I do not make a new and fresh patched img . FROM the same installed OS running the MAGISK installed FROM that same OS you plan to ROOT (meaning do not use anything other than the boot.img made from the SAME OS you installed, using the right boot.img from the zip).

You also didnt really answer my questions about install steps and processes used, so I am best guessing based on what you did reply with. If you follow the OP steps to a T, it wont fail, so I am confused what failed, where (halfway through), is that MAGISK, the OS ROM, ETC?

Do this, extract the payload.bin from the PD 10 ROM zip, then use python to extract the boot.img from the SAME PD ROM zip used to install the OS, thats what you patch in MAGISK. THEN take that NEW boot.img (from the original payload) install within MAGISK, select patch, select the boot.img you just extracted using python (payload dumper), then ADB that to the boot. Thats the right process and anything else isnt stable.

This isnt a slot issue so I wouldnt expect that to solve anything. I suspect you arent using python to extract boot.img using the payload dumper scripts (since you didnt note that anywhere but its CRITICAL), then using that dumped boot.img (from payload script) and using the installed PD 10 ROM, install MAGISK and patch that and ONLY that boot.img within MAGISK (once its installed and running in the OS). Its kind of critical you know what you're doing, reach out if you need exact steps and more help.

 

[appro77]

The easiest way to know what firmware to use (assuming its not in the OP), is to open the ROM zip, go to META-INF\com\android and read this line"

post-build=google/coral/coral:10/QQ3A.200805.001/6578210:user/release-keys

I highlighted the important lines, then go to the official Google firmware page for the device, and find the matching firmware. This corelates to:

10.0.0 (QQ3A.200805.001, Aug 2020)

I dont think thats your issue though, I think its either kernel related, or you are not patching the boot.img from the same OS you are using, with the same MAGISK installed in the OS. That's the only time I get bootloops, when I do not make a new and fresh patched img . FROM the same installed OS running the MAGISK installed FROM that same OS you plan to ROOT (meaning do not use anything other than the boot.img made from the SAME OS you installed, using the right boot.img from the zip).

You also didnt really answer my questions about install steps and processes used, so I am best guessing based on what you did reply with. If you follow the OP steps to a T, it wont fail, so I am confused what failed, where (halfway through), is that MAGISK, the OS ROM, ETC?

Do this, extract the payload.bin from the PD 10 ROM zip, then use python to extract the boot.img from the SAME PD ROM zip used to install the OS, thats what you patch in MAGISK. THEN take that NEW boot.img (from the original payload) install within MAGISK, select patch, select the boot.img you just extracted using python (payload dumper), then ADB that to the boot. Thats the right process and anything else isnt stable.

This isnt a slot issue so I wouldnt expect that to solve anything. I suspect you arent using python to extract boot.img using the payload dumper scripts (since you didnt note that anywhere but its CRITICAL), then using that dumped boot.img (from payload script) and using the installed PD 10 ROM, install MAGISK and patch that and ONLY that boot.img within MAGISK (once its installed and running in the OS). Its kind of critical you know what you're doing, reach out if you need exact steps and more help.

Thanks for your detailed reply. The issue that I was having with PD10 was getting it installed. I wasn't trying to root it with Magisk because I couldn't install the rom, let alone try to root it.

I followed the procedure at the start of the thread to install the rom i.e. Installed the Aug 20 factory image, flashed the downloaded boot image from the link at the start of the thread, fastboot erase data, then sideloaded the rom linked at the start of the thread. The sideload failed at 47% with an error.

I let it sit for a while because I think I read somewhere that the 47% thing can be a bug. It wouldn't proceed any further though and PD wouldn't boot.

I tried the whole procedure above a second time, starting with flashing the Aug 20 stock image, but I ended up with exactly the same result.

As I mentioned earlier when I did all of the above with PD11 it installed fine with no issues. It was only when I tried to root PD11 with Magisk that I had problems. I then found that the dialer seemed to be buggy so I have now flashed back to stock and rooted that so I can use Skyvalex.

 

[GROOVYJOSHCLARK]

Thanks for your detailed reply. The issue that I was having with PD10 was getting it installed. I wasn't trying to root it with Magisk because I couldn't install the rom, let alone try to root it.

I followed the procedure at the start of the thread to install the rom i.e. Installed the Aug 20 factory image, flashed the downloaded boot image from the link at the start of the thread, fastboot erase data, then sideloaded the rom linked at the start of the thread. The sideload failed at 47% with an error.

I let it sit for a while because I think I read somewhere that the 47% thing can be a bug. It wouldn't proceed any further though and PD wouldn't boot.

I tried the whole procedure above a second time, starting with flashing the Aug 20 stock image, but I ended up with exactly the same result.

As I mentioned earlier when I did all of the above with PD11 it installed fine with no issues. It was only when I tried to root PD11 with Magisk that I had problems. I then found that the dialer seemed to be buggy so I have now flashed back to stock and rooted that so I can use Skyvalex.

I am so sorry, somehow I missed / overlooked what you meant when you said the percentage, that threw me off. I misunderstood the percentage for the ROOT / ADB push, but not the ROM install itself, I have had this myself before. Easy peasy workaround. You're saying you can't get 10 to even install, it's error'ing on the adb sideload I take it?

We can get around that with TWRP. Now that we have a working TWRP for 10, we can use TWRP to install but you'll need to get back to 10 firmware (the one I laid out above), and when you do get back to 10, quickly go through the OS setup (stock firmware - 10), then once done, install a kernel that works with TWRP and 10. Once you have a working TWRP with kernel, then ADB boot TWRP, factory reset and copy the ROM zip to SD, then simply use TWRP to install the ROM from internal SD (no ADB sideload needed). This removes the ADB sideload hiccup failure.

I'm not on the 11 version right now, so I can't advise on those other issues you reported with 11, but using TWRP will work to get you on 10. Since you will do the install from TWRP and not ADB, you will get past that issue. Then setup 10 PD OS, and install magisk then patch the boot.img (from the 10 ROM using python to pull the boot.img to patch in MAGISK) and you will have a rock solid 10 PD with root and pass safetynet (I had to also install the universal safetynet module).

Once you get 10 working and setup the way you like it, betcha you don't leave PD 10. I didn't, it's so stable, I almost never reboot, and forget about plugging in, if I let my phone idle (not playing games and only use it for email, txt, and calls), it lasts 2/3 days. I only plugin when I'm playing games or it's been a couple days. I took a screenshot of my battery, it was last plugged in 14 hours ago, 72 percent left and I streamed showtime anytime all night long, overnight to my TV (and obviously not plugged in or on wireless). I still have this much battery leftover after a night long stream (plugged in 14 hours ago), it's amazing to say the least! One thing I will add in is that I do disable all apps autostart for games and apps I don't want running in the background using SD Maid (but any root app manager to can do this). I get incredible battery life with 10 PD and stopping those apps from running on their own. With my job and kids, I cannot really ever go without using my phone so I truly do not know how long it will last sitting at idle. My best guess is it would be days based on what's left after using it for calls, texts, and emails after 36 hours of what I've seen so far. 36 hours was as long as I could go without going on the road (IE having to plugin for the road trip) so I cant comment past 36 hours idle and once on road, that uses more battery with roaming but still, 36 hours is great I'm my book! And NO, I am not lying or exaggerating, 36 hours was at idle, using only calls/txt, and yes it truly lasted 36 hours, then I plugged in, and left but I was low, I was at like 2 or 3% left after 36 hours, but still, 36 hours idle, no phone has ever gotten this much idle time for me, so this was cool to see it last that long!

 

[appro77]

I am so sorry, somehow I missed / overlooked what you meant when you said the percentage, that threw me off. I misunderstood the percentage for the ROOT / ADB push, but not the ROM install itself, I have had this myself before. Easy peasy workaround. You're saying you can't get 10 to even install, it's error'ing on the adb sideload I take it?

We can get around that with TWRP. Now that we have a working TWRP for 10, we can use TWRP to install but you'll need to get back to 10 firmware (the one I laid out above), and when you do get back to 10, quickly go through the OS setup (stock firmware - 10), then once done, install a kernel that works with TWRP and 10. Once you have a working TWRP with kernel, then ADB boot TWRP, factory reset and copy the ROM zip to SD, then simply use TWRP to install the ROM from internal SD (no ADB sideload needed). This removes the ADB sideload hiccup failure.

I'm not on the 11 version right now, so I can't advise on those other issues you reported with 11, but using TWRP will work to get you on 10. Since you will do the install from TWRP and not ADB, you will get past that issue. Then setup 10 PD OS, and install magisk then patch the boot.img (from the 10 ROM using python to pull the boot.img to patch in MAGISK) and you will have a rock solid 10 PD with root and pass safetynet (I had to also install the universal safetynet module).

Once you get 10 working and setup the way you like it, betcha you don't leave PD 10. I didn't, it's so stable, I almost never reboot, and forget about plugging in, if I let my phone idle (not playing games and only use it for email, txt, and calls), it lasts 2/3 days. I only plugin when I'm playing games or it's been a couple days. I took a screenshot of my battery, it was last plugged in 14 hours ago, 72 percent left and I streamed showtime anytime all night long, overnight to my TV (and obviously not plugged in or on wireless). I still have this much battery leftover after a night long stream (plugged in 14 hours ago), it's amazing to say the least! One thing I will add in is that I do disable all apps autostart for games and apps I don't want running in the background using SD Maid (but any root app manager to can do this). I get incredible battery life with 10 PD and stopping those apps from running on their own. With my job and kids, I cannot really ever go without using my phone so I truly do not know how long it will last sitting at idle. My best guess is it would be days based on what's left after using it for calls, texts, and emails after 36 hours of what I've seen so far. 36 hours was as long as I could go without going on the road (IE having to plugin for the road trip) so I cant comment past 36 hours idle and once on road, that uses more battery with roaming but still, 36 hours is great I'm my book! And NO, I am not lying or exaggerating, 36 hours was at idle, using only calls/txt, and yes it truly lasted 36 hours, then I plugged in, and left but I was low, I was at like 2 or 3% left after 36 hours, but still, 36 hours idle, no phone has ever gotten this much idle time for me, so this was cool to see it last that long!

Thanks for this info. Battery life looks incredible. So after installing stock Android 10 I need to install a kernel before installing TWRP? Can you elaborate on which kernel to use and how to install it? I've used ElementalX before and just installed it with the ElementalX Manager.

 

[GROOVYJOSHCLARK]

Thanks for this info. Battery life looks incredible. So after installing stock Android 10 I need to install a kernel before installing TWRP? Can you elaborate on which kernel to use and how to install it? I've used ElementalX before and just installed it with the ElementalX Manager.

Yes the battery life is amazing, that's one of the main reasons I'm on PD 10, but know, I use the native, built-in kernel that comes with PD and I disable all apps that autostart but are not needed (like games). This keeps the background free of running rogue apps stealing precious battery life. 4.14.191-unicornblood-pixel4-q is the kernel that's installed by default.

EX used to be my only go to kernel, but with PD 10, I had weird issues using EX originally and I haven't been back to EX. If you use EX under PD 10, I cant comment if it works or not so user beware. Kirisakura DOES work for 10 but don't go higher than 5.2.6 (last 10 kernel release before rebasing to 11). I left the default PD 10 kernel in my daily driver though and its awesome.

For stock 10 to use TWRP, EX kernel worked though (so once you revert to stock 10 firmware, ROOT IT, install EX kernel or Kirisakura), boot TWRP, factory reset, then install PD 10 with GAPPs and boom, you are done.

---NOTE if you have issues with TWRP going black, or rebooting to BL, boot stock firmware again, download the Kirisakura kernel 2.5.6, open EX app again, go to tools, then flasher, and install Kirisakura 2.5.6 kernel, this will remove EX kernel and replace with Kirisakura kernel, then reboot to TWRP again (ADB TWRP.img). This should work, I was able to get TWRP running with EX kernel a few times, but I found Kirisakura was far more stable. EX went black when booting TWRP a few times whereas Kirisakura seemed to always work, so its up to you, but either way ROOT and EX app will be the easiest way to get the stock firmware prepped, sure its more work, but its the best, sure-fire method I found (and I tested all sorts of scenarios).

This is the exact process I used to install PD 10 weeks ago and its STILL rock solid! The only time I move from PD 10 is to test other ROMs for users, but this is my go to ROM.

NOTE you do not have to ROOT the stock firmware, but it makes it much easier to install EX kernel from the app so its up to you but its not a requirement (if you can get the kernel installed without ROOT or TWRP).

This is how I did it:

-Revert to 10 firmware with -w (after backing up everything)
-Run through stock firmware setup, skip most things (I only setup G account for store)
-Install EX app from store (or from another location)
-Install MAGISK app
-Root (using the STOCK firmware boot.img), patch in MAGISK, boot patched .img
-EX App kernel --> install kernel (leverages ROOT to install EX kernel)
-Boot TWRP
-Factory reset
-Install PD 10

My device says it averages over 1 day but really I get 2 to 3 especially when I'm not doing anything but phone, text, or email. Even when I'm playing games, it still lasts pretty decent, yes it sucks battery life if I'm playing resource intensive games, but otherwise, it idles forever. This wasn't out of the box though, remember what I said about rogue apps running on their own in the background, those have to be controlled to get the best battery life, same as wakelocks so get a decent app manager to handle them:

 

[appro77]

Yes the battery life is amazing, that's one of the main reasons I'm on PD 10, but know, I use the native, built-in kernel that comes with PD and I disable all apps that autostart but are not needed (like games). This keeps the background free of running rogue apps stealing precious battery life. 4.14.191-unicornblood-pixel4-q is the kernel that's installed by default.

EX used to be my only go to kernel, but with PD 10, I had weird issues using EX originally and I haven't been back to EX. If you use EX under PD 10, I cant comment if it works or not so user beware. Kirisakura DOES work for 10 but don't go higher than 5.2.6 (last 10 kernel release before rebasing to 11). I left the default PD 10 kernel in my daily driver though and its awesome.

For stock 10 to use TWRP, EX kernel worked though (so once you revert to stock 10 firmware, ROOT IT, install EX kernel or Kirisakura), boot TWRP, factory reset, then install PD 10 with GAPPs and boom, you are done.

---NOTE if you have issues with TWRP going black, or rebooting to BL, boot stock firmware again, download the Kirisakura kernel 2.5.6, open EX app again, go to tools, then flasher, and install Kirisakura 2.5.6 kernel, this will remove EX kernel and replace with Kirisakura kernel, then reboot to TWRP again (ADB TWRP.img). This should work, I was able to get TWRP running with EX kernel a few times, but I found Kirisakura was far more stable. EX went black when booting TWRP a few times whereas Kirisakura seemed to always work, so its up to you, but either way ROOT and EX app will be the easiest way to get the stock firmware prepped, sure its more work, but its the best, sure-fire method I found (and I tested all sorts of scenarios).

This is the exact process I used to install PD 10 weeks ago and its STILL rock solid! The only time I move from PD 10 is to test other ROMs for users, but this is my go to ROM.

NOTE you do not have to ROOT the stock firmware, but it makes it much easier to install EX kernel from the app so its up to you but its not a requirement (if you can get the kernel installed without ROOT or TWRP).

This is how I did it:

-Revert to 10 firmware with -w (after backing up everything)
-Run through stock firmware setup, skip most things (I only setup G account for store)
-Install EX app from store (or from another location)
-Install MAGISK app
-Root (using the STOCK firmware boot.img), patch in MAGISK, boot patched .img
-EX App kernel --> install kernel (leverages ROOT to install EX kernel)
-Boot TWRP
-Factory reset
-Install PD 10

My device says it averages over 1 day but really I get 2 to 3 especially when I'm not doing anything but phone, text, or email. Even when I'm playing games, it still lasts pretty decent, yes it sucks battery life if I'm playing resource intensive games, but otherwise, it idles forever. This wasn't out of the box though, remember what I said about rogue apps running on their own in the background, those have to be controlled to get the best battery life, same as wakelocks so get a decent app manager to handle them:

Thanks for the instructions. Much appreciated! I won't be able to get to it for a few days, but when I can make the time I'll give it a go and report back.

 

[GROOVYJOSHCLARK]

Thanks for the instructions. Much appreciated! I won't be able to get to it for a few days, but when I can make the time I'll give it a go and report back.

My pleasure! Let me know when you're rocking PD 10! I bet you love it so much, that you remain on it for the foreseeable future!

 

[GROOVYJOSHCLARK]

Delete, sorry, wrong forum

 

[joeo10]

PixelDust ROM is an Android 10 ROM especially built for Google Pixel and Nexus devices.

The code is based off directly from AOSP. We strive to keep the PixelDust Experience as close as possible to Android as Google intended. We add a decent selection of the coolest custom ROM features that would've been missed if they hadn't been included.
The PixelDust Crew would highly appreciate if you would take a little of your time and leave your valuable feedback, your honest opinion or just say hello. If you should encounter a bug, or some kind of glitch that seems to be abnormal and you are pretty sure that it is related to the ROM (and not related to any special apps or mods you flashed on top), then please give as many details as possible.

Special shoutouts to Roger.T for his amazingly designed wallpapers, logos and the best bootanimation I ever had on my Pixel!!! If you like our work, please consider to buy Roger the first beer, and a few more for the other team members and spezi77. Cheers!


BTW, please consider to take a logcat, because you know that:




Disclaimer:
If your device fails to comply with your standards of what you consider functioning, I am not liable. This is provided free of charge and does not come with a warranty. Although, if you provide a log, I can provide some sort of assurance that I will look into your issue.

* Periodic AOSP security updates
* Pixel GApps included (no need to flash any third party GApps)
* Pixel 4 wallpapers
* PixelDust Launcher
* Enhanced theming engine (big thanks to DirtyUnicorns for their commits)

Additional QS tiles
* Always On Display
* Caffeine
* Language
* NFC
* PixelDust Settings
* Screenshot (Partial/Full/Longshot)
* and many more

Display
* Theming: Dark/black themes, Accent colors, Fonts, Icon shapes, QS tile styles

Lock screen display
* Battery level on bottom
* Ambient music ticker
* Charging info

Security
* Lock screen PIN quick unlock

System Gestures
* Swipe fingerprint for notifications
* Swipe fingerprint left or right to dismiss notifications
* Volume rocker skips music tracks
* Three-fingers-swipe to screenshot

PixelDust Wallpapers
* A set of 15 breathtaking space themed Wallpapers

Theme options
* Themes: Choose between 48 different accent colors, 8 different clock interfaces and more
* Style: Automatic, Light, Google dark, Pitch black, Solarized dark, Black Coffee

Status bar
* Status bar icon whitelist
* Network traffic display
* Clock & date settings
* Battery settings

Quick settings
* Vibrate on touch
* Secure tiles require unlocking
* Battery percentage
* Battery estimate
* Display clock in QS header
* Footer brightness slider
* Brightness slider on/off toggle
* Brightness slider bottom
* Auto brightness icon
* Min-Max icon
* Status bar pulls down Quick Settings

Buttons
* Accidental touch
* Screen off power button torch
* Volume Settings: Playback control, Volume wake, Volume steps
* Volume Panel

Navigation bar
* Navbar visibility toggle
* Layout (normal, compact, left-leaning, right-leaning)
* Invert layout of Navbar buttons
* Show arrow keys while typing

Gestures
* Status bar dt2s
* Lock screen dt2s

Lock screen
* Left & right lock screen shortcuts
* Fingerprint authentication vibration
* Pocket detection
* Media cover art
* Media artwork blur level
* Lock screen charging animation

Power menu
* Disable power menu when locked
* Power Menu options incl. advanced Restart options and many more

Notifications
* Notifications light
* Battery charging light
* Ambient display brightness
* Ambient notification brightness
* Edge lighting

Misc
* Pulse for NavBar, LockScreen and Ambient Screen
* Gaming Mode
* Wake up on charge
* Rounded corners
* Disable device identifier restrictions

Not working:

* ---

Terms & conditions:
By downloading this custom ROM you agree that I, the developer of PixelDust ROM, am not liable in any way, shape or form for any damage done to your device. The PixelDust ROM is provided free of charge and does not come with a warranty.

Downloads:
* Pixel Dust ROM Android 10 incl. GApps
* Boot image (must be flashed before each installation process)

Telegram Discussion Channel: https://t.me/pixeldustcommunity
Telegram Announcements Channel: https://t.me/pixeldustproject
Telegram Build Support Channel: https://t.me/compile_pixeldust
Discord Server: https://discord.gg/ANtVnW8

Pre-requisites:
* You are familiar with helping yourself out of awkward situations. You won't defame or complain at the developer of this ROM for your misfortunes.
* You are familiar with using fastboot
* Before you are ready to flash this custom ROM, you have to install the latest Google factory image
* Bootloader unlocked
* You have created a backup of your ROM & data

First time installing PixelDust ROM, or coming from another ROM:

YOU MUST HAVE AUGUST FACTORY IMAGE!

1. Flashing stock ROM:

1. Follow these instructions: https://developers.google.com/android/images#coral

2. Flashing PixelDust ROM:

1. Download the ROM and boot image
2. Flash the boot image (this allows stock recovery to flash unsigned rom zip since we dont have TWRP)
   

   fastboot flash boot boot.img

3. Wipe userdata (required for first PixelDust/Android 10 install)
   

   fastboot erase userdata

4. Reboot into fastbootd
   

   fastboot reboot fastboot

5. Use volume keys and power button to select "Enter Recovery"
6. Select "Apply Update from ADB"
7. Sideload the ROM zip
   

   adb sideload PixelDust-X-aosp-coral-***.zip

8. Reboot
9. When the device is not booting PixelDust, please change the boot slot to a or to b in fastboot mode
   

   fastboot --set-active=a or fastboot --set-active=b

IF THERE IS AN ERROR AFTER FLASHING IN RECOVERY JUST IGNORE IT!

Dirty flashing PixelDust ROM:
Just skip the step "Wipe userdata"

Thanks to all development teams, e.g. ABC ROM, AICP, AOKP, AOSPA, AOSP Extended, BenzoROM, Bootleggers, CarbonROM, crDroid, DirtyUnicorns, Havoc OS, LOS, MSM-Xtended Project, OmniROM, Potatoes Project and PureNexus, we borrowed a few features and tweaks from.

Unicornblood kernel (by Dirty Unicorns)
Source code: https://github.com/DirtyUnicorns/android_kernel_google_floral


PLEASE DO NOT USE THE INTEGRATED UPDATER TO UPDATE THE ROM. IT WILL MOST LIKELY BRICK YOUR DEVICE.




XDA:DevDB Information
[ROM][Pixel 4 XL][10.0] PixelDust Android 10 for coral, ROM for the Google Pixel 4 XL

Contributors
spezi77, fKm
Source Code: https://github.com/pixeldust-project-x

ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: AOSP

Version Information
Status: Release

Created 2020-01-31
Last Updated 2020-08-05

Can anyone have a Android 10 PixelDust boot img. from August 2020? I tried to flash the 20200805 build but have errors trying to flash the ROM. It has to be a boot img issue.

 

[fKm]

Can anyone have a Android 10 PixelDust boot img. from August 2020? I tried to flash the 20200805 build but have errors trying to flash the ROM. It has to be a boot img issue.

All boot images are in the folder: https://sourceforge.net/projects/pixeldustproject/files/ota/coral/

Just pick the one you need.

 

[GROOVYJOSHCLARK]

Can anyone have a Android 10 PixelDust boot img. from August 2020? I tried to flash the 20200805 build but have errors trying to flash the ROM. It has to be a boot img issue.

Depends on the error, you didn't provide us enough info (no info), so who knows what happened. Can you provide either a screenshot of the issue you face, or layout your install procedure and where you got stuck (or logs)?

If it's in the ADB SIDELOAD stage, did it error in push (like 47% then failed)? I have had this happen in the past, and I laid out how to overcome it with TWRP a few posts up. If it's in the ADB push stage, TWRP will solve it. Otherwise, as our awesome dev noted above my reply, ALL boot.img's you would ever need are in the folder he listed.

I would start over, flash the right firmware and go through a quick setup of the stock OS, then patch the STOCK boot.img (while still in and using the STOCK firmware), once ROOT'd install Kirisakura (2.5.6 which is the LAST 10 kernel version), then boot TWRP.img, factory reset, copy the ROM.zip to SD (TWRP allows SD access), once factory reset and the ROM.zip is on the SD, flash it normally. The ROM.zip includes GAPPs so thats done with it.

Once you have PD 10 running, pull the boot.img (using python / dumper script), then install MAGISK app and patch, repeat the ADB boot to enable ROOT in PD10.

 

[hjephj1990]

I really need call recording function. You have a way to install without root . Thank you

 

[xLoveHateLegend]

So to root on this rom I would use the PD boot file and patch that in Magisk?

 

[Prey521]

Had to switch back to stock root. Couldn't figure out why I was having so many problems with phone calls hanging up when another call would come through or why the phone app would stay running after a call ended no matter how many times I did a clean install. No problems since switching to rooted stock. Will come back when 12 is up and running. Thanks for all of the hard work, this is an awesome ROM!

 

[SonKim297]

Sorry sir, but i can't reboot to boot.img for enter adb side load . How can i fix issuel>?

 

[androidtechmb]

No edit on my part.

Did you root with Magisk before or after installing PD 10?
I'm a bit rusty, just installed Pd 10 (Aug.) on a new Pixel XL 4 yesterday and working great. Hadn't messed with PD since I did ver. 9 on PIXEL XL that I'm still using and about to retire.
Magisk info states that I needed to root before installing custom ROM. Can someone point me in the right direction? Didn't find much as of yet. Sure would like to root without going back to Stock 1st. AdAway is really the main reason, should I even bother. Thx.

 

[Curiousn00b]

Did you root with Magisk before or after installing PD 10?
I'm a bit rusty, just installed Pd 10 (Aug.) on a new Pixel XL 4 yesterday and working great. Hadn't messed with PD since I did ver. 9 on PIXEL XL that I'm still using and about to retire.
Magisk info states that I needed to root before installing custom ROM. Can someone point me in the right direction? Didn't find much as of yet. Sure would like to root without going back to Stock 1st. AdAway is really the main reason, should I even bother. Thx.

The boot.img that you used to boot into recovery is the same image that you want to patch.

Just install the Magisk app and patch the boot.img you used, then fastboot flash boot magisk_patched.img

Lastly, open the Magisk app and I believe it'll ask you to reboot to finish installing Magisk. You'll be good to go then.

 

[androidtechmb]

I really need call recording function. You have a way to install without root . Thank you

Been using PD 10 Aug. revision last couple of days. Haven't rooted yet. I installed Boldbeast Recorder yesterday (without root option) and it works as expected. Note that your carrier may block call recording in your area because of federal regulations. In that case, you'll need to root your device to use advanced root settings in Boldbeast.

 

[androidtechmb]

The boot.img that you used to boot into recovery is the same image that you want to patch.

Just install the Magisk app and patch the boot.img you used, then fastboot flash boot magisk_patched.img

Lastly, open the Magisk app and I believe it'll ask you to reboot to finish installing Magisk. You'll be good to go then.

Thank you. Gave me enough info to finish the job. Glad I don't have to go back to stock.