yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] Shmackitup:
I too am stuck on the boot screen using latest Magisk and patched init_boot.img

I've used ADB Shell to remove all Magisk modules and still no luck.

I've reflashed the stock image and re-patched init_boot and re-installed Magisk multiple times.

If I flash the stock init_boot.img it will boot right up but without root. I'm glad to see that I'm not the only having this problem but would certainly appreciate any suggestions on a fix other than wiping data and starting from scratch. Thanks in advance!
[Google Pixel 7 Pro] RulingCzar:
Same situation here, using PixelFlasher, stuck in a boot loop. I wish I had to the foresight to look at the forums before I attempted the update. I'm hoping some kind soul comes up with a solution that does not require wiping.
[Google Pixel 7 Pro] badabing2003:
Submit a support file in a PF thread and I'll take a look, I don't want to derail this thread to side topics.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Google rolls out the Pixel 8 Magnifier app to older models

The app is a valuable accessibility function, designed to make small, dimly lit or distant text easier to read.

www.androidcentral.com

Magnifier - Apps on Google Play

Zoom in, brighten, and adjust contrast to aid your vision.

play.google.com
[Google Pixel 7 Pro] supermansaga:
Has this issue been resolved? Don't want to remote in on my folks' phones and then brick them as I mull upgrade to A14. Thanks
[Google Pixel 7 Pro] RulingCzar:
Not as of yet, I just posted the support file requested.
[Google Pixel 7 Pro] badabing2003:
Answered here.
[Google Pixel 7 Pro] synesthete:
Is anyone else having bugs with Google Camera on Android 14? It seems that rotating the device to landscape orientation (and maybe switching between camera and video) causes the camera button to stop working.

On the plus side, my battery life has been incredible after the update. My phone has lasted close to 2 days on one charge. When I got home at 1:30 am last night after a day off IDT it was at 70% and it's 8:50pm the next day and I'm down to 17%.
[Google Pixel 7 Pro] mochamoo:
While I was hoping to be able to just do a "dirty" flash I went ahead and did backups of the important things (see post #7) Good thing. I ended up with bootloops and at some point I said screw it and wiped it. A pain but think that I am good to go now.
[Google Pixel 7 Pro] Ghisy:
For those having troubles with PF, maybe try to use adb with manual commands to flash the factory image (with the -w removed in the script to avoid wiping)?

That's what I use to update and it usually works fine.
[Google Pixel 7 Pro] Shmackitup:
I tried it with and without PF and got the same results. I just tried downgrading to A13 but that was a bad idea. I just wiped data and am reloading A14 from scratch. I hope it works this time!

Edit: It worked using PF and Wipe
[Google Pixel 7 Pro] Ghisy:
Oh man, that sucks 🙁 Hope next time will work!
[Google Pixel 7 Pro] mochamoo:
I've only ever used adb method. First time with boot loops. All good after wipe. Magisk up and running.
[Google Pixel 7 Pro] fk4mil:
Why Evolution X / CrDroid etc. have 4CarrierAggreation for my Carrier Play Poland. Why stock a13 and a14 only 2CarrierAggreation? How can I unlock it?
[Google Pixel 7 Pro] savergiggio:
Yes sorry i meant 26.3... no i flashed it without wiping, dirty installation
[Google Pixel 7 Pro] RulingCzar:
I was able to flash stock and boot as expected. Patching/Flashing magisk results in the inability to boot all the way so unless they have weird modules or are even rooted I wouldn't worry too much.
[Google Pixel 7 Pro] supermansaga:
They were rooted to enable 5g. I would say very few weird modules, be it LSPosed or Magisk itself
[Google Pixel 7 Pro] Shmackitup:
Yeah, I'm up and running after wiping, flashing and rooting w/ PF.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Just letting you know that I haven't had any trouble with the camera app. Shortly after I updated to Android 14 Stable, there was a camera app update from the Play Store, too.
[Google Pixel 7 Pro] synesthete:
Thanks for letting me know. Maybe I just haven't received the latest camera update.
[Google Pixel 7 Pro] roirraW "edor" ehT:
The one thing that made it obvious to me that it was updated was the Night Sight was no longer on the far left, it was immediately to the right of the default "Photo". (and I'm glad, too, because I use Night Sight often)

You're welcome!
[Google Pixel 7 Pro] synesthete:
I figured out the issue. The app "Repainter" was causing the problem. After turning it off, camera is working fine.
[Google Pixel 7 Pro] rester555:
The manual way to return to stock is flash the correct factory image (A14 for me) with adb flash-all.bat full wipe (-w in script) batch file and then relock the bootloader with adb commands correct?

Also, I am using the latest platform tools to update the last couple of updates. Is the earlier version 33.0.3 still recommended?

EDIT: It seems like both 33.0.3 and 34.0.4 both work based on past comments.
[Google Pixel 7 Pro] simplepinoi177:
Is there a particular reason you are re-locking your bootloader? I've recently been a part of some discussions where there were some misinformed members believing they had to relock their bootloaders just to run an OTA from the stock system updater or to update A14 in general....it's the only reason why I'm asking (just for confirmation)...

But looking at your posting history it looks like you're planning on trading in your device so I have to assume you're relocking in preparation to trade-in. In my experience, Google will take a device even with an unlocked bootloader. But if you are insistent on relocking it, I really do suggest Android Flash Tool...I've seen too many instances of Pixel users permanently bricking their device re-locking their bootloader. As Android Flash Tool is an official tool, it's the least likely option that would brick the device -- it is the official tool after all so it really should be "keyed into" the device/Pixels -- with the best chance at successfully accomplishing it. It's what I ended up doing to my Pixel 5 for my Pixel 7 Pro trade-in. I was really wary of re-locking the bootloader after reading so many horror stories over the years (since the beginning of the Pixel 2), but it was a breeze as I could take confidence in the official tool (that it would do everything absolutely correctly) and it pretty much did everything for me....

Just my 2 cents....good luck to you!
[Google Pixel 7 Pro] rester555:
Yes, it's in preparation for the trade-in. My trade-in is going with Best buy. I wonder if they will allow turning in a phone that has the bootloader unlocked but the phone is fully stock.
[Google Pixel 7 Pro] Ghisy:
I don't like the fact they switched the pictures and front/back camera switch shortcuts at the bottom. I'm used to pictures (photos album or whatever you call it) being on the right, now it's on the left. I don't even see the reason for this change... Muscle memory needs a refresh now!
[Google Pixel 7 Pro] pp085ster:
Couldn't agree more. Change for the sake of change... not unheard of when it comes to Google.
[Google Pixel 7 Pro] Ghisy:
Yeah, that's Google in a nutshell nowadays, huh? 😑
[Google Pixel 7 Pro] roirraW "edor" ehT:
That's one way, yes.

Some users have still had problems when using 34.0.4. If you have any doubt, I'd stick with 33.0.3.

Someone forced Pixel 8 Pro's special camera features to run on Pixel 7 Pro

A series of posts made on X (formerly Twitter) reveal the Pro Controls from the Pixel 8 Pro reportedly running on a Pixel 7 Pro. The feat was made possible by modding the Google Camera APK.

www.neowin.net
[Google Pixel 7 Pro] roirraW "edor" ehT:
I agree with you, too. What the heck!?
[Google Pixel 7 Pro] kornball:
Was out of town for the weekend and unable to update my P7 to A14. Was excited to try today, but it seems some folks over the last few pages of this thread are having issues and experiencing bootloops? That makes me a bit hesitant now ugh. I already have Displax's 1.3 module working properly with the September A13 update.

I'm still using platform tools 33.0.3, and my typical process would be to patch the A14 init_boot.img with Magisk 26.3. Boot into bootloader, fastboot flash the A14 bootloader, reboot bootloader, flash the radio, reboot bootloader, and flash the update with --skip-reboot flag. After that's done, I flash the patched init_boot.img and boot into Android.
[Google Pixel 7 Pro] justDave:
The media went crazy with rumors that Apple might change the end call button.

Google on the other hand moves the call answer button while you're trying to press it.
[Google Pixel 7 Pro] roirraW "edor" ehT:
All I can speak to is that I had no problem updating and booting after flashing the Magisk'd init_boot.img.
[Google Pixel 7 Pro] simplepinoi177:
Oh if it's to BestBuy, I could see your concern...

You never know how the workers (not so informed as Google one's might be) will react to an unlocked bootloader (as it is not stock) rather than the one's at Google. I'm sure it all ends up in the same place -- in the end it will be on a Google service center's worker -- and BestBuy will get whatever credit they get, but then again returning it straight to Google would have it like "Well...even if it's not absolutely stock state, it's here already and we can easily lock it as needed. We probably would in any case", where BestBuy they are not central or the endpoint of the return/trade-in and might freak out and put up a fuss (without knowing better; I mean, all it would take is one simple phone call, but again, it's BestBuy and their employees)....

So, if that's the case, again, you can't go wrong with Android Flash Tool

From what I read, once you upgrade successfully, the Displax MOD_1.3 module works just as properly on A14 October update as it does September A13.....

But I share your hesitation -- what's most concerning to me is that I've read similar issues/bootlooping whether upgrading manually or even using PixelFlasher! -- that I am pushing off a bit just to see if there are any more reports that come of it and/or if it gets figured out before I take the plunge.

As with any update/upgrade, just be sure to make all the prerequisite backups in case a wipe is required is all....it's what I plan to do (do every month; I mean, I'm going through the process of manually updating, I might as well spend the 40 minutes extra to backup as well)...
[Google Pixel 7 Pro] badabing2003:
All the reported issues that I have investigated turned out to be related to one or many of

keeping Magisk modules enabled before proceeding with the update, and some modules not being compatible.

using outdated Magisk (use latest)

Android platform tools related, I recommend 33.0.3 on all platforms except Macs for which I recommend 34.0.4

Driver / connection / port issue

None of these have anything to do with either using PF or doing things manually, these requirements apply to any update and are nothing new.
[Google Pixel 7 Pro] rester555:
With the newer bootloaders, is everyone flashing to both slots for A14?
[Google Pixel 7 Pro] badabing2003:
I have, but not everyone, but it doesn't hurt if you do.
[Google Pixel 7 Pro] kornball:
What do you use for making your backups? Something like Swift Backup?
[Google Pixel 7 Pro] simplepinoi177:
yes Swift Backup (mainly), SMS Backup & Restore, Google Account sync, and I just learned of a Backup and Restore Magisk Module that's supposed to be very similar to nandroid backups that I think I'll try considering the major OS version update (and of the reports of bootlooping)....

Hope this helps...
[Google Pixel 7 Pro] Fishawy:
Very interested in this! Any link?
[Google Pixel 7 Pro] simplepinoi177:
I bookmarked it HERE, but here's a quote to the post I saved anyways

I read, though, that unfortunately the developer passed away this past August, so I'm unsure where development will go from here and/or how well it works from here on out....

Hope this helps!
[Google Pixel 7 Pro] Fishawy:
Thank you for that, and I'm really sorry about the dev's passing. Our thoughts are with their family and friends in this difficult time.
[Google Pixel 7 Pro] Ghisy:
Anyone using Nova Launcher Prime 8.0.6 on A14? I have a weird random bug with the recents screen but I was told recents are handled by the stock launcher on their Discord. True, I actually forgot about that.

Here's a screenshot of what happens randomly: Nova appears as a regular app I can swipe away. It doesn't do anything if I do but it's just weird it's showing up at all in recents. Guess it's a Google bug? 🤔
[Google Pixel 7 Pro] rester555:
Pixel flasher worked for me. I am now on Android 14, rooted. Now to see how this safety net stuff works. There's seven pages of you guys trying to figure out what was the right method.
[Google Pixel 7 Pro] rester555:
Here to report that installing play protect magisk module v9.2 worked for me. I have certified play store and pass CTS and basic integrity.
[Google Pixel 7 Pro] badabing2003:
Works for me.
[Google Pixel 7 Pro] albsat:
I disabled my magisk modules. Updated to android 14. Everything works great. The notification sound option is so welcomed for me. However I don't get how comes that Google thinks that back button should be on left for me. I hate to install a magisk module just for this option. I want the back option on the right side at navigation bar.
[Google Pixel 7 Pro] joro666:
I'm currently also on the July update and rooted. Should I update to the latest September version and then to A14, or can I directly install (throug flash tools)A14 without losing root or breaking anything?
[Google Pixel 7 Pro] Jon.StatiK:
Trying to use the AndroidFlashTool to update the phone, everything Magisk is disabled. Selecting the A14 public branch and it keeps choosing Japan? There's no way to change it either, should I be concerned?
[Google Pixel 7 Pro] kornball:
I was able to update to A14 with my usual method, but I now see the play store no longer lists the device as certified. I imagine the typical procedure is to clear cache/data for the Google play store and reboot. Anyone else experience this and can confirm this will fix the issue? I am using Displax's 1.3 mod.
[Google Pixel 7 Pro] rester555:
You can update straight to A14. That's what I did from July update.
[Google Pixel 7 Pro] rester555:
If you look back several pages, a bunch of people are having issues with safety net. Right now there is play store fix and safety net fix. I am using the play protect fix 9.2 and can use all my apps.
[Google Pixel 7 Pro] kornball:
Ah okay thanks. So I'll need to use both modules. Thank you for clarifying!
[Google Pixel 7 Pro] rester555:
No I just used the play integrity fix not display 1.3
[Google Pixel 7 Pro] kornball:
As a data point for others, simply clearing the cache/data for the Google Play Store allowed my device to be seen as 'certified' once again. Using Displax's mod 1.3.
[Google Pixel 7 Pro] rester555:
I did the same method and it eventually certified at first but did not persist.
[Google Pixel 7 Pro] kornball:
Wow, good to know - thank you. I'll certainly keep an eye on it.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I don't use the Flash Tool site much, except when I'm returning a phone to completely stock unrooted with bootloader locked, or trying to fix a weird issue, so I don't know what you would experience if you let it flash the firmware made for Japan.

If it were happening to me, I would use the factory image and Platform-Tools 33.0.3 (to be safe) instead.

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

Personally, I've noticed most of the time that when another user experiences trouble with the safetynet fix after updating their phone, and all the other workarounds (clearing Play Store data and cache) don't work right away, waiting a few hours and checking again usually does the trick.

I know you've solved it for now, but I just wanted to let you know that it's common that there are issues immediately after an update, but it usually goes away without much or any effort.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Google Pixel phones are getting a bunch of funky new ringtones

Custom ringtones: still very much around.

www.theverge.com
[Google Pixel 7 Pro] mac796:
Same thing happened to me no matter what I did it would pick Japan. I ended up using the pixel flasher for the first time. Was very simple. My root didn't stick after a reboot with the pixel flasher maybe something I did. Just re flashed patched boot with platform tools and all good again.
[Google Pixel 7 Pro] Lin_Not_Nothern:
Hi ,I had updated my pixel 7pro to a14 stable ver ,and i am going to root it .I don't know where the stock a14 rom is? i looked up the web and the link. But it just for a13(I didn't see anything that say it a14)

Build:UP1A.231005.007

Pls give a link that has stock rom ,i would thanks a lot for it
[Google Pixel 7 Pro] simplepinoi177:
A lot of people have been bringing up/complaining of not seeing the latest factory images....

It's been determined a while back that unless you look at the US page (.com) -- unlike .nz (New Zealand) .fr (French) .au (Australia), etc. -- the latest does not show, for whatever reason....

That's probably the reason....check if it's that...
[Google Pixel 7 Pro] Lin_Not_Nothern:
Thanks for your help ,it really helps me a lot. You have to switch to en page to find ,on other lanugage pages it wouldn't show up.(What a google "thing")
[Google Pixel 7 Pro] swieder711:
Great success.

Bootloader unlocked, newest factory image flashed (.31), rooted init_boot with latest Magisk stable (25200).

Now restoring all my apps with Swift Backup.
[Google Pixel 7 Pro] LLStarks:
I have my regular 7. Time for fun.

Just waiting for the T-Mobile unlock to go through.
[Google Pixel 7 Pro] Bologner:
Folks, don't follow the instructions on the Magisk install guide, disabling verity and verification on `vbmeta.img` seems to have bricked my P7Pro. Phone doesn't boot at all, computer will chime when I plug it in, but will do the unplug chime shortly after, but will chime if I hit the power button.

I should have came here first.
[Google Pixel 7 Pro] v12xke:
Trying to help... can't you just extract the stock vbmeta.img and flash over it? you can also relash the stock init_boot.img if necessary.
[Google Pixel 7 Pro] pijiman:
So far every single application I backed up with Swift Backup either crashed on restore or simply ignore all my previous data and configurations. Am I missing something? I do know that some apps like Signal or banking apps can detect a device change and there's no way around that, but Firefox wouldn't restore my configs, for example :(

Both phones are rooted
[Google Pixel 7 Pro] exocetdj:
Great guide

Anyone been brave enough to try AOSP mods and lsposed yet? o_O
[Google Pixel 7 Pro] Larakali:
Here we go.

EDIT:

Netflix L1 Widevine pog?????????????
[Google Pixel 7 Pro] V0latyle:
Since init_boot is patched instead of boot, I wonder how to temporary boot a patched image?

Also, I did a quick Google search on "root pixel 7", and the first few "guides" that came up are wildly inaccurate. I would say to expect people to come pouring in for help, but experience has shown me that people seem to prefer Reddit for some stupid reason...
[Google Pixel 7 Pro] Bologner:
I would try if I could get the phone to even boot.
[Google Pixel 7 Pro] xChickens:
I've installed both, and they seem to be working well.

@roirraW "edor" ehT I know you thumbs upped, but not sure if you meant to confirm or not. I'm currently not using MHPC and Google Wallet seems to be okay.
[Google Pixel 7 Pro] v12xke:
Please confirm you cannot boot to fastboot mode using the power+vol(-) buttons. Alternatively, If you can get to the recovery menu, select reboot bootloader
[Google Pixel 7 Pro] exocetdj:
thanks bud :cool:
[Google Pixel 7 Pro] Bologner:
Oh yeah no dice, I've tried holding the power button by itself, I've tried Power+Volume Up, and Power+Volume Down, I've tried all of those while the phone is plugged into a computer as well, nothing will boot the phone.

I've been flashing Android since I had an HTC Touch Pro 2, so it's very embarassing for me that I just YOLO'd a flashing command and bricked the phone
[Google Pixel 7 Pro] wrongway213:
Both are working for me
[Google Pixel 7 Pro] Renate:
Oh, great.

After them beating us up with Android image header versions #0, #1, #2, #3 and #4, we have none of the above!

I guess that Magisk has this figured out if people are modding on it.

FWIW, it's a headerless (except for ANDROID! and a size) file with decompressor stub and payload and AVB signature and footer.
[Google Pixel 7 Pro] Displax:
Can someone with rooted Pixel 7 send full getprop output? Just type in terminal:

su
getprop > /sdcard/getprop.txt

Or same from adb shell:

adb shell
su
getprop > /sdcard/getprop.txt

Thanks.

And output from unrooted device (locked bootloader) may be helpful too.
[Google Pixel 7 Pro] exocetdj:
Great to hear and happy to report the same here too
[Google Pixel 7 Pro] Larakali:
https://pastebin.com/raw/eYDMdhHL
[Google Pixel 7 Pro] Annie the Eagle:
I have made the plunge and rooted. I've installed Magisk Stable (25.2) and patched my init_boot.img, then flashed it over to init_boot partition and all is working good!

The device uncertified setting on the Play Protect area has disappeared on Play Store (it doesn't say Uncertified, but it doesn't say Certified either!)

I can see Netflix, Revolut, etc despite only have "BASIC" integrity on YASNAC.

I am going to set up my banking app and Google Pay now (will edit how it goes) and test tomorrow at the coffee shop.
[Google Pixel 7 Pro] bosox284:
From a rooted device. I can unroot if nobody gets you one soon too, I haven't done any setup yet.
[Google Pixel 7 Pro] NCVol:
I just upgraded to A14. I used the safety net fix mod 1.3 by Displax and it's working to pass the checks. There's a version 2.0 but I've seen reports that it doesn't work for some. I just wanted to share in case someone is looking for a solution.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Disregard. It would happen that I actually quickly adopted the new version for once, and the developer of AOSPMods says that the new LSPosed breaks some things so avoid updating for now.

New LSPosed version at the GitHub link. Mentions a crash with Android 14.

LSPosed Xposed Framework [8.1-13.0]. Simple Magisk Module

Developers: LSPosed Developers Homepage: GitHub ✱ Requirements: • Magisk 21+ • Android 8.1-13 • Riru(NOT NEEDED) USE ZYGISK Description: Riru module providing ART interception framework (natively for Android Pie) that provides consistent API...

xdaforums.com
[Google Pixel 7 Pro] xflowy:
Would someone be so kind an drop me the command line to disable all magisk modules in fastboot mode?
[Google Pixel 7 Pro] Ghisy:
Thanks for the tip! I'm always weary of new LSposed versions. I usually wait to update.
[Google Pixel 7 Pro] roirraW "edor" ehT:
See post 3 in this thread.

I've got several helpful tips about that kind of thing. I think those items are near the bottom of post 3.

Edit: forgot which thread I was answering in. 🤣

Edit 2: Corrected to say Post 3, not Post 2. Sorry about that.

Post #3 - Other, most important resources:

Find problem apps, Magisk, and LSposed Modules by (three different methods)

You're welcome! Me, too, as a rule, for everything. 😁
[Google Pixel 7 Pro] roirraW "edor" ehT:
Actually, the information you need is in Post 3, not Post 2, as I said earlier:

Post #3 - Other, most important resources:

Find problem apps, Magisk, and LSposed Modules by (three different methods)
[Google Pixel 7 Pro] mac796:
I updated to 1.91zygisk. I noticed there's a 1.92 lsposed. I had some problems with screen freezing after I updated to Android14 and setup aosp. Wonder if I should be on a different build?
[Google Pixel 7 Pro] xflowy:
Thanks! I found the command for disabling from a reboot. Just out of curiosity: isn't there no command to do that in fastboot?