yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] fillwithjoy1:
Hey does anyone know the fingerprint model of Pixel 7 Pro? I'm trying to update Pixelify-GPhotos and I need the fingerprint of the model.

Examples of other ones look like

Pixel XL:

google/marlin/marlin:10/QP1A.191005.007.A3/5972272:user/release-keys

Pixel 2 XL:

google/walleye/walleye:8.1.0/OPM1.171019.021/4565141:user/release-keys

Pixel 3 XL:

google/crosshatch/crosshatch:11/RQ3A.211001.001/7641976:user/release-keys

Pixel 4 XL:

google/bonito/bonito:11/RQ3A.211001.001/7641976:user/release-keys

Pixel 6 Pro:

google/raven/raven:12/SD1A.210817.036/7805805:user/release-keys

You can find more of these when looking in this file

Pixelify-Google-Photos/app/src/main/java/balti/xposed/pixelifygooglephotos/DeviceProps.kt at 5c47617d69fa11950c11ee1be7e12d9e76d122dd · BaltiApps/Pixelify-Google-Photos

Pixelify GPhotos. Contribute to BaltiApps/Pixelify-Google-Photos development by creating an account on GitHub.

github.com
[Google Pixel 7 Pro] JohnTheFarm3r:
Pixelify on a Pixel phone? What could possibly go wrong? :ROFLMAO:
[Google Pixel 7 Pro] Schroeder09:
... Jokes on you. You don't know what your talking about. You obviously didn't read the link he posted. This gets the free probably quality storage that's still available for the OG pixel phones.
[Google Pixel 7 Pro] JohnTheFarm3r:
Jokes on you if you think that those Lposed modules don't break anything on a PIXEL device. (talking about PIXELIFY modules). Not the unlimited storage for Gphotos.
[Google Pixel 7 Pro] cmh714:
DevCheck will give you that since its based on what code your running....
[Google Pixel 7 Pro] fillwithjoy1:
No jokes here, you're missing the entire point of this post.

Correct, it does work but I'm trying to get a Pixel 7 fingerprint so I can get the Unblur face feature that is still exclusive to the Pixel 7 series.
[Google Pixel 7 Pro] fillwithjoy1:
Hmm is there any other way, since I don't have physical access to a Pixel 7 device
[Google Pixel 7 Pro] JohnTheFarm3r:
I'm not, I exactly know what are you trying to do here. But as I said, have fun when stuff starts breaking down. This was already mentioned by a few devs around here. Spoofing the fingerprint...
[Google Pixel 7 Pro] fillwithjoy1:
Is that why there's no update to GPhotos Pixelify?
[Google Pixel 7 Pro] fillwithjoy1:
What about using the driver binaries that Google supports through it's drivers?
[General Questions and Answers] mic_0:
I was using a gsi image then I decided to go back to stock rom

I used after sales tools made for transsiom devices(infinix, Tecno,Itel)

After it flashed boot and recovery and on getting to super image it showed an error message 'sending failed' this file doesn't match with the one in the device

Now when I try to power on it tells me

Dm verity corrupted

I can't access fastboot nor recovery

If I press power button to continue it remains stuck on boot logo
[General Questions and Answers] mic_0:
Please this is urgent

The device is not mine

🙏
[General Questions and Answers] mic_0:
Please how
[General Questions and Answers] mic_0:
Thanks

Will try it
[General Questions and Answers] mic_0:
I solved it by flashing empty vbmeta using
[General Questions and Answers] GinoC.O.B:
So how did you get the phone to boot into fastboot if you couldn't access fastboot mode?
[General Questions and Answers] mic_0:
I used sp flash tool and flashed super,recovery, boot image then i managed to boot into fastboot using volume keys

mtk bypass utility helped me
[General Questions and Answers] Kerseymarlene@gmail:
My cloud T1 Elite tablet turned it on and says DN, not dm verity corruption. I can't even shut it off.HELP
[General Questions and Answers] Timelinex:
I have a Galaxy S23 Ultra and I see an option to show place names in the gallery. To turn it on I have to accept the "foursquare privacy policy" where they get to receive and keep my location data. I am obviously very skeptical of this, but on the other hand this seems like a great feature to help for searching photo's as I travel alot.

Does anyone know more about this feature? How it works and any known privacy concerns?

Thanks!
[General Questions and Answers] James_Watson:
The camera app tracks your geographic location and adds it to the photos you take. The gallery app shows location information. All of these involve your privacy. Therefore, to use this feature, the camera and gallery app must obtain your consent to comply with the privacy policy.
[General Questions and Answers] Timelinex:
Yes I am aware of all that.....

I am specifically referencing the "add place names" feature in the gallery which has it's own separate tick mark, and privacy policy that you have to accept with "foursquare".
[General Questions and Answers] TheMystic:
I would stick to Google Photos for this purpose. Not comfortable handing data over to a hundred and more unknown entities.
[Moto G5 Questions & Answers] randomguy3356:
Hello, im trying to update my phone to android 8 without custom roms, but every guide I find, has dead links, and also I didn't update to NPPS25.137-93-2-5 when it was still available, thanks.
[Moto G5 Questions & Answers] alecxs:
TWRP is official available for that device

https://twrp.me/motorola/motorolamotog5.html

stock ROM can be downloaded here

https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/cedric
[Moto G5 Questions & Answers] randomguy3356:
Does blank flash mean it will erase everything?
[Moto G5 Questions & Answers] alecxs:
look at the size of the file, it is only the bootloader. you need to download stock ROM according to your region, for example RETAIL or RETEU
[Samsung Galaxy Z Fold 4] thebizerker2010:
I paid for an IMEI repair and I believe it messed up my phone. I was told it was not rooted, but I can not get Samsung Wallet to work at all. Is there a way I can restore the original IMEI without having to root the phone? The phone was originally Branded to AT&T. Can anyone help me please? I had to repair the screen myself because the IMEI shows up as a S21 Ultra so I couldn't even file an Insurance claim when I broke my screen to get a new phone. Any help will be appreciated.
[Samsung Galaxy Z Fold 4] thebizerker2010:
I am just trying to restore my phone to the original IMEI it had before I did this. I am not trying to get anyone in trouble just would like to fix my phone.
[Samsung Galaxy Z Fold 4] iron@ss:
Who originally changed the IMEI that you paid for?
[Samsung Galaxy Z Fold 4] iron@ss:
You do know that it is an offence in most countries for a 3rd party to change an IMEI number don't you...

Mobile Telephones (Re-programming) Act 2002 - Explanatory Notes

www.legislation.gov.uk

Thieves use this method to try to get around blocked stolen phones. I suggest that you contact the company that did this for you.
[Samsung Galaxy Z Fold 4] Clark Joseph Kent:
This ^^^^^^^
[Google Pixel 6a] G5-User7080:
I don't wanna risk the on device ota via restoring images through magisk again

Does the following check out?

I'd greatly appreciate if someone, perhaps @V0latyle could look over it, you already helped me a lot the last time.

Download ota, as well as firmware and check if boot.img got updated (or perhaps someone on an updated phone can check but idk how to even check your boot version)

Either patch new boot.img or keep the old one at hand if it didn't get updated

Disable all magisk modules and reboot

Go to magisk -> uninstall -> restore images and reboot

Go in sideload mode and sideload the ota

Reboot to system so the ota can complete

Turn off and boot again from magisk patched boot.img

Direct install through magisk and enable modules

Reboot so modules work and done

All those reboots might not be necessary but I don't know if f.e. magisk modules immediately stop affecting the system after disabling them or if a reboot is required to fully disable them, same with unrooting, even after restoring images the current system has still root so I might need to reboot before sideloading.

I know that technically I don't need to unroot at all for sideloading to work but I really want to make this as safe as it can get.
[Google Pixel 6a] V0latyle:
No need to unroot or restore images. You can disable modules if you want. Just sideload the OTA, and live boot the old patched image, then perform Direct Install in Magisk.

By the way, instead of creating a new thread, you could have asked this question in an existing one...
[Google Pixel 6a] G5-User7080:
Perhaps I could have, I am hoping that this way it might be easier to find for others than having to look somewhere on the 30th post of a thread that is about a bricked device after ota.

mhh I see, I'm just a little scared of the ota process after what happened the last time so I wanna be like extra sure nothing can go wrong.

Doesn't help that I don't really understand what OTA's do exactly..

That I don't have to unroot when flashing factory makes sense as I'm just overwriting boot anyway.

Is an OTA the same thing essentially? Like is it basically a bunch or partitions in a zip that get flashed over whatever is there previously?

Meaning all things that could go wrong or get checked happen through the system update app rather than through the OTA itself?

Also you are saying "unroot or restore images", is that not the same thing?

And let's say boot gets updated and I live boot the older outdated image, does that not matter at all?
[Google Pixel 6a] frank93:
why do you wanna take the OTA route if you already downloaded the complete firmware package anyway? i’ll do a firmware flash (instead of OTA) without wiping each month and that’s it, i’ll even patch boot.img before flashing (and flash it directly together with the rest of the new firmware). works just fine. :)
[Google Pixel 6a] media-fort:
This sounds like the "Quick Method" mentioned here:

https://www.xda-developers.com/how-to-install-ota-updates-keep-root-google-pixel-phone/

You're doing that?
[Google Pixel 6a] G5-User7080:
As far as I understood sideloading OTA is the most safe and uncomplicated way
[Google Pixel 6a] frank93:
yes, sounds like that’s "my way" of doing it. originally got this from a magisk-issue-comment here, basically it’s a "complete firmware flash with an already patched boot.img, no wipe", and that’s it. never done an OTA/sideload for years tbh.
[Google Pixel 6a] media-fort:
Damn, I tried this and it seems that my PC cannot write the image to the Pixel 6a?!

Do I have old ADB drivers or whats the reason for that?

View attachment 5857025

Edit:

Sry, I'm not involved here all the time. Figured it out myself. Reason for the failure were the freakin' platform_tools_r34. Switched to r33 and worked straight away..

https://xdaforums.com/t/pixelflasher-for-google-pixel-7-pro-support-thread.4505287/post-88134573
[Google Pixel 6a] G5-User7080:
Not in the 6a forum as far as I'm aware, there might be more in the Pixel 6 forum, but I've already seen your guide that covers all kinds of methods.

Wouldn't it make sense to restore the unrooted boot partition on the currently active slot given that OTA will switch me to the currently inactive slot?

So that after the OTA procedure I'm in the same situation as now, being on a rooted slot with having the original unrooted slot as sort of "backup".

I think it was on the magisk ota guide but im not sure, that it said that it's important to disable all system modifying modules before attempting an update.

While all modules I use should by systemless,.. I think?.. I still think it's just easier to disable them all and re-enable them later, just to avoid trouble and make it easier to write in a guide, as in "just disable them and don't bother checking if theyre really all systemless".

Yes, that was my intention, let it boot normally without touching anything to complete the OTA.

Didn't know I would have to wait a few minutes after already being in the system tho to wait for the notification, I'll look out for that.

Is this equivalent to the way you described in your Pixel 6 guide?

As in doing adb reboot sideload to go to sideload mode, followed by adb sideload ota.zip

If it bootloops how would I even get back into system?

Why would it even bootloop, if there is a known cause can't I just avoid whatever is causing it to begin with?

I mean I don't assume I'll bootloop following the steps carefully but this time I'll post and wait for replies before just nuking everything like last time ^^

Yes, I'd prefer to make it as safe as possible.

Is the boot.img extracted from the OTA the same as the one from the according firmware?

Would be easier to just extract that on PC.

Oh and two more question that came to mind.

When restoring images through magisk it replaces the rooted boot partition with the stock one.

But root only disappears on next reboot.

So can I restore images and then directly do adb reboot sideload followed by doing the OTA?

Meaning I don't need to do one reboot back to system to sort of "complete the unrooting preocedure"?

Is that the same for magisk modules?

If I want to disable them just in case, do I need to reboot once after for them to like get removed from the system or are they instantly disabled the moment I press the "disable module" switch?
[Google Pixel 6a] V0latyle:
Not if you're going to sideload the OTA. There's no point to doing so.

Yeah, this is the "safe" option. I just use MHPC + USNF mod + systemless hosts so I don't bother disabling, but those who use Xposed or other more "invasive" system mods might want to.

This is because it seems to take a few minutes for the system to "get happy" and decide that all is well, and if you live boot an older boot image before it does so, it will assume the update failed and recycle back to the old slot.

Yep. The commands and the method is exactly the same for all Pixel devices. The only thing that is different are the files. Only the Pixel 7 / 7 Pro are slightly different in that we have to patch init_boot instead of boot.

Use the command I gave you: adb --wait-for-device shell magisk --remove-modules while booting

There isn't a known cause, the exception being trying to boot an old boot image without letting the system complete the update post-reboot as described above

Yes. It's just packaged differently.

Since Payload Dumper requires Python, I've found it simpler to just use the factory image - although if you're at that point, you may as well just flash the factory image anyway.

I never suggested you'd need to reboot after restoring images. Once you've restored the original boot image, that's what is in the boot partition. It takes effect immediately. What doesn't take immediate effect is what's currently running in memory, which is why I pointed out that upon a reboot, your device will load the unpatched image because that's what's in the partition. But, as I explained above, there's no point to restoring the original boot image if you're sideloading the OTA. The only time this ever appears to be necessary is when you're taking OTA through system update.

I am honestly not sure about this one, but since we are talking about OTAs, the point is moot - when the update completes and the phone reboots, it's booting an unpatched boot image, meaning there's no way for the modules to load. It doesn't matter if you've made changes to system, either, because the system partition also has two slots - system_a and system_b

The only thing that MIGHT matter is when you boot the patched image, because if you haven't disabled modules, they will load during boot, and if one of them causes a bootloop for whatever reason....It still shouldn't matter because in this case, the device -should- try to boot the same slot again, and since you never patched the new boot image, it will boot without root.
[Google Pixel 6a] G5-User7080:
yea it seems like its the same as restoring images, it disables them but obviously they are already loaded for the current session and probably don't get "unloaded", they just won't load again from the next boot on, so I don't think there would be any need to reboot, except when you want to do something in system that requires modules to be disabled.

So it seems like we'll have to wait til like the 20th for the march update, so I'll just go straight for the april one.

Considering what you said, would this be the correct procedure, just to confirm?

Extract boot.img from factory image and patch it, then move it to pc.

In Magisk app, disable all modules.

On pc do adb reboot sideload and after rebooting in download mode adb sideload ota.zip

Choose "reboot system" from menu or use adb reboot... does that command work in download mode?

Let it reboot, unlock, wait for the update completed notification to appear.

Confirm that adb debugging is still enabled and the version number below quick tiles matches the update, then do adb reboot bootloader.

Live boot the new magisk patched boot.img with fastboot boot patched_boot.img.

Magisk app -> Install -> Direct Install, then re-enable all modules and reboot.

done

Additionally, I'm wondering what all the different "menus" are for.

Like first there is bootloader where you can flash partitions through the fastboot command and enter recovery or boot system.

Then there is the recovery that... doesn't really do anything when it's stock?

Then there is sideload or download mode that is accessed from the recovery.

Then there is adb fastboot, does that bring you to the fastbootd screen? I have no idea what that is for.
[Google Pixel 6a] V0latyle:
ADB commands work in recovery mode, yes.

If you're going to download the factory image, why not just use Pixel Flasher to perform a factory flash? Contrary to popular belief, flashing the factory image itself does not wipe data. OTA updates are still the "safest" way but I've been using the factory image for a couple years now on my Pixel 5 and have never had a problem.

Bootloader is used for flashing bootloader, modem, and boot.

Recovery mode is a small kernel in of itself that can perform functions that the bootloader can't, and provides a software interface to perform a "safe" recovery should the device stop working - like flashing an OTA.

Sideload mode is part of that recovery software interface - it allows you to serve OTA files over ADB

Fastbootd is "userspace fastboot" that allows advanced flashing functions.

More information on fastbootd
[Google Pixel 6a] G5-User7080:
cause I'd need to remove the -w from the update command in the flashall.bat as well as possibly add --skip-reboot

I can see the day coming when I simply forget doing that and wipe my device by accident.

Or when using pixel flasher I might just forget to untick the wipe option.

I want to use a method that ideally I only have to prepare once, say if I could just make a "flash factory without wipe" script that works every time, but due to changing version numbers I have to use the new script every time.
[Google Pixel 6a] V0latyle:
You don't have to use the script. Learn to do the commands manually. You don't have to skip reboot either, but if you want to flash a patched boot image, it helps.

Pixel Flasher settings are persistent....

You seem to misunderstand how flashing the factory image works. You don't have to use the script. Learn to use ADB and fastboot commands manually. You can follow my guide for the 6 Pro here; the commands are all the same.

Otherwise, you can use Pixel Flasher. All you have to do is set it up once, and the settings persist even after updates. This is what I've gone to as a means to simply free myself for other tasks while my phone is updating; I used to do it manually.
[Google Pixel 6a] media-fort:
If you flash a full factory image via fastboot (without wiping the device in that process), is it safe and possible to leave your login information for screen unlock (password, fingerprint) installed before flashing?

And can I stay logged into my Google Account on the device before flashing as well?

I don't want to brick my device, therefore I've always deleted these Login infos before full flashing process.

But after each full flash, it's always very annoying to add all that info again, for each banking app, for Google pay and so on....
[Google Pixel 6a] frank93:
i never logged out or deleted anything before flashing. it "feels" like an OTA, i just flash (without wipe) and after the next boot the device is ready to be used.
[Google Pixel 6a] WoKoschekk:
Flashing a full firmware w/o wiping = OTA update. Since an OTA won't delete anything of your settings/data, a full firmware flash w/o wiping will do the same.

All settings, data and apps are stored on /userdata. When saying "without wiping", then it means "do not erase /userdata".
[Google Pixel 6a] V0latyle:
Almost, but not quite.

Flashing the full factory firmware installs it to the currently active slot and can be done regardless of what version you're already on; if you try to flash the system update alone, it'll complain if it doesn't see the right bootloader and radio version but you can use --force to get around that

Flashing the OTA installs it to the currently INACTIVE slot and can only be done when you're on an OLDER version.
[Google Pixel 6a] WoKoschekk:
yes, that's right. but regarding to the question

it doesn't matter which slot is active.
[Google Pixel 6a] V0latyle:
Right, because that information is contained in /data. There is only one data slot.
[Google Pixel 6a] frank93:
i usually use the flash-all-script for the monthly update, removing the wipe-option and adding a line for patching boot/init_boot in the end to both slots - but reading your message i just realised i "break" my inactive slot there, right?

like, flash-all updates the currently active partition with the new firmware (only), and when i flash the magiskpatched boot.img to both slots, the inactive slot contains an "invalid mix" of firmware & boot.img?

i mean, apparently

fastboot flash boot magiskpatchedboot.img

.. is enough, after the firmware, for flashing the patched boot.img? dunno where i got the "--slot all" option from, always used it, assuming flash-all updates both slots or something - never ran into problems yet, but just to be safe i’d better leave it out in the future then. :)
[Google Pixel 6a] WoKoschekk:
as long as OEM unlocking is enabled it doesn't matter
[Android Software/Hacking General [Developers Only]] rafal70:
po emmc nie działa na inny problem z RPMB HELP
[Android Software/Hacking General [Developers Only]] Clark Joseph Kent:
Note: Questions go in Q&A Forum

If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...

xdaforums.com

And please post on English as per the forum rules you agreed upon.
[Pixel C General] tabormeister:
Hey all! I found someone who's interested in trying to upgrade the RAM and eMMC of the pixel C, does anyone have broken tablets around that we can test with? Dead backlights, broken screens, whatever.

The plan is 8GB lpddr4 and 128GB eMMC 5.1, 256 possibly. eMMC should be easy, might only be able to do 6 or 4gb ram but going moonshot first because why not.

Who's with me? The tablet is still SO good especially with @michie putting out these incredible builds lately. We just need some extra dead ones to test with, pm me or post here if you're interested in helping out.
[Pixel C General] tabormeister:
Update! 8GB RAM boots, now just need some help getting it recognized by the OS. Currently still showing 3gb in Android.
[Pixel C General] SigmundDroid:
Funny, I would have expected the OS recognizes it on the spot :unsure:
[Pixel C General] tabormeister:
I also would've thought that, did some research and apparently the bootloader has device tree lists with hardware specs for the device (can define multiple profiles) and then passes that into to kernel during initialization if I understand correctly, just need somebody who actually understands the process lol
[Pixel C General] ragwo:
Any progress in the RAM upgrade project?
[Pixel C General] tabormeister:
Haven't gotten a version of the DragonShield rom flashed yet, tried and failed. Will try again soon, @michie is done with school and someone said they were able to get it flashed successfully!
[Pixel C General] Dismal.:
With upgraded RAM and Emmc could it compete with the New pixel tab iPad and Samsung tablets