yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] simplepinoi177:
It seems you are not in the US, but if you were or were raised/lived here....

It seems Google is adopting the practice of car dealerships and car manufacturers...."the second it's off the lot, it loses 10% (or more IMO) of it's value" and continues -- maybe not at that rate, but considerably more than you'd expect.

Google, you are

NOT

Apple yet! (or even close to in the US) Just because you have an ecosystem, doesn't mean you are there yet nor are your customers (or even that many people in general) are

that

locked into it! Being a monopoly search engine (to the point of being your own verb) probably got into their heads (among all the other things/crap)...!

Yes, I paid $1200 for my Pixel 7 Pro 512GB, and would only get $420 a year later? A single model year prior....get out of here....very easily to be insulting as they are really insulting our intelligence. I mean, we are more tech savvy than most of the iPhone sheeple, you would think insulting our collective superior (in just tech) intelligence....

I like @roirraW "edor" ehT 's tactic of comparing the best trade-in values and getting crappy ones on Swappa....
[Google Pixel 8 Pro] diesteldorf:
I bought 1 from Gazelle and traded it last year for $430 to my Pixel 6 Pro. I paid a little extra for a "good" one to increase the chances of getting the full $430.00.

Worked like a charm and saved me around $175-$200.

Prior to placing my Pixel 8 Pro, I was shocked when I saw the Iphone 11 was valued $10.00 higher at $440.00...Yes, I ordered another "Good" one from Gazlle and will immediatly trade it back to Google when my envelope arrives.

Next year, when the Pixel 9 Pro is released, I'm fully expecting the Iphone 11 to fetch $500.00 or more......Joking
[Google Pixel 8 Pro] Lughnasadh:
Google confirms Pixel 8 series has a new main camera sensor, likely Samsung ISOCELL GNV

Google Pixel 8 and Pixel 8 Pro have a new main camera sensor, but the company won't say what the exact model is.

9to5google.com
[Google Pixel 8 Pro] Paz9:
Given that AVB/verification doesn't need to be enabled on the p7 for new kernels would it be safe to say we can leave this on when the 8 arrives? Or be safe and disable?
[Google Pixel 8 Pro] roirraW "edor" ehT:
Do you mean that Verity/Verification doesn't need to be

disabled

on the P7/Pro for custom kernels (instead of enabled, as you wrote)?

And if this is the case, that's awesome news for the P7/Pro. Hopefully, it'll translate to the P8/Pro as well.

Edit: Kirisakura still says they have to be disabled on the P7P, so I'm very curious if you can share where the news is from.

Edit 2: Now I see news about that here:
[Google Pixel 8 Pro] Lughnasadh:
As far as I know, Sultan's kernel is the only one so far that doesn't need verity and verification disabled. Maybe others have or are planning to implement it that I'm not aware of though.
[Google Pixel 8 Pro] Paz9:
Freak implemented it in kirisakura as of 2.0 which just recently dropped.
[Google Pixel 8 Pro] Lughnasadh:
I used it to flash QPR1 Beta 2.1 (without wiping, via flash-all & using Windows) and it worked just fine. Interestingly, it uses fastbootd again where the previous 34 versions didn't. Maybe this will help Mac users??? Saw someone else report that wiping did indeed work with 34.0.5 when using flash-all.
[Google Pixel 8 Pro] Bofahad:
Thx ✅
[Google Pixel 8 Pro] roirraW "edor" ehT:
I had to pop in on XDA long enough to post this:

Platform-Tools v34.0.5 (no changelog yet, and not tested by me):

SDK Platform Tools release notes | Android Studio | Android Developers

Android SDK Platform-Tools is a component for the Android SDK.

developer.android.com

Direct download links:

https://dl.google.com/android/repository/platform-tools_r34.0.5-windows.zip

https://dl.google.com/android/repository/platform-tools_r34.0.5-darwin.zip

https://dl.google.com/android/repository/platform-tools_r34.0.5-linux.zip

Edit: Also, this comment from https://issuetracker.google.com/issues/268872725:
[Google Pixel 8 Pro] b0uNz:
tested Platform-Tools v34.0.5 with Pixel Flasher, 14.0.0 (UD1A.230803.041, Oct 2023) flashed with patched boot.img and verity, verification disabled. works fine.
[Google Pixel 8 Pro] LLStarks:
There's been a bit of a breakthrough in understanding the service and engineering modes on this phone. Might not need to rely on ShannonDM or Network Signal Guru anymore for hidden menu access. It looks like it still requires root but it would be a reimplementation of what Vivo does for their Exynos phones.

Reference: Shannon Telegram
[Google Pixel 8 Pro] stu5797:
All you have to do is follow the OP's instructions line by line. It seems as though your drivers are not installed correctly
[Google Pixel 8 Pro] roirraW "edor" ehT:
@almahix. I don't know if you noticed, but you typed your reply inside where you had quoted a message by me, replacing the quote of my post instead of typing your reply below it.

This is on a Windows PC, correct? What does Windows' Device Manager show for your phone after you adb reboot bootloader? A screenshot of your phone's entry in Device Manager after you rebooted the phone into bootloader mode would be best. You followed the directions (also in Post #2) about installing the drivers potentially twice, once while the phone is running and once in bootloader mode?

After you reboot into bootloader mode, what does fastboot devices say?

You have OEM unlocking and USB debugging enabled in Developer options? When you adb reboot bootloader, you authorized your device for receiving adb commands from the computer? FYI, that authorization timeouts by default, after I think a week, but you can disable the timing out of that in Developer options, as well.

What error message do you get when you do fastboot flashing unlock while in bootloader mode?

Apologies if you've answered some of this before - right now I've got a lot going on, and so I haven't been very active on XDA for a little over a week now, and I'm not exactly sure when I'll be able to resume as much activity as I had in the up until recently.
[Google Pixel 8 Pro] almahix:
Thanks so much for your reply. Fastboot devices shows a 14 character alphanumeric string. In bootloader mode and when booted.

"Fastboot flashing unlock" does not give an error message, but it displays the possible uses of the fastboot command, as if "flashing" isn't understood.
[Google Pixel 8 Pro] roirraW "edor" ehT:
You're welcome! I'm going to jump ahead and guess that maybe you have an old version of Fastboot somewhere, and you're using that by accident.

What version of the platform tools are you attempting to use?

Do you have the command prompt open in the same folder that you have the latest platform tools extracted in?

Try the Fastboot command using its entire path, such as (include the quotes "):

"C:\Users\your profile name\Downloads\platform-tools\fastboot.exe" flashing unlock

to ensure it's using the copy of Fastboot that you're intending.

Maybe we can spot something in a screenshot of your command prompt after having run that, if that doesn't work.
[Google Pixel 8 Pro] almahix:
I'm using platform tools 34.0.5. The platform tools are in the same folder as my command prompt.

I'm sitting here shaking my head in absolute disbelief. I tried again with the command .\fastboot and lo and behold it worked. I am shocked. After everything I've tried it was this simple. Thank you so much for your wisdom and forum leadership. You're A+ in my book!
[Google Pixel 8 Pro] Lughnasadh:
Out of curiosity, were you using PowerShell instead of command prompt?
[Google Pixel 8 Pro] almahix:
No, just plain old command prompt.
[Google Pixel 8 Pro] roirraW "edor" ehT:
You're welcome! Glad that solved it. You should do that from now on unless you figure out the hidden reason.

So it is possible the problem is an old fastboot.exe you have in your command path, although in that case, with the command prompt open in the same folder as Fastboot, I would expect the one in the same folder to take priority. Who knows, though.
[Google Pixel 8 Pro] almahix:
I'm unlocked and rooted. Color me happy and grateful to my fellow members of this and other forums.
[Google Pixel 8 Pro] crisco654:
Just making sure I can still do these exact steps since I'm more familiar with them to root/update my pixel 8 pro. These are the steps I did every time to update/keep root for my Pixel 6 pro-

Reboot to bootloader

fastboot flash bootloader --slot=all <bootloader image> (if needed)

fastboot reboot bootloader

fastboot flash radio <drag and drop radio.img here> (if needed)

fastboot reboot bootloader

fastboot update --skip-reboot image-codename-buildnumber.zip

fastboot boot <patched boot image> (I will patch the image before I update. Also, I know it's init_boot.img instead of boot.img)

Finally, direct magic install.

Also, I saw someone talking about magisk delta. Are there any advantages using that over the regular magisk? Thanks
[Google Pixel 8 Pro] rester555:
Hopefully this puts an end to the using older platform tools moving on. This was ridiculous.
[Google Pixel 8 Pro] simplepinoi177:
Is there a reason why you don't run the flash-all.bat (or flash-all.sh for non-Windows OS) script (making sure to remove the "-w" to not wipe your device)? Why manually the bootloader & radio, and just them?

Additionally, do

NOT

fastboot boot <patched boot image>!!! *you did this on your Pixel 6? The only reason I ever "fastboot boot'd" anything was to temporarily boot into TWRP to install it and/or install Magisk/Towelroot....

You can either "direct magic[sk] install" or, to save a few steps, just do as you did fastboot flash'd bootloader & radio and fastboot flash init_boot <patched init_boot image>
[Google Pixel 8 Pro] crisco654:
Just because I'm just used to doing it this way lol. Also, so I will never run into the problem of forgetting to remove -w(which has come close to happening to me before)

And yeah that's what I did to get root back after updating....fastboot boot patched_magisk_image to get temporary root. And then direct install with magisk. And I did that with every update for my pixel 6 pro, and never ran into any issues.
[Google Pixel 8 Pro] simplepinoi177:
Hmmm...fascinating, but then again, you miss updating the other partitions as well...and I'm sure badabing2003 or someone could assess the risks of having different versions of bootloader & radio with the other partitions....

Really? I've been rooting since Pixel 2 Xl, and I don't recall ever doing it that way.

I guess that is a certain way to update & retain root with Magisk ("Direct Install"), but since the Pixel 7 & up, Magisk's "Install to Inactive Slot" no longer works (in the early days, some have gotten it to work, but for most it causes a bootloop and has since not been suggested in How-To guides) and "Direct Install" is only there after permanently patching the partition (init_boot in this case) -- something about the change to init_boot caused Magisk to not be able to re-apply the original partition and/or returning it back to patched or something like that. There has been new developments with Magisk so I might be out of loop with its capabilities and all of this might be corrected/updated and me wrong now (I believe I heard that you can patch the init_boot.img and apply it directly now, but I can't recall where exactly I saw this so I don't want to say for certain). *what it actually was is that Magisk can directly patch the init_boot.img (or boot.img I imagine; since it can with init_boot.img and knows to restore that image when uninstalling) from an Full OTA image file (and probably the Full Factory image file). In any case, at this time I don't suggest you temporarily boot with a patched init_boot.img -- I don't even believe it will work as it did with the patched boot.img (I'm betting the boot partition is still more central/vital and fundementally different [which is why it still holds the recovery partition] than init_boot) -- and do as the OP directs in this thread; which is to simply fastboot flash it right off the bat -- honestly, it is easier and less steps than doing it from the Magisk Manager app and/or pretty much the same exact thing it would do (flashes the patched image to/over the stock partition) in the app.
[Google Pixel 8 Pro] gururoop:
Any ideas how to get past "There are problems with the security certificate for this server" error? I am getting this every time I try to open LG Thinq app. I already tried clearing the certificate store in settings and also the data/cache of webview.
[Google Pixel 8 Pro] simplepinoi177:
I use that app on my P7P August firmware update and don't get that -- I'm updating to A14 tomorrow so I can't say for certain it isn't because of that. Why aren't you Force Stop and Clear Cache of the LG ThinQ app? If you are willing to sign back in and set everything back up, why don't you try Clear Data as well?

If none of that works, probably all the myriad various root hiding methods may be required...
[Google Pixel 8 Pro] Lughnasadh:
You can't live boot/temporarily root on the Pixel 7 or 8 series because you patch the init_boot image, not the boot image, on these devices. You can live boot a patched boot image, but not a patched init_boot image.
[Google Pixel 8 Pro] crisco654:
Yeah, reading more, it just seems easier for me now just to do the flash-all method. I don't why I try to complicate things for myself haha.

Also, do you(or anyone else) know if delta magisk has any advantages over regular magisk. First time hearing about delta, and now I'm curious
[Google Pixel 8 Pro] Lughnasadh:
I don't use Delta Magisk so can't help you there.
[Google Pixel 8 Pro] almahix:
I've always updated with Android flash tool, then use magisk to fix boot, then boot patched ini, and direct install with magisk. I'd like to find an easier way. I've tried to use pixel flasher but I can't get it to do anything at all.
[Google Pixel 8 Pro] simplepinoi177:
PixelFlasher is truly the easiest and simplest way to go about that (just a couple of clicks and everything is done for you), if you can get it working. You probably have driver issues. You should bring it up in the PixelFlasher thread (I'm sure there's a P8P thread version, but there's always the main thread as well) to find support and assistance.
[Google Pixel 8 Pro] almahix:
I have the pixel 6 drivers; would the 8s be different?
[Google Pixel 8 Pro] badabing2003:
nope, there's only one set of Google published USB drivers.

If you follow the usage guide you shouldn't have any issues, if you do, please bring it up in PF threads.
[Google Pixel 8 Pro] almahix:
I appreciate the courtesy of your reply.
[Google Pixel 8 Pro] Homeboy76:
Does anyone know what was updated on this thread SDK Platform tools release notes on this 2023-10-23 UTC?

Did the update Platform-tools r34.0.5?
[Google Pixel 8 Pro] Pixel86:
I flashed using 34.0.5 on a Chromebook and did not run into any issues.
[Google Pixel 8 Pro] Homeboy76:
Thanks, the reason I asked is, Staff nember @roirraW "edor" ehT at one point had and app/program that could check the date that the SDK Platform-tools zip file was created.
[Google Pixel 8 Pro] roirraW "edor" ehT:
No particular program - I just noticed with one of the 34.x releases - probably the second 34.0.4 release, that the filedates were actually recent - whereas previously, I remember the dates of the files in the Platform-Tools always had the exact same 2008 date. I haven't thought to check the latest package.

So, I was just looking at the date the files had through either Windows/File Explorer, or more likely for me, GPSoftware's Directory Opus (a different Windows file manager I've used for ~32 years).
[Google Pixel 8 Pro] roirraW "edor" ehT:
Found my post:

Ah-ha! You were correct @Homeboy76! You have a better memory than I do. I was specifying what I saw the dates in, since at the time, I had no plans on extracting and using 34.0.4 #2, so I couldn't swear that the newer dates would come out when actually extracting.

At work, a coworker and I had noticed some inconsistencies with extracting some archives where the files inside it had no date at all specified, so the extracting program "made up" a date for them. So I couldn't be sure the file dates were accurate until I actually extracted them.

Good memory, @Homeboy76! And thanks for reminding me about this - I've been so busy lately I completely forgot about this.

Checking now, I see the date on the extract 34.0.4 #2 Platform-Tools files is 7/14/2023, and the date for the 34.0.5 files is 10/4/2023. Thanks again for the reminder, and I've confirmed that the same date appears when extracted and viewed through a file manager.
[Google Pixel 8 Pro] Morgrain:
Battery test results from PhoneArena

It seems that the new panel is paying off

Video:
[Google Pixel 8 Pro] rester555:
The battery and display are much better for me this go around compared to the P7P. As well as the phone not overheating.
[Google Pixel 8 Pro] stu5797:
I have a little issue... I am rooted, stable magisk 26.3, passed yasnac and play integrity, have wallet in the deny list with modules systemless hosts and USNF 1.3 running. I have disabled verity and verification check doing a clean install thru Android flash tool and now I can't get Google wallet to work as it does not meet security requirements. Any help would be appreciated!
[Google Pixel 8 Pro] stu5797:
Figured it out... Needed to clear data and clear cache on Wallet, play store and play services, reboot and it works!
[Google Pixel 8 Pro] roirraW "edor" ehT:
Cha-ching! :) Glad you got it working.
[Google Pixel 8 Pro] ThatOneGuyOverThere:
There might be some hope for 32-bit apps if this can be ported to the pixel:

https://twitter.com/i/web/status/1717916987387469842
[Google Pixel 8 Pro] crisco654:
Just wanted to get clarification on something. If I want to flash both slots while updating every month, I should always do this

And I shouldn't use --slot all(by adding it after each fastboot line in the flash-all file), since the way the factory images are flashed on the 8, rendering the other slot unbootable, it wouldn't work, correct? Just making sure I understand everything correctly.
[Google Pixel 8 Pro] roirraW "edor" ehT:
That is correct. Or at least, as of the extensive testing @Lughnasadh and @badabing2003 did with the Pixel 7 Pro (or was it the 6 Pro?), it's just wasting your time if you use flash-all.bat on both slots, because the only slot that will work is the most recent slot you flashed. I mention the caveat ("at least, as of...") because Google is always changing things behind the scenes without telling anyone, although I'm sure this is likely still true.

If you want both slots to be bootable, use the Full OTA Zip method, which is also in Post #2 below the "Factory Image / Android Flash Tool method" section. I've been using the Full OTA Zip method for months, and with it, both slots are useable at will. You can even leave one slot unrooted if you want.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Modified/added some info to the Post #3 - Other, most important resources:

@siavash79 and @Typhus_'s thread [MOD][Xposed+Magisk][14 Compatible] Pixel Xpert - System modifications for Pixel phones 12+. This is a big one for me, personally.

Alongside Pixel Xpert above, since it removed some Theming options, I'm using and recommend three additional modifications:

@DanGLES3's thread Fullscreen/Immersive Gesture Tweaks for Android 10-14 (most up-to-date version available at the GitHub link in his OP). You configure it while flashing the module using the volume keys. I choose:

- (Immersive)

+ (Hide keyboard buttons - Back/Switch keyboard)

+ (Reduce the size of the keyboard bar)

+ (Pick the gesture sensitivity - Low/Module Default)

+ (Enable Gcam fix)

- (NOT Wish to disable the back gesture)

@Osanosa's [APP][8.0+]Themed Project - I use this specifically just for the Status Bar IconPacks it includes. I prefer "Kai" for the lined Wi-Fi and Mobile Data strength indicators, and the Bluetooth connected icon, but there are a handful of others available.

The Play Store Project Themer · Android 12⁺, I use this for QuickSetting Panel tile shapes, customized Brightness Slider, Notification style, and 100% opacity. This app is a paid app, I paid for it in 2022.

Added those XDA users and @badabing2003 to the Thanks section.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Removed all reference to Platform-Tools v33.0.3, since I think 34.0.5 fixed all the bugs that 34.x had.
[Google Pixel 8 Pro] fijasko:
is there a reason you're not recommending Iconify?

it has almost all the theming options missing from PixelXpert, including statusbar icon packs. it has the option to choose immersive/fullscreen gesture tweaks and the new debug build also has the option to only hide the navbar and use 3rd party gesture app if you wish so.

it also has theming options for QS panel and icons, notification themes, making qs and notification panel transparent etc.

and it's free.

btw, thank you for your amazing guide, it helped me a lot!
[Google Pixel 8 Pro] roirraW "edor" ehT:
The only reason is that I haven't tried it. :) I only stick to what I've tried and tested (at least at some point) as far as what I recommend. Edit: I wasn't even actually looking for something to modify the status bar icons at first - I was mainly looking for Pitch Black and removing the space under the keyboard, so when I was testing various solutions out, the status bar icons were kind of an afterthought for me. Iconify didn't happen to come up in my searches for fixing my issues.

Thanks! I'll try to check it out when I have a chance. I've heard of it, but I just forgot about it when looking for replacements for Pixel Xpert's old features. If I try it out, I'll add it to the post. No guarantees on when I get around to trying it out, though.

You're welcome and thank you! I'm glad it helps. All I'm after is to help other users and to "pay it forward" for all the help I got on XDA over the years.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Okay, you both sold me. I like it. I'll add it as soon as I can get some more sleep.
[Google Pixel 8 Pro] Lughnasadh:
For what it's worth, I've seen several people report success using the "Install to Inactive Slot" method on Pixel 7s in recent months. I've also seen a few failures (reasons unknown).
[Google Pixel 8 Pro] roirraW "edor" ehT:
Added to Post #3:

Mahmud0808's Iconify on GitHub
[Google Pixel 8 Pro] WhiteAsIce:
Just received a P8P from Spectrum. Anyone know the unlock status of this carrier?
[Google Pixel 8 Pro] roirraW "edor" ehT:
I *think* when I looked up what carrier Spectrum uses, it's Verizon, so it may not be unlockable, but if you can enable OEM unlocking in Developer Options, then you're set. If you are making payments on the phone to Spectrum, then you might not be able to find out until after it's paid off whether you can enable OEM unlocking or not, as they could have it locked out until it's fully paid for.

Let us know your experience with trying to get it unlocked.
[Google Pixel 8 Pro] Lughnasadh:
For what it's worth...

how many will update to pixel 8pro?

i am wondering how many of you guys gonna upgrade your phone to pixel 8 pro? there is zero reason for me, as i also have s23 ultra lol

xdaforums.com
[Google Pixel 8 Pro] LLStarks:
It may not be the Verizon variants. The Spectrum regular Pixel 8 is 699 instead of 799 like the special Verizon model with mmwave.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Google is increasingly providing Pixel support on Reddit

Google is increasingly using Reddit to provide product support for Pixel phones. Its use of the discussion/forum site picked up...

9to5google.com