yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7] zyxwvut:
Unlocking the bootloader immediately creates a CTS profile mismatch with SafetyNet and will cause issues with Gpay and most banking apps. The post in this thread saying that unlocking your bootloader doesn't break anything is completely false. If you unlock the BL then you should also just root so you can install the Universal SafetyNet Fix Mod 2.0 and fix the CTS issue and use Gpay and banking apps. I went from a rooted stock ROM, to Paranoid Android. I had no issues with Gpay on PA until I rooted it and then even after passing SafetyNet checks Gpay wouldn't work no matter what I did. I'm currently back to a factory image stock Rom and locked BL because Gpay and banking apps are very important for my use case. I also enjoy OTA updates and not patching

init_boot.img every time an update comes out. You have to decide for yourself what's important for your use case but at least be properly informed of the potential issues that may come with a modified setup.
[Google Pixel 7] terry274:
l use Kiwi browser and Ublock Origin to prevent ads. With Kiwi, all the Chrome extensions can be used on your phone browser.

I am not rooted.
[Google Pixel 7] edwardenglish:
And what do you do about ad banners within apps or nasty overlays?
[Google Pixel 7] terry274:
At home I run an OpnSense firewall with Zenarmor to block ads. This takes care of app banners. Away from home I sometimes see ad banners.
[Google Pixel 7] mruno:
Just change your DNS to use an adblock provider. Root is not needed.

In the Network & internet settings, change Private DNS to dns.adguard.com
[Google Pixel 7] 96carboard:
That will help a bit, but the limitation is that it will still have to make an external dns lookup, which costs resources and time and costs privacy.
[Google Pixel 7] razercortex:
Breaks verified boot and potentially OTAs if they're not full updates.
[Google Pixel 7] sic0048:
For years I unlocked and rooted every phone I owned. Of course this was when Android OS was extremely limited in features, TWRP was king, and security features like safety net weren't a thing yet. Those were the glory years.... ;)

The Pixel 6 was the first phone I didn't unlock. Honestly I didn't miss anything except the hassle that comes with rooting now (manual updates, trying to pass safety net, no TWRP backups if something goes wrong, etc, etc). All the things I used to root for are either part of Android OS now, aren't being developed anymore, or are things that I used to care about that when I'm honest with myself, I haven't really missed.

Now I have moved on to a Pixel 7 and I just cannot see a situation where I will feel the need to unlock and root my phone. I won't say "never" because who knows what the next big thing will be, but there simply isn't a compelling reason to root right now IMHO.
[Google Pixel 7] Danvdh:
As someone who released ROMs for years on this site.

Not worth rooting this time around imo. You break more than you gain.
[Google Pixel 7] EtherealRemnant:
What exactly do you break?
[Google Pixel 7] JovialQuestion:
Yes always unlock. Why get the ability to be able to unlock taken away when the manufacturer decides to lock it down. Imagine buying a Asus laptop with say windows 95 on it. Asus decided not to support it anymore. Now in 4 years windows drops support for 95 and now you cannot use basic applications unless you update. If your bootloader is locked you would have no choice but replacing a device that works perfectly fine that's hardware supports the update you need. Unlocking the bootloader doesn't automatically break updates. If you simply unlock the bootloader and make no changes to the software it will and has for me always worked as intended and would get updates. Tho I usually deny doing a update through settings and download it to sideload in the stock recovery. When updates and you can find other Systems and won't be forced by a company to buy a new device. I just like options lol
[Google Pixel 7] bobby janow:
That doesn't make sense. If you can unlock the bootloader now you can unlock it later. The manufacturer, Google at this reading, will not remove the unlock oem switch to non functional. If you are only readying the device for down the road then flip the OEM switch and leave it at that. This way the banking apps that check for bl unlock will not trigger and you can always unlock later. I usually flip it when doing a manual update to the OS just in case and then flip it back.

As for computers that's a horse of another color. Aren't there utilities that can wipe out a boot partition so you can install anything you want? Been a while since I've had to do that though. Well hmm.. for instance I took an old Asus clunker and made it a Chromebook recently. That wiped out everything but I guess I could still get into the BIOS.
[Google Pixel 7] JovialQuestion:
Did you update the pixel 6. Or many Samsung devices. They do if the unlock was not supposed to be allowed so if your given the chance jump on it. So I'd say it does make sense
[Google Pixel 7] bobby janow:
I never heard of that happening on any Pixel device. Can you provide any evidence of that? As for Sammy that's a different forum and I really have no idea what they do.
[Google Pixel 7] JovialQuestion:
Regardless of hearing about it. The bootloader unlock program is not a guarantee nor promise. Look at LG for example. They ability to unlock the bootloader can be revoked at any time by Google or any manufacturer for Any reason. I've had personally two pixel phones and one Samsung that updating to a new VS or the OS took away the ability to unlock the bootloader by taking away the bootloader unlock command or by removing support entirely from the device to unlock. Sometimes it's an error yes and another update would fix it or all together they decided the device you have doesn't qualify anymore for the unlock. Either way. I personally don't let it stay locked once I see the ability to unlock it. As the ability to toggle the oem in development setting has no bearing on the unlock when the bootloader is fused and unlockable. I currently have two pixel 2 xls that have that toggled but you cannot unlock it in fastboot. Ultimately the bootloader has to support it as well as the toggle in settings. So my advice is to unlock while you can so if you so decided to make changes later on you can.
[Google Pixel 7] JovialQuestion:
Just to add. I'm using a pixel 3 with android 13 rooted and my banking apps and all apps including Google pay work just fine. You just need to make sure your hiding root and your not overly modifying and the apps can work fine without to much effort. I've never had a banking app not work with it just being unlocked with the stock OS installed
[Google Pixel 7] 41rw4lk:
I'd make an argument to unlock simply to have a way to repair your phone if something went wonky, like an update. It does happen and as we know, you can't simply flash a factory image on a locked bootloader even if it is a signed official image.

That still baffles me, google should at least have a rescue boot.img or a blankflash instead of having to RMA your phone for a software issue.
[Google Pixel 7] JovialQuestion:
A great point. Yes being unlocked does make it easier to repair. I do agree on the rescue boot. They could sign a boot.img that would boot the stock recovery even. So a ota could repair the device or at the very least allow the command to change boot slot to work on locked devices so you could at least try the other slot without change.
[Google Pixel 7] bobby janow:
I don't deny your experiences but I've never heard of a bootloader being fused. Anyone else out there? As I said I just flip the switch when I do something I'm not sure about and then flip it back. Never had an issue. I can flash anything I want if I unlock when needed.
[Google Pixel 7] JovialQuestion:
Do you know if this works on a locked pixel

Google Pixel - Update and Software Repair

It uses the rescue mode from bootloader. Says android 10 and up for pixel 3 and up.
[Google Pixel 7] JovialQuestion:
Here another reason I suppose I would unlock. As soon as I get the device.
[Google Pixel 7] JovialQuestion:
Clearly you have never bought a Verizon branded Pixel and missed your chance to unlock the device when it was allowed on release by mistake... And that's okay. However some people do experience these issues and an unexpected update will take away the ability later on to unlock
[Google Pixel 7] bobby janow:
I've had about 8 Verizon Pixels to date. Since the exploit in the 2 was closed it's not been possible. But seriously one mistake over 5 years ago hardly portends current unlocking abilities for non Verizon Pixels. Can Google do it, maybe. Have they or will they, no. And with the OEM switch in the allow position there would be a riot if they did. Simply not happening.
[Google Pixel 7] JovialQuestion:
And I was clearly including Samsung and LG in my responses so I wasn't only referring to the Verizon pixel I was giving my experience and my reasoning for unlocking based on all of the devices combined I'm sorry that you've zeroed in on pixels when my responses stated the other devices as well. Next time I will be sure to be clear
[Google Pixel 7] JovialQuestion:
And I have a pixel 2 XL that I can toggle the switch and cannot unlock. It's a 64 gig LG model. I was able to toggle the switch in Android 10 when you were still able. After the update to 11:00 the ability to unlock in the bootloader was removed for that model so the toggle no longer matters on Android 11 for the pixel 2 XL and was explained in the update that took it away. So again in my experience and my alone this is why I unlock my devices when I have the ability to do so. My responses and opinions are not the same as everyone's. Nor are they to speak for the manufacturer. So again my responses are solely my opinion based on my experiences alone.
[Google Pixel 7] bobby janow:
The 2XL was never able to unlock that's why you can't do it. The Pixel 2 had an exploit early on but it was closed almost immediately with an update. It was an oversight by Verizon and it has never happened again. So even though you could toggle the switch on the 2XL with the hack, it couldn't be bl unlocked whereas the P2 could. But that was so long ago and why hang on to old exploits and hacks, they're long gone. If you feel more comfortable running with an unlocked bootloader then by all means go for it. But if you can toggle the OEM switch you will be allowed to bl unlock whenever you desire, they won't make that mistake again. Besides it was a Verizon model back then, all other models could bl unlock at will so this discussion is pretty much moot since the exploit was closed. I remember people were quite upset that the 2 could unlock but the 2XL could not.
[Google Pixel 7] JovialQuestion:
Okay. I'm going to assume you are confusing your experiences with mine. The pixel 2Xl "Tamien" 128gig "NON-VZW" model was infact able to be unlocked. However the Pixel 2XL "Tamien" 128gig "LGE" Wasn't supposed to be so that's partially correct. All of the Pixel 2XL 64gig models were not able to be unlocked. However after PIE update. The LGE 128gig was Mistakenly "DEPENDING ON the boot cid 000001 and not 000000 so the response of adb shell getprop ro.boot.cid = "xxxxxxx" To my knowledge no RMA devices were affected. So it allowed these devices to toggle the OEM switch and unlock. That's why after android 10. These devices can toggle if it lets them however the command will fail at fastboot unlock flashing and upon reboot the OEM will be unselected and you can toggle all you want. If you have one. I encourage you to factory reset without a sim card and setup offline. Enter adb shell pm uninstall -k --user 0 com.android.phone

Reboot.

Enable dev settings

Connect to internet

Then open chrome and navagate a few pages

You can toggle the OEM however it will not last a reset from settings only recovery and the unlock command wi grey it back out.

As the bootloader no longer has the command..

This used to also be a work around in itself until the removal of the ability

So as I have said in every post. I am not saying the devices were made to be unlocked I'm saying if you can unlock it unlock it before an update fixes a mistake that prevented you even if that is with some type of script or other means of unlocking it The unofficial way. Hopefully this explains it. I think you've been misunderstanding me from the start. So again this is just my experience in my opinion on why to unlock it..

I want to clarify something the pixel 2 XL in the 64 GB variety. None of them were unlockable please do not confuse the 64 gig with the 128 gig. The 128 gig that I have purchased over 20 of directly from Google or Amazon as they are a authorized vendor for Google. They have always been bootloader unlockable. Unless you financed with Google fi any US carrier that restricted the unlock ability. iE: Verizon. And if it were financed through Google fi once it's paid off then you will be able to OEM unlock it. But that information is incorrect the pixel 2 XL was able to be unlocked provided it was the right model handset. I think you have misunderstood me from the very beginning. I am including in my opinion to unlock it. Unlock it even if it's a third party way of unlocking it before you lose the ability to do so. I'm not sure how I haven't made this clear but hopefully this clears it up. And hopefully there won't be any more miscommunication. But it simply say the pixel 2 XL was not able to be unlocked is not correct.
[Google Pixel 7] bobby janow:
@JovialQuestion I get what you're saying. My bottom line is I buy now from Google only, no carrier branded phones for me. I can therefore unlock to my heart's content and that's not going away. I don't need to unlock it to be able to unlock it when I want. That was really all I was saying. Old Pixel 2 and 2XL are long gone out of my drawer.
[Google Pixel 7] JovialQuestion:
@Nateg900t hopefully we haven't confused you on it. I hope you are able to decide whether to unlock it or not. Sorry if this got a little off topic but ultimately unlocking your device is user's preference. If you don't plan to make any modifications on the device I would just leave it locked then if replacing the device is no obstacle. If you don't want to have to replace the device to get an update after the updates has stopped then unlock it as third-party updates are usually available shortly after the release.
[Google Pixel 7] Nateg900t:
Yeah, I unlocked my pixel 1 (Verizon model, before they closed that hole) and my pixel 3 and rooted both.

Decided to see how my experience would be with not unlocking my 7. After 5 months, I think I value not having to spend hours reading forums to make sure I've learned the intricacies of applying the latest update without a bootloop or losing access to features like tap to pay, and instead just updating my phone when the latest security update comes out...I do miss being able to freeze apps instead of uninstalling. And by the time Google isn't doing updates anymore I'll probably want a new phone because of crap battery life, and I'll relegate this one to around the house duties, and can unlock if I need.
[Google Pixel 7] JovialQuestion:
" Get Package Disabler (OWNER) " the one developed by "Policedeveloper"

just have to use dpm command for device owner and you can disable/freeze any app. (no Root).

Once you get the app it has instructions to set the device owner command
[Google Pixel 7] bobby janow:
That is only for a Samsung device or was. Last update I see is from 3 years ago. Do you have it working on a Pixel 7/Pro with no root?
[Google Pixel 7] JovialQuestion:
NOOO. the blue icon is the brown (OWNER) Is for any android device with the ability to use the DPM command android 5.0+ it sets the app as the device OWNER and disables packages with that policy.

Please read up on it. There is many posts on this platform alone about it.

Currently in use on all my devices. This one being Blueline pixel 3 with android 13

Package Disabler

The only NON-root solution that let’s you disable any unwanted packages that come pre-installed / installed with your phone / tablet.

www.packagedisabler.com

The command to activate

adb shell dpm set-device-owner com.pdp.deviceowner/.receivers.AdminReceiver

Ensure you have logged out all accounts and no apps are logged in. Restart then send the command. The command will fail if you have accounts logged in. If you do get a failure read the response and it will state at the beginning of the result why it failed. Otherwise once it says succeed simply reboot. You will see a notification "Device Managed By Organization" as long as this is displayed it's working you can now login to your accounts. Typical I set this after a factory reset. To ensure the command succeeds

https://play.google.com/store/apps/details?id=com.pdp.deviceowner

"I uploaded a copy of the apk I'm using"
[Google Pixel 7] andybones:
Same! Unlocked from Google is the way to go IMO.

You get the same device which works on all carriers but with the option and ability to unlock the bootloader which is how it should be considering we own and bought the device.

One thing with the Pixel 7 though I see I have the slower modem and no mmwave with the GVU6C model but I still get 5g and have zero complaints.
[Google Pixel 7] waywardfrantz:
Are you able to increase the maximum volume for bluetooth headsets with the device rooted? Or are there roms that offer that? Been poking around and haven't seen a direct answer. I know on my note 3 the bluetooth audio was something finnicky in a lot of apps, it would only connect as a communication device so the bass was just gone.
[Google Pixel 7] Klusio19:
For me the biggest dealbreaker is using Pixelify mod for unlimited Google Photos storage. I just love it.
[Samsung Galaxy A21s ROMs, Kernels, Recoveries, & O] RestlessGoose:
---

Disclaimer: This will void warranty.

You will need to unlock bootloader.

*All your data will be lost*

---

Info:

Android version 12.1 (12L)

July 2022 patch

Tested on A217F & Dual SIM working

GApps included so you don't have to flash them

Part 1 - Unlocking bootloader:

Skip this if you've already done it.

1. Enable Developer Options, go to OEM Unlocking and turn it on.

2. Plug in phone to PC, restart the phone and right when it turns off, keep holding VOLUME DOWN + VOLUME UP till you see the Download Mode

3. Hold VOLUME UP to enter Bootloader Unlock mode

4. Press VOLUME UP to accept, and let the phone restart and erase

* To check if it worked, head back to Download mode and check if "OEM LOCK" is "OFF"

Part 2 - Flash recovery:

1. Download Odin and recovery U7/recovery U6/recovery U5

2. Put device to Download Mode (Hold VOLUME UP + VOLUME DOWN while plugging in phone to PC)

3. Open Odin and hit AP and select recovery file

4. (optional) go to Options tab and untick Auto Reboot

5. Hit start

* If it fails with error "Only official binaries are allowed to be flashed(recovery)", then boot device up, connect to internet, and then change Date to some time ago like January 5th 2022

Part 3 - Flash the ROM:

1. Download and Extract the ROM

2. Download the kernel

3. Download and Extract platform-tools (ADB and Fastboot)

4. Open up Command Prompt and cd into platform-tools folder

5. Plug in phone to PC, restart or turn off phone and hold VOLUME UP + POWER for about 5 seconds. You should enter Lineage Recovery.

6. Tap Advanced, then Enter Fastboot

7. Type in command prompt "fastboot flash system " and drag the ROM .img file and hit enter. This should take around 3 to 5 minutes.

8. Exit Fastboot mode on the phone and go to Apply Update, Apply from ADB

9. Type in command prompt "adb sideload " and drag the kernel .zip file and hit enter. Press Yes when the phone asks to.

10. Reboot the phone.

Notes:

* DO NOT APPLY A SCREEN LOCK, or else the settings app will crash along with the setup wizard, and if you do it from settings you won't be able to change it, disable it or enable fingerprint unlock

* SuperSU root is pre-installed so you can 'adb sideload ' the UPDATE-unSU.zip from recovery, then 'adb sideload ' the Magisk apk attached below ("app-debug.apk") after renaming it to .zip

Credits:

@physwizz for kernel

Kernel source https://github.com/physwizz?tab=repositories

@phhusson for GSI ROM

Good luck!
[Samsung Galaxy A21s ROMs, Kernels, Recoveries, & O] oli231:
Why you don't Look on my thread?
[Samsung Galaxy A21s ROMs, Kernels, Recoveries, & O] RestlessGoose:
Hi,

I have tried the GSI you linked in your guide but it just gave me a bootloop similar to many other guides, including the Samsung PixelExperience Android 12.0 GSI further down in the comments. So after I did my own research and tries I put together this guide with the resources I used to make the device work.
[Samsung Galaxy A21s ROMs, Kernels, Recoveries, & O] salmonfall99:
thank you for all the effort made to give us an amazing experience I have a question when can we expect a stable version
[Samsung Galaxy A21s ROMs, Kernels, Recoveries, & O] 7MODE__TN:
I have U8 Binary what should i do about it ?
[Samsung Galaxy A21s ROMs, Kernels, Recoveries, & O] Keinergatitotriste:
Does it work on A217M?
[Samsung Galaxy A21s ROMs, Kernels, Recoveries, & O] Kevonism:
how do i fix the fingerprint?
[Samsung Galaxy A21s ROMs, Kernels, Recoveries, & O] Kevonism:
mine also u8, i use lineage recovery from youtube. and its work
[Samsung Galaxy A21s ROMs, Kernels, Recoveries, & O] nxs_neo:
Hi I did all the steps and it is stuck on boot screen showing Samsung Galaxy A21s.

I used u8 lineage recovery.
[Samsung Galaxy A21s ROMs, Kernels, Recoveries, & O] nxs_neo:
Hi is this working for you? Do you have a link to the recovery?
[Samsung Galaxy A21s ROMs, Kernels, Recoveries, & O] Kevonism:
u8 lineage recovery.tar

drive.google.com
[Samsung Galaxy A21s ROMs, Kernels, Recoveries, & O] shottiemodder:
Hi, i do all the steps in the tutorial and use the u8 bootloader and recovery that Kevonism has uploaded. But after the install via adb sideload it goes in a bootloop (with kernel flash). Could someone help me out?

My discord is: cristiano#0717
[Samsung Galaxy A21s ROMs, Kernels, Recoveries, & O] nxs_neo:
Same for me
[Samsung Galaxy S22 Ultra] Alexanderkrakn:
I need help, restore the factory, return to the one ui 4.1 rom, restore the phone again and it continues to give me the problem that after 5 minutes it tells me to enter the sim card. At first it gives a signal and data, then it 5 minutes later, only tells me to enter the sim card
[Samsung Galaxy S22 Ultra] malikin:
yes!
[Touch HD General] jackthekayman:
I've just hard resetted my hd, I've installaed network wizard but when I lauch it the filed country and operator remain blank...I can't choise and I can't configure...why? what can I do?
[Samsung Galaxy A51 Questions & Answers] bigzks:
I don't know if I'm in the real place, I'm really new here(about posting something)

So I got an a51 from my brother, it was rebooting constantly and wouldn't play or record audio. I tried a bunch of things that will be listed further. But you know now what I know. I can't tell when it started, the phone is kinda old. And that's what I got. Audio wouldn't play, I started to focus on that first. Weirdly enough when I first flashed stock firmware, audio was working just fine, until it rebooted by itself. Also, after that, I noticed build.prop was missing almost everything, including USB mtp settings, audio codecs, just quite literally enough to boot phone. I tried to change it for some fota.zip that came in ap with stock firm, no luck tho. If you think that's the problem, can you help me find a stock and not installation build.prop or idk?

It recognizes if the one connected is a headset, or a Bluetooth, or even the phone's speaker, but nothing. If I try to play an audio file it says the format is unsupported, and any application that uses microphone or audio output will prompt an error.

I've tried:

...Flashing custom audio (drivers? Idk, it was v4a and james)

....Changing the entire sub board, or whatever it's called in English

...changing settings

...nand option in Odin

...downgrading to android 11 and 10

Device:

...android 11 (it came as android 12)

...sm-a515f/t

...carrier: zto

I thank you since now sz