yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7] mrnapolean1:
1. Amazon Flex refuses to run because it detects root

2. Best Western Opens and closes with an error saying there's malware (magisk) on the device (attempted to obscure the magisk app as "Settings 2.0" but that didnt work)

3. Uber Driver is saying it cannot authenticate the device.

4. Roadie Driver says this app isnt compatible with modified devices.

I would just unroot but ACR Phone requires root to function. And I have to have ACR phone on my device. (There is no alternative)

Is there anything I can do to make root untraceable (make the apps think this device is factory and unmodified) but still have it available for when ACR Phone needs it?

Its a Pixel 7 with Build number TQ2A.230305.008

Under Magisk it says: Installed 25.2 (25200)

Under Modules it says:

ACR Phone Helper (APH) 6 by NLL

Systemless Hosts 1.0 by Magisk

Universal SafetyNet Fix v2.4.0 by kdrag0n

Is there anything I can do to get these apps above to work on my rooted device?
[Google Pixel 7] Hitman478™:
Have you tried this: https://xdaforums.com/t/october-4-2...r-root-pixel-7-pro-cheetah-safetynet.4502805/

Have you enabled Zygisk and hide the apps (from zygisk list) that detect root? Have you tried to hide magisk itself?
[Google Pixel 7] simplepinoi177:
This is a very loaded question with a very complicated answer....

There are a large number of threads dedicated to answering this question; both in general or individual apps. The search function will be most helpful in this regard. So I will answer a bit of it...

Here is a post of mine that covers much...

As for Uber Driver (and Roadie Driver, I imagine as they seem similar), I was involved in a thread/discussion where one of the members found a way, but it was rather convoluted and success hasn't been reproduced other than for himself. You can find his solution HERE .
[General Questions and Answers] gojo123:
Hi,

i was planning to root LG leon h320 but i cant with kingoroot or any other, but framaroot is the only one to help me but it says: Check Vurnabilities: your device seems not vulnerable to exploit included in framaroot

Any fix? Also Bootloader is locked
[Introductions] Peelp5090:
Hello there My name is Vincent, I hope I caught you doing exceptionally well today! The reason why I decided to name myself Archos fan is because my favorite looking tablet ever is the Archos 101 internet tablet I find it quite interesting how I managed to get Google accounts on it, I decided to join XDA to to share some daily Android information and to talk to some other people like me! I hear the people on this site are very nice and always caring. I hope I enjoy my stay at XDA!
[Introductions] TopNotch729:
Hello Vinny. Enjoy your stay at XDA!😉
[Introductions] Peelp5090:
i see your new to i just got my badge of member
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] kudos1uk:
I have bought 2 Toocki 67W GaN chargers one with a Euro plug ad one with a UK plug.

This is what I find:

Use original phone charger and cable = 67w charge (on screen)

Use new 67w charger and original cable = Mi Turbo Charge (on screen)

Use new 67w charger with a 100w rated TypeC to TypeC = Quick Charge

Use new 67w chrger with a Ugreen 240w rated TypeC to TypeC = Quick Charge

Exactly the same result with either the new UK or Euro plug charger.

The phone is fully updated original untouched ROM.

The only way I can achieve a 67w charge is with the original charger and cable, is there something in the charger that tells the phone the original charger is in use and limits the charge if not?

​
[Touch Pro, Fuze Themes and Apps] CR7KB24:
Does any one know the manilla files that make this possible like the images and everything else because i want to get the TF3D in landscape mode on my Fuze with original HTC Black theme but i don't know what manilla files i need, i have tried Herg's v7 but for some reason the peoples tab won't show on mine,

so please any help would be greatly appreciated :)

-CR7KB24
[Touch Pro, Fuze Themes and Apps] Warjcowski:
NM. uve tried this sticky... http://xdaforums.com/showthread.php?t=447056
[Touch Pro, Fuze Themes and Apps] CR7KB24:
I said that that theme won't work on my Fuze, and have tried asking this question there and have gotten no response.
[Samsung Galaxy S22 Ultra] trackingmystuff:
The list of programs on the device installed are a bunch of dating apps, card skimmers, alphapro, AnLunux, Bakkt, Bingx, appcall, configure for kodi, control center ios15, yplus classifieds, evident, Gofundme, invisblepro tor plus firewall, kodi, link to microsoft, linux deploy, live mobile phone locator app, metroplay, metrozone, NFC/RF reader writer, real vnc Remote Desktop, reverse phone lookup, termux, upjoy, venmo, userland, wink, watchworld, total commander, spyradar find hidden cameras, try rewards giftcards. So whatever this is, it doesn't look good.

I believe they have converted it to run on an iPhone 15 distro, and are using it to steal people's card info, watch tv, and mine while they sleep. I can't access it because of the invisblepro tor plus firewall, but am still recieving location data because they did not write over the imei's its 7 miles away. Already contacted the police, went to location, following on smartthingsfind, and am looking for an alternative solution to shut down tor temporarily, and lock them out until the police can get it.
[Samsung Galaxy S22 Ultra] Oswald Boelcke:
@trackingmystuff Thread closed!

However, I'm glad to see that you've followed the advice of my esteemed team mate @Clark Joseph Kent when he closed your other related thread: https://xdaforums.com/t/closed-stolen-galaxy-s22-ultra.4634857/post-89088984

In future you might want to consider to protect your mobile device even better than a hand gun if you convert the mobile to such an omnipotent privacy and more targetting weapon system.

Regards

Oswald Boelcke

Senior Moderator
[Samsung Galaxy M21 ROMs, Kernels, Recoveries, & Ot] ghazz_<>:
View attachment 6020154

/*

*Disclaimer
*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.

*/

Introduction :

OrangeFox Recovery is one of the most popular custom recoveries, with amazing additional features & fixes

Features :

- Synced with the latest Teamwin changes
- Designed with latest Material design 2 guidelines
- Implemented support for Flyme and MIUI OTA, and incremental block-based OTA in custom ROMs
- Included assorted customizations
- Inbuilt patches, like Magisk and password reset patch
- Several addons
- Password protection
- Fully open-source
- Frequently updated

Build Specfic Features :

- Passes AVB (no need to flash null vbmeta)

Changelog v4.2:

- Added nano
- Added bash
- Settings now persist (on encrypted devices)
- themes work now (on encrypted devices)
- made the device trees compliant to official maintainer guidelines

Notes :

- Ofox App Manager does not work on encrypted storage
- The ofox settings are stored in /data/recovery now to make the settings persist on encrypted phones , so it is advised to make a backup of your settings (exynos moment)(curse sammy)
- Fixed all the bugs I could find myself , need testers for proper testing

Bugs :

- Decryption (cuz exynos)
- Found any tell me

Downloads :

Releases · kartik gupta / ofrp_device_samsung_universal9611 · GitLab

GitLab.com

gitlab.com

Device Trees :

kartik gupta / ofrp_device_samsung_universal9611 · GitLab

GitLab.com

gitlab.com

Credits :

@TotallyNotH & @KrutosX for creating device trees
@kartik01_g(me) for patching ofox trees for avb and building
@ ofox dev team for helping with avb fixes
@ronyatech for grass kernel
@pikachuxaa for lending his laptop to build on

Spoiler content hidden.
[Samsung Galaxy M21 ROMs, Kernels, Recoveries, & Ot] ghazz_<>:
reserved
[Google Pixel 7 Pro] xflowy:
I am on a rooted stock a14 phone, running LSPosed to get AOSPmods working.

I just updated to latest LSPosed version and this happend: s. attachment.

Everything is so small... how can I fix this?

Thank you guys!
[Google Pixel 7 Pro] sawdoctor:
There's an issue with the latest lsposed and the framework mods in Aosp mods. Downgrade (flash previous lsposed) until aosp mods is updated Theres more info the telegram group
[Google Pixel 7 Pro] xflowy:
Yea I figured, but I somehow made it worse by downgrading and resetting my DPI. Now I cannot see what I am entering in the PIN menu at boot up. Can I somehow disable the modules in Fastboot? Or would a stock re-flash solve it?
[Google Pixel 7 Pro] sawdoctor:
You want to disable the module? The easiest way is to boot into safe mode, that will then disable all your magisk modules on the next reboot
[Google Pixel 7 Pro] fijasko:
ah, damn. wish i saw your post earlier.

do you even have AOSPMods installed?

i had exactly the same problem a couple of days ago, everything was in tablet mode, smallest width in developer settings changed from the default value and wouldn't stick, and playing with the display text and size option just made it worse, as well as the changing of display resolution.

i was on lsposed v. 1.9.1, not the latest.

it drove me crazy, but i finally figured out that AOSPMods was the culprit.

i reset all settings through the app menu, restarted the phone and completely uninstalled AOSPMods. then restarted phone again.

in developer options, smallest width, i entered 411 which is the dafault value for P7P.

i reinstalled AOSPMods afterwards and it worked fine.
[Google Pixel 7 Pro] simplepinoi177:
This has happened to me for some reason earlier this year -- I never could find out what was causing it -- and you change DPI in Developers Mode | Drawing (section) | Smallest width = 485dp (my personal display slider setting "Display Size" is set all the way to the left, so 485 might be indicative of that, but at the very least 485 is my default and should get you back to at least being able to customize the "Display Size" to your preference).

This is just to change the screen resolution -- so if this is the reason why you can't see the PIN menu at boot up, then this should help. If it's another reason (OS or root related), this has a chance of not improving things....
[Google Pixel 7 Pro] fijasko:
has it always been 485p as your default smallest width value? what is your display resolution, high or full?

i thought the default was 411.
[Google Pixel 7 Pro] simplepinoi177:
That's why I couldn't quite remember, so I Googled it a bit and found this Reddit post:

https://www.reddit.com/r/Pixel6/comments/12t7gb5
So, apparently, it seems to be default for this user and/or at least on the Pixel 6....

So, funny side-story, when this first accidentally happened to me, I kinda freaked out at the weird new layout and new buttons! I had to search it up a bit to find out that you can put a Pixel in "tablet mode" (I think in preparation for the Pixel Tablet and Pixel Fold) by doing this or when this happens! For whatever reason (again, I could never figure out what was causing the glitch), this would happen to me now and again; I actually hated it because the glitch would reset all my homescreen -- I was able to restore most of it from a backup (Swift), but it would still get rid of/not-save all widgets (not shortcuts, but active widgets though).

IIRC, my wife's phone might've been set at 411; she liked her display a bit more zoomed in (until I convinced her what she's missing without it zoomed all the way out and she can just make the font size bigger then...)
[Google Pixel 7 Pro] zgfg:
The command is for ADB, hence not for Fastboot mode (and it will uninstall all modules on the next reboot):

adb wait-for-device shell magisk --remove-modules

You can also disable a particular module, eg:

adb wait-for-device shell su c- touch /data/adb/modules/zygisk_lsposed/disable

You must start the command before/while the phone is booting and reboot afterwards

But it doesn't work on all phones - adb wait-for-device does not catch up or catches up at the wrong time regarding to Magisk

There is a better way - boot to Android safe mode and then reboot to normal mode. See Magisk User guide on the Magisk GitHub, how to deal with modules causing eg bootloop

However, if you have TWRP, it will be a piece of cake - run the following command from TWRP Terminal:

touch /data/adb/modules/zygisk_lsposed/disable
[Google Pixel 7 Pro] xflowy:
Thanks guys!

It first worked. Now, after a reboot I am back to screwed up DPI. Now everything is so small, that I cannot navigate to dev options to change it. Is there a command to do it?

Disabling modules and **** doesnt work. I tried everything.
[Google Pixel 7 Pro] simplepinoi177:
I'm glad it worked for, sorry it didn't keep....

A quick Google search resulted in this; try this adb command out and see if it does anything adb shell wm density 485 && adb reboot.

*note: I recently did adb shell commands after years of never doing it. I had forgotten that in some instances you'll have to enable it in Magisk (at the time it was kingroot); sometimes it doesn't even pop up with the prompt and I had to go into Superuser and manually enable/check it....
[Google Pixel 7 Pro] xflowy:
I factory resetted the whole thing..the was no saving haha

thanks man!
[Google Pixel 7 Pro] simplepinoi177:
That sorta sucks....but glad it's back up and running properly though!
[Google Pixel 7 Pro] gpvecchi:
I have no issues with mine...
[Google Pixel 7 Pro] xflowy:
i read somewhere that lsposed new version and/or aosp mod breaks sth (on a14)!? is that confirmed or was it really just me?
[Google Pixel 7 Pro] HipKat:
Uninstall AOSP Mods, update Lsposed, reinstall AOSP Mods. All good!
[Google Pixel 7 Pro] simplepinoi177:
I also read somewhere that AOSP Mods Canary versions is working well enough with LSPosed now (AOSP Mods stable is having issues with LSPosed)....
[Google Pixel 7 Pro] HipKat:
I'll have to check. After I reinstalled all my backups on my P7P yesterday, I haven't setup AOPS Mods yet but I did install it in Magisk sop I just need to get into the app
[Google Pixel 7 Pro] simplepinoi177:
So I think i found what I was referring to from the below quotes
[Google Pixel 7 Pro] Fishawy:
I had this problem about a week ago, and nothing worked including the above density adb command. It was indeed AOSP Mods (me playing with the settings).

I asked folks on Telegram for help, and the only thing that worked for me was this command.

adb shell wm size 1080x2400

Have since restored my device to a proper DPI, and I even reflashed AOSP Mods and restored a config I had backed up.

I guess it might be something that gets triggered when you apply certain changes in AOSP Mods settings, but I can't say for sure.

I now have the above command saved everywhere in case things go wrong.

Sucks you had to reset for this, and sorry I just saw this thread.
[Google Pixel 7 Pro] xflowy:
And it happened again. Am I the ****in only one, that is getting this issue? It's definetly the AOSP/Pixel Xpert Module. Happened while i was browsing the app and just clicked on an settings entry (think it was Themes). Now my DPI is ****ed again. Managed to go into settings with a ****ing magnifier and switched back from a DPI of 1973 (!!!) that was set by the app back to 512.

Went into the app to set everything back to default and delete this ****. When reverting back to default it again ****ed my DPI up and now everything is so large (probably a DPI of 20 or so) that I cannot see 90 percent of the screen and I definetly have to factory reset again. Again losing my stuff.
[Google Pixel 7 Pro] Locoman_:
I think this issue was recently posted and you are not alone.
[Google Pixel 7 Pro] simplepinoi177:
I recall having this issue in March or April....but I don't know what resolved it because it stopped. But it happened to me like twice a week and I hated having to reset all the shortcuts every time. But it was definitely AOSP Mods that was causing it....

But if you let go of Pixel Xpert, would you really need to factory reset? You can't/don't-wanna manually change it (adb command or trying to scroll as much as you can)?
[Google Pixel 7 Pro] wangdaning:
Instead of factory reset couldn't you just flash back factory init_boot and remove the module?
[Google Pixel 7 Pro] xflowy:
the people in the module thread claim that no one had the issue before 😄
[Google Pixel 7 Pro] xflowy:
when the density was that high and managed to find the setting in dev options by increasing the font size (went almost blind there). then when it changed it to a low dpi there were like two big letters only showing on the screen. no chance to navigate. i then made the error of rebooting the phone (before trying out the adb command, no idea if it works tbh) and then i couldnt enter the pin any more because the screen offered only a fraction of the usual size.

no. the change the module inflicts persists without the module existing.
[Google Pixel 7 Pro] simplepinoi177:
Yeah I imagine it would persist as even if it is the module's fault for changing the DPI, the DPI is set on/by the system -- so removing the module wouldn't necessarily change it back what's on the system and/or reset it back.
[Google Pixel 7 Pro] xflowy:
Could a mod edit the title to: "AOSP/Pixel Xpert Mod messes with dpi and screen size" or sth like that?
[Google Pixel 7 Pro] simplepinoi177:
I/We sure can.

But just for future reference, you should be able to do this yourself as OP -- the 3 dots next to "Search this thread" at the top should allow you to edit the title as you wish (I'll refrain from changing it just yet to give you a chance to change it to something you intend for first).

Additionally, if you need to get the Moderator Team's attention on anything (a post/thread rule breaking, request to move/delete a post, requests to add reserved posts, etc.), it's best to report the post/OP as it directly & immediately brings it to our attention; vs. us just so happening to stroll into a thread & its new posts and seeing the request....
[Google Pixel 7 Pro] YKS_Gaming:
welp it seems that there is now one more victim of this.

Got the bug after messing with the force android taskbar and/or pill size/shape/color toggles

It will then make the dpi very big(over 2000), then after you try to set it back in developer settings and then mess around again in the app, it will try to set a dpi that is too low and then proceed to crash the systemui

my efforts to recover it had been unsuccessful, the phone would just get completely stuck at boot logo before the animation could start.

Trying to use windows manager through shell would return cmd: Can't find service: windows

presumably everything can't be loaded because the system ui died?

Anyway reflashed everything in the end
[Google Pixel 7 Pro] xflowy:
@YKS_Gaming i feel ya. you on stock a14? any custom kernel? please report in the xpert thread. perhaps this gets the attention of the dev there. he wouldn't reply to me any more when i tried it.

system ui didnt crash for me tho.

could you elaborate what you tried with windows manager and what that even is lol. i only use the usual cmd window thing.

perhaps i could have salvaged it in my case (if i hadnt rebooted) since system ui was still there.

also: what you mean by reflashing? you didnt need to reset/wipe?
[Google Pixel 7 Pro] YKS_Gaming:
It was on stock android 14 with kirisakura 2.0.2.

I tried to use adb shell wm size 1440x3040 and adb shell wm density 484 through the command prompt on my PC, but wm doesn't seem to be loaded which throws out the error

It was all broken and messed up since the minimum density presumably was set way too big and only the status bar symbols can even be displayed. I also think the systemUI started crashing at this point, since I remembered there being black screens and it attempting to show a dialogue box.

I had to wipe everything in the end since it was in a bootloop and couldn't get to the boot animation(stuck on the Google screen).

Now here is some speculation on what could have happened:

Perhaps the force android taskbar app requires a higher minimum density to be set to run, in which case pixelXpert/AOSPmods tries to momentarily raise the density to get it to run and then set it back. Perhaps here the taskbar app crashes due to some unknown reason and could not start(or starts in a weird way) and pixelXpert/AOSPmods just tried to raise density again and again.

This is all speculation though, maybe I'll take a look on GitHub this afternoon to see if this could have happened.
[Google Pixel 7 Pro] YKS_Gaming:
ok, it bootlooped again, but this time without aosp mods/pixelxpert.

This time i rebooted after enabling use ANGLE display driver and it just hung on the google logo, so maybe it wasn't AOSPmods

Will edit once I fixed it again

EDIT: reverting to stock kernel with steps under the kirisakura kernel thread fixed it WITHOUT wiping and losing data. Bonus is that if you already have a magisk patched init_boot.img, then you don't even need to reroot it(well technically when you flash the patched init_boot.img you are rerooting it)

Steps to recover if anyone needs it, its mostly copied over from Kirisakura's thread.

Hold power and volume down to reboot into bootloader, alternatively hold power button and use the command

Once in bootloader, use the following command, and replace xxxx.img with the respective files in the stock factory image from google.

Then boot to fastbootd with the command

Then use

and then reboot

Althought the reason for the bootloop is still unclear, at least now I can narrow down to the things I have installed in both the bootloops:

1. kirisakura kernel 2.0.2, which includes a new graphics driver from QPR A14 beta, and imo the graphics driver and me messing with ANGLE settings would be the most likely cause of the bootloops

2. Play Integrity Fix/Shamiko/Google Photos Unlimited Backup magisk module, which seems to be unlikely since I couldn't even access magisk during the bootloop (adb shell magisk --remove-modules just returns not found error), and from what I know, magisk starts loading after the boot animation, during the big "G" logo, so it would seem pretty unlikely for magisk modules to be the cause.

Anyway, will stay on stock A14 & stock kernel with magisk to see if it bootloops again
[Google Pixel 7 Pro] xflowy:
@YKS_Gaming glad that you got it worked out the second time, although the bootloop issue you refering to there isnt the one I was expierencing. I had no issues with bootlooping, "just" the density/screen size thing. Which cant be fixed by flashing stock boot either.

It is also definitely an AOSP/Pixel Xpert issue since, that is the only module I had installed both times, it also happened twice while just navigating in the xpert app (doesnt matter if you change something navbar related or sht else) and was even made worse by resetting to default in the app.
[Google Pixel 7 Pro] YKS_Gaming:
you can try using scrcpy(a tool to project your phone's screen to PC on github) to navigate easier if you have a PC(though you will have to enable ADB debugging some way)

you can also use

to try to set the minimum width back to normal, and

if the resolution/aspect ratio is also messed up
[Google Pixel 7 Pro] Fishawy:
Had the same issue with the latest Kirisakura kernel (older ones are fine) and without any Magisk module. Reflashed stock without wiping to save my device.
[Google Pixel 7 Pro] xflowy:
@YKS_Gaming if you ever find out, what the dpi/screen size issue is caused by, let me know. Would love to use the app, but in the dev thread, there is no real support present.
[Google Pixel 6a] atreyu 96 2077:
I tried flashing all (base) firmware iterations from launch to try to get the uncertified notification and inability to use pay, reverted. Didn't work

Also camera is crashing non-stop

Android 14 first stable build

Could I get any help, suggestions or advice?
[Google Pixel 6a] Dopamin3:
Use Android Flash Tool

Android Flash Tool

flash.android.com
[Google Pixel 6a] Zaxx32:
Just don't try n take it back to A12...that RBP ain't no joke!
[Google Pixel 6a] atreyu 96 2077:
Rbp?