yashsingh1/xdaforums huggingface dataset:
[OnePlus 8T Questions & Answers] Sami_Q:
Phone: OnePlus 8T

Build number: KB2003_11_C.36

Android Version: 12

Model: KB2003

Hi everyone,

ORIGINAL PROBLEM (Partially fixed): "I recently tried installing Kali NetHunter on my OnePlus 8T. I followed a tutorial on YouTube (for the OnePlus 7T) up to the point where he installed "Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip" with TWRP. However, when I tried to boot into "twrp-3.7.0_11-0-kebab.img" for the OnePlus 8T, it got stuck on the fastboot mode logo for a long time, so I decided to reboot the device, and it rebooted fine. I tried it a couple more times, same issue.

Then, I tried booting a different TWRP image (TWRP 3.7.1 for the OnePlus 9) but the phone was stuck in the fastboot mode in partition_b and was not booting to the OS. When I switched to partition_a, it worked just fine

I also tried flashing the boot.img from the OS dump into boot_b and recovery.img to recovery, but this hasn't fixed the issue."

Edit: I flashed the phone with MSM Tool, now both partitions work, I rooted the phone once again on Android 12, but I have still problem with booting into TWRP image : View attachment 6127039

and the phone is just stuck at Fastboot Mode logo like this :

View attachment 6127040

I kept it like this for 30+ minutes just to be sure, and it was still stuck, after reboot the phone is booting fine to OS, do someone know where might be the issue or is there any unofficial TWRP image for Android 12 that might boot ?
[OnePlus 8T Questions & Answers] M.Mosa007:
You should try flash MSM file

It might be worth looking here in XDA's paid software forum.https://xdaforums.com/t/oneplus-auth-flash-all-other-services-only-1-all-in-one.4677333/
[OnePlus 8T Questions & Answers] Sami_Q:
What is MSM file and where can I find it? And one more question, what will happen if I tried completely reinstalling oxygen os (or maybe upgrading to android 13 and then maybe downgrading again) from the working partition_a, would it fix partition_b?
[OnePlus 8T Questions & Answers] BillGoss:
[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS

Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...

xdaforums.com
[OnePlus 8T Questions & Answers] TheNewHEROBRINE:
Booting the wrong TWRP image probably just made your phone switch slots. If you can boot fine with slot a it means you were using that slot before everything happened and there is no harm in keeping that slot active.
[OnePlus 8T Questions & Answers] Sami_Q:
I don't think so, because i switched the slots manually using "fastboot set_active other", and when I opened root checker on slot a, there was the message that this phone is not rooted... even if it was rooted before.
[Samsung Galaxy Watch 6] sac23:
WATCH 7 ULTRA APKS​

well im posting this here becouse i dont see a watch ultra thread if anyone wants it her yea go

pulled it from watch there all app and priv-app apks enjoy

https://www.mediafire.com/file/1izvrtsbpln0r2z/watch_apks.zip/file
[Samsung Galaxy Watch 6] Dan Gnana:
thanks
[Samsung Galaxy Watch 6] cakirrecep:
watch 7 ultra analog is not installing. what should we do for this?
[Samsung Galaxy Watch 6] dhe2035:
What apps though..?
[Samsung Galaxy Watch 6] gettinwicked:
Are the pulled apks all watch faces? Otherwise, what apps? I have a watch 7, but it doesn't have at least one of the ultra watch faces. Not sure what apps mine might be missing though.
[OnePlus 12] eeebbr:
Hey,

I have op12,

Latest update 810.

Lately, I recive notification but most of the time they don't show on lockscreen. On rare occasions they do show up but I couldn't find why. Thought it might have to do with locked/unlock but it doesn't.

Email, WhatsApp, sms, etc..

Sometimes they do show but with no content( just Gmail notification, since privacy isn't a problem I want it to show content).

When I recieved the op12 I did show the notification content.

Same problem with media controller (YouTube music, Spotify)

Any way to fix this?

Photos as example attached.

Gmail notification is present.
[OnePlus 12] bautrupp:
Same problem for me.

810 seems to be the problem. Oneplus pulled it from their server. Either wait for an update or revert back to an older version.
[OnePlus 12] burnwithme:
I'm on 610 with the same issue, so I'm not sure it's related to that specifically.
[OnePlus 12] MC_loud:
Same issue here related to media player controls. YT/Spotify/Symfonium. None show up on lock screen. Tried clearing app data, making sure the option is toggled on in lock screen settings, nothing works. Started having this issue with 810.
[General Questions and Answers] zerodaywild:
HOW DO I GET A BLANK VBMETA

tHANKS
[General Questions and Answers] khusika:
It looks like your question is similar to this thread

ROOT with mtkclient : How to create vbmeta.img.empty?

I tried to root my LG phone with mtkclient following official README and I do not know how to create on vbmeta.img.empty file https://github.com/bkerler/mtkclient python mtk.py w boot,vbmeta boot.patched,vbmeta.img.empty DAXFlash - Boot to...

xdaforums.com
[General Questions and Answers] xXx yYy:
IMO flashing a blank vbmeta is not recommended when unlocking an Android bootloader. To disable AVB checks you simply run the Fastboot command fastboot -disable-verity on your device.

Reasons:

Disabling verity essentially makes flashing a new vbmeta image pointless.

Since verity is disabled, there's no verification happening anyway, so any vbmeta image you flash wouldn't be enforcing any security checks.
[Magisk] MitzaBobitza:
Hello!

As I said in the title, I need help in order to bypass the root detection of the banking app that I use.

My phone is a Samsung Galaxy A53 5G (SM-A536B). I recently installed TWRP, LineageOS 21 and Magisk on it.

Things I've tried until now:

- Enabled zygisk, enforce denylist, and added the app to configure denylist

- Installed the Play Integrity Fix module by chiteroman (I'm passing device integrity, basic integrity and safetynet)

Back when I was using stock recovery and stock ROM (only Magisk installed) the steps above used to work, but one day after an update they started detecting my root anyways.

I imagine it's gonna be harder now that I also have a custom recovery & ROM, but I really hope it's not impossible. Any help is greatly appreciated.

The app is called "BT Pay".

They are pretty serious when it comes to blocking modified phones. I've been trying to bypass their checks for such a long time because I really need this app, so I'd be really grateful if you guys manage to find a solution.

Thanks in advance!

Edit: here's the link to the app in case you wanna do some testing: https://play.google.com/store/apps/details?id=ro.btrl.pay
[Magisk] MitzaBobitza:
Update: tried using Shelter to isolate the app and I also tried the Zygisk Assistant module by snake-4, no luck.
[Magisk] Big Dumb Object:
Are you sure you set it up correctly? Check how it works using testing apps such as Momo, RootbeerFresh, VD-Infos etc.
[Magisk] MitzaBobitza:
Tried Zygisk Assistant again, pretty sure I set it up correctly this time. I enabled zygisk, I left enforce denylist disabled and I installed the module. The only modules I have are PIF, Systemless Hosts and Zygisk Assistant. I tried the apps you suggested (made sure that they were added to the denylist) and got the following results: Ruru doesn't detect anything, RootbeerFresh detects "SE linux flag is enabled" (but i think it's a false positive because I checked the SE linux flag status and its "Enforcing"), both Momo and VD infos detect a bunch of stuff (see attached screenshots).

Update: tried using Shamiko (version 1.0.1 because im running Magisk v27.0) instead of Zygisk Assistant, same results.
[Magisk] tutibreaker:
the best solution is flash stock firmware and lock de the bootloader 100% effective
[Magisk] Shuaib_Ahsan:
I once encountered such a problem, i had a stubborn banking app which used to detect root. Heres how i managed to make it work:

1. Clear yours banking apps data

2. Add banking app and Google playstore to Magisk's DenyList (make sure the Enfore DenyList toggle is off in Magisk's settings)

3. Download and install the latest version of Shamiko (https://github.com/LSPosed/LSPosed.github.io/releases) via Magisk

4. Download and install the latest version of LSPosed (https://github.com/LSPosed/LSPosed/releases/latest) module via Magisk (also install the LSPosed (https://play.google.com/store/apps/details?id=org.lsposed.manager)) app from the Play Store)

5. Reboot and open the LSPosed app to make sure it is working correctly

6. Download and install the latest version of Hide My Applist (https://play.google.com/store/apps/details?id=com.tsng.hidemyapplist) (HMA) app

7. Enable HMA in LSPosed

8. Reboot and open the HMA app to make sure it is working correctly

9. Follow the following steps to configure hiding in the HMA app:

Select Effective Apps -> Tap on "com.(name of your banking app)" -> Toggle Enable hide

Under the Preference head, tap on Select hide methods -> Check API requests, Intent queries, ID detections -> Tap OK

Under the Template config head, tap on 0 additional apps invisible -> Check Magisk, LSPosed and HMA

10. Tap on the save button on the top right corner of the app

11. Reboot and open your banking app, it shouldn't complain of root anymore!
[Magisk] Big Dumb Object:
You got it right.

But perhaps presence of Magisk isn't the only red flag in your case. If the above suggested steps don't help, maybe you should try to eliminate these points one by one (e.g. there is Xposed module to hide unlocked bootloader).
[Magisk] MitzaBobitza:
I don't understand what's the issue but I've tried using LSPosed before and every time I get this in the manager: "Partially activated. SEPolicy is not loaded properly. Some features will not work.". I've tried some fixes I found on the internet like disabling LSPosed in Magisk, rebooting, then enabling it and rebooting again but it didn't work.

Also I don't know why but when I use Shamiko and test it on Momo I get even more detections than without Shamiko, it's really weird.
[Magisk] Big Dumb Object:
SEPolicy issue in RootbeerFresh is really just it's bug.

Shamiko and Momo developed by the same guy as far as I know, so maybe that's the case.

it would be great if you have another Android device with better system installed (official LineageOS e.g.) to perform some comparison. Samsung running unofficial ROM isn't good starting point for anything, I think.
[Magisk] Clems92:
I managed to hide to reluctant my bank app using this https://xdaforums.com/t/module-zygisk-assistant-foss-root-hider.4664761/page-15

Only this module + "enforce deny list" disabled in Magisk and Zygisk activated.
[Magisk] MitzaBobitza:
At this point I'm pretty sure that the app checks for an unlocked bootloader, that's because back when I was using Displax's fork of the USNF module, which also spoofed the bootloader unlock state, the app was working. Obviously, that module doesn't work anymore (doesn't pass device verdict and safetynet) since it hasn't been maintained anymore for quite some time now, and it's also not compatible with PIF so I can't install both of them.

Yes, I did try the BootloaderSpoofer LSPosed module. It works fine on apps like Momo or Key Attestation Demo, but when I try using it on my banking app, the app breaks, as in it keeps crashing within a few seconds whenever I try opening it. If I disable BootloaderSpoofer, the app comes back to normal and works (but detects my root).

This is where my question comes into place: Is there any other way to spoof the bootloader unlock state?
[Magisk] wilsonhlacerda:
Read last pages of the PIF thread. You'll see trickystore mentioned/linked. Try it.
[Magisk] MitzaBobitza:
I'm honestly so tired, I don't know what to try anymore. I've been doing this for the past few days. I was actually hopeful when I discovered TrickyStore, but I honestly don't know what kind of ****ing witchcraft they're doing with that app. Like, I swear, that thing is the final boss of root detection. I bet they spent more time on the detections than on the app itself.

I even reinstalled the stock ROM with a custom kernel, TWRP and Magisk Canary. Momo literally detects NOTHING, so honestly I don't know what they could possibly detect. Probably some ****ty nitpicking thing.

I'm so tired of doing this all day, but if you have any other suggestion, please let me know.
[Magisk] MitzaBobitza:
Note for anyone who is willing to do some testing on the app: if the app detects root, it will blacklist your Device ID. To try using it again you have to force stop the app and clear all its data from settings and then install Device ID Changer from the play store and spoof the Device ID for the app, then reboot and try again. If the app detects root again, repeat.
[Magisk] pndwal:
@MitzaBobitza, Just seen this thread...

There are various ways to see B/L unlocked... PIF, like original USNF, works for cases using Google device integrity APIs... Bootloader Spoofer can work for apps doing their own verification of key attestation extension data locally, but Google recommends verifying on their own servers... If that's being done (very few verified cases), new Tricky Store could potentially help, but I don't think it handles this currently.

https://github.com/5ec1cff/TrickyStore/issues/11#issuecomment-2253723699

More likely app is detecting something else...

Assuming you're taken Hide the Magisk app and banking app is in denylist...

Many apps detect original Zygisk but Magisk has moved to more hide-able native bridge injection method (originally utilised by @canyie for Rikka's Riru injection/hiding). However some apps have begun detecting that too... ZygiskNext now seems to have the hiding advantage (uses ptrace+fuse injection), but this is potentially detectable too... Nb. Shamiko is the purpose-build Zygisk and other root trace hiding module, also @canyie's baby and reimplantation of her original MomoHider module...

Some apps use permission and other loopholes to detect directories (eg TWRP, addon.d, XPrivacyLua even after uninstalled as it leaves data/system/xlua directory behind, etc), others detect Accessibility options, Developer options, OEM unlocking, USB debugging etc enabled, and others detect modding related apps (nb. not just root apps)...

Using HMA and LSPosed is essential for many apps as has been mentioned... Hide all modding or root-related apps (including detector apps like Momo, Ruru etc) + hidden Magisk App (some apps, eg Sparkasse push-TANs Promon engine, were detecting Magisk App with either Magisk app in stub by using Dex file pattern matching, or if hidden with HMA, but not when hidden by both), and all Xposed modules, or use whitelist mode...

Also, if on latest Pixel ROMs or other late Android builds, you'll need to use the last CI build rather than public build of HMA (fixes issues with apps with 14 QPR2+)... If you haven't got a GitHub account, I put it here:

https://xdaforums.com/t/hide-my-applist-a-brief-guide.4519731/post-89489285

Hope it helps after you've had a rest... 👍 PW
[Magisk] Captain_Throwback:
App works fine here, but I'm using APatch, which may not be an option for you. Could you possibly use KernelSU? That should also work.

EDIT: I did hide the root apps from it with HMA, so that was probably a factor as well, plus APatch has a good hiding kernel module. KernelSU plus the latest Zygisk Next and umount set for the app should also be effective (I actually have both KernelSU and APatch installed, but either/both will work)
[Magisk] wilsonhlacerda:
I have it now running fine. It is detecting Magisk's Zygisk.

You can replace with: (closed source; tested and works with it)

https://github.com/Dr-TSNG/ZygiskNext

Maybe also this one (open source):

https://github.com/Admirepowered/Zygisk_mod

Or maybe switching to newest Magisk Alpha (27006) + Shamiko (1.1.1, on official LSPosed Telegram channel), both closed source:

https://xdaforums.com/t/discussion-magisk-alpha-public-released-fork-vvb2060.4424845/

NEW TO ME, FIRST TIME SEEING APP DOING THAT:

BT Pay send to their servers the ID of all failing/rooted users installs, being impossible to run it again once failed. No matter forced stopped + clean data.

Thus have also to change its SSAID (and reboot) in order to try it again. This can be easily done with App Manager (available on F-Droid).
[Magisk] MitzaBobitza:
Thank you sooo much guys. I was actually starting to believe it was impossible.

I will try these solutions soon and let you know if I succeeded, but I'm pretty sure I will.

I really appreciate it though, love this community.
[Magisk] MitzaBobitza:
Am I missing something? I thought these should work with ZygiskNext. At first I thought I could ignore those warnings and they would still work, but I'm not passing any integrity verdict.

I probably just don't know how to set up ZygiskNext correctly since I've never used it before.
[Magisk] pndwal:
Is built-in Zygisk disabled? 🙃 PW
[OnePlus 11] bynarie:
It's pretty obvious that magisk is coming to an end, as all root solutions go. So I think it's time to switch off to something else.. Do I need to uninstall magisk/do an images restore or what? I don't wanna mess up my setup. Can someone give me a simple explanation of how to do this? Thx
[OnePlus 11] wfred:
Here's the link to the APatch thread https://xdaforums.com/t/dev-apatch-an-alternative-root-solution-to-kernelsu-and-magisk.4655727/

There's a thread on this forum about rooting 1+ 11 with KSU (I used it for A13, don't know about A14)

Edit: KSU website https://kernelsu.org

Check those
[OnePlus 11] JPower123:
Edit: listen to causical lol

If you find the stock boot IMG online, then you can just flash kernelsu onto it, then flash the IMG onto the phone. This MAY keep your modules, it seems like it does for me. This will most likely be your init-boot.img? Don't quote me on that. Not sure if the same applies to apatch.

Can't really go wrong with restoring images/ full uninstall with magisk and then just rerooting with something else. Just backup modules probably
[OnePlus 11] Causical:
I don't particularly agree that magisk is coming to an end, but...

If I were you and I were already rooted as you say and I wanted to do things in the safest manner possible (although obviously accountability is purely on you and no one else can be held responsible) I would pull my own unmodified boot.img with...

dd if=/dev/block/by-name/boot_a of=/sdcard/boot_a.img

Then (if you're gonna use ksu, truthfully you may as well just use Apatch) I would install Apatch and go into it and choose "select a boot image to patch"... choose your boot.img that you just copied to your internal storage.

Then I would reboot into fastboot and do fastboot boot boot_a.img [[[NOT FLASH]]]

At that point you should be able to go back into Apatch and choose "patch and install" to directly patch your systems boot.img...it'll ask you to set a super key at the bottom of the patch screen. You'll need to enter that after the next time you reboot and go into Apatch again.

Should tell you it's working and then also show up a box below the first saying Android patch which you'll click to install.

ALSO of course uninstall/restore images in magisk after you're done pulling your boot.img in the first step and before you reboot to fastboot.

summary of the idea: you're patching your own boot.img to gain temporary root by booting from fastboot, which makes Apatch think you're rooted and allowing it privileges to patch your current system's boot.img, that gives you permanent root after you reboot and you continue setting up Apatch.
[OnePlus 11] bynarie:
OK so I need to completely remove magisk first though before trying to install apatch? Obviously I need to dd the boot image first but after that I just completely uninstall magisk?
[OnePlus 11] Causical:
Yeah

Yeah because you're going to be temporarily rooted with your patched boot.img that you'll boot from fastboot.

It's just to ensure a clean system for getting ready to use a different root method.

It's possible it doesn't need to be done first, I'm just trying to give you what I feel is safest, it's what I would do.

Why not have everything as close to stock when doing something new? The main advantage magisk gives you in this scenario is that it allows you to dd your own boot.img and so you don't gotta grab it from anyone else and so you can patch it yourself. Magisk literally serves zero other purpose for this procedure.

Although you can install the app Apatch at any point in time regardless of anything.
[OnePlus 8 Pro Questions & Answers] HOrobOD:
My stock OnePlus 8 Pro got bricked recently, and I'm trying to dirty flash the stock OS again as a first recovery attempt.

Where can I obtain the latest official stock ROM to flash? I found a listing on the OnePlus support website, but the latest version was OOS11.
[OnePlus 8 Pro Questions & Answers] Vancore36:
You can check this link

https://oxygenos.oneplus.net/OnePlus8ProOxygen_15.X.21_OTA_0210_all_2106032247_ee04b174c5b84ff5.zip
[OnePlus 8 Pro Questions & Answers] HOrobOD:
Which device is this for? Will it work with the NA variant (IN2025)?
[OnePlus 8 Pro Questions & Answers] Vancore36:
It's for a Oneplus 8pro

its the stock rom but a beta version

and yes it will work with the NA variant
[OnePlus 8 Pro Questions & Answers] HOrobOD:
I think I managed to download the full zip through the Oxygen Updater app on another phone. If I don't have any luck flashing that version, I'll give this one a try. Thanks!
[General Questions and Answers] BenjiWiebe:
I'm trying to set up scrcpy (going to attempt a screen replacement, and I want a backup plan) on a Moto G100 running LineageOS (Android 12).

I have scrcpy working when I plug in the cable with the screen unlocked. However, if it is plugged in with the screen locked, the phone doesn't even negotiate a USB connection.

scrcpy --otg doesn't work, scrcpy doesn't work, lsusb doesn't show the phone, etc. There is no USB connection until the screen is unlocked, and *then* the cable is re-plugged.

I've tried changing the "default USB options" or whatever it's called, in the developer settings. Makes no difference.

Is this a known issue? Is it a "feature" of Android 12? Of LineageOS? Is it a bug? Is there a setting to change?

I've tried Googling, which I'm usually pretty good at, but got nothing relevant. I even tried ChatGPT - no luck.

I'm at my wit's end. Thanks for any ideas or suggestions.
[General Questions and Answers] xXx yYy:
scrcpy by default won't work with a locked screen due to security restrictions on Android versions 11 and above.

Consider using a wireless alternative to scrcpy if your device supports it. Tools like Vysor or AirDroid might offer screen mirroring functionalities over Wi-Fi.
[General Questions and Answers] BenjiWiebe:
Thanks! Is there a place I can read more about that? Is there a way to allow scrcpy to work anyways? This is a rooted device. EDIT Also is that why scrcpy's OTG mode doesn't work to type in the unlock PIN also? Or is that a separate problem?

Anyway, I went ahead with the screen replacement, since I realized the phone could be unlocked with fingerprint even with the screen not working. And the screen replacement went quite smoothly and it's working fine.
[Android Head-Units] Kokerm998:
Welcome

I have an android screen

I want to apply modified music in ROMs
[Android Head-Units] marchnz:
Is unit an MTCD type? Post screenshots of Android system information including MCU version
[Android Head-Units] Kokerm998:
Can I install a modified version?

I want a music app
[Redmi Note 8 Pro Questions & Answers] NOON1010:
Hi guys, so I bricked my phone and I didn't have the time to look for a solution (since I'm a noob). I took it to the local phone repair shop, they figured it out then they unbricked the phone and now it has a miui 12.5.1 official ROM and can be updated to miui 12.5.8.

I just wanted to make sure if it's the official global ROM and doesn't have any unwanted spyware or some sort of modified version of the official ROM. How do I do that??

Thanks a lot in advance.