yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] weriwd:
Thank you for bringing this topic to the discussion and enlightening us that both methods are equally "dangerous". In that case, would it be safer to disable all Magisk modules, flash back to the stock init_boot, proceed with the OTA update on the device, and then flash the newly patched init_boot?
[Google Pixel 8 Pro] BillGoss:
Oops! It helps if I actually reply.

Yes, you're on the right track. The simplest process is, assuming you've used the following process previously, is:

1. Magisk>Uninstall Magisk>Restore image to restore stock init_boot

2. Manually start the update from Settings>System>Update

Note: if there is no OTA, step 3 must still be run

3. Magisk>Install>Direct Install to re-patch

the current slot init_boot

4. Magisk>Install>Install to Inactive Slot to patch the updated init_boot

5. Reboot from Magisk or the update screen

It relies on the fact that when you do a Direct Install or Install to Inactive Slot in Magisk it saves a copy of the current stock image.

The very first time you root, you get a copy of the stock init_boot and patch the file, then flash the patched image and boot the phone.

To get Magisk to create its copy of the stock init_boot you need to do the following when you're already running on the patched init_boot image:

1. Manually restore the stock init_boot while the system is running. Something like this: su -c dd if='/sdcard/<path>/<stock init_boot.img>' of=/dev/block/by-name/init_boot_<current slot>

2. Magisk>Install>Direct Install to re-patch the current slot stock init_boot as this will create the Magisk saved copy of the stock image in /data/Magisk*
[Google Pixel 8 Pro] roirraW "edor" ehT:
Thanks for addressing in a way more capable way than I could have, especially since I didn't sleep long enough.

I've added the post you linked, which explains succinctly but has your further links for more detail, to the OPs for both the Full OTA Zip and Factory Image methods:
[Google Pixel 8 Pro] BillGoss:
@badabing2003 , thanks for taking the time to write a detailed reply. I need to carefully go through what you said before I respond. I'm always happy to learn new things about our phones.
[Google Pixel 8 Pro] badabing2003:
Sure, take your time, and don't hesitate to point out any mistakes or incorrect assumptions i might have made, like yourself, I'm always happy to learn.
[Google Pixel 8 Pro] BillGoss:
I had to smile at this. Both of us assumed, without stating, how we do the initial rooting.

I always take a copy of the stock init_boot from a factory image.

I'm guessing that in your case you were using Magisk to create the patched file from an OTA zip.

That's why, in my case, I do have a copy of the stock init_boot image. And in your case you rightly can't use dd because the only image available is the patched one.
[Google Pixel 8 Pro] badabing2003:
You know what assumptions (assume) makes us right ;)
[Google Pixel 8 Pro] roirraW "edor" ehT:
Pixel Watch 3 arrives at FCC with UWB, 5 GHz Wi-Fi

With Made by Google 2024 next month, the Pixel Watch 3 has arrived at the FCC for regulatory approval. Four model...

9to5google.com
[Google Pixel 8 Pro] roirraW "edor" ehT:
Since I had posted about my alarm sync issue between my Pixel 8 Pro and Pixel Watch 2 here, I'm updating here as well.

As a refresher of the background, I had to factory reset my Pixel 8 Pro. After setting it back up, and resetting my watch (because Google's supposed way of setting a watch up with a "new device" without resetting the watch is broken for either most people, or a lot of them, anyway), initially the Pixel 8 Pro Clock app's Settings didn't list any devices available to sync the alarms to.

After a day or two (or more?), eventually it listed my Pixel Watch 2 as being able to sync the alarms to. I enabled it. Until now, no matter what, although everything else would sync to the watch including Do Not Disturb, the phone alarms wouldn't sync to the watch.

I had previously tried disabling and re-enabling, disabling, waiting a half hour or hour, and re-enabling, et cetera, without any luck.

Last week (I don't know what day), I went ahead and disabled the alarm sync setting on the phone.

Just now, I re-enabled it, set a test alarm, and lo and behold, the alarm finally went off on my watch.

So the solution for me was disabling the sync, leaving it disabled for (4 or 5 days I guesstimate), and then re-enable it, and it worked right away.

If this and anything else new I would ever think of trying failed to succeed in getting it to sync alarms ever again, I would not plan on ever buying another Pixel Watch until/if they fixed that, and fixed the ability to "transfer" a paired watch to a phone that has been factory reset (after having already been paired with that watch before the factory reset).

They better be working to smooth these things out, and I'm still tempted to not buy another Watch until/if they ever do get these things to just work the way they're supposed to.
[Google Pixel 8 Pro] badabing2003:
Bill, thanks for the numbers

I'll get back to you when I go in details over them, (probably over the weekend) but you know I'll come back still disagreeing with this statement.

Because there are numerous cases of PF users that had failed full OTA and yet were able to boot back to active system (I'll get you links when I have the time)

Furthermore keep in mind that

The logical partitions within the super partition show only the active partitions in the lpdump output.

You need to examine partition metadata with tools like sgdisk to get full details (which is quite involved to be honest, I'll see if I can get to that, but would probably need more tools installed on the device)

It's fun to be challenged, makes me question my assumptions and findings, but the proof is in the pudding, numerous cases of people (including myself) being able to boot to active slot with a failed OTA flashing.

That is never the case with a factory flashing.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Google System Release Notes - Help

Google System updates make your Android devices more secure and reliable and give you new and useful features. They include updates from Google to the Android operating system, Google Play Store, and

support.google.com
[Google Pixel 8 Pro] roirraW "edor" ehT:
Google Play Protect could soon get an upgrade for local APK scanning (APK teardown)

Google Play Protect could soon support YARA for local APK scanning, letting it identify malware groups better. Read on to know more!

www.androidauthority.com
[Google Pixel 8 Pro] BillGoss:
What I want is the option to turn off all this, pointless from my perspective, advertising in the guise of being helpful. I know how to use search functions and don't want Google to suggest apps for me.
[Google Pixel 8 Pro] roirraW "edor" ehT:
I don't think it's required. It says, "you can..." (...choose the types of apps you're interested in to improve your recommendations).

Personally, I welcome any improvement to helping me find certain types of apps, as it's rare when I install a new app, but when I'm looking for one, I'm usually looking to solve a very particular issue, and if it could, for example, automatically filter out certain kinds of apps that wouldn't likely be among what I would consider.

We'll see how it works when I have a real-world need, though.
[Google Pixel 8 Pro] BillGoss:
From my perspective, if the full ota update fails before it starts writing the logical partitions, then you can restart the active slot. But if it fails after writing the logical partitions then there's no coming back.

So maybe we're both right!

I was thinking about the factory image issue. Google includes flashing system-other (you pointed me to the post about this) which effectively overwrites the other slot logical system partition. I'm toying with manually flashing the phone's current factory image to the Inactive slot but skip the system-other. That should allow the currently active slot to boot.

But don't hold your breath as may not get around to doing this test.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Good luck if you do, although I wouldn't blame you for not doing it, since you could end up in an unplanned-for situation. I would definitely be curious to find out the results.
[Google Pixel 8 Pro] BillGoss:
I'm an intrepid explorer traversing dangerous falls. I've be in this situation before and have always managed to finally get across. (Though without an MSM Tool for the P8P I'll have to be far, far more careful)
[Google Pixel 8 Pro] badabing2003:
I've already tried this, and I think I reported it either in that post or some other post.

It worked fine with Pixel XL, didn't work with Pixel 5 or Pixel 7 Pro

But nothing that we can't recover from.
[Google Pixel 8 Pro] freezingpoint:
I rooted my phone probably 4 months ago.

I have decided to update it as the system update popup is annoying, so I followed the steps for the full OTA. I got everything ready and patched the full OTA file, but when I go to sideload via adb, it shows up some error 7, which ended up not updating the phone.

I've booted up the phone as normal and root is intact, but not updated.

Not sure what went wrong.
[Google Pixel 8 Pro] roirraW "edor" ehT:
I've had limited luck finding out about Error 7 through Google. There are these posts in the Pixel 8 PixelFlasher thread:

The normal things I would suggest are using a different cable, using a different USB port on your computer, and reboot your computer. If that doesn't help, maybe someone else can make some suggestions, or if you have to, you could try PixelFlasher and submit logs if things still go wrong. I'd try the USB cable/port/reboot suggestion first, though.

I update the P8P, spare P7P, and Pixel Watch 2 every month with the Full OTA Zip, and I haven't encountered Error 7 that I recall.
[Google Pixel 8 Pro] badabing2003:
One thing I would add,

I have seen many cases where OTA sideloading the July release fails and stops at 47%, often this is due to the phone receiving an update through Google's OTA (not sideload) and unless that is cleared, the sideloading is failing.

If you're still able to boot back to system and are rooted, try to do the Cancel OTA update in PixelFlasher and then repeat the sideloading however you please (either in PF or manually)

Version 7.0.0.0 of PF automatically does the cancelation first (when doing sideload) if the device is in adb mode and rooted.
[Google Pixel 8 Pro] freezingpoint:
Thank you so much for this! It does seem the cancel OTA is the key thing.

I also tried your app, it's really easy to use. It saves a lot of time and effort and less chances of making any mistakes.

I put off updates as it's such a hassle, but your app is just wonderful.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Interesting, but not good enough.

FCC docs reveal the Pixel 9's smart home superpower

The Thread mesh network will let Google Pixel 9 phones communicate directly with your Matter smart home devices.

www.androidauthority.com
[Google Pixel 8 Pro] danw_oz:
Wow this phone is horrific after installing July update, does not charge properly on USBC and wirelessly just drove 2 hours and still at 50%, phone was not too hot either.

Applications don't work properly with touch screen issues

5G signal drops, completely lost signal today, then had to reboot the phone to get it back, phone would not connect to my car WIFI when the signal was crap.

Battery drain is crazy as well.

Had bluetooth issues, and when I got home the automated door opener did not work, which is phone and car bluetooth detection of the car.

July update I feel like a beta tester
[Google Pixel 8 Pro] roirraW "edor" ehT:
For what it's worth, I haven't had any of these issues on the July Stable firmware.
[Google Pixel 8 Pro] danw_oz:
Good to know, might need to dirty flash it again, and or see if they created a mobile vendor specific build.

Update no vendor specific build, dirty flashed again, lets see.

Update - Dirty flashing the phone again has made it better, but bluetooth and or wireless android auto is locking up at times, or music starts playing with no sound. And I had the phone full lock up for the first time that I had to hard power off.
[Google Pixel 8 Pro] StanWiz:
I have experienced some of the same issues you describe after installing July update - wifi connection, charging and battery drain .
[Google Pixel 8 Pro] sensui123:
Wanted to report back on some strange stuff I'm dealing with on the new pixel 8 pro.

I was away for a month and received the phone at the beginning of June. The only thing I did to the phone was unlocking it, then updating it with a flash-all to the most recent factory image for husky, and then rooting it.

Came back to the phone and installed all my apps and see that the July update was available so decided to try OTA method after reading through the explanation about having both slots fully bootable.....this is where things got very strange.

1) Initially tried to sideload per adb (following all the typical instructions about disabling magisk modules etc) and ran into the error 7 :

Error applying update : 7 (ErrorCode::kInstallDeviceOpenError)

Error in /sideload/package.zip

I read earlier in the thread that it might have something to do a pending OTA that's been downloaded so I rebooted into the OS and saw indeed there was one that there was a stuck OTA. Was going to use the Pixel Flasher to remove it but the download ran into issues with a virus software (that for some odd reason didn't have an easy way to disable temporarily or being able to restore the actual downloaded file vs the cached temp file the browser tried to grab) so I decided to update it via the typical flash-all approach.

2) Took out the -w flag as usual and initiated flash-all......everything went through without errors and the phone went into a full bootloop. It wasn't a typical bootloop as it didn't loop when you saw the G logo in the middle but immediately after displaying "google"......started to get scared about the slot brick scenario at this point.

3) Held the buttons down and manually got back into bootloader and did another flash-all....no success. Was just about to do a flash-all with a wipe until I remembered the Android Flash Tool so gave that a try.

4) Selected the latest public image and unchecked everything. Initially had force flash all partitions but it warned me it would wipe so I took that off as well. And boom, the phone boots up again with the latest updates installed and I quickly rooted with the updated init_boot file without issues.

5) So now I figure with all the updates done and out of the way, I can proceed to do an OTA for the other slot to avoid future slot bricks etc......but going through the sideload option via ADB gives the same error 7 as back in #1......I even tried flashing the init_boot back to stock to see if it would make a difference and no dice. I also redownloaded the OTA file and double checked the SHA-1 on both the initial download and the new download, no difference.

Could someone advice possible options at this point to move forward? I'm not exactly sure what's missing and maybe I'm just missing something from a late night. Will also try things in the office tomorrow at a different computer to see if it makes a difference. Thanks for reading and helping out in advance.
[Google Pixel 8 Pro] badabing2003:
That's because you never cleared the other slot where OTA is being sideloaded to.

All these flash_all or Android flash tool flashing is all happening directly on the active slot, leaving the problem you had with the inactive slot still there.
[Google Pixel 8 Pro] sensui123:
Thanks for getting back to me so quickly and reviewing.

I guess the next question would be is pixel flasher the only way to clear the other slot (I'm assuming you mean a pending ota and it makes sense since it switches slots everytime an ota is initiated)?

Makes sense about operations on current slot with update command (flash-all batch file) and Android Flash Tool but do you have any insight on what caused the bootloop after the manual fastboot command? Trying to understand for the future. Thanks.
[Google Pixel 8 Pro] badabing2003:
I'm not aware of any tool that does that, and PixelFlasher can only clear it if your system is bootable (adb mode) and rooted.

If your device is rooted and in adb mode and you flash OTA (sideload) in PixelFlasher, it will do the clearing the OTA prior to sideloading (automatically).

As for what caused the boot loop, hard to guess without seeing the log output of flash_all command.

There's a reason why it is now recommended to sideload OTA over factory flashing ;)
[Google Pixel 8 Pro] roirraW "edor" ehT:
Update to my last update where I thought I managed to fix my wake-up alarm going off on my phone to actually alarm on my Pixel Watch 2. It's still broken for me, after all.

I can set a manual alarm to test any time on my phone during the day (silent, but vibration only), and it'll respect the "Adaptive" or "Both Phone and Watch" setting. I just tested this again right now.

But my alarm to wake up in the morning, despite me having my Do Not Disturb schedules set to be turned off (not just temporarily bypassed) by alarms, won't go off on my watch - not even just delayed. I've also triple-checked how I have my watch

I had previously even tried having the DnD schedule set to turn off at the very same time that I have my wake-up alarm set to, without any change in behavior.

My last resort, and I'd rather not do this, is now I have DnD set to turn off one minute before my alarm. There's a greater than zero chance that as soon as DnD turns off, a loud notification will be triggered by overnight emails and other things. I could configure the Automate app to disabling GMail syncing for a few minutes after the normal wake-up time, and disable audible notifications for some other apps like Swift Backup that I have run in the middle of the night, but I'd rather not do that.

We'll see what happens tomorrow.

(As a refresher, this whole conundrum started when I had to factory reset my phone, then had to factory reset my Pixel Watch 2 since Google's built-in capability to switch an already paired watch to a new device is broken for many people. I have my Pixel Watch 2 - and the phone's Clock app set to sync everything, although for some reason when I check the Alarm app on the watch, there's only a single one of my phone alarms that's showing up there, currently. So bizarre. I've tried so many things to fix this, and I think I even had factory reset the Watch an extra time, but I don't want to have to set my phone back up yet again, so I'm not factory resetting that since I'm not convinced that'll fix it, either.)
[Google Pixel 8 Pro] sensui123:
Downloaded your Pixel Flasher to play with in this situation on another computer (that I regularly usd ADB/fastboot commands on so I know the drivers/cables are good etc). First thing I noticed was the "cancel OTA update" option was grayed out.. Downloaded the latest OTA again and used Pixel Flasher to process the OTA. Got the same error and exit code (#7) and rebooted me back to the system. One thing I noticed is under the console debug screen it says my device isn't rooted (which is strange because it clearly is through a manual flashing of init_boot with a patched magisk img):

Device Model: husky

Device Active Slot: a

Device Mode: adb

Device Name: Pixel 8 Pro

Device First API Level: 34

Device Version End Date: October 2030

Device Security Update End Date: October 2030

Has init_boot partition: True

Device Bootloader Version: ripcurrent-14.5-11693900

Device is Rooted: False

Device Build: AP2A.240705.005

Device API Level: 34

Android Version: 14

Android Name: Android 14

Android Codename: Upside Down Cake

Android Release Date: Q3 2023

Android Latest Update: Present

Device Architecture: arm64-v8a

Device Kernel: Linux localhost 5.15.137-android14-11-g316696f1d1a4-ab11798290 #1 SMP PREEMPT Fri May 3 09:41:21 UTC 2024 aarch64 Toybox

Device Kernel Version: 5.15

Device KMI: 5.15.137-android14

oem_unlock_supported:

sys_oem_unlock_allowed:

ro.boot.flash.locked: 0

ro.boot.vbmeta.device_state: unlocked

ro.product.first_api_level: 34

ro.boot.veritymode: enforcing

ro.boot.verifiedbootstate: orange

ro.secure: 1

ro.zygote: zygote64

ro.vendor.product.cpu.abilist: arm64-v8a

ro.vendor.product.cpu.abilist32:

Magisk Manager Version: 27.0:27000

Checked for Package: com.topjohnwu.magisk

KernelSU App Version: :

APatch App Version: :

Any insight on how to get me on the OTA train? Kind of a strange case no? Thanks.
[Google Pixel 8 Pro] badabing2003:
Yep, OP
[Google Pixel 8 Pro] sensui123:
Thanks for that......that got the root recognition working properly. Did the cancel OTA command and got this back:

2024-07-15 15:01:50 User Pressed Cancel OTA Update

Pushing local file: C:\Users\...\AppData\Local\Temp\_MEI249242\bin\update_engine_client to the device: /data/local/tmp/update_engine_client ...

Return Code: 0

Setting permissions 755 on /data/local/tmp/update_engine_client on the device ...

Return Code: 0

Cancelling ongoing OTA update (if one is in progress) ...

Resetting an already applied update (if one exists) ...

Initiated the OTA through PIxel Flasher (and as you stated, it did the clearing again for good measures on the console) and it got through the verifying part without errors! Should be gravy from here. Thanks for the help and apologize for not reading the initial instructions about the root portion of Pixel Flasher. Appreciate the fine work on the app.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Google System Release Notes - Help

Google System updates make your Android devices more secure and reliable and give you new and useful features. They include updates from Google to the Android operating system, Google Play Store, and

support.google.com

In other news, my Pixel Watch 2 still didn't go off when my phone's wake-up alarm did, even though I had DnD turn off a minute before the alarm would, and that other test alarms I set sync to the watch just fine.

Next step: experiment with wiping the Clock app's data.

Edit: Wiping the Clock app's Cache and Data did the trick. Every alarm is syncing as normal now. I used Google Lens on extended screenshots of my dozens of alarms I keep handy, so I can copy-paste the descriptions onto the phone using ScrCpy.

Edit 2: And done! All alarms that mattered copied back to my phone and set, and the watch reflects all of them being synced.

Since the issue seems to have been caused by using USB-C wire data transfer from my Pixel 7 Pro to the 8 Pro, and I expect the cloud restore also might have the same issue, it'll be interesting to see what happens in the future - of course, I don't expect to be upgrading for another six years - or at minimum two years from now, but there may be some reason to factory reset my 8 Pro again sometime.

I had even first tried a Swift Backup of my Clock app data, wiping the app data, then restoring it, but of course, it was only fixed after wiping and before restoring.
[Google Pixel 8 Pro] Lughnasadh:
FCC moves forward with rule to unlock phones within 60 days​

FCC moves forward with rule to unlock phones within 60 days

The FCC recently proposed a new rule requiring all wireless carriers in the US to unlock phones within 60 days of activation.

www.androidheadlines.com
[Google Pixel 8 Pro] roirraW "edor" ehT:
Pixel Satellite SOS is coming, but it won’t be free for long (APK teardown)

Google is working on satellite connectivity for Pixel devices through the Pixel Satellite SOS feature, and it could be free for only a while.

www.androidauthority.com
[Google Pixel 8 Pro] roirraW "edor" ehT:
Might be of interest to some users:

Releases · chiteroman/PlayIntegrityFix

Fix Play Integrity (and SafetyNet) verdicts. Contribute to chiteroman/PlayIntegrityFix development by creating an account on GitHub.

github.com
[Google Pixel 8 Pro] r0ni3:
I have a working installation of the latest beta on slot B (root).

If I try to change slots, it obviously won't boot.

Putting the old slot back in, everything is ok.

What do you recommend me to do to have everything working on the second slot as well?

Do I change slots and flash with pixelflasher? (OTA or Factory?)

I think factory is right, but I don't want to lose data.

What do you recommend me to do?