yashsingh1/xdaforums huggingface dataset:
[Magisk] evdenis:
These modules are not meant for everyday use. They are intended for debugging and modification of a firmware. They significantly lower security of your device while active and even could softbrick it. You've been warned.

ADB Root

Magisk Module that allows you to run "adb root". adb root is not an ordinary root (su), it's adbd daemon running on your phone with root rights. adb root allows you to "adb push/pull" to system directories and run such commands as "adb remount" or "adb disable-verify".

Download v1.0: https://github.com/evdenis/adb_root/releases/download/v1.0/adb_root.zip

Source code: https://github.com/evdenis/adb_root

Support: Telegram

SELinux Permissive

This module switches SELinux to permissive mode during boot process. This module intentionally lowers security settings of your phone. Please don't use it if there is a better solution to your problem, e.g., magiskpolicy. The module will not work if your kernel compiled with always enforcing config, e.g., stock samsung kernels. It's not possible to enable permissive mode on such kernels.

Download v2.0: https://github.com/evdenis/selinux_permissive/releases/download/v2.0/selinux_permissive_v2.0.zip

Source code: https://github.com/evdenis/selinux_permissive

Support: Telegram

Enable Eng

This Magisk Module enables engineering build props. It allows to activate debugging parts of a firmware. Please, disable Magisk Hide for this module. If you don't know what you are doing, don't use this module. It can easily softbrick your device.

Troubleshooting

If your device doesn't boot then you need to reboot to TWRP recovery and

$ adb shell rm -fr /data/adb/modules/enable_eng

If ADB doesn't work that means adbd in your firmware is build without ALLOW_ADBD_ROOT. You can fix adb autostart either by installing "ADB Root" magisk module or by disabling this module.

Download v1.0: https://github.com/evdenis/enable_eng/releases/download/v1.0/enable_eng.zip

Source code: https://github.com/evdenis/enable_eng

Support: Telegram

Kexec tools for Android

This module adds statically linked kexec binary to your system. Aarch64 only. Kexec is a system call that enables you to load and boot into another kernel from the currently running kernel. Your kernel should support kexec.

Download v1.0: https://github.com/evdenis/kexec/releases/download/v1.0/kexec.zip

Source code: https://github.com/evdenis/kexec

Support: Telegram

GDISK/Parted for Android

The module adds statically linked parted/sfdisk/fdisk/gdisk binaries to your system. Aarch64 only. These utils are standard linux tools to edit the partitions tables on disks.

Download v2.0: https://github.com/evdenis/disk/releases/download/v2.0/disk-v2.0.zip

Source code: https://github.com/evdenis/disk

Support: Telegram
[Magisk] tmviet:
Is also valid for One Plus 5 ?

Inviato dal mio ONEPLUS A5000 utilizzando Tapatalk
[Magisk] evdenis:
Hi, these magisk modules are device independent. Yes, you can use them on One Plus 5.
[Magisk] tmviet:
Tks. A lot [emoji6]

Inviato dal mio ONEPLUS A5000 utilizzando Tapatalk
[Magisk] bpaxda:
Thanks [MENTION=10496119]evdenis[/MENTION], this module is great! I haven't gotten the 100% desired behavior (getting adbd with actual root perms) because I'm running a 32-bit architecture (armeabi-v7a) and you've supplied only the 64-bit version of adbd, but I've been using your module to swap out 32-bit versions of different versions of adbd I have lying around (older devices). I'm a n00b when it comes to building adbd from scratch using the latest sources with your patch so I'm planning on using the adbd that came with the device and using a disassembler and a hexeditor to NOP out some calls, such as the call to minijail_enter() and see if I have any success. The original device version of adbd doesn't seem to have the functions in it that you built with the patch, but instead appears to use a bunch of minijail library functions. The device is a rooted android 8.1.0 OS, but it is only rooted systemlessly so many of the ro.* build properties affecting adb are changed well after the OS-essential portion boots rendering my efforts thus-far using the original adbd ineffective I'm guessing. I can now issue the "adb root" command from my machine, but adbd on the device is always being launched with the following command line arg "--root_seclabel=u:r:su:s0" and never gains root permissions by default (the behavior I'm trying to achieve). I can manually use "su" but this doesn't help me with push/pull requests to protected parts of the OS and chainfire's "ADB Insecure" patches adbd successfully, but I still don't get the root perms.

Do you know if the system is starting the process with reduced permissions (i.e. adbd will never be able to gain root access on its own no matter what I modify) and I should go a different route like modifying something else in the system rather than adbd? Again, I've already modified the ro.* properties affecting adbd so it does attempt to re-launch itself as root, it just doesn't end up getting the root perms. Manually launching adbd after killing it from within a shell on the device doesn't seem to affect the permissions in ultimately gets.

If you are anyone has any insight as to what I need to do so that adbd gains root permission, that would be much appreciated.
[Magisk] evdenis:
It was my initial attempt to gain "adb root" on samsung s10. And noping a couple of calls is not enough on the phone. adbd binary on your device could be compiled without "adb root" branch. This is the case on samsung s10. If "adb root" branch exists one need to force should_drop_privileges() function to return false (https://android.googlesource.com/platform/system/core/+/refs/heads/master/adb/daemon/main.cpp#65) in order to get into the "adb root" branch of code (https://android.googlesource.com/platform/system/core/+/refs/heads/master/adb/daemon/main.cpp#151).

You could try enable_eng magisk module (https://github.com/evdenis/enable_eng). The module changes ro.* props to engineering build props. Depending on a firmware this could help to get "adb root". However, no guaranties that the module will not softbrick your device. In case of softbrick you will need to reboot to TWRP and delete the module, instruction is in the README.md.

Try to disable SELinux either with the magisk module or with a script.
[Magisk] bpaxda:
Thanks for your response.

I think you're right. Despite having adjusted the ro properties post-boot, there was nothing in ADB that would change the privileges as if it has been compiled out. By sheer luck, I managed to grab adbd from an identical device that had a recent forced firmware update, but the "improved adbd" actually let me get closer. The updated adbd had code changes to its adbd_main function so that it at least looks at the properties "ro.secure" and "service.adb.root" not to mention new calls to minijail_capbset_drop(), minijail_change_gid() and minijail_change_uid(). Using magisk to dynamically replace my original adbd binary with this updated one actually worked in getting adbd to start root shells without needing to invoke "su"!

However its a weird type of root that can't read certain files like /verity_key but I can see some things I should be able to see as root. I'm no SELinux expert, but my guess is that if everything is functioning correctly, I may be getting an SELinux "restricted" root. In this case, it might be the most I can expect from an SELinux enabled kernel launching adbd as root. Let me explain: since I'm using Magisk, post-boot systemlessly, (the system boots restricted and then I use the mtk_su exploit, to gain root and disable permissive SELinux mode), I'm getting permissive root on a session by session basis. I think the nature of this type of root means the kernel is probably still locked down and thus whatever daemon may be responsible for launching adbd remains locked down. Does this sound correct to you? If so, I can live with that :)

I'd love to get TWRP on this device, but I'm not sure its possible since TWRP doesn't list my device as supported on their website nor can I get into fastboot mode (I didn't try that hard because I wanted to exhaust other options before flashing anything). Do you think enable_eng would work *after* the ACTION_BOOT_COMPLETE event is processed? I.e. my device is rooted after bootup by a script which runs the exploit, but it is well after the system is fully running and locked-down. Luckily Magisk has a utility to change ro properties, but some of those properties are not looked-at by the system this late in the boot stage. Do you think in this case "enable_eng" would work for me? Thanks again!
[Magisk] evdenis:
I'm not sure that my modules will work with this rooting scenario. As far as I could understand, magisk by default replaces the init process, patches selinux policy before it is loaded and next, calls the original init binary. I don't think that it will be possible to alter selinux policy with different boot scenario for magisk.

I'm not sure that enable_eng will work. adbd daemon check some properties such as ro.secure dynamically, but they could be cached after the boot. I don't know the ways to drop the cache and re-read these properties (altered with magisk) after the boot. Here are the main properties the modules changes https://github.com/evdenis/enable_eng/blob/master/system.prop
[Magisk] ModWilliam:
Thanks for making this tool! I'm just wondering if I need to modify my adb to use the module - I run "adb root" normally and get "adbd cannot run as root in production builds" still
[Magisk] warrencoakley:
Anyone know why when i install SELinux Permissive version 2.0 of the module it still states version 1 in Magisk?
[Magisk] cheeklitched:
I flashed this in Magisk and rebooted. Now my phone is stuck in a boot loop. Any ideas? I'm using Sony Xperia XZ1 compact.
[Magisk] davidmoore0:
If you have twrp installed just uninstall and reinstall magisk.

Otherwise,

Boot to bootloader and flash your boot.img file

fastboot flash boot boot.img

Then let phone boot. Reboot to bootloader again. Flash magisk_patched.img

fastboot flash boot magisk_patched.img

During startup, as soon as you get to the Google logo, hold the volume button down. This should start the phone in safe mode. See if it loads. If not, reboot phone, and execute this in terminal/command prompt:

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

This should allow the phone to start up all the way. Enable whatever modules you want. You may need to flash magisk_patched.img again.

This has fixed multiple problems for me. It's redundant, but it tends to work.
[Magisk] 1branchonthevine:
I installed the Magisk selinux script, but after installing it no longer shows in Magisk, so how do I dissable/undo/uninstall the script? I installed a Selinux checker and it says it is on permissive, so the scrip must have installed, but I want to remove it. Is there an undo script, or can I manually delete the script in my root filesystem? THX
[Magisk] minproducer:
Hello guys

I used Redmi K20 pro with Eu rom 10.4, android 10.

I used the lastest version of this module but my devices was not found on ADB system on my computer.

So what I do now? I tried to fix it but I cannot find anything about it.
[Magisk] Extreme_Ninja2099:
Recently, setting SElinux to permissive is not advised. I had a issue with V4A setting my SElinux to permissive permenantly, but editing the magisk module to set SElinux to enforcing instead of permissive also works.

This is probs the only module that actually sets SElinux properly.

Here's the modded magisk module with the same credited creator, but just sets SElinux to Enforcing instead of permissive
[Magisk] jenneh:
OMFG I THINK THIS IS WHAT IVE BEEN LOOKING FOR. TEH HOLY GRAILLLLL OMGOMGOMG THANK YOU THANK YOU THANK YOUUUUU
[Magisk] Windsor1959:
Will ADB Root work for Android 8.1?
[Magisk] GbnrVR:
how can i make permissive enfocing because in 2022 i heard thats a BIG security risk and my custom ROM (havoc os) if selinux permissive
[Android Q&A, Help & Troubleshooting] Ken@7:
I own Motorola One Action running Android 10 and bootloader unlocked and unrooted. I would like to root this phone so I tried to install TRWP. However, I found TRWP doesn't support Android 10. So I installed Magisk Manager and tried to install Magisk but got an error massage saying "- Unpacking boot image, Unsupported/Unknown image format Installation failed".

Would you please help me what to do?

Thank you very much.
[Android Q&A, Help & Troubleshooting] toolhas4degrees:
Download your stock formate, extract the payload.bin with a payload bin extractor. Find the stock boot img. Copy to root of phone storage.

Open magisk manager select install on magisk. Pick patch image make sure the top 2 check boxes are checked on main screen before doing this. After magisk will say the patched image is in download folder on your phone. Copy the patched image to your PC. Open your command prompt in your fastboot tools folder put the patched image in it.

Reboot your phone to bootloader or fastboot mode. In your command prompt type fastboot flash boot (name of patched img).img

Reboot phone.

Before doing this make sure bootloader is unlocked and USB debugging is active
[Android Q&A, Help & Troubleshooting] Ken@7:
Thank you very much for your reply. However, I am still the beginner for Android and would like to have more explanation concerning the first sentence. I would like to know (1) how can I download my stock formate and where, (2) How can I extract the payload.bin. Thank you for your help.
[Android Q&A, Help & Troubleshooting] toolhas4degrees:
Sorry typo. Was supposed to be firmware. And on Android 10 inside the firmware zip. There is a payload.bin file. Search Google for a payload.bin dumper don't know what is you are on ex Linux mac or PC.

https://www.androidinfotech.com/motorola-one-action-android-10-stock/
[Xiaomi Redmi Note 5 Pro Questions & Answers] crni_vatreni:
Hello,

I've bought a used Redmi Note 5 AI Dual Camera, but after hard resetting it, MI account was locked. Previous owner couldn't help.

So the idea was to try unlock it using Miracle box, or flash new ROM, but the bootloader is locked and there's no way for me to access developer options, so the only way was through EDL.

I was successful only once while trying to ender EDL. In my device manager, there was a Qualcomm port. There was no way for me to enter EDL again, by shorting the two testpoints. They look very suspicious to me. Any idea how to enter EDL?

https://imgur.com/kWAS5yv
[Samsung Galaxy Note 10+ Questions & Answers] johntudd:
Hi guys I got a Verizon N975U note 10 plus and its stuck on Verizon I'm trying to flash it with U1 so I can pop a sim in and changes it to that carrier. Do I just need to flash it with the U1 file here https://androidfilehost.com/?w=files&flid=297980 or will it need something special the build # is SQS2ASJ8
[Samsung Galaxy Note 10+ Questions & Answers] scottusa2008:
Can't say for sure it would work on U firmware (lack of first hand experience to verify) as it would for U1.... As long as the phone is network/sim unlocked then you should be able to just put the new sim card in it (and the phone will read the sim card settings and apply them).

Flashing the U1 firmware instructions on flashing U1 firmware have been at link below (bottom of first post). You can get the firmware from that thread also.

https://xdaforums.com/showpost.php?p=80072192&postcount=1

Of course keep in mind that none of this will matter unless the phone is sim/network unlocked. As long as you meet the requirements from Verizon (or the phone was blacklisted for either non payment, lost/stolen or a warranty/insurance exchange that wasn't sent in) then this shouldn't be an issue.
[Samsung Galaxy Note 10+ Questions & Answers] johntudd:
its locked to Verizon at the moment when I put a sim in it will work for a bit then say its not allowed to use another carriers sim at this time.
[Samsung Galaxy Note 10+ Questions & Answers] scottusa2008:
Either wait until the phone is able to be unlocked by Verizon, or call them and request that they unlock it for you. Until that happens you will not be able to use a non-verizon sim card.

I would also advise keeping the U firmware for Verizon installed and not flashing the U1 firmware, as the Verizon sim/network unlock requires the carrier firmware... At least that is what I am gathering from various discussions/threads.
[Samsung Galaxy Note 10+ Questions & Answers] badutahboy:
Is your phone carrier locked to Verizon? Has it been activated on Verizon's service for 30 days? If not, I'm pretty sure firmware flashing won't help anything. I'm on a Verizon MVNO and they wouldn't even unlock it for me to use on their own network. I had to activate with them for 30 days.

However, now that mine is unlocked, it's still locked down to Verizon in a lotof ways. My SIM card for my current carrier can't apply an APN, for example, so I have to do it manually. I'm contemplating flashing U1 to fix that issue (I hope).
[Samsung Galaxy Note 10+ Questions & Answers] baumanbt:
I have a very similar situation. I bought a Note 10+ N975U (Verizon Unlocked) and I want to take it to U1 and then maybe to Sprint. I tried to go to the OP here and follow instructions. So I downloaded and selected all the files for U1 and apparently I did the "no-no" and got stopped with the SW Rev Check Fail : abl Fused 2 > Binary 1. I looked at what my phone is on and it is the SJ8 (November?) from Verizon. I'm guessing that means the BL file (bootloader?) in the U1 folder (SGO?) is older than what is on my phone? What do I need to do differently? I already tried without selecting the BL file, but it still gives the same error. Any help is appreciated! Thanks in advance!
[Samsung Galaxy Note 10+ Questions & Answers] scottusa2008:
The bootloader of the U1 firmware you were trying to flash is lower then what is currently on your phone. So yes you are correct that is the no-no. Also you can not skip the bootloader file when flashing, so that wouldn't have worked.

If you read through that thread you will have found others asking how to go from U to U1 firmware. Also the error within regards to trying to flash a lower bootloader version firmware was also asked and answered. I would encourage you to browse that thread and the Q&A forum because this process has been discussed on more then one occasion... It might contain helpful/useful info for you.

In short you need to get a newer firmware release. Using samfirm or frija apps, or the sammobile website look for the firmware your seeking. Google searching will show you how to obtain samfirm, frija is posted the forum here if I recall correctly.

For U1 the model is SM-N975U1 and the region is XAA.
[Samsung Galaxy Note 9 Questions & Answers] deliveryman99:
i just installed TMO firmware in my At&t phone since i was not able to use wifi calling, but now it works after firmware conversion, my question is how do i get rid of the At&t logo and sound when i start the phone? is there i can put T-mobile logo in its place or something else. thanks
[JAM, MDA Compact, S100 Software Upgrading] broadband:
after i upgrade my Magician , i see on bootscreen "NoGSM " and ofcourse i can t use the GSM services when it s working,,and when i try to reflash it with a new upgrade , it couldn t go on ,,,0% and give me error 114

Could anyone help me pls ,,,,,

Thanks
[JAM, MDA Compact, S100 Software Upgrading] Nokia 3650:
Did you try reflashing the RadioROM only (radio.nbf)?
[JAM, MDA Compact, S100 Software Upgrading] broadband:
yes i tried to reflash it only with the radio ROm .... but no way ,,gives me thesame errror

pls help
[JAM, MDA Compact, S100 Software Upgrading] Nokia 3650:
You will have to use the "NoID RUU" instead. There are many pages here with different versions that you can choose from.
[LG G8X ThinQ Questions & Answers] ppczouz:
Hello All

O

I love my G8x, and I love using it in landscape with the 2 screens attached.

But everytime i go back to home screen, it's in portrait.

This gets disorienting especially when using the full screen LG keyboard on the second screen.

Any fix to that? Is there a launcher that supports landscape and can span the two screens?
[LG G8X ThinQ Questions & Answers] pfroo40:
I haven't found a way to use a different launcher as the default launcher on the second screen, or a way to rotate the LG home. Hopefully the Android 10 update adds some extra features, there. I'd love to be able to use the Microsoft Launcher beta which supports landscape, or Nova.
[LG G8X ThinQ Questions & Answers] Flavio:
You can sort of do this with Nova Launcher and Tasker to automatically launch Nova Launcher when pressing the right side home button and switch Nova Launcher to widescreen with G8XWideMode.
[LG G8X ThinQ Questions & Answers] ppczouz:
Indeed, the Microsoft launcher is my favorite and has been my default launcher fir a while until I switched to the G8x.

Another thing, I switch to the gestures bar, and now main screen operates on Android 9 interface style while the second screen does Android 8 style (with buttons and vertical stacking of recent apps as opposed to gestures and horizontal side by side apps on the main)... Again, very disorienting.

I hope these will be addressed by the Android 10 update.
[LG G8X ThinQ Questions & Answers] Deathbot64:
The best way i have to get this done is using apex launcher. Doesnt affect the second screen but the phones screen will rotate and give you access to the app drawer.

---------- Post added at 03:51 PM ---------- Previous post was at 03:39 PM ----------

Apex launcher works for this. And i got both screens rotating
[Samsung Galaxy Tab S6 Questions & Answers] Kaylee_12:
Hi guys!

I'm unable to find a way to get the navigation bar to appear on the side, (within much easier reach - right under my thumb) , while tab is in landscape mode. It always goes to the bottom.

I've searched for days, but can't find a solution. Am I missing something, or is this not possible?

I have played with Smartlock. Don't want to root, though.

Thanks!
[Samsung Galaxy Tab S6 Questions & Answers] jed84:
Just install Good Lock from the Galaxy Store and then install NavStar via Good Lock.

This will not move the navigation bar to the side but you can easily move the icons within the bar to the side.
[Samsung Galaxy Tab S6 Questions & Answers] Kaylee_12:
Much better! I never would have tapped on the "new configuration" button had you not pointed out this possibility. Thank you very much. : )
[Android Q&A, Help & Troubleshooting] Ciren__:
Specs:

Xiaomi Mi A2 (A/B part. scheme)

Android 10 Pixel Experience

I'm currently using F2FS for the added read/write speed but with no encryption at all. And that's not really ideal, as you might've guessed.

fastboot --wipe-and-use-fbe

formats to ext4 by default and there's no way to choose the FS. What I'm asking is is there a way to do this manually, via adb shell from recovery, for instance?

Edit: I mean, of course it's possible to use fscrypt directly but I'm not even sure that that's what Android uses by default and where it stores the passphrase to unlock it
[Android Q&A, Help & Troubleshooting] matiusman:
enable file based encryption

yes you can do it.

let me search little bit about it.

i will be back to you soon
[Android Q&A, Help & Troubleshooting] Ciren__:
So, any new info?