yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] gitrazorhub:
Of course. I'm using the init_boot.img. I was exercising brevity in my writing. Also, I'm on the 5 not 7.
[Google Pixel 7 Pro] Lughnasadh:
Are you in the right thread? The Pixel 7 Pro never had Android 12. Sounds like you might have another phone.

EDIT: I see you have a Pixel 5 so you are indeed in the wrong thread. Btw, you patch the boot.img for the Pixel 5, not the init_boot.img (The Pixel 5 doesn't have an init_boot.img as far as I know). Direct install will show up if you boot that patched boot.img (rather than flash) or if you are already rooted it will show up when Magisk itself has an update.
[Google Pixel 7 Pro] xunholyx:
On the Pixel 5 patch the boot.img
[Google Pixel 7 Pro] Badger50:
Moderator announcement
​

Greetings to all. Well, after reading this entire thread, I have edited several posts for content rather than removing them to keep the basic conversation

intact.

While I will give some of you credit for your, shall we say, Colorful Colloquialisms, many of them were removed since they were in violation of XDA Rule 2.3:

So please, let us treat each other with respect without the clorful language, and PLEASE, just report post rather than replying to them so as to avoid these types of situations. Thank you all for your cooperation, and have a pleasant and calmer day.

-Regards: Badger50
[Google Pixel 7 Pro] gitrazorhub:
Mea culpa. I got my threads crossed. If it's any consolation I followed topjohnwu's installation instruction to a tee for Android 12 and 13.
[Google Pixel 7 Pro] gitrazorhub:
My apologies for not using the proper nomenclature. I've been following topjohnwu's instructions perfectly. I get no installation option after booting immediately after the flashing of the patched boot image.
[Google Pixel 7 Pro] yurishouse:
One click root (especially on device) has been deprecated due to really huge security risk. You could be rooting your phone from malicious software without you knowing.

Also, third party rooting software has been useless for a long while now... KingRoot went out first, then SSU. They no longer support the newer generation devices.

As of needing a computer.... Use your local library computer is totally fine since you're not using much anyway.
[Google Pixel 7 Pro] HipKat:
Truer words...... :(
[Google Pixel 7 Pro] yurishouse:
In a sense it is. It really depends on your definition of the word "jailbreak" I guess. I won't argue with this further as your opinion is also valid
[Google Pixel 7 Pro] V0latyle:
The way I look at it is this:

Jailbreaking is an exploit used to compromise proprietary software, where the intent of the original design is for the user to never have the abilities/privileges involved or run unapproved software. In the designer's eyes, this is "bad" and should be prevented - and indeed Apple has made a point of doing everything they can to prevent it.

Unlocking the bootloader on the other hand is by design intended to allow the user to run custom software, including applying a patch or installing binaries to gain root privileges. This has always been intended to be possible from the start, in keeping with Android's open source nature - indeed, you don't even need root to install whatever apps you want from whatever source you want.

The "official" Android model is for the device to be bootloader unlockable, although it's been largely left up to the OEM to decide whether it's allowed. We've seen notorious examples on both sides of this aisle:

The Nexus/Pixel line for example was practically designed with developers in mind, and indeed have been the "proof" platforms for CTS testing.

Samsung devices often allow bootloader unlocking, but Samsung, in their obstinate insistence that they're a legitimate software company, has been making the process a lot more complicated with Knox Guard and Vaultkeeper.

Then there's Sony/Motorola/Realme, who have made the process more difficult by requiring an unlock token.

XIaomi makes you wait a week for the token.

Lastly, Huawei and OPPO do not allow unlocking the bootloader the "right" way, so unofficial methods such as low level firmware modification must be used.
[Google Pixel 7 Pro] hp420:
probably because you already have one and don't need to now come up with a way to save HUNDREDS OF DOLLARS just to flash the phone you JUST BROKE THE BANK to buy.

fucx google
[Google Pixel 7 Pro] hp420:
how convenient...google fucxed me on custom recovery, so now i have to send Google $300 for another piece of hardware to take its place?? a piece of hardware that's a literal paperweight except for fixing their fucx-ups in the first place???? i think not!! they should send me one for free. this is their mess.

fucx google
[Google Pixel 7 Pro] EtherealRemnant:
Google never guaranteed anything when it comes to third party development. Your frustrations are purely of your own creation. Sounds like it's time to just get rid of the phone and go to an ancient and insecure one that allows you to do what you want. I'm personally glad that Google shored up their security and continues to do so because while it makes modding it more difficult, it's making it more difficult for hackers to cause damage as well.
[Google Pixel 7 Pro] xunholyx:
You should have done some research before you bought it, instead of assuming that root methods haven't changed since whatever you owned before.

EDIT: You keep blaming Google. Why not the developers of the software that created one click root methods? They figured it before, why can't they figure it out now? Maybe it's their lack of interest in pursuing it because it's super simple to root now without a custom recovery (I agree with you there, why are they making it so hard for custom recoveries) because almost everybody with the money to buy a phone has access to a PC/MAC/Linux machine to be able to root their device.

BUT!!!! Even with one, your phone might not have an unlockable bootloader. That's why it's a good idea to see what it takes to root of it before buying it. Do some research on rooting what you are going to buy. If you had done that before buying the Pixel you wouldn't be so upset right now.
[Google Pixel 7 Pro] mavssubs:
Because those only work on older Android Operating Systems.
[Google Pixel 7 Pro] mebetree:
Hello, do you know if itd be possible to root my pixel 8 using that magisk app and without a pc? Ive downloaded magisk on previous phones and half heartedly attempted to root but its been way too complicated and 90% of the terminology is over my head. Any help would be greatly appreciated.
[Google Pixel 7 Pro] xunholyx:
I could walk you through it, but you'll need a PC, a Mac, or a Linux computer. I won't bother doing it here, because there are already endless tutorials here. If you can find a computer to borrow/use from someone else I'll give you directions. It would be better to contact me on Telegram with the same username.

ALSO!!! Don't use one click methods. Some were okay once upon a time, but now they are notorious for malware.
[Google Pixel 7 Pro] mebetree:
Thanks for the info! I can borrow a mac laptop, thatd be awesome if you could help me. Xfinity shipped my phone Friday but due to the long weekend ill probably have my phone by Wednesday latest. Should i go on telegram and type your username to get ahold of you? Sorry never used telegram.
[Google Pixel 7 Pro] stoag:
Um.... am I missing something or haven't devs already come up with ways to root without a PC..? you just need another rooted phone to use fastboot.
[Google Pixel 7 Pro] xunholyx:
Yes. But keep in mind that I am gone from home from 6am to about 5/6pm and am at work Pacific Time during the week. You can try to message me then, but the weekend would be a better time.
[Google Pixel 7 Pro] xunholyx:
From what I know for adb commands yes, but not for fastboot commands.
[Google Pixel 7 Pro] mebetree:
Ok awesome. I appreciate you. I live on the east coast. Massachusetts but im willing to do this whenever is best for you. Just let me know what day and time and im on it. Thanks again!
[Google Pixel 7 Pro] simplepinoi177:
@mebetree , if you want some to some light reading/research, you should look into Pixel Flasher (works on macs) -- if you are truly open to doing it with a computer (because that's a requirement for this tool), it's the easiest way to root (traditional for sure; i'm not sure about root methods like KSU, Kitsune, APatch etc.) any Google Pixel device (phones, folds, even the watches!)

📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.

DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...

xdaforums.com
[Google Pixel 7 Pro] mebetree:
Ok thank you! Ill check it out.
[Google Pixel 7 Pro] mebetree:
Wow. I just scanned through it and its like trying to read a foreign language tbh 😂. Id absolutely brick my phone if i tried using this tool. Thanks for trying to help me though but im way to dumb to use this tool successfully.
[Google Pixel 7 Pro] simplepinoi177:
mmmmm it's fairly straightforward....honestly, you'd have to set up adb/fastboot from platform-tools in the same way, then you could literally root in probably 7-9 clicks -- it does all the installing (will find & download all that you need from the program itself without you going to any github page or pulling/pushing any apks), adb & fastboot commands, device connecting, locations for where/what to download and process/use it to on your computer once you show it where, and so much more.

I don't know the step-by-step method @xunholyx is planning on walking you through, but if it's in any way the manual method, all PixelFlasher is doing is entering all those commands for you with clicks of buttons -- rather than you downloading & processing an image via Magisk Manager app yourself or any adb/fastboot commands; or, lord forbid, the ultra manual method of doing everything through a command prompt.

I'd hope you'd reconsider, but to each their own...
[Google Pixel 7 Pro] xunholyx:
Forgot all about PixelFlasher. That would be the simplest way. I was going to help him with manual commands.
[Google Pixel 7 Pro] simplepinoi177:
Yeah...I also feel that's the simplest way. Though you might have to go about a bit of convincing.....but I commend you for even offering to walk through particularly with the manual commands...

I kinda only know the manual commands -- it's how I do my monthly updates.

But I believe I read a while back that Magisk (Manager app) can now process an OTA firmware file, and I know their install to inactive slot has been corrected and working for a while (unless you have to have patched the init_boot partition first to be able to have the option), so I figured that's how you were going to go about it; i imagine if all that is correct then it can go without adb or fastboot or manual commands....
[Google Pixel 7 Pro] bdr127:
Do you not remember a few days ago you asked in the Pixel 8 PixelFlasher support thread (https://xdaforums.com/t/pixelflasher-for-google-pixel-8-support-thread.4635556/page-14#post-89526002) about a "non-pc root solution," and I replied to you? You even acknowledged it and asked an additional question to which I replied. Hmmm......
[Google Pixel 7 Pro] mebetree:
? Yes you said its not possible. I dont understand the reply.
[Google Pixel 7 Pro] mebetree:
My phone just got in, but im way too stupid with things like this to be able to successfully root my phone. Id need to be told precisely what to do step by step. The other thing is, ive used 1 non 1 click root method previously and that was odin. I could never get Odin to work on mac and i believe i even soft bricked one of my phones trying. Tbh im a dumbbell lol. Watching a few youtube tutorials in every one there are multiple options to achieve the same result in the series of steps to root and that alone confuses me. Point being id need everything spelled out for me because if one step wasnt explained id screw up for sure.
[Google Pixel 7 Pro] bdr127:
In the PixelFlasher support thread, you were asking if you could use PixelFlasher to unlock the bootloader and root your phone.... without a computer. To which I replied that PixelFlasher requires a computer.

Then you asked if there was any way to unlock the bootloader and root your phone by connecting it to a second phone (a Samsung "S14".... Was that supposed to be A14 or S24?), to which I initially mentioned a Magisk module ("adb ndk" by osm0sis).... but then I edited my reply after remembering that the module will work for the adb commands needed for the rooting process, but it wouldn't be able to unlock your bootloader (which uses fastboot commands) and that is the necessary first step.
[Google Pixel 7 Pro] mebetree:
Ok thanks. Id like to try that pixel flasher but i only have acces to a mac and everytime ive attempted to use odin or any other root tool itd never work and id download a million drivers trying to get whatever program to work on mac. I appreciate the replies though.
[Google Pixel 7 Pro] bdr127:
Can I ask what it is you are looking to accomplish by rooting your phone? Is there something you're trying to do that you can't do without rooting it?
[Google Pixel 7 Pro] mebetree:
I like being able to modify files for gaming, idk if there are any custom roms but if so i love switching through and using dif ones. I like to delete all apps i dont use of which there are several. There are a few more reasons i cant think of as its been years since kingroot worked, or odin (i believe odin works only on Samsung, whatever it works with i haven't had for a long time).
[Google Pixel 7 Pro] bdr127:
I'll warn you that things are a lot different in the rooted world than they used to be.... You used to be able to root easily and then use any and all apps and games with no repercussions. Now many apps are able to detect various root methods and/or installed root modules. Getting those apps to work requires a lot of fiddling, trial and error, and research.

Then there is the whole Play Integrity thing.... It's a constant fight in a cat-and-mouse game with Google, requiring frequent updates and modifications. (Just take a look at the 800 pages of the Play Integrity thread!) Some apps require a certain level of "integrity" and won't work unless that is achieved. With some apps and even some games, the highest "strong integrity" is required, and simply unlocking your bootloader will make your phone ineligible for "strong".... and there is no work around or "hack" to make it work. If you are using various kernels that may be banned by Play Integrity, you'll need to use a hex editor to modify your kernel to pass integrity. Many custom ROMs (especially ones that are unsigned) won't pass integrity, so you'll need to compile your own ROM from source code and manually sign it with private keys. Etc, etc, etc...

All of this to say.... Please fully know what you're getting into by unlocking your bootloader and rooting nowadays. If simple fastboot and adb commands to unlock and root seem very difficult and complicated, then the more advanced tasks to even make some apps simply function could potentially be more than you bargained for.
[Google Pixel 7 Pro] simplepinoi177:
Some info and links will help you get started....

source: Stack Overflow

source: Android Developer site

Platform Tools (adb & fastboot) for Mac

https://dl.google.com/android/repository/platform-tools-latest-darwin.zip

Pixel Flasher for Mac

https://github.com/badabing2005/PixelFlasher/releases/download/v6.9.5.0/PixelFlasher.dmg
[Google Pixel 7 Pro] Locoman_:
I remember trying that back in the day. It flooded my my phone with all kinds of malware. I'd have to wipe everything..
[Google Pixel 7 Pro] mebetree:
Wow! Ok the

Wow! Thanks for the info. Im not rooting, that's too much to deal with thanks.
[Google Pixel 7 Pro] xunholyx:
ODIN is for Samsung devices only afaik
[Google Pixel 7 Pro] mebetree:
I know, was just saying thats the only non 1 click and otherwise the only program not on the phone ive ever used.
[Google Pixel 7 Pro] mebetree:
So ive had the pixel for a few weeks and overall i love it. Its a million times better than my galaxy a54 5g whatever phone. Also i think my Xfinity pixel is unable to be rooted as the option for oem unlocking is blacked out. Also i did an imei check for some reason or another and verizon popped up somewhere. Possibly a merger? I heard verizon phones cant be pem unlocked and that same thing shows up when trying. Anyways, there isnt alot of bloat and im not having any real urge to root as is thanks.
[Google Pixel 7 Pro] simplepinoi177:
glad you're enjoying the phone.

Unfortunately it's not quite a "merger", but Xfinity Mobile is an "MVNO" of Verizon. And Verizon notoriously locks down all their devices' Bootloader under all circumstances. So, regretfully, you still not be able to root that device. If you're capable, next time, order a non carrier global variant straight from The Google Store or Swappa (if you're alright with 2nd hand)...
[Google Pixel 7 Pro] Locoman_:
I've used Swappa for my last two phones. Both were used but were in "mint" condition. My next phone will be via Swappa for a "mint" or "new" condition phone.
[Google Pixel 7 Pro] mebetree:
Thanks! Also ive been streaming xbox games including assassin's creed and not only does the game look amazing its smooth and i played for hours with 0 issues overheating or even getting overly warm! Love the phone.
[HTC Excalibur] prelives14:
Hello,

When i edited the registry for settings to use a created icon instead of the default one, the new icon only shows up for "silent" (i guess the phone was turned to silent when i edited the registry). When the phone is in normal, vibrate, etc. mode, the icon won't show up. I tried fixing this with CHome Config, but that didn't help.

Here, in silent mode, the icon shows up:

And here, in normal mode, the icon doesn't show up:

Additional info:

Using Rose 1.3 ROM

Edited the registry in: HKLM\Security\CHome\Default Settings\Settings\Profile

and: HKLM\Software\Microsoft\CHome\Settings\Profile

(in both of these i edited the "PICTURES" and "PLUGINICONNAME" strings and put the URL of my created icon)

Any one know how to fix this? Sorry if this is a dumb question, or has been answered before (i couldn't find anything when i searched).

Thanks in advance!!
[Android Q&A, Help & Troubleshooting] del32:
Hi everyone, I am currently at work and we have two Honeywell CT40 devices. We need to somehow get the apk for our stock management app onto one of them. It fails to provision with a cannot find wifi error. Does anyone know how I can pull the data i need from a provisioning qr code?
[General Topics] troyer1234:
hi

i have a Redmi Note 8 with RROS custom rom installed

sometime the network goes on LTE+ but i want to know if there is a way to set it only on LTE+ ?
[Wear OS Q&A, Help & Troubleshooting] dummy76:
Hi everyone,

I'm a bit new to watch / wear os dev but have lots of experience in .net and java. I've developed an app for AOS 9 and am doing some testing (sports app) - but have a bucket of older watches on hand that I feel I could use for extended testing if I could just deploy the app to the watches. Specifically, I have Ticwatch e and s watches here along with some random fossil watches. Anyway, is there a way to develop apps deployable to AOS 8 watches? I understand I'll need to sideload the apk since I can't upload to the store, but it would at least mean I get some use out of these watches! Thanks for the advice.
[Wear OS Q&A, Help & Troubleshooting] a1291762:
When you make your app, set the minimum version low enough to target Android 8. You can target whatever is current, just ensure the minimum is low enough.

I used a TicWatch E until fairly recently so this is how I made my custom watch face.
[Wear OS Q&A, Help & Troubleshooting] a1291762:
I looked up my build.gradle for the settings...

android {
compileSdk 31 // Android 12
defaultConfig {
minSdk 26 // Android 8
targetSdk 30 // Android 11
...
dependencies {
implementation 'com.google.android.support:wearable:2.8.1'
compileOnly 'com.google.android.wearable:wearable:2.8.1'
implementation "androidx.wear:wear:1.2.0"

I am compiling against Android 12 because the androidx.wear:wear:1.2.0 dependency requires that.

I'm targeting Android 11 because that's what the Android Studio Wear OS 3 emulator image runs (so it is something I'm actually testing, just not on hardware). The minimum is Android 8 so I can run the resulting APK on a TicWatch E.

You'll notice I am using the old android support wearable dependency. I had some old code and examples I started from and I wasn't much interested in translating it all into the new androidx interfaces. If you're starting from scratch, or you're already using androidx interfaces, you should be able to continue doing so. Note that Google officially states "The Wearable Support Library does not work on Wear OS 3." but ... it works fine on the emulator image, at least the things I use do.
[Google Pixel 7 Pro] Jimmyxdlol:
Hi, so I need a little help here as I am not sure what I can do anymore. So yesterday got my new phone and rooted and everything worked fine. Revolut and my other banking app worked, in fact everything worked fine netflix google wallet etc.

Today i don't know what happend but my other banking app which is Reiffeisen Smart Mobile stopped working while everything else including Revolut(a banking app) still works. I tried to downlaod other common banking apps in my country and they are not working aswell. I have tried to switch to Shamiko module but its still not working.

Does anybody has any ideas what went wrong or what else I can try?

Oh yeah I forgot to mention that YASNACgives me basic integrity pass cts profile match pass andevaluation type basic.

Play Integrity API Checker giiives me MEETS_DEVICE_INTEGRITY and MEETS_BASIC_INTEGRITY green and the other one red but that is fine from what I know.
[Google Pixel 7 Pro] ffuser1:
add the desired apps to the denylist, but don't enable the denylist. seems counterintuitive but it's needed for shamiko. enable zygisk and shamiko. if that doesn't work, check the magisk forum as certain banking apps simply will not work and others may have their own tricks to get working.
[Google Pixel 7 Pro] krakout:
For me Wallet won't work, and my main banking app probably sees something as it won't enable fingerprint login... So there's something at play here probably.
[Google Pixel 7 Pro] EtherealRemnant:
Some apps just won't work no matter what you do. In fact there is an app called AirFrozen - https://github.com/hyongbai/AirFrozen that can freeze Magisk from the system and still my app Security Service Federal Credit Union cannot even get to the login screen.

You have to decide if being forced to use the bank's website is a worthwhile tradeoff for what you get from root.

Wallet works. I hid all Google apps. But trust me, just get a watch. I forgot my phone at home tonight on a liquor run and I decided to try my (unrooted) Samsung Galaxy Watch 4 LTE edition anyway... Even though it was not connected to the network (my provider doesn't have watch capability yet) and thus had no data, the transaction went right through. This was so thrilling I literally did a tiny jump in the air and a very very short dance at the grocery store (note to self: don't go there buzzed again, really hope it was slow enough I won't be TikTok'd)... I can do whatever I want with my phone and as long as I don't root the watch, I can always tap to pay! Seriously cool as hell. Plus the rotating physical crown on the watch makes it look like an actual watch instead of a piece of glass on a fancy strap.

But yeah... All my apps work when I use AirFrozen except that SSFCU app...
[Google Pixel 7 Pro] otonieru:
Try "IAmNotADeveloper" module. I used to whack my brain looking for a way to bypass my banking security, turned out the lazy ass developers of these respected bank decided to simply detect whether developer option was turned on or not to assume whether the phone is rooted. Such a lazy and stupid way.