yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] Namelesswonder:
It's patching the kernel binary, but it's included with another block of patches that appear to be for Samsung devices. It's possible that this specific patch is based on Samsung kernels, but patching the kernel in whatever way to want_initramfs instead of skip_initramfs is something that could be done on any kernels. However doing this might not ever work because the bootloader is now the arbiter of the ramdisks with it choosing between the "normal" ramdisk or the recovery ramdisk.

But as you said, the bootloader and kernel could just be ignoring a ramdisk we put into boot.img because it's already set to point to init_boot or one of vendor_boot's ramdisks based on where the device needs to boot to.

I believe the support was added without the knowledge of how it would actually function because it was all added months ago based on documentation, and the only device using this new scheme in practice is the Pixel 7.

As for upgrading devices to use this new scheme, I believe there won't ever be as this would require changes to the bootloader on top of repartitioning the device. That is extremely scary to do with an OTA, would require a wipe, and manufacturers can't be releasing two different firmwares for users that did manually repartition in EDL and users that only take OTAs.

I'm not positive on how Magisk determines if the device has a ramdisk, I would have to read into it's functions.

But yes, patching boot.img was more elegant, but I can't complain with the improvement that AK3 kernels won't ever have to worry about preserving Magisk or users having to worry about patching Magisk back in if they change kernels. Magisk having it's own partition to itself is nice in a way.

I just realized there's still one thing I need to test, whether a patched in ramdisk to boot.img is actually being loaded, as cpios will overwrite files as they are being loaded. The patched ramdisk has the Magisk init, but init_boot already has an init, so if the patched init gets overwritten by the stock init from init_boot then Magisk can't load. One test I can do for this is the existence of the overlay folder with the Magisk compressed payload, if it's still there on boot then that means it is being loaded. I'm going to have to do that later today.

Edit: Nope, didn't load it, might have to look at rebasing the want_initramfs patch.
[Google Pixel 7 Pro] Lughnasadh:
QPR1 Beta 3 is out for the Pixel 7 series ( and others). Is there a QPR thread started for this device @roirraW "edor" ehT ?
[Google Pixel 7 Pro] vurtomatic:
Can someone ELI5? I've only flashed custom ROMs on a OnePlus 3 that I'm replacing—which is usually flashing the ROM zip with TWRP. TIA.

After following these steps to root the P7P the first time, how would I update to a new version of the ROM from Google? And is the new version called the GSI (I see we have a thread for it)? I've never rooted and maintained a Pixel before. How does QPR fit into this?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Hi, my post 2 instructions cover both rooting for the first time, and updating each month (or however often you choose to).
[Google Pixel 7 Pro] EtherealRemnant:
Google will only send a carrier locked device if you are replacing one that was originally carrier locked. This is why people should buy the unlocked one always.
[Google Pixel 7 Pro] V0latyle:
That's the million dollar question. All I can tell you is what determines a device to be unlockable and how it's implemented but exactly how a device gets that property set in the first place is a bit of a mystery. The closest suggestions I've seen have alluded to server side IMEI/serial number whitelists, because some devices have OEM Unlocking unavailable until they've had a chance to connect to the Internet. That would seem to suggest that it's ultimately Google's responsibility, but there's no clear and established reasoning behind why some devices are and some aren't, nor is there any clear communication path between Google and carriers. I would think that carriers "buy" blocks of serial numbers/IMEIs in that whitelist and have them essentially blacklisted, but there's some users who have claimed to gain OEM unlocking through a conversation with the carrier.

There's theory, then there's practice. They should only send the same type of device that you are replacing, but this isn't always the case, and there's been a few outliers.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Indeed! There have been several times at work when I asked a separate technical department "What about _______?" and their answer is "That shouldn't happen.", to which I respond "Let me show you the times that has happened." 😂
[Google Pixel 7 Pro] V0latyle:
Lol don't I know it!
[Google Pixel 7 Pro] Paz9:
Are we assuming we'll be able to patch the boot image for the 7 pro in magisk and just flash it like we do with the 6?

Thought the main challenges with 6 came with A12?
[Google Pixel 7 Pro] siavash79:
Having bricked my p6 with ARB, I don't think I have that much of a stable place in your list sir
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yes.

That's correct.

Oh, no! Are you getting it replaced by Google?
[Google Pixel 7 Pro] Ghisy:
No way?! That sucks :(

I hope you can get a replacement!
[Google Pixel 7 Pro] Paz9:
So theoretically should be fine patching the p7
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yes, theoretically. We never know, there could even be a new version of the Platform Tools (ADB / FastBoot) required for the Pixel 7 Pro. Only waiting will tell for sure. :)
[Google Pixel 7 Pro] roirraW "edor" ehT:
Have you seen this? Magisk Delta - Another unofficial third-party Magisk fork

I wonder if it has any effect for STRONG_INTEGRITY. No mention of that specifically in the thread. If I remember when I get the P7P, I'll try this first just to see what happens. I don't want to bother with my P6P.
[Google Pixel 7 Pro] V0latyle:
No, it has nothing to do with Magisk.

The three elements in Play Integrity are:

MEETS_BASIC_INTEGRITY: Corresponds to SafetyNet basicIntegrity. The device likely hasn't been tampered with, but hasn't necessarily passed Android compatibility testing (System/kernel modifications not detected).

MEETS_DEVICE_INTEGRITY: Corresponds to SafetyNet ctsProfileMatch. The device profile matches that of a profile that has passed Android compatibility testing. (Pretty much every device should pass this on stock ROM).

MEETS_STRONG_INTEGRITY: Corresponds to SafetyNet HARDWARE_BACKED attestation. The device is able to provide cryptographically signed valid results as a trusted compute platform; Hardware Key Attestation is available. (Not possible with unlocked bootloader because untrusted images can be loaded, therefore HKA throws an exception)

As far as how this is going to affect us in the future, it's up to the app developers to decide what results they want. In most cases, all they care about is BASIC and DEVICE. But if they really want to ensure that they're running on a trusted platform, they can require STRONG attestation, which cannot be spoofed or bypassed. BASIC and DEVICE can, because they use the same mechanisms that SafetyNet did.

It's worth nothing that SafetyNet already had the ability to report HARDWARE_BACKED integrity, but no one chose to utilize it or enforce it. Probably because of this:

Older versions of Android just used hardware values such as the device serial number to provide hardware backed attestation, which is a pretty obvious security vulnerability. STRONG_INTEGRITY requires Android Verified Boot to verify the integrity of the system and boot images, as well as access to the hardware keystore and the Trusted Execution Environment to ensure that the results of operations are genuine, trustworthy, and untampered.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Gotcha, makes sense, thanks!
[Google Pixel 7 Pro] Superguy:
Normally I would agree. However, the 256 GB model for a little over $6 a month is a pretty good deal. Would just need to get it unlocked.
[Google Pixel 7 Pro] Superguy:
Best Buy was selling unlocked versions too. Google online store had unlocked 512 GB versions last time I looked for $1099.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I know, thanks. The original user who asked appeared not to be in the United States, so Best Buy would likely not be an option for them.

The only reason I didn't go the Best Buy route myself is that trying to order the P7P unlocked and arrange a trade-in online at Best Buy's site, they don't list the 512 GB version of the Pixel 6 Pro as a trade-in they would accept. I chatted and was "on hold" with Best Buy customer service for over an hour but in the end, the best they could tell me was to go into a store. I'm 45+ minutes away from the closest location, so I didn't feel it was worth it to find out *if* I could use the 512 GB P6P for a trade-in, and for how much, if so.

Now, it's likely they might and if they did it would be for the same amount the Google Store was offering for trade-in, but it's just too much hassle to go there physically to find out. I considered selling the P6P on Swappa, but the price that's been paid on Swappa keeps going down, and they'll be flooded with P6Ps from other users who are upgrading soon, which will drive the price down even further, so I thought it was a fair trade to be able to count on the solid trade-in value directly with Google instead.
[Google Pixel 7 Pro] Ghisy:
Found a thread on the Google Pixel SubReddit where someone in Italy already received his P7P from Amazon:

https://www.reddit.com/r/GooglePixel/comments/y19noa

He's posting some impressions little by little.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Awesome! Thanks for sharing.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Edit:

Original:

Not that this has anything specifically to do with the Pixel 7/Pro but...

https://twitter.com/i/web/status/1579695277778571266
[Google Pixel 7 Pro] xdagee:
That's interesting... very detailed. Thanks.

I'm missing the days where you could request for the bootloader to be unlocked.

I think HTC was the only OEM who cared for developers, they had a smooth process to request for your bootloader to be unlocked. Even with that one, they specifically state the devices whose bootloaders can be unlocked. Apart from that, all the OEMs make it look like it is illegal*** (Is it illegal to unlock your bootloader?) to unlock your bootloader.
[Google Pixel 7 Pro] jucin:
i installed all drivers and i am using the newest sdk the command fastboot flashing unlock end uo in this its not working. Hope anyone can help
[Google Pixel 7 Pro] newszik:
Hi all,

When I want to root my device (Pixel 7 Pro) , I get the error message :

I followed the procedure correctly, the init_boot was patched by last magisk stable and I changed the usb port too. I was able to unlock the bootloader with no problem.

Can you help me please ?
[Google Pixel 7 Pro] badabing2003:
What version of Android platform tools are you using?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Open Windows' Device Manager. Can you attach a screenshot of it? Try a different USB port or cable, and even reboot the PC. But show us that screenshot and hopefully we'll get some ideas.
[Google Pixel 7 Pro] jucin:
The newest 33.0.3
[Google Pixel 7 Pro] badabing2003:
What version of Android platform tools are you using.

You should always be using the latest, it is in the OP
[Google Pixel 7 Pro] roirraW "edor" ehT:
Are you in fastboot or fastbootD mode?
[Google Pixel 7 Pro] badabing2003:
Please show the output of

fastboot --help

You might have an old one in the path that is being picked up.
[Google Pixel 7 Pro] newszik:
Fastboot Mode

Enter reason : reboot bootloader
[Google Pixel 7 Pro] jucin:
when i put the command fastboot --help it show the same like that when i put fastboot flashing unlock
[Google Pixel 7 Pro] badabing2003:
see this

https://xdaforums.com/t/unlock-boot...gain-all-relevant-links.4502805/post-87606253

it does not show a version?

then you are definitely not using the latest, you probably have another one in your path.

please type this command and see what you get

where fastboot
[Google Pixel 7 Pro] xgerryx:
Having a lot of trouble getting device manager to recognize the device after unlocking the bootloader. Installing the driver manually is resulting in a code 10 error. (the device cannot start). Has anyone had this happen? I've rebooted back into bootloader, opened and closed device manager.

The result is I can't push the boot image to the device from fastboot.
[Google Pixel 7 Pro] badabing2003:
Disconnect your phone from your computer.

In Device Manager | Show hidden devices

Then expand every node in the tree, and delete anything you see in Gray or exclamation mark / warning triangle

Repeat this for every node.

Connect the phone and try again,

If there is a driver issue you should see it in warning mode.
[Google Pixel 7 Pro] badabing2003:
try

where fastboot.exe
[Google Pixel 7 Pro] jucin:
nothing happen its very strange. i will try now with android studio
[Google Pixel 7 Pro] xgerryx:
Thanks, I think that fixed the issue. I don't see the drive in my PC though. I'll keep working at it. I can't ever remember it being this hard to get a device recognized. And I know it's not "hard" just a lot of bumps it seems.
[Google Pixel 7 Pro] badabing2003:
No worries.

Install Search Everything

After that open it and let it finish indexing your files.

Then search for fastboot and see what you get.
[Google Pixel 7 Pro] newszik:
Thx !

I had 3 old versions of adb.exe & fastboot.exe on my PC.

Root ok !
[Google Pixel 7 Pro] badabing2003:
you won't see the the MTP mounted in fastboot mode, only in adb / recovery mode.

And you have to set

USB File transfer on on the phone, you can set that to be the default in developer options.
[Google Pixel 7 Pro] jucin:
its not working and i dont know why
[Google Pixel 7 Pro] xgerryx:
OK I got it now. Thanks for your help. TBH I didn't think it was going to boot up without flashing the rom image. I've done this a million times on Oneplus phones but never on a Pixel. I just let it boot up, skipped the setup and got the boot image there that way when the phone in the OS. The bat file is running now. Something that should be added to the OP is about the length of time this takes. I ALMOST unplugged it when the screen went dark the first time, after the partitions finished.

Now stuck in fastboot loop. Niceeee. All I did was flash the patched boot image.
[Google Pixel 7 Pro] jucin:
so i unlooked the bootloader now it worked with CMD. But now my phone dont connect to my Laptop
[Google Pixel 7 Pro] roirraW "edor" ehT:
Okay, I lost the post - I know I saw a screenshot of Device Manager for someone, and it showed the phone as LeMobile (or whatever Microsoft offers as their own driver update). Right-click the entries in there and choose uninstall driver (and check the option to delete it). Then go to Device Manager's menus and tell it to re-scan. When it finds it, update the entry to Google's driver. Don't let Microsoft Update change this driver.

You do NOT flash the boot partition on the Pixel 7/Pro. You only flash the init_boot partition. You root the init_boot.img with Magisk, and then flash it to the init_boot partition. Not the boot partition.

fastboot flash init_boot magisk_patched-25200_1a2B3c.img

is exactly how I rooted my Pixel 7 Pro.
[Google Pixel 7 Pro] roirraW "edor" ehT:
What does Device Manager show?
[Google Pixel 7 Pro] badabing2003:
@jucin

As you can see you have many old copies.

I would delete each and every one of those, Ideally you should delete the folder not just the fastboot.exe to make sure adb or other files don't get picked up either.

Then install the latest, and you'd have a single one that you know is the latest.
[Google Pixel 7 Pro] xgerryx:
Without the boot partition it comes up with an unknown partition. but just in case someone sees my post I will edit that out, sorry.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Something is very wrong. I hope we figure out what it is. A puzzler, that's for sure.

fastboot flash init_boot magisk_patched-25200_1a2B3c.img

is exactly how I rooted my Pixel 7 Pro.
[Google Pixel 7 Pro] xgerryx:
What if I flashed it to the boot partition? Just run the bat file again and start over?
[Google Pixel 7 Pro] roirraW "edor" ehT:
You could, or you could just flash the proper stock unpatched boot.img to the boot partition, but yeah, maybe starting from "scratch" isn't too bad an idea. I promise, that extra "boot" you found necessary in the command is an oddity.

You're not the first who tried to flash to the boot partition. It definitely won't work if you flash the init_boot or patched init_boot to the boot partition. It'll boot loop if it flashes successfully (and you reboot).
[Google Pixel 7 Pro] roirraW "edor" ehT:
@jucin for some reason XDA isn't quoting your post with the screenshot, but it showed the phone as LeMobile (or whatever Microsoft offers as their own driver update). Right-click the entries in there and choose uninstall driver (and check the option to delete it). Then go to Device Manager's menus and tell it to re-scan. When it finds it, update the entry to Google's driver. Don't let Microsoft Update change this driver.
[Google Pixel 7 Pro] badabing2003:
agree 100%

@xgerryx

1- make sure you don't have old Android platform tools, search everywhere on your system, and old one could be in the path and throw you off see this.

2- I would flash_all (-w removed)

3- I would switch slot

4- flash_all again.

You would have two good slots.

5- do fastboot flash init_boot patched.img (or whatever the patch filename is)
[Google Pixel 7 Pro] xgerryx:
Thank you, really appreciate everyone's help here. I did actually flash the original boot images on both slots and it booted up. I have root and all is well. Again thanks for all the work you put into it.
[Google Pixel 7 Pro] roirraW "edor" ehT:
If anyone else still needs help and you accidentally got dropped due to all the activity that's been going on, please give a shoutout and let us know where we left off. 😎
[Google Pixel 7 Pro] roirraW "edor" ehT:
I forgot to address this part of your quoted post. @PurppleMonkey also suggested something along these lines, I believe. I'm a little resistant, but with two users suggesting it, I'm sold.

Edit: Done.
[Google Pixel 7 Pro] jucin:
I will reset my Laptop tomorrow to get everythink Clean. I flashed the Firmware with android flash to Stock and locked the bootloader again and it is still not detecting my Laptop.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Good luck! Let us know what happens. Try a USB 2.0 cable (like the one that comes with the phone, along with the USB-A -> USB-C adapter that comes with it), and if you have any USB 2.0 ports on the laptop, try those as well.
[Google Pixel 7 Pro] BIGWORM:
Well, you sent "adb devices" command and it didn't come back with your device's ID. IMO, I find using a CMD prompt with elevated privileges a lot cleaner than PowerShell. USB Debugging enabled on your phone? If so, send the "adb devices" command again then look at YOUR phone to allow your computer to send adb commands.
[Google Pixel 7 Pro] caspianprince33:
My system is read-only even after root and dm verity. How to make it writeable? Any workaround?
[Google Pixel 7 Pro] PurppleMonkey:
Thank you !

What confused me is that the phone restarts in fastboot d, without any process showing up on the phone or in the command prompt, so I thought it was finished or that there had been a mistake!

EDIT: My first pixel 7 will come back from repair. Official version of the breakdown: error in using the official Google flash tool :D
[Google Pixel 7 Pro] pndwal:
For P7?... Not yet I don't think... But you could watch this space until the big yellow notice disappears:

https://xdaforums.com/t/script-andr...uring-makerw-read-write.4247311/post-84658055

😜 ... Tumnus, of Lantern Waste...
[Google Pixel 7 Pro] Lughnasadh:
On a side note, despite the anticipation that the 7 would use EROFS, it still uses EXT4 for its read-only partitions, unfortunately.
[Google Pixel 7 Pro] roirraW "edor" ehT:
@BIGWORM has a great point below. You're using PowerShell. You can use PowerShell if done properly - the commands need ".\" added to the beginning of them for them to work right, I believe, but it's simpler to use Command Prompt.

You're welcome! Thanks for looking out.

Well, that's definitely the next best thing to getting a completely new one, versus getting a completely refurbished one. :)
[Google Pixel 7 Pro] IdrisMC:
For updating with magisk, can't you just install the ota and patch the init_boot on the inactive slot and reboot to that?
[Google Pixel 7 Pro] roirraW "edor" ehT:
I have no idea if that OTA method will work. Is it possible it will? It's possible. I find it simpler to just use the factory image from the computer, but I understand that some users want to use an OTA method.
[Google Pixel 7 Pro] meinlet:
Hello guys, tried to update to latest factory image and after i execute flash-all.bat on line

"extracting super_empty.img (0 MB) to disk... took 0.000s

Rebooting into fastboot

<waiting for any device>"

phone reboot to fastbootd and is waiting for me to choose one of the below

"Reboot system now

Enter Recovery

Reboot to bootloader

Power off"

I tried the first time the "Reboot to bootloader" but got a message after reboot that my phone is corrupt and then phone stuck at googles logo.

What did i do wrong?
[Google Pixel 7 Pro] roirraW "edor" ehT:
You may have rebooted while the flash-all.bat was still working. If you can get into the bootloader, I suggest using the Official Google Android Flash Tool.

If using the Android Flash Tool, you should have the following items not selected:

Deselect Wipe

Deselect Force Flash all partitions (which will also wipe)

Deselect re-lock bootloader

If the phone still gives you grief after that, I'd try with a wipe and force flash all partitions.

The only other possibilities I can think of is not using the latest drivers, not using the latest Platform Tools, or a problem with your USB cable or port. Try a USB 2.0 cable, and if you have one available, a USB 2.0 port.
[Google Pixel 7 Pro] jucin:
Finally i unlocked the bootloader and rooted my Pixel 7 pro. And i flashed the Despair Kernel. I have some questions:

If i want to Update the Kernel do i Just need to Put the ZIP in the Kernel flasher and do i need to factory Reset the Phone everytime after doing this?

And can i Install the Google Safty Patches without loosing root etc?

And my Last question is does the system Update is working or i need to flash everytime when Update comes Out manually on my Laptop?
[Google Pixel 7 Pro] meinlet:
Im trying the official tool right now, i will update.

As of the previous procedure no i didnt interfere maybe is the cable if the official tool wont work i will try and with another cable. Also i've downloaded platform tools and drivers today so i have the latest versions on both of them.
[Google Pixel 7 Pro] Lughnasadh:
If you are talking about using the "Install to Inactive Slot" method in Magisk, it's not working right now for the Pixel 7. Magisk isn't restoring the stock init_boot.img so you end up still rooted, thus having the OTA fail. Best to use another method to update and re-root, as @roirraW "edor" ehT suggested.
[Google Pixel 7 Pro] IdrisMC:
Is the Despair Kernel worth installing? What are the differences between that and stock