yashsingh1/xdaforums huggingface dataset:
[Nokia 6.1 (2018) Questions & Answers] Kevin.Long:
I have the Nokia 6.1 (2018) international version. I am trying to enable the US LTE bands for compatibility with T-Mobile. Is there a way for me to do this without root? Is there a way to do it with root? Any help you can provide would be appreciated.

Thanks,

Kevin Long
[Nokia 6.1 (2018) Questions & Answers] toonmaster74:
Did you ever figure this out?
[Nokia 6.1 (2018) Questions & Answers] smartuser8:
Hum... what is the "international version"? (TA-????)
[Nokia 6.1 (2018) Questions & Answers] reorder_tone:
The international version is TA-1068

I'd also like to know.

I'm getting band 4,5 on AT&T only.
[Nokia 6.1 (2018) Questions & Answers] klauer:
You can only manage / force your phone to do that with root.

No root = use provider / googles android-one standard settings.
[Nokia 6.1 (2018) Questions & Answers] mattgoldey:
This isn't something you can do with or without root. It's not that those bands are somehow locked by software or firmware. The hardware is different.
[Samsung Galaxy S8 Questions and Answers] Skipperkind:
Hello!

I mess up by flashing my Samsung S8 SM-G950F, now it stuck in booting and red text "Only Official Released Binaries Are Allowed To Be Fashed "?

How fix that?

Thanks for answers!
[Samsung Galaxy S8 Questions and Answers] MrSteelX:
That means only official stock firmware can be flashed. So you should download stock rom and flash.
[Samsung Galaxy S8 Questions and Answers] Skipperkind:
Did tahat, now in phone settings under dev option, oem unlock button is missing, is there way how skip 7 days waiting?
[Samsung Galaxy S8 Questions and Answers] spawnlives:
Try this method

https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
[Samsung Galaxy S8 Questions and Answers] Nonny_SA:
THANKS Working for me on Galaxy Note 8 SM-950F oreo 8.0
[Android Stick & Console AMLogic based Computers] techspy:
I have a TX9 Pro and would like to be able to capture IR commands/keys from another remote to perform actions. For example, I would like to use the Guide key of my TV remote to launch DirecTV Now app etc. Searching has turned up only apps to turn an android device into a universal remote which is NOT what I am looking for. I know there is the remote.conf file but have no idea how to use that to capture a specific IR command and have it perform a specific command like launching a specific App. Any help appreciated.
[Android Stick & Console AMLogic based Computers] oldman20:
good idea, any advanced now>?
[Mogul, XV6800 ROM Development] coolsac32:
i have the dcd 2.3.2 rom i installed the nuemms cab but it would nt send pictures, n neither will sprintmms cab. should i have certain settings? i need picture mail and im mad cuz the titan can watch youtube, play gba games but cant send pics n flics. that doesnt add up. please help. or at least steer me in the right direction because i cant ind the answer.
[Mogul, XV6800 ROM Development] NotLutzik:
Look on ppcgeeks there is new program that let u use picturemail account
[Mogul, XV6800 ROM Development] coolsac32:
could sumone give me the link to the page or program because i looked for an hour and i could not find it
[Mogul, XV6800 ROM Development] NotLutzik:
http://forum.ppcgeeks.com/showthread.php?t=22509
[Magisk] Launchy21:
Magisk v16.4 (also tried v16.0)

I've hidden the app in the HIDE list, I repackaged Magisk, force stopped NemID, cleared cache and data, and the app still spots root. I've successfully hidden apps from root before using this method, so it's just this app here that somehow goes beyond the usual. Are there any further steps I can take to hide root from the app more thoroughly?

Thanks
[Magisk] vbajs:
I believe that the app detects root by any of the following things :-

1. Bootloader unlocked detection

2. Custom ROM detection

3. Presence of apps that require root

4. Reading log of root being used (which is very rare, but possible)

5. Some very private code that renders Magisk useless
[Magisk] Didgeridoohan:
Tested it, and the app looks for both Magisk and the Manager. With the app on the Hide list and the Manager repackaged I can open the app without issue. It doesn't seem to "remember" root. This is on stock OxygenOS and also NitrogenOS (both on Oreo).

The app might be detecting other properties of the ROM your using (if not stock) or other known root apps on your device. Try running a logcat when the app detects "root" to maybe see what it's detecting, or simply uninstall some root apps and try again.
[Magisk] Blumse:
It works for me aswell, im using custom rom 8.1, hide the app, repackage, reboot, open app

So if that doesnt work, you might wanna try another rom as mentioned above me
[Magisk] kqueenc:
It seems the app changed its way of detecting root after their upgrade on 25/6. It also worked for me before by using Magisk Hide and repack Magisk manager, but not anymore.

It is a losing battle anyway, just a matter of time. So I do not expect this method will work for good.
[Magisk] mbeltoft:
yeah my nemid app also stopped working a few days ago. This is not good if its not possible to hide root from an app anymore
[Magisk] Didgeridoohan:
Since there are users reporting that they can open up the app with MagiskHide active for NemID and the Manager repackaged, it's very likely that the app is detecting some other thing on your device. It could be a property of a custom ROM you're using, it could be a root app, etc... Possible solutions: try a different ROM (as stock as possible), uninstall root apps, etc.

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] mbeltoft:
Ok I'm running Samsung s7 stock oreo w. Root. Knox is tripped

Removed all apps needing root, installed magiskhide props config module, disabled systemless hosts.

Still no go. It worked until before latest update
[Magisk] Didgeridoohan:
What Magisk version do you have? If not on beta v16.4, the issue might be that the app has a sub-process that previous Magisk versions can't hide automatically. Scratch that... Just went back and saw that the OP has tested it on v16.4.

Or, if you're unlucky it's checking Knox...

Does it only check for root at the start, or is it other points as well? As stated before, I can open the app just fine on both my Oneplus 3T and Nexus 6.
[Magisk] mbeltoft:
AFAIK it's only checking at start-up. It shows it's load screen for a few seconds ( but longer than before when it was working) and then give the error screen OP posted.

If you leave the app and reenter it it will show the main screen but jump back to the error screen whenever a button is pressed
[Magisk] peter_dk01:
I tested this on a pixel 2 with stock rom in this order :

All root apps installed, no magisk or root : working fine

All root apps installed, no magisk or root, custom kernel: working fine

All root apps installed, root and magisk, magisk hidden+magisk hide: not working

No root apps installed, root and magisk, magisk hidden+magisk hide: not working

No root apps installed, root and magisk, magisk manager not installed+magisk hide: working

I then tried cloning the apk without changing the name: not working

I tried cloning the app but changing the name of Magisk Manager from "Magisk Manager" to just "Manager" and then Nemid worked again.

Could it be the Nemid app is just looking to see if there's an app called Magisk Manager installed and if there is, the app failes

Unfortunately the cloned app doesn't work. Maybe we could have the "Hide magisk" function rename the app name too?

//Peter
[Magisk] peter_dk01:
Just tried cloning an entirely different app and renaming it "Magisk Manager" - after this the nemid app failed, so I guess that confirms that nemid just checks the name.

//Peter
[Magisk] Remmerboy:
Nice detective work.

By uninstall the app (not unroot) NemID works. If you use magisk 16.6 you can just reboot phone to get the manager again or just install the apk.

But if being able to change magisk managers name to something generic (like manager) or a custom name could be a great solution (I would change name to NemID). Because if nemid can defeat magiskhide, others will follow
[Magisk] peter_dk01:
I posted the findings in the beta thread but I think it got removed during thread cleanup. Any other way to let the developers know?
[Magisk] Didgeridoohan:
It's already on the to-do list.
[Magisk] peter_dk01:
Perfect! Thank you ?
[Magisk] kqueenc:
Unfortunately, the change is not included in the latest 5.8.1 release.:eek:
[Magisk] Didgeridoohan:
Manager v5.8.1 was simply a bug fix. Stability is prioritised over new features. You'll have to wait, and that feature will be available when it's available. Not before that...
[Magisk] kqueenc:
Is there any other workaround to change the name of Magisk Manager App in order to bypass the check? And will there be any other consequence (like root cannot be detected by other app)?
[Magisk] Didgeridoohan:
Until there is a feature like that, you can uninstall or freeze the Manager whenever you need to use whatever app detects it.
[Magisk] eried1:
Just got it working - don't ask how - so I am now inclined to agree with you, @Anders Mogensen.

Magisk Delta + Zygisk + Magisk Hide. No modules.
[Magisk] MrMEEE:
@eried1 Does MitID still work for you?? which combination?
[Magisk] mrspeccy:
It works for me on a rooted phone with EvolutionX (Android 14). PlayIntegrity must be at DEVICE level, which is spoofed by EvolutionX out of the box.

Note that MitID scans system property variables from strings like "Lineage" and reports the device as rooted if such strings are found (even if the device is not rooted and just runs a custom ROM). See more on https://community.e.foundation/t/app-called-mitid-keeps-saying-my-device-is-rooted/38271/21?page=2 (some of the advice there is outdated since today, PlayIntegrity is checked.)
[Magisk] MrMEEE:
So, Magisk Delta + Zygisk Module + MagicHide Module + PlayIntegrity module ?

I have changed lineage to linage and removed debug stuff from my build.prop..
[Magisk] mrspeccy:
Just Kitsune Magisk (formerly known as Magisk Delta) without any modules is enough in my case. If your ROM does not spoof DeviceIntegrity out of the box, you may need to add PlayIntegrityFix.
[Magisk] eried1:
Unfortunately broken again. The previous method was unreliable.
[Magisk] MrMEEE:
Now I have Kitsune+Playintegrity+playcurl, and still MitId finds root :(

Any ideas??
[Magisk] mrspeccy:
I guess you have added MitID to the "Magisk hide list"? Other than that, it could be some system variable. Can you open a terminal (e.g. Termux), type "getprop" and post the output here? If there still is a substring like "Lineage", then MitID will refuse to work.
[Magisk] MrMEEE:
yes, I have added it to the Hide list..

getprop:

1|gargoyle_slim:/ # getprop |grep linea

[ro.build.description]: [lineage_gargoyle_slim_bvN-userdebug 13 TQ3A.230901.001 eng.rumple.20240227.142023 test-keys]

[ro.build.display.id]: [lineage_gargoyle_slim_bvN-userdebug 13 TQ3A.230901.001 eng.rumple.20240227.142023 test-keys]

[ro.build.fingerprint]: [Unihertz/lineage_gargoyle_slim_bvN/gargoyle_slim:13/TQ3A.230901.001/eng.rumple.20240227.142023:userdebug/test-keys]

[ro.build.flavor]: [lineage_gargoyle_slim_bvN-userdebug]

[ro.build.host]: [lineageos-build]

[ro.lineage.build.version]: [20.0]

[ro.lineage.build.version.plat.rev]: [0]

[ro.lineage.build.version.plat.sdk]: [9]

[ro.lineage.device]: [gargoyle_slim]

[ro.lineage.display.version]: [20-20240227-UNOFFICIAL-gargoyle_slim_bvN]

[ro.lineage.releasetype]: [UNOFFICIAL]

[ro.lineage.version]: [20.0-20240227-UNOFFICIAL-gargoyle_slim_bvN]

[ro.lineagelegal.url]: [https://lineageos.org/legal]

[ro.product.build.fingerprint]: [Unihertz/lineage_gargoyle_slim_bvN/gargoyle_slim:13/TQ3A.230901.001/rumplestilzken02271409:userdebug/test-keys]

[ro.product.name]: [lineage_gargoyle_slim_bvN]

[ro.product.product.name]: [lineage_gargoyle_slim_bvN]

[ro.product.system_ext.name]: [lineage_gargoyle_slim_bvN]

[ro.system.build.fingerprint]: [Unihertz/lineage_gargoyle_slim_bvN/gargoyle_slim:13/TQ3A.230901.001/rumplestilzken02271409:userdebug/test-keys]

[ro.system.ota.json_url]: [https://github.com/rumplestilzken/unihertz_titan_lineageos20/releases/download/ota/ota.json]

[ro.system_ext.build.fingerprint]: [Unihertz/lineage_gargoyle_slim_bvN/gargoyle_slim:13/TQ3A.230901.001/rumplestilzken02271409:userdebug/test-keys]

[sys.lineage_settings_system_version]: [1]

So that seems to be the problem, but there is nothing in /system/build.prop.. where does it come from??
[Magisk] mrspeccy:
Yes, you definitely have to change some of these props. Sometimes the build.prop lies in /vendor/system etc. You could try "find / -name build.prop"

Changing the build.prop file is not the most sustainable solution since it has to be repeated after each ROM update. I would try to use some Magisk module that can hook into "getprop" and spoof different outputs. Earlier I would have used MagiskHidePropsConfig, but this one is now dead. Maybe the advice on

https://www.reddit.com/r/Magisk/comments/174sx3n
can be used.
[Magisk] MrMEEE:
I have tried using MagiskHidePropsConfig, but that still doesn't work...

I have also found other files with Lineage in them, changed them, but still no luck
[Magisk] mrspeccy:
Which variables did you change using MagiskHidePropsConfig? Did you do "getprop | grep lineage" to find out which ones have to be spoofed?
[Magisk] MrMEEE:
Yeah, I did a grep.. And now it reports nothing, still no cigar :(
[Magisk] MrMEEE:
I have also tried changing my fingerprint to a Samsung S21.. but doesn't seem to make any difference...
[Magisk] mrspeccy:
Not sure whether MagiskHidePropsConfig is compatible with Kitsune Magisk. Maybe the module has no effect for processes on the hide list. Can you put your terminal application on the hide list and check whether getprop still returns the spoofed values?

I have MitID up and running on a Lineage 20 GSI (https://sourceforge.net/projects/andyyan-gsi/files/). I replaced all occurrences of "lineage" by "lineege" in "/system/build.prop" and added MitID to the hide list in Kitsune Magisk. That's all.
[Magisk] MrMEEE:
Well, it works fine.. with Termux on the hide list, it can't see anything that contains lineage or debug.. :(

This is SOOO frustrating.. does anyone know where the Lineage check comes from, can't find it anywhere in the apk?
[Magisk] mrspeccy:
Decompiling the apk is a daunting task. Before trying that, I would rule out other checks that the MitID app might carry out. For example, there might be apps on your phone that MitID associates with rooted phones (e.g. the classical Magisk app - Kitsune is not a problem), or it might scan the internal storage for TWRP folders, Magisk installers and such.

My advice would be to install the Island app (https://play.google.com/store/apps/details?id=com.oasisfeng.island&hl=en_US) and to clone MitID to the secondary profile. Does the clone still report root?
[Magisk] MrMEEE:
@mrspeccy I have just tried the Island app.. it's exactly the same for all three apps..
[Magisk] MrMEEE:
Just found out that this has to do with the bootloader being unlocked..

I restored the original rom, but still had the same problem.. but as soon as I relocked the bootloader, the apps worked perfectly..

So something is checked in regards to unlocked bootloaders..

But the funny thing is that I also have a Razer Phone 2, also with unlocked bootloader, and that doesn't get detected??
[Magisk] mrspeccy:
My bootloader is also unlocked but MitID works. However, an unlocked bootloader results in DeviceIntegrity failing unless you use PlayIntegrityFix or similar. What does the SPIC app (SimplePlayIntegrityChecker) - or similar apps - say?
[Magisk] MrMEEE:
I have tried basically everything, also PlayIntegrityFix, and SPIC is happy...
[Magisk] mrspeccy:
Interesting. Did you try https://github.com/chiteroman/BootloaderSpoofer ?
[Magisk] MrMEEE:
I did not.. Thanks
[Magisk] Pietolsen:
You can change the app name with the app called APK Editor on the playstore. Works for me, just select Magisk Manager and select common edit, change the name and installe the new APK you generate. I just changed the name to Magic Manager and it works just fine for me now.

*Edit* It seems to have detected it anyway later in the process of installing it on my phone, one the 1hour wait was up it had detected it.

*Edit #2* I tried renaming the manager again, this time to just "Manager" and i also ticked the "Rename package name in DEX file(s)" box, it seems to be working fine now, I am able to have both apps open at the same time and login to NemID sites.
[Magisk] emilrune:
What a basic-ass way of detecting root tampering. Well done NemID app devs...

/Massive eyeroll
[Magisk] krede99:
the rename trick seems to work fine - Thanks
[Magisk] Anders Mogensen:
Tried deleting the Magisk app, but NemID still detects root, maybe Xposed are detected...
[Magisk] Didgeridoohan:
If they're detecting the Magisk Manager, you can bet that they're also looking for Xposed...
[Magisk] Djizox:
Magisk NemID FIX

I have been able to hide magisk without removing the magisk manager app as a quick fix.

After the lastest update for nemid, they just searched for the app name (Magisk Manager) and then blocked you cause of root.

Steps for magisk manager to hide it from Nemid (Reboot when asked)

1. Hide magisk manager under settings so it gets another package name. And hide nemid in Magisk hide

2. Go to downloads under magisk manager and install the Xposed SDK 27 (for my version of OS 8.1) systemless module

[IMG="xposed installer link"]https://media.discordapp.net/attachments/508985606270091275/509077171436912651/Screenshot_20181105-195045.jpg?width=339&height=677[/IMG]

3. Install a modified Xposed installer to read systemless xposed. go to downloads in magisk manager and select your downloaded xposed SDK XX you will find a link for modified xposed installer.

this was main reason it failed for many people.

4. when you open Xposed Installer it should look like this

[IMG="Xposed installer"]https://media.discordapp.net/attachments/508985606270091275/509065919411257346/Screenshot_20181105-190546.jpg?width=339&height=677[/IMG]

it should say it's active with systemless.

5. Install Xprivacylua through Xposed installer app in downloads

6. Go to xprivacylua app and find nemid app and expand and enable the block app overview/list (mine is on Danish so don't know presisely what it's called)

7. Check nemid app

This method worked for me and hope it will help others too.

DISCLAIMER

WITH XPOSED THERE IS A CHANCE TO SOFTBRICK YOUR DEVICE. By following this guide, it's your own responsibility if it's not working or softbricking your device.
[Magisk] thyttel:
Not working for me. Clean factory reset phone to completely rit any trace of magisk. Followed all steps and no problems installing either magisk and renaming app, exposed + module. Still getting root detected. Gave up for now as its too important for me to have Nemid working so removed any root until a solution is found.

Sendt fra min SM-N950F med Tapatalk

---------- Post added at 04:23 AM ---------- Previous post was at 04:23 AM ----------

Not working for me. Clean factory reset phone to completely rit any trace of magisk. Followed all steps and no problems installing either magisk and renaming app, exposed + module. Still getting root detected. Gave up for now as its too important for me to have Nemid working so removed any root until a solution is found.

Sendt fra min SM-N950F med Tapatalk
[Magisk] emilrune:
It's a matter of having the option to just rename the Magisk Manager app yourself, after you hide it right?

Fingers crossed this will get added [MENTION=4470081]topjohnwu[/MENTION] ;)
[Magisk] Elfomze:
I'm facing the same scenario. I'm running a rooted stock ROM, hid magisk, set up the xposed module - and still no luck.

So it might very well be that it now checks for other root apps (as was suggested in an earlier post).
[Magisk] MBDdk:
Before updating the NemID app, I was able to use it just fine while having Magisk Manager and NemID hidden. Also while having Xposed for Magisk installed. However, after adding the Gravitybox Xposed module, the NemID app stopped working again. My choice was easy though and I'm now back to using a photo of the NemID card on my phone ;)
[Magisk] kqueenc:
Thanks a lot. It works for me as well. :good:
[Magisk] Ghashul:
So far I've managed by restoring a backup of the previous version and unchecking that it can be updated automatically in the play store.
[Magisk] Remmerboy:
That works on my rooted Nexus 5x.
[Magisk] alpsayin:
After using APK editor I keep getting a "error while parsing the package error".
[Magisk] Rallerbabz2:
Seems like I am unable to install APK from that app. I can't seem to find the setting that allow the APK editor app to install apps from unknown sources.. Or maybe it is something else?

Imgur. com/a/4u8QRDL
[Magisk] Pietolsen:
You need to navigate to the apk it creates with a file manager and run it from there.
[Magisk] Rallerbabz2:
Thanks, I tried that as well, but the api editor folder (tmp) seems empty? Even with hidden files enabled
[Magisk] mbeltoft:
didn't work on my samsung s7 - installed the modded APK but NemId still detect it
[Magisk] adamhassel:
APK Editor doesn't work on Android 8.1. It fails reading the key file it uses to sign the package, and also fails to recognize that as an error. So it reports success, but writes nothing to file. Then it sits there. Then it laughs at you.
[Magisk] mrspeccy:
You can try AppCloner instead of APK Editor. It also allows you to rename an app's visible name and its internal package name.
[Magisk] zeptobyte:
Rename with apktool

You can rename the apk from your computer using apktool (Google "ibotpeaches apktool")

Decompile apk

$ apktool d magisk-manager-vX.X.X.apk

Go to ./magisk-manager-vX.X.X/res/values/strings.xml,

rename the following key to somthing other than "Magisk Manager"

<String name="app-name">Magisk Manager</String>

Recompile apk

$ apktool b magisk-manager-vX.X.X.apk

Sign the builded file (Google "How to Sign an Already Compiled Apk")

Install the new apk on your phone

You can download a version of Magisk Manager, that I have renamed from dropbox.

dropbox com /s/c4zqf30omma5833/MagiskManager-v5.8.3-renamed.apk

(I cannot post links yet)
[Magisk] Kocane:
Did you make it work with this? I uninstalled the default Magisk Manager and installed yours but NemID still doesn't work. It's also added on the magisk hide list, naturally. Safetynet checks OK
[Magisk] mrspeccy:
You must also hide the renamed manager via the "Hide Magisk Manager" setting. Afterwards, neither the package's internal name nor the displayed name trigger NemID's amateurish root detection.
[Magisk] Kocane:
Ah, I missed that one after installing the modified magisk manager. Now it works.

Amateurish indeed, I thought they were onto something more sophisticated than this.

Tak! ;)
[Magisk] Kocane:
Hmm.. I was hoping that this app would function like the "Dankort" app where, after configuration, it seemingly doesn't check safetynet again, so one can for instance enable xposed and use that. This app fails the check no matter what when xposed is installed.

What I don't get is that it doesn't fail before installing the Xposed Installer app. When having Xposed module in Magisk enabled alone, it fails safetynet but NemID functions still. When I install Xposed Installer it detects the root.

I tried renaming the app with ApkTool but it still fails. Can that be because I'm missing what the "Hide Magisk Manager" feature does for Magisk?

Does anyone have an idea what I can try? Otherwise, I guess it's back to having my NemID on my phone in form of a encrypted photo ;) I still dislike the trend of making life hard for those who root, though.
[Magisk] zeptobyte:
The NemID app checks both the package id and the package name of the Magisk Manager app, when you "Hide" Magisk Manager from its settings, it scrambles the package id.

Maybe it is possible to fool NemID if you change both the package name and the package id of the Xposed app?