yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] roirraW "edor" ehT:
After what I described in my earlier post today (way above now), it goes to this screen after the "Google" boot logo starts - there's no way to avoid it now. I can ADB reboot bootloader, but flashing anything doesn't help, so...

I don't know what precisely caused the phone to go from recovered from corruption. After having fastboot flashed all slots with March's boot and init_boot, I no longer got the corruption screen, but then when I tried to take the Full OTA Zip back to May, which I was last running, that's when this screen started happening.

No. I've never disabled them on this phone.

I ADB reboot recovery from that corruption screen, but it reboots back to the corruption screen. If I ADB reboot bootloader and then fastboot reboot recovery, I also get rebooted back to the corruption screen.

Oh welll, good thought. :)

In the past, we've always been able to recover from the other kind of corruption screen (where the phone is still fully bootable and workable, it just pauses on the corruption screen) by flashing an old boot.img, attempting to boot it (which will normally fail), and then re-upgrading to the correct boot.img that matches the currently installed rest of the firmware.

Since I wasn't have luck with just the boot.img (or just the init_boot.img to the init_boot partition, for that matter), I thought I'd try your suggestion from your PF thread where I believe you said I should downgrade both boot and init_boot, and I didn't think that would cause any issues. I downgraded those two, tried to boot in it, for the first time in ~24 hours, I no longer saw a corruption screen, and then I tried to re-upgrade the boot and init_boot to the proper (May) ones.

Normally a factory reset wasn't necessary for this. I never completely downgraded the firmware other than the boot and init_boot, unless you count that after my initial attempt to upgrade to June using the Full OTA Zip caused bootlooping and the "Your device may be corrupted" paused message. So, it never actually successfully booted into June's firmware. Then, I was only able to get a running system again (but still with the paused corruption screen) by using the factory image (without wipe). I forget what exactly happened when I tried the May Full OTA Zip, but it didn't surprise me that it didn't work since it was at least partially upgraded to June.

After that, May was working just fine for me, albeit. still with the paused corruption screen if I rebooted.

Sorry about the book. :D

I'm prepared to factory reset.

I'll reply to @Lughnasadh separately, to help everyone's eyes get a brief rest. :D
[Google Pixel 8 Pro] roirraW "edor" ehT:
Yes, I was getting that message consistently starting with almost 24 hours ago when I tried using the Full OTA Zip to upgrade to June. As in my post above this one, after the semi-failed June Full OTA Zip, it would bootloop and give me the eio (e-i-e-i-o? :D ) every time I rebooted. I was then only able to use the May factory image to get the phone working again, but would still get the eio screen.

My attempts to temporarily downgrade either boot or init_boot (first accidentally tried init_boot, so tried each individually while the other was not downgraded), then attempt booting, and then re-upgrade to May boot and init_boot, did not make eio go away.

Edit: By the way, the example picture is definitely not a match for what it looked like on my phone, but I think it's the same thing. Just click the power button to continue, and everything else works just fine.
[Google Pixel 8 Pro] Lughnasadh:
Ah, okay. Maybe they updated the picture for the red eio corruption message. The one I posted is still on their website. Hope you get this all sorted out!!! 🤞🤞🤞
[Google Pixel 8 Pro] roirraW "edor" ehT:
I think I'm going ahead and factory resetting. I really don't think there's any choice, anyway. Thank you, though! I'm just glad I'm rooted, all always backed up, have SyncThing sync my music to all my devices, and all that good stuff. :)
[Google Pixel 8 Pro] badabing2003:
Exactly, the tool is just a layer that is doing those steps, nothing magical in it, the steps are the same whether it is done manually or through PF.

I've always said and continutue to say it, I strongly recommend everyone to do the manual steps until they know what it takes to achieve the goals, familiarity of every step of the way is key to getting out of trouble when it hits us, and it definitely does hit us.. Once fluent with manual steps, one can venture into automated tools to speed up the tedious repetetive operatioon, fully being aware that if anything goes wrong, then can figure out how to recover. It is inherent to such tools to have bugs or introduce regressions, it's a balancing act of risk vs reward.

If you're will to test further, we can use PF's logging mechanism to troubleshoot this.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Missed it by that much! ;) I already factory reset just a few minutes ago. Sorry, I felt like getting the phone started back on the road to root recovery. LOL! Thank you for all your efforts.
[Google Pixel 8 Pro] badabing2003:
@roirraW "edor" ehT

When you're flashing OTA, are you flashing stock or patched?
[Google Pixel 8 Pro] Lughnasadh:
In the meantime, maybe you can use that shoe phone of yours 😅
[Google Pixel 8 Pro] badabing2003:
I've done it so many times , it works, there was one incident, if you modified flash_all.bat manually to add flashing to both slots, I'm not sure when that bug was introduced by Google (and am not sure if it ever got resolved)

You could flash bootloader / radio with the flag, but flashing the image had to be done in two steps, otherwise it wouldn't work.

I recall having to change PF to accomodate for that bug.

Update:

Found the details.
[Google Pixel 8 Pro] roirraW "edor" ehT:
I normally flash patched. I had tried flashing the completely stock OTA, though, with no difference. When I was downgrading the boot or init_boot, it was always with stock.

Despite the phone now being factory reset and working, I'm now going to flash the Full OTA Zip for June again just to get the other slot sorted, while my running Android is completely fresh.

LOL! Nice reference! You win.
[Google Pixel 8 Pro] badabing2003:
I suppose Magisk 27?

It might not necessarily be the same issue, but Magisk 27 seems to be causing more issues than 26.x

See this post, what I had to go through to recover, the only way I was able to is by downgrading Magisk and the upgrading after recovery.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Yes, Magisk Stable 27 (27000). Very interesting!
[Google Pixel 8 Pro] Ghisy:
Anyone? What's the right procedure to update/change the installed LSPosed version without breaking things?
[Google Pixel 8 Pro] roirraW "edor" ehT:
I think I'm still on 1.9.2. I noticed for a long time I can't open the LSposed Manager, but I haven't had a need to, either. I don't know where 1.9.3 comes from, since it's not on GitHub. I only see it on some random site I wouldn't trust, but maybe there are other sources I'm not aware of.

When I updated previously, however, I just installed the new Magisk module in Magisk Manager over top of the old one, if LSposed didn't have an Update button in Magisk Manager for LSposed. I wouldn't know what to do, either - and would be cautious, if an update came as an .apk instead of a Magisk Module (.zip).
[Google Pixel 8 Pro] Dataman100:
FYI. I just finished the June update with no issues. I followed the manual steps in post #3 just like I do every month. The first slot seemed to take longer as well as the first boot after. The second slot went much faster.

I'm using Magisk Canary 27002. I'm not running LSposed or anything fancy. Just Seemless Hosts for Adaway. I'm passing DEVICE with Osmosis' PIF with the public FP. Duo and Okta both show no security issues and root seems to be working.

Good luck to everyone!
[Google Pixel 8 Pro] Ghisy:
Oh well, I guess I'll stay on 1.9.2 for now then. Thanks anyway!
[Google Pixel 8 Pro] Winryr:
Lsposed mod is just forked from Lsposed teams build since they no longer support it, the zip file on the github is to be flashed in magisk not extracted and installed via the apk.

If everything is working as it should I would keep things as they are. To go from the old version to the new, i just uninstalled the old module and immediately after installed the new one and all was well and working after a reboot.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Thank you! Didn't come up in my Google search. I've now added that project to my watchlist for releases, so I'll likely add that to my OPs sooner or later.
[Google Pixel 8 Pro] badabing2003:
FYI

I don't use LSPosed, but I've been referred to this one as a currently maintained version.

GitHub - pumPCin/LSPosed: LSPosed Framework

LSPosed Framework. Contribute to pumPCin/LSPosed development by creating an account on GitHub.

github.com

I don't know the differences.
[Google Pixel 8 Pro] DougMG:
I have tried them both and have observed no difference between them other than than the first one supports Android 15 beta.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Interesting, thank you! Apparently, I had already been aware of that one, as I had it set up to notify me of new releases. So, both forks have a 1.9.3.x. :D

I probably won't update until I have to, so probably not until Android 15, and then we'll see.

So...observations from a fresh setup of my Pixel 8 Pro:

Wireless data transfer from my P7P to P8P

:

Still sucks.

It claimed it was going to take a little less than two hours to transfer (including over 4000 mostly FLAC format audio files).

I left both phones completely alone and next to each other and just under my primary router, but about an hour or an hour and a half into the process, I checked, and it had stopped transferring. It had successfully transferred over 3000 audio files before it broke off, and it hadn't transferred any of the other categories that come below music.

Wired data transfer from my P7P to P8P

:

Not bad at all, if you use the right cable.

Despite it saying to use the cable that came with the phone, I knew those cables are only USB 2.0, so I got out my fastest USB-C <--> USB-C cable, which is about 18 to 24 inches and actually supports up to USB 3.2 Gen 2x2 (20 Mbps) whereas the P8P supports Gen 2 (10 Mbps), and I believe the P7P and below support Gen 1 (5 Mbps).

It estimated 5-6 minutes for the transfer of everything, including all that music. It probably took 10-15 minutes, but it completed everything successfully - at least as far as it indicates. I haven't actually confirmed file by file that it got everything, but I'll find out when I configure SyncThing on the phone and reconfigure it on my PC, and see if there's anything that hadn't made it over.

I used to always restore my Google cloud backup from my phone, and have been very satisfied with that for the Play Store apps and app data, and device settings, but I wanted to see what the phone to phone offerings were like these days. I'll still use Swift Backup, of course, to restore almost everything that I'm still missing.

Nova Launcher v8.x conundrum

:

This didn't happen during my wireless restore attempt, but probably because the attempt stopped part-way through:

I

definitely

had Nova and Nova Prime set in the Play Store not to auto-update on my P7P (and P8P, and tablet). I checked again on both phones just yesterday, and I had Nova v7.0.58 running.

During the wired data transfer from my P7P to P8P, it installed the latest from the Play Store on the P8P, which makes sense. However, it also updated Nova on my P7P in the process.

This is a big one to me:

Nova v8 also definitely had "Error & usage reporting" enabled by default. This once again goes against what they said when Branch took over. They touted the data collection as optional and disabled by default. It may indeed have been that way on the first Betas, or maybe on all of them, but they were inferring that it would be that way when it went Stable.

Nova 8 Stable still doesn't work right with their Companion app (for the Google Discover page).

Their download link for the Companion app was working in the last month or two, but leads to 504 error right now. Good thing I have backups.
[Google Pixel 8 Pro] deusfaux:
so are ppl fixing their RCS by finding their own random fingerprint or ...?
[Google Pixel 8 Pro] ThatOneGuyOverThere:
Solution RN is to use apatch for root and to not install zygisknext and just use riru if needed. RCS working for me for over a day now.
[Google Pixel 8 Pro] mlord:
All good here. Updated manually with a simplified procedure, extrapolated long ago from Post #3:

0. Disable any "extra" Magisk modules, other than built-in BusyBox, PlayIntegrityFix, or SystemlessHosts.

1. Download full OTA image from google.

2. Push OTA to /sdcard/, and point Magisk at it to Direct Install.

3. Pull the patched magisk-xxxxx-init_boot.img file from /sdcard/Downloads/

4. adb reboot sideload

5. adb sideload husky-ota-xxxxxxxxxx.zip

6. Reboot to booloader from onscreen menu.

7. fastboot flash init_boot magisk-xxxxx-init_boot.img

8. fastboot reboot

9. Re-enable any "extra" Magisk modules.

Repeat if desired to do the other slot as well.

Cheers
[Google Pixel 8 Pro] fil3s:
I flash each update with android flashtool, and I've never had an issue, I wouldn't use anything else. June firmware with magisk stable working no issues
[Google Pixel 8 Pro] Morgrain:
Edit: Nvm didn't see the sentence about Swift Backup
[Google Pixel 8 Pro] rester555:
Awesome! I want to try this out. So then I would install youtube revanced through the non-root method here right? What modules are you using with riru? How are you implementing adblock? What riru repository are you using?
[Google Pixel 8 Pro] roirraW "edor" ehT:
Extended repair program for Pixel 8
[Google Pixel 8 Pro] dr_rick13:
hi folks - I hope everyone is doing well!

Checking in to see how I can Google Wallet to work with a rooted device. It used to work about 6 months but then it stopped.

I know there are a few guides out there and I would be extremely grateful for anyone who could point us in the right direction.

Thanks, all
[Google Pixel 8 Pro] roirraW "edor" ehT:
Hi @dr_rick13! I hope you're doing well, too.

Post #5 - Play Integrity / SafetyNet

The first option that's listed there has been working for me. There are tips in that post, too, which can help resolve any lingering issues.
[Google Pixel 8 Pro] dr_rick13:
Thank you my friend!
[Google Pixel 8 Pro] roirraW "edor" ehT:
You're welcome! Unfortunately, passing Play Integrity is something that has to be more or less actively kept after these days. Commonly, all that's needed is to update the Magisk Module, and possibly manually re-check certification in the Play Store, or do some of the troubleshooting steps like waiting for some time to pass, wiping the Play Store's cache and data after updating the Magisk Module, rebooting...et cetera.

Even then, the Play Integrity Fix doesn't handle every situation. There are other solutions I have yet to fool with, so I'm not comfortable detailing them here. Other users have talked about the APatch root solution, but other than what little I've read here, I really don't know enough to go into it.

I also don't have the time currently to check out the alternatives, but maybe that will change eventually, and if necessary.
[Google Pixel 8 Pro] rester555:
The annoyance for me is when you clear cache/data for play store? if you have a wear os watch, you have to reset the watch. A BIG pain in the ass.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Oh, wow. You have to reset it for that, too? I just had to factory reset my phone yesterday, so I'm experiencing that. I didn't know or remember (if I knew) that you have to set it up as new if you wipe the Play Store cache/data.

Sigh...
[Google Pixel 8 Pro] rester555:
It's either play store or play protect. I can't remember which one. Or it's the Google App.
[Google Pixel 8 Pro] ThatOneGuyOverThere:
I just use root zip. I use lsposed with riru. Systemless host module + AdAway for adblock. I use Kitsunemask fork of riru.
[Google Pixel 8 Pro] rester555:
Can you post some links to the riru fork? I am having a hard time finding this. root.zip? What is that?

I see that Kitsunemask has a magisk module, but I can't find the riru fork.
[Google Pixel 8 Pro] ThatOneGuyOverThere:
Riru: https://github.com/KitsuneMagisk/Riru/releases/tag/v26.1.7.r539.c4a63e519a

Revanced:

Releases · j-hc/revanced-magisk-module

Extensive ReVanced builder. Builds both modules and APKs. Updated daily. - j-hc/revanced-magisk-module

github.com
[Google Pixel 8 Pro] rester555:
Thanks, are you using this module for systemless hosts with adaway? https://github.com/gloeyisk/systemless-hosts/releases

Also, do you have wallet working?
[Google Pixel 8 Pro] ThatOneGuyOverThere:
I use https://github.com/symbuzzer/systemless-hosts-KernelSU-module and wallet is not working for me.
[Google Pixel 8 Pro] rester555:
When it comes to doing a play integrity check, what are you passing/failing?
[Google Pixel 8 Pro] rester555:
I CAN CONFIRM! RCS is working with Apatch root method, riru (Kitsunemask fork), youtube revanced, systemless hosts kernelsu for adaway. I have basic integrity (no device integrity) so no google wallet. Thanks @ThatOneGuyOverThere.

Pixel Xpert is working as well
[Google Pixel 8 Pro] rester555:
Another interesting tidbit about Google Wallet. I have it working on my watch with the cards I need, but on the phone since it doesn't meet device security, I can't use the google wallet app on my phone.

It seems the API is bypassing the device integrity check when using my watch over my phone.

I see this potentially being patched by google at some point?
[Google Pixel 8 Pro] DougMG:
Unlikely as your phone is only used to add your cards to the watch. After that you don't even need to have your phone with you to use wallet on your watch.
[Google Pixel 8 Pro] rester555:
Understood. So essentially all of the API functions being used to verify for the phone are used for the watch. I can live with this since I got the watch for free. This will be a good workaround moving forward using the watch instead.
[Google Pixel 8 Pro] badabing2003:
Play services, and at least for Samsung transfer phone feature does not work, it falls every single time.

Such a PITA
[Google Pixel 8 Pro] roirraW "edor" ehT:
Since I had to factory reset my phone due to corruption the other day, I was trying like crazy to get the transfer phone feature to work. Scouring the internet for helpful advice. On the one hand, I'm glad I'm not alone in how broken it is (even with my Pixel 8 Pro), but it's shameful that Google doesn't have it working anywhere remotely reliably.

I tried dozens of times in all sorts of combinations (fresh reboots on both, charging or not charging, you name it), with no luck. I'm sorry to hear that it doesn't work with Samsung, too.

One thing that's confusing is that unlike a fresh Pixel Watch 2 setup, when using the transfer phone feature, and it gets to the point of pairing, the code pop-up for pairing security has a confirmation button on both the phone and the watch. Meaning not just the phone code pop-up screen has an Okay button, but the watch has a checkmark (and X) button, whereas on a fresh setup, the code on the watch doesn't have any interactive elements.

It does make a kind of sense since using the transfer phone feature is trying to pair a watch that's already considered paired, but it makes me ask - does it matter which device's Okay/Checkmark you click first? Do you have to click both, first one, then the other? In most of my attempts, I clicked both - I tried the phone first, and the watch first bunches of times.

Whenever I only clicked on one, nothing would happen, but immediately (but very quickly) after having clicked on both, then I see the message "Transfer failed", but the message disappears so fast.

So I gave up and reset the watch. It paired with no issues at all, except this morning I find out that despite that I had the "Alarm sync" toggle enabled in Google's Clock app, it set to "Adaptive" and my watch was on my wrist, and everything set for syncing everything in the Pixel Watch app, my alarm went off on my phone instead of watch.

I double-checked the Clock app's sync toggle to confirm it was enabled, so I disabled it, planning on re-enabling right away, but it won't let me enable it, saying: "Can't pair with a watch. Check the Google Pixel Watch app to pair a Pixel Watch with this phone.", with an OK button.

It is paired. I get the notifications on my watch. What the heck? I tried rebooting both, with no luck. I'd rather not wipe cache and data for my Clock app because I have a lot of very specific named alarms I need to enable or adjust from time to time.

Sigh...

Edit: Oh, I was already seriously leaning towards not getting the Pixel 9, but there's no way I'd get a new phone until the watch can be transferred successfully.
[Google Pixel 8 Pro] badabing2003:
Tell me about it, it sucks as hell.

just like you I have tried every damned combination first on the watch, first on the phone, at the same time, you name it, and so many times ...

I have a Samsung Watch, and when the transfer option shows up it tells me I have to sign in with Google account or Samsung account on both devices for the transfer to work.

After clicking on the checkmark of the pairing code, in my case it prompts me to sign in with Samsung account, and after signing in, it fails.

I tried removing the Samsung account from my phone in hopes of forcing it to use Google account, but it kept on coming back with Sign in with Samsung prompt and of course it failed afterwards,

It's just such a major pain to go through all the setup and customization ... to get it the way I had it, it is truly pathetic on Google's part.

But I don't think holding off on Pixel 9 would help, now that most watches are gravitating towards wearos, we're stuck with Google's services behind the scenes even if we don't use Google phone. :(
[Google Pixel 8 Pro] roirraW "edor" ehT:
Very much, yikes! That's an even bigger pain that you went through trying to get it to function correctly.

LOL! Got to laugh or cry. It's always a gamble with Google. Will it be fixed in 1 day, or 5 years?

I feel I'd be more tempted by a new Pixel once their TSMC CPU (supposedly the Tensor G5 in 2025) hits its stride, so maybe 2026 or 2027. A factor which would further influence my decision would be the incorporation of Samsung's S-Pen technology, but Samsung will likely never give up that monopoly, and I wouldn't blame them.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Google patches exploited Android zero-day on Pixel devices

Google has released patches for 50 security vulnerabilities impacting its Pixel devices and warned that one of them had already been exploited in targeted attacks as a zero-day.

www.bleepingcomputer.com

"It's fixed on Pixels with the June update (Android 14 QPR3) and will be fixed on other Android devices when they eventually update to Android 15. If they don't update to Android 15, they probably won't get the fix, since it has not been backported. Not all patches are backported."
[Google Pixel 8 Pro] roirraW "edor" ehT:
Okay, this is a GMail on the web complaint - not on Android, but what the heck!? When multi-selecting (or even just selecting one) emails, they moved the Snooze button to the overflow menu. I've got plenty of space in the UI for the snooze button, which I use a ton, to be there all the time.

Oh! Interesting. In the overflow menu, I had to choose "Switch to advanced toolbar". Now it's back.

Edit: Back to my Pixel Watch 2, and getting the phone Clock app "Sync" toggle to be enabled. I did another reset of the watch, but from the Watch app on the phone this time (the previous time I didn't have access to it on my phone, because I had to factory reset the phone from corruption). At first, it still wouldn't let me enable the Alarm sync, but after an hour, maybe less or more, I was then able to toggle it to enabled.

The previous time, I had waited over 12 hours without being able to toggle it.