[ROM][Pixel 4 XL][11.0] [Clang 13] PixelDust Android 11 for coral

[Curiousn00b]

WARING: Previous installation has failed.Yor device may fail to boot if you reboot or power off now.

Whats this?

Never seen that message before.

Mind posting the steps you took?

 

[zangxx66]

Never seen that message before.

Mind posting the steps you took?

I updated the ROM according to the installation wizard as usual.And then reroot and device dont work.I tried to update the ROM again.Hence the warning message

 

[fKm]

I also never saw this. I recommend a clean flash.

 

[zangxx66]

I also never saw this. I recommend a clean flash.

uh...I checked the logs.
Falied to read /sys/class/thermal/thermal_zone62/tmp: Invalid argument
Falied to read /sys/class/thermal/thermal_zone63/tmp: Invalid argument
Falied to read /sys/class/thermal/thermal_zone64/tmp: Invalid argument
Falied to read /sys/class/thermal/thermal_zone65/tmp: Invalid argument
Falied to read /sys/class/thermal/thermal_zone66/tmp: Invalid argument
Falied to read /sys/class/thermal/thermal_zone67/tmp: Invalid argument
Falied to read /sys/class/thermal/thermal_zone68/tmp: Invalid argument

 

[Ejay Soe]

How to root pixel dust. I flashed magisk patched image . My phone not booted and the devices is corrupt.
What should I do?
Please

 

[Curiousn00b]

How to root pixel dust. I flashed magisk patched image . My phone not booted and the devices is corrupt.
What should I do?
Please

Using Magisk Canary, patch the latest boot.img in the OP, then flash the patched image, boot up and open Magisk. Should work fine then.

You may have to clean flash. If you're trying to recover your data before clean flashing, you could dirty flash stock by removing -w in the script to avoid wiping the device to see if it still boots fine.

 

[zangxx66]

I have to clean flash.I noticed one thing.Even if I erase the data but adb sideload command run 94% still has a error info called failed to read command: no error

 

[GROOVYJOSHCLARK]

I have to clean flash.I noticed one thing.Even if I erase the data but adb sideload command run 94% still has a error info called failed to read command: no error

I get that almost every ROM I deploy on my PX4 XL, its normal and noted numerous places to ignore it (check out LOS install guide), they show it as well. If it boots and didnt error out (meaning it says no error), you can safely ignore it so try booting, if it boots normally, you are solid:

Install LineageOS on coral | LineageOS Wiki

wiki.lineageos.org

 

[zangxx66]

I get that almost every ROM I deploy on my PX4 XL, its normal and noted numerous places to ignore it (check out LOS install guide), they show it as well. If it boots and didnt error out (meaning it says no error), you can safely ignore it so try booting, if it boots normally, you are solid:

Install LineageOS on coral | LineageOS Wiki

wiki.lineageos.org

Ok.I will try to reroot

 

[chewy74]

Safety net is not working in the latest update

Same for me

 

[Ejay Soe]

Using Magisk Canary, patch the latest boot.img in the OP, then flash the patched image, boot up and open Magisk. Should work fine then.

You may have to clean flash. If you're trying to recover your data before clean flashing, you could dirty flash stock by removing -w in the script to avoid wiping the device to see if it still boots fine.

Edit:
It's works now with canary app.
Thanks


I did same. But I use magisk 23. I didn't try magisk canary version.

 

[GROOVYJOSHCLARK]

Ok.I will try to reroot

Well now I am confused, because you said it was a 47% error on the sideload process, this is only done on the initial install OR an update, but nothing to do with ROOT. Can you clarify the re-ROOT comment, what did you mean? If the sideload process says "adb: failed to read command" then boot it and its good to go and works, its done and successful. You shouldn't need to re-ROOT anything to fix this, you only need to ROOT if/when you wish to have a ROOT'd device, but re-ROOT'ing is not part of the install (ADB sideload).

 

[zangxx66]

Well now I am confused, because you said it was a 47% error on the sideload process, this is only done on the initial install OR an update, but nothing to do with ROOT. Can you clarify the re-ROOT comment, what did you mean? If the sideload process says "adb: failed to read command" then boot it and its good to go and works, its done and successful. You shouldn't need to re-ROOT anything to fix this, you only need to ROOT if/when you wish to have a ROOT'd device, but re-ROOT'ing is not part of the install (ADB sideload).

Root can't start properly after install the update, and flash the unmodified boot doesn't solve the problem, so I try to restart sideload

 

[GROOVYJOSHCLARK]

Root can't start properly after install the update, and flash the unmodified boot doesn't solve the problem, so I try to restart sideload

OIC what you meant, yes, that is by design. When you dirty the update, it also replaced the boot.img with stock (update). This is why you lost ROOT, your patched boot.img was restored with the update. This happens to me with every dirty, and anyone who dirties an update. Sorry, I didn't get what you meant with the wording, but this is to be expected. You will always have to re-root an update when the boot.img is part of the update (which almost all ROMs are, if not all ROMs) so expect to patch the boot.img with an update if you wish to retain ROOT. Make sure you are using the newer boot.img to patch, the one from the updated ROM but not the original ROM's boot.img (before you updated it). Patch it in MAGISK, then fastboot the ROOT'd boot.img, and reboot, you will have root then.

 

[Prey521]

Anyone else experiencing an issue with the Google Phone app refusing to close after a call is hung up? I've been having this problem for about a month, so I decided to factory reset and start from scratch with PD and the June update.

After a call, no matter how many times I press the Hang Up button, that screen will not disappear even though the person on the other end has already hung up. I can swipe the screen away and use other apps, but the Google Phone app will remain in the notifications and if I press on it, it opens as if the call was still active. The only way to make it go away is if I restart the phone.

Any ideas? This happens almost every time I end a call and it's pretty frustrating since the phone itself thinks that there's an active call and I can't use Bluetooth audio in my car or record a video with sound.

Thank you

 

[Ejay Soe]

Anyone else experiencing an issue with the Google Phone app refusing to close after a call is hung up? I've been having this problem for about a month, so I decided to factory reset and start from scratch with PD and the June update.

After a call, no matter how many times I press the Hang Up button, that screen will not disappear even though the person on the other end has already hung up. I can swipe the screen away and use other apps, but the Google Phone app will remain in the notifications and if I press on it, it opens as if the call was still active. The only way to make it go away is if I restart the phone.

Any ideas? This happens almost every time I end a call and it's pretty frustrating since the phone itself thinks that there's an active call and I can't use Bluetooth audio in my car or record a video with sound.

Thank you

I don't have any issue.

 

[Curiousn00b]

Anyone else experiencing an issue with the Google Phone app refusing to close after a call is hung up? I've been having this problem for about a month, so I decided to factory reset and start from scratch with PD and the June update.

After a call, no matter how many times I press the Hang Up button, that screen will not disappear even though the person on the other end has already hung up. I can swipe the screen away and use other apps, but the Google Phone app will remain in the notifications and if I press on it, it opens as if the call was still active. The only way to make it go away is if I restart the phone.

Any ideas? This happens almost every time I end a call and it's pretty frustrating since the phone itself thinks that there's an active call and I can't use Bluetooth audio in my car or record a video with sound.

Thank you

I've been experiencing this issue. It's quite a weird one because it's not an every single call thing, but seems like every 2-3 calls it'll pop up.

Yesterday, I hung out while making food and noticed the call kept going about 8 minutes later thinking my father forgot to hang up, but really, the call was ended and it was just stuck on the process of it.

I think it's the reason I've been getting weird audio issues as well. Been noticing my volume buttons only controlling the phone call volume or strictly coming out the earpiece as well.

 

[GROOVYJOSHCLARK]

Anyone else experiencing an issue with the Google Phone app refusing to close after a call is hung up? I've been having this problem for about a month, so I decided to factory reset and start from scratch with PD and the June update.

After a call, no matter how many times I press the Hang Up button, that screen will not disappear even though the person on the other end has already hung up. I can swipe the screen away and use other apps, but the Google Phone app will remain in the notifications and if I press on it, it opens as if the call was still active. The only way to make it go away is if I restart the phone.

Any ideas? This happens almost every time I end a call and it's pretty frustrating since the phone itself thinks that there's an active call and I can't use Bluetooth audio in my car or record a video with sound.

Thank you

YES! It happens to me on Bliss as well, its not ROM related, but something weird with Google phone I believe. I am on Verizon, so IDK if its just the phone app, or also the provider and phone app.

 

[Prey521]

I've been experiencing this issue. It's quite a weird one because it's not an every single call thing, but seems like every 2-3 calls it'll pop up.

Yesterday, I hung out while making food and noticed the call kept going about 8 minutes later thinking my father forgot to hang up, but really, the call was ended and it was just stuck on the process of it.

I think it's the reason I've been getting weird audio issues as well. Been noticing my volume buttons only controlling the phone call volume or strictly coming out the earpiece as well.

Yep, when the Phone app gets hung up like that, it takes over your audio controls and messes everything up. Only way to fix is a reboot.

YES! It happens to me on Bliss as well, its not ROM related, but something weird with Google phone I believe. I am on Verizon, so IDK if its just the phone app, or also the provider and phone app.

I'm on TMobile. I thought that maybe it was an issue with Google Voice. I uninstalled the Voice app but it still did the same thing. It's super frustrating!

 

[GROOVYJOSHCLARK]

Yep, when the Phone app gets hung up like that, it takes over your audio controls and messes everything up. Only way to fix is a reboot.




I'm on TMobile. I thought that maybe it was an issue with Google Voice. I uninstalled the Voice app but it still did the same thing. It's super frustrating!

yeah its pissing me off too, and I thought it was something I setup wrong (I test everything, all options, all ROM features, ETC), so I thought maybe it was setting I changed and forgot to undo, or enabling WiFi calling but with firewalling the verizon app and all services causing it.