Related
Hi, Does anyone know if Magisk root is supported on the Xperia XZ (F8331)?
The reason I ask is I want to be able to hide root from some apps that will not work with root otherwise i'd use SuperSU.
rasseru16 said:
Hi, Does anyone know if Magisk root is supported on the Xperia XZ (F8331)?
The reason I ask is I want to be able to hide root from some apps that will not work with root otherwise i'd use SuperSU.
Click to expand...
Click to collapse
Yes V12 works great so far
dillalade said:
Yes V12 works great so far
Click to expand...
Click to collapse
Perfect thanks. Now rooted with Magisk
rasseru16 said:
Perfect thanks. Now rooted with Magisk
Click to expand...
Click to collapse
I have had boot loops twice now.
First time I had to do a reinstall.
2nd time I ran the magisk uninstall from TWRP.
Booted up after that
Just a heads up.
I'm researching how to resolve this. Not to sure
rasseru16 said:
Perfect thanks. Now rooted with Magisk
Click to expand...
Click to collapse
I'm rooted with magisk too but unable to hide root from apps like 8ball pool and other apps. Hide root functionality don't work at all.
Have no problems with Magisk V12 so far had it running for several days now. Hiding root from Snapchat, My EE and some other apps without issue. I dont have TWRP installed though.
rasseru16 said:
Perfect thanks. Now rooted with Magisk
Click to expand...
Click to collapse
How do you hide root? With me it just doesn't work. I enable hide root and select app.
Has anyone faced any bootloops with magisk.
Some research has shown it's perhaps when using viper4android together with magisk that can cause a bootloop. But that was on a Nexus 6p from my research.
Has anyone set up magisk and also viper4android, that can let me know if they have faced this bootloop?
I have found that I can use Magisk Root with 'AndroPlus Kernel' but not 'Sony Stock Patcher for Xperia XZ by AdrianDC'. Installing MAGISK under the Sony Stock Patcher Kernel caused TWRP to create an error "Unable to repack boot image!"
latest update working without any hiccups
pw1nce said:
I'm rooted with magisk too but unable to hide root from apps like 8ball pool and other apps. Hide root functionality don't work at all.
Click to expand...
Click to collapse
yes it works, u need to enable magisk core only to make safetynet work and magisk hide too
fastbooking said:
yes it works, u need to enable magisk core only to make safetynet work and magisk hide too
Click to expand...
Click to collapse
Can you prove that or do you mind writing a little guide how to get past safetynet?
I literally tried everything I could find to get Magisk Hide working with unlocked bootloader yesterday after the change to pass Safetynet for Pokemon Go. No chance. Before I could at least remove Magisk to run Go but now that's over. What I tried was latest A.35 with Stock + Patcher or AndroPlus with twrp and then Magisk 13.2 (plus fixes). But I always failed CTS and Basic Integegrity.
Even with Magisk Hide turned on and Core Modules only activated. No chance.
Delvius said:
Can you prove that or do you mind writing a little guide how to get past safetynet?
I literally tried everything I could find to get Magisk Hide working with unlocked bootloader yesterday after the change to pass Safetynet for Pokemon Go. No chance. Before I could at least remove Magisk to run Go but now that's over. What I tried was latest A.35 with Stock + Patcher or AndroPlus with twrp and then Magisk 13.2 (plus fixes). But I always failed CTS and Basic Integegrity.
Even with Magisk Hide turned on and Core Modules only activated. No chance.
Click to expand...
Click to collapse
How to fix this:
1. This fix is only a temporary fix. You will have to apply it after every reboot.
2. Use a Terminal emulator app or adb to enter these commands.
3. Use resetprop to delete the properties - again: I have no idea how this interferes with magisk behavior!!!! Do this at your own risk:
Code:
su
resetprop --delete init.svc.magisk_pfs
resetprop --delete init.svc.magisk_pfsd
resetprop --delete init.svc.magisk_service
resetprop --delete persist.magisk.hide
Using Magisk Core mode? also execute this command:
Code:
resetprop --delete ro.magisk.disable
smellz said:
How to fix this:
1. This fix is only a temporary fix. You will have to apply it after every reboot.
2. Use a Terminal emulator app or adb to enter these commands.
3. Use resetprop to delete the properties - again: I have no idea how this interferes with magisk behavior!!!! Do this at your own risk:
Code:
su
resetprop --delete init.svc.magisk_pfs
resetprop --delete init.svc.magisk_pfsd
resetprop --delete init.svc.magisk_service
resetprop --delete persist.magisk.hide
Using Magisk Core mode? also execute this command:
Code:
resetprop --delete ro.magisk.disable
Click to expand...
Click to collapse
Does it work for you? It doesn't for me. As I worte I did exactly this - no chance.
If it works for you, which firmware, kernel and twrp do you use?
Delvius said:
Does it work for you? It doesn't for me. As I worte I did exactly this - no chance.
If it works for you, which firmware, kernel and twrp do you use?
Click to expand...
Click to collapse
Yes it works with me.
Fw: 41.2.A.7.8
Kernel: AndroPlus kernel v27
Twrp: twrp-3.1.1-20170523-boot-kagura (DL: https://mega.nz/#F!bg9QhDzC!TTkhy2Fi6cNTZ1ojlmobRQ )
Magisk: v13.2 and 5.0.6 Manager
Delvius said:
Can you prove that or do you mind writing a little guide how to get past safetynet?
I literally tried everything I could find to get Magisk Hide working with unlocked bootloader yesterday after the change to pass Safetynet for Pokemon Go. No chance. Before I could at least remove Magisk to run Go but now that's over. What I tried was latest A.35 with Stock + Patcher or AndroPlus with twrp and then Magisk 13.2 (plus fixes). But I always failed CTS and Basic Integegrity.
Even with Magisk Hide turned on and Core Modules only activated. No chance.
Click to expand...
Click to collapse
You need to know that Google updated safetynet for magisk 13.2 so for the moment it's pretty random to get it working, the team is aware of that and they're making the necessary to fix this
smellz said:
Yes it works with me.
Fw: 41.2.A.7.8
Kernel: AndroPlus kernel v27
Twrp: twrp-3.1.1-20170523-boot-kagura (DL: https://mega.nz/#F!bg9QhDzC!TTkhy2Fi6cNTZ1ojlmobRQ )
Magisk: v13.2 and 5.0.6 Manager
Click to expand...
Click to collapse
Thanks a lot! You give me hope.
Delvius said:
Thanks a lot! You give me hope.
Click to expand...
Click to collapse
V13.3 fix safetynet
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Code:
v13.3
- [MagiskHide] Update to bypass Google CTS (2017.7.17)
- [resetprop] Properly support removing persist props
- [uninstaller] Remove Magisk Manager and persist props
Still not working for me even with latest version. I'm still waiting silently for any help here.
boydzethuong said:
Still not working for me even with latest version. I'm still waiting silently for any help here.
Click to expand...
Click to collapse
What kernel are you using?
Here is a small guide which definitely works:
1.Flash firmware 4.2.A.7.8
2. Uses tobias.waldvogel tool for fido_keys
Code:
-.ftf with WinRAR open,
-Kernel.in unpack,
-Open Flashtool,
-Select Top Tools,
-Sin Editor and in the next window
-Extract data.
-Now the extracted kernel.elf in the folder of the waldvogel its tool,
-There open the WinKonsole,
-Enter this command:
-Rootkernel kernel.elf boot.img,
-Disable sony_ric => YES
-Disable ... verity => YES
-DRM-Fix => YES
-TWRP => NO
-BusyBox => NO
-
NOW THE KERNEL FLASH
3. Flash TWRP: twrp-3.1.1-20170523-boot-kagura (DL: https://mega.nz/#F!bg9QhDzC!TTkhy2Fi6cNTZ1ojlmobRQ )
4. Flash Kernel via TWRP - AndroPlus kernel v27 and Reboot
5. Flash Magisk v13.3 via TWRP
Finished and safetynet should work
Introduction
This is an unofficial build of LineageOS 16 for Redmi Note 7 Pro. Differences from the one provided by Dyneteve include:
- Ported the CAF wrappedkey encryption stuff, which is what MIUI uses, over using patches from https://mokeedev.review/q/topic:%22fbe-wrapped-key%22+(statuspen%20OR%20status:merged), This requires an recovery with wrappedkey decryption support, e.g. this one
- Applied unmerged patch https://review.lineageos.org/c/LineageOS/android_build/+/247066 to mount system as /system_root properly on install. This makes addon.d scripts (e.g. Magisk / GApps survival script) work again on our device. This requires an recovery with proper system_as_root support, e.g. this one
- ROM includes its own vendor image instead of relying on one provided by MIUI. I intend to try to build as much of vendor image as possible from CAF source in the future.
Flash instructions
- Make sure you have the latest firmware images. If not, update them before flashing.
- Flash a TWRP recovery that supports mounting system as /system_root and supports wrappedkey encryption (the one provided above)
- Wipe data partition (without wiping /data/media). If you came from another non-CAF ROM (ROM that do not support wrappedkey mode) and had encryption enabled, you will need to format your data partition (including /data/media).
Note: If you decide to format your data partition, always format with 'advanced wipe' in TWRP recovery. DO NOT use fastboot -w or fastboot erase, even if you do, please format again in recovery, otherwise the system might not work.
- Install the zip in TWRP.
- Install whatever you want e.g. Magisk, OpenGapps
- DO NOT install the fcrypt disabler.
- Reboot and enjoy
Known issues
DO NOT remove screen lock passwords if you set one. You can change the password just fine, but DO NOT REMOVE IT. YOU WILL LOSE ACCESS TO ALL DATA IF YOU DO THIS AND REBOOT.
Removing screen lock passwords work after 20190528-1.
Downloads
20190609-1: https://mega.nz/#!PdRnxIia!Boh-a8e5JHt8YEBwbXKt8rWYj3PC56mdpEIXwDEY2ng
changelog: 1) Merged upstream LineageOS (June security patch) 2) Updated kernel to 4.14.123 3) Updated MIUI binary blobs 4) Some clean-up
NOTE: /proc/last_kmsg support is removed due to incompatibility. This feature is replaced by pstore, which you could find more information on through some Google-fu.
History versions:
20190528-1: https://mega.nz/#!nZRTQCbS!qf-RdT-ijayg8UBxyyz3Hoi2O_8ZtpWewgNv-eVDcqA
changelog: 1) merged upstream LineageOS; 2) fixed the bug of removing screen lock passwords, now it won't swallow all your data (this commit: https://github.com/PeterCxy/android...mmit/d2fe3434cddb98eeb414906e71a817559ade1b26; 3) merged LTS kernel 4.14.122, thanks to YaroST and aviraxp; 4) fixed potential charging problem; 5) some other kernel improvements
20190526-1: https://mega.nz/#!rRgwmY5T!2fQyDjukLoGmk7KRtas5n2Y_it9QS_s2noAItzNvFfY
Sources
Device: https://github.com/PeterCxy/android_device_xiaomi_violet
Kernel: https://github.com/PeterCxy/android_kernel_xiaomi_sm6150
Other changes and patches: see what is available on my GitHub https://github.com/PeterCxy/, everything is open-source for this ROM.
Contributors
PeterCxy, GuaiYiHu, aviraxp
Source Code: https://github.com/PeterCxy/android_device_xiaomi_violet
Thanks ?
Thank you for the ROM!
There's a Typo in the ROM os version description.
cant boot. installed as mentioned in instruction. its automatically rebooting to recovery (twrp, the given one). now whenever i try to flash other rrecovery its not booting into. stuck. please help.
jyoti.id said:
cant boot. installed as mentioned in instruction. its automatically rebooting to recovery (twrp, the given one). now whenever i try to flash other rrecovery its not booting into. stuck. please help.
Click to expand...
Click to collapse
If you can't boot to recovery at all you may need to flash a fastboot ROM of MIUI (of course in fastboot mode) and try to install twrp again.
jyoti.id said:
cant boot. installed as mentioned in instruction. its automatically rebooting to recovery (twrp, the given one). now whenever i try to flash other rrecovery its not booting into. stuck. please help.
Click to expand...
Click to collapse
Sorry I have no idea here.. What ROM you were on before flashing this?
Dwughjsd said:
If you can't boot to recovery at all you may need to flash a fastboot ROM of MIUI (of course in fastboot mode) and try to install twrp again.
Click to expand...
Click to collapse
iv flashed the stock rom, but now the internal storage is showing only 16GB of storage.
Edit: fixed everything. Thank you. I was curious about the battery backup of this ROM badly, so I just rushed in things so maybe I made some mistakes.
jyoti.id said:
iv flashed the stock rom, but now the internal storage is showing only 16GB of storage.
Edit: fixed everything. Thank you. I was curious about the battery backup of this ROM badly, so I just rushed in things so maybe I made some mistakes.
Click to expand...
Click to collapse
Just keep in mind that safety first
Download link not working
Edit: UC browser was the culprit
dwughjsd said:
just keep in mind that safety first
Click to expand...
Click to collapse
how u fixed storage issue
gsunil said:
how u fixed storage issue
Click to expand...
Click to collapse
It was @jyoti.id that faced and solved the issue, so let's call him for an answer
rom keeps rebooting into twrp , i did every step
gsunil said:
how u fixed storage issue
Click to expand...
Click to collapse
I just flashed the whole fastboot rom again & it fixed everything.
---------- Post added at 04:34 AM ---------- Previous post was at 04:33 AM ----------
King_Dinoco10 said:
rom keeps rebooting into twrp , i did every step
Click to expand...
Click to collapse
Same thing happened with me too
Device not charging above 86%. Anyone else facing this bug ?
PeterCxy said:
Sorry I have no idea here.. What ROM you were on before flashing this?
Click to expand...
Click to collapse
The phone does not charge more than 91%!
lapo_chel said:
The phone does not charge more than 91%!
Click to expand...
Click to collapse
now should be fixed, try today's new build
PeterCxy said:
now should be fixed, try today's new build
Click to expand...
Click to collapse
Safetynet does not pass.
lapo_chel said:
Safetynet does not pass.
Click to expand...
Click to collapse
It's because I used vendor files from MIUI beta. You can bypass it with a magisk module to reset the build fingerprint
Many thanks for your build! I like it much.
IMHO, SELinux should be enabled.
Hello,
can anybody help me for my Problem with my Galaxy S4 GT-I9506
i have do the following
1. TWRP install the actual version
2. flash lineage-16.0-20190609-UNOFFICIAL-ks01ltexx https://forum.xda-developers.com/galaxy-s4/i9506-develop/rom-lineageos-16-0-unofficial-galaxy-s4-t3848597
3. flash open_gapps-arm-9.0-pico-20190612 TWRP
4. flash Magisk-v19.3 mit TWRP
But i have problems with them
https://prntscr.com/o7onem
https://prntscr.com/o7oneu
https://prntscr.com/o7oner
i have no idea what i can do can anybody help me please?
Does the ROM come rooted? It may have system root inside still, my s5 ROMs always did I think. I always had to use adb shell or flash a zip inside twrp. Usually did both.
Search XDA for osm0sis tool called unsu, it should be a .zip. Flash in twrp after installing gapps and booting once. This should clear system root, and allow you to pass once magisk is installed.
The other issue I can think of is maybe signature verification or something with the playstore. I don't remember what it is, my phones and ROMs have always worked after magisk. If the above steps don't work maybe that's related. We will have to look around if that's the case
I had a look at the device tree and I can see a couple of things for your dev @kyasu to possibly add
- we had safetynet start failing a few weeks back on i9505 and these were the fixes I found
- Product_name - Samsung never released a product called full_ks01ltexx - will need to be set to correct product that google recognises by a build_prop_override ("GT-I9506" or similar).
- Change build fingerprints to pixel3 versions.
- hide permissive with init script.
these 2 commits here show what needs done:
https://github.com/JDCTeam/android_...mmit/ea27cf29e4084d860fb8549be2e3cdb1599a6d08
https://github.com/PixelExperience-...mmit/045dc32219172a288c10f503478deb3eb3b2aee5
andrew2432 said:
Does the ROM come rooted? It may have system root inside still, my s5 ROMs always did I think. I always had to use adb shell or flash a zip inside twrp. Usually did both.
Search XDA for osm0sis tool called unsu, it should be a .zip. Flash in twrp after installing gapps and booting once. This should clear system root, and allow you to pass once magisk is installed.
The other issue I can think of is maybe signature verification or something with the playstore. I don't remember what it is, my phones and ROMs have always worked after magisk. If the above steps don't work maybe that's related. We will have to look around if that's the case
Click to expand...
Click to collapse
is this tool correct? https://forum.xda-developers.com/showpost.php?p=63615067
is the rom correct what i use?
OK i have unSu the device and have reinstall Magisk ..
https://prnt.sc/o929eu
but i have the same problem
tuvok1981de said:
OK i have unSu the device and have reinstall Magisk ..
https://prnt.sc/o929eu
but i have the same problem
Click to expand...
Click to collapse
- have you tried changing fingerprint with Magiskhide?
- has it worked previously and just recently stopped working or is this your first attempt?
- do other users on the same ROM have similar results?
I incidentally also checked DT if the ROM is rooted and doesn't look like it. Kernel also has namespace commits too, so it's not that.
Buff99 said:
- have you tried changing fingerprint with Magiskhide?
- has it worked previously and just recently stopped working or is this your first attempt?
- do other users on the same ROM have similar results?
I incidentally also checked DT if the ROM is rooted and doesn't look like it. Kernel also has namespace commits too, so it's not that.
Click to expand...
Click to collapse
- yes i have make with MagiskHidePropsConf-v.4.0.3 and terminal props S4 and S4 Active variante but it will not do this
- it will not work all the time where i have flash my S4
- i have no idea iam not the developer from the rom iam only a User
1. Flash twrp
2. Full wipe, system data internal
3. Flash ROM, boot
4. Flash gapps, boot
5. Flash magisk, should pass
6. If not, change selinux to enforcing
Let us know?
andrew2432 said:
1. Flash twrp
2. Full wipe, system data internal
3. Flash ROM, boot
4. Flash gapps, boot
5. Flash magisk, should pass
6. If not, change selinux to enforcing
Let us know?
Click to expand...
Click to collapse
Point 1. is on the Phone
ähm where must i make Point 6 ?
andrew2432 said:
1. Flash twrp
2. Full wipe, system data internal
3. Flash ROM, boot
4. Flash gapps, boot
5. Flash magisk, should pass
6. If not, change selinux to enforcing
Let us know?
Click to expand...
Click to collapse
OK i have make flash new all 5 Points
but ctsProfile: false / basicIntegrity: false on Magisk Manager
tuvok1981de said:
-
- i have no idea iam not the developer from the rom iam only a User
Click to expand...
Click to collapse
Yeah, well this is a developer forum. There is a thread for the ROM you use. It is assumed you have already seeked advice there from other users of the same rom...?
Being aware of whether others have this working or not shows whether you are wasting your time or not.
Buff99 said:
Yeah, well this is a developer forum. There is a thread for the ROM you use. It is assumed you have already seeked advice there from other users of the same rom...?
Being aware of whether others have this working or not shows whether you are wasting your time or not.
Click to expand...
Click to collapse
in this forum say the users i must go in the Samsung S4 Forum and ask my Question!
tuvok1981de said:
in this forum say the users i must go in the Samsung S4 Forum and ask my Question!
Click to expand...
Click to collapse
I searched safety net inside the ROM forum, it said to change selinux to enforcing. I am not sure how. Maybe with a magisk module
Edit: credit for these instructions goes to @DiamondJohn
The user only installed magisk and safety net passed. Are you installing xposed or anything?
stecko said:
Can you guide me how to switch selinux to enforcing?
Click to expand...
Click to collapse
in a terminal, or part of a boot script
Code:
su;
setenforce 1;
or you could try the app I built, where you will find it under the menu
Code:
Current State>SELinux>Set SELinux Enforcing.
https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260
andrew2432 said:
I searched safety net inside the ROM forum, it said to change selinux to enforcing. I am not sure how. Maybe with a magisk module
Edit: credit for these instructions goes to @DiamondJohn
The user only installed magisk and safety net passed. Are you installing xposed or anything?
in a terminal, or part of a boot script
Code:
su;
setenforce 1;
or you could try the app I built, where you will find it under the menu
Code:
Current State>SELinux>Set SELinux Enforcing.
https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260
Click to expand...
Click to collapse
Very Nice .. this part have help ..
Code:
su;
setenforce 1;
https://prnt.sc/o9gchi
thank you!
A new tool is available which can install Magisk in emulators. See Delta Magisk
This tool is depreciated. No support will be provided.
Magisk
Note:- This is a experimental feature. I made this guide only for SuperUser management in MEmu. If you want modules then don't expect it to work. Modules like MigiskHideProps are not working. So don't expect much.
As of now there is no working way for passing SafetyNet for playing games and apps that use it.
For someone who want to install Magisk in emulators MEmu v7.3.2/LDPlayer v4.0.45 which is based on Android-x86, follow below guide.
What is this method?
-This method is used by exploits like mtk-su, qu1ckr00t without patching boot.img. I used this method because I don't know how to modify .vmdk as seen in here. Drawback of this method is that, many modules like MagiskHideProps are not working.
If you are using MEmu then follow https://forum.xda-developers.com/t/...-3-2-or-ldplayer-4-0-45.4222919/post-84574053
If you are using LDPlayer then follow https://forum.xda-developers.com/t/...-3-2-or-ldplayer-4-0-45.4222919/post-84580333
Reference:-
-https://forum.xda-developers.com/t/...diatek-armv8-2020-08-24.3922213/post-82081703
-https://github.com/grant-h/qu1ckr00t/blob/master/app/src/main/res/raw/magisk_install
Credits:-
@topjohnwu
@diplomatic
Enjoy!
SuperSU
If you want SuperSU instead of Magisk, then follow below guide
Enable Root mode
Download SuperSU zip from here
Download and install BusyBox from here
Download update-binary script from here. We can save this with CTRL + S if using browser in Windows OS
In Terminal Emulator run below commands
Code:
su
export PATH=/system/xbin:/system/bin
cd /sdcard/Download
sh update-binary 2 1 $PWD/SR5-SuperSU-v2.82-SR5-20171001224502.zip
Restart MEmu. Enjoy!
Credits:-
@Chainfire
Xposed
I have modified youling257's xposed at Github. Since it is not flashable zip by default, we have to do it our own. Made it x86_64 flashable zip like x86 one. Nothing is changed. Just added x86_64 files to x86 system folder after deleting its contents, changed `arch` to x64 and signed.
We can also install Xposed in MEmu/LDPlayer Android 7.1.2(25) by below
Download last version of Xposed from
x86 => https://dl-xda.xposed.info/framework/sdk25/x86/xposed-v89-sdk25-x86.zip
(Tip:- 32bit users can directly install Xposed from Xposed Installer app without this manual flashing)
x86_64 => https://forum.xda-developers.com/attachments/xposed-v89-sdk25-x86_64-signed-zip.5197651/
copy it to /data/local/tmp
extract only META-INF/com/google/android/update-binary from the zip to /data/local/tmp
Run below commands in Terminal Emulator app with root.
Code:
su
cd /data/local/tmp
chmod 777 update-binary
if your arch is x86, then run below one
Code:
NO_UIPRINT=1 ./update-binary 2 1 xposed-v89-sdk25-x86.zip
rm update-binary xposed-v89-sdk25-x86.zip
if your arch is x86_64, then run below one
Code:
NO_UIPRINT=1 ./update-binary 2 1 xposed-v89-sdk25-x86_64-signed.zip
rm update-binary xposed-v89-sdk25-x86_64-signed.zip
Download Xposed apk from https://forum.xda-developers.com/attachments/xposedinstaller_3-1-5-apk.4393082/ and install it and restart.
Reference:-
XposedInstaller/app/src/main/java/de/robv/android/xposed/installer/installation/FlashDirectly.java at 8f8f2d7072d1f7b02f237e4ac864e767b7aa6e4c · rovo89/XposedInstaller
Contribute to rovo89/XposedInstaller development by creating an account on GitHub.
github.com
Credits:-
@rovo89
@youling257
@Camlin3 for initial thread.
Enjoy!
Deprecated Guide
Spoiler
Start MEmu/LDPlayer and enable Root mode in Settings
Download and install latest Magisk Manager from here
Download Magisk.zip from here and take magiskinit file from it according to your architecture and place it like /sdcard/init.d/bin/magiskinit.
Download the script from here. We can save this code with CTRL + S in Browser in Windows OS.
Install Terminal Emulator app and run below code in it
Code:
su
sh /sdcard/Download/magisk-boot.sh
Now, you have successfully installed Magisk.
You have to execute the script on every boot. We can use 'Termux:Boot' or 'init.d scripts support'(don't forget to turn off battery optimization for the app)
please, would it be possible for you to record a step by step video?
rickkarpov said:
please, would it be possible for you to record a step by step video?
Click to expand...
Click to collapse
I can't do that, because of my Internet issues to upload. You can message at Telegram with username 'HemanthJabalpuri', so that I can guide you.
Thanks
after running script, it says magiskinit not found. I followed all steps, please help.
Anubhav001 said:
after running script, it says magiskinit not found. I followed all steps, please help.
Click to expand...
Click to collapse
Ok, tell me if /storage/emulated/0 is there or not.
If it is there, then make sure that magiskinit in placed in /storage/emulated/0/init.d/bin
Thanks
Nice guide.
Thank you very much
This is cool magisk was installed and everything was fine... I expected it to be
But the Modules are the issue, can't make them to work..... any help??
I have installed the magisk hide module and its shown activated but can't bypass safteynet, is that because of the superuser within the emulator?
rushi12565 said:
This is cool magisk was installed and everything was fine... I expected it to be
But the Modules are the issue, can't make them to work..... any help??
I have installed the magisk hide module and its shown activated but can't bypass safteynet, is that because of the superuser within the emulator?
Click to expand...
Click to collapse
I have also tried that, but failed. But some modules like Busybox are working. But it does not work along with MagiskHideProps.
@VD171 suggested to use HiddenCore module from Xposed to pass SafetyNet. I didn't tested it. May or may not work. Give it a try.
Thanks
HemanthJabalpuri said:
I have also tried that, but failed. But some modules like Busybox are working. But it does not work along with MagiskHideProps.
@VD171 suggested to use HiddenCore module from Xposed to pass SafetyNet. I didn't tested it. May or may not work. Give it a try.
Thanks
Click to expand...
Click to collapse
I'm using HiddenCore-module with Android 6.0, Android 7.0, Android 8.1, Android 9.0 and Android 10.0.
It is working perfectly on all them.
MagiskHideProps has a FANTASTIC intention, but a poor execution.
It has conflicts inside itself.
Unhappy, I can't suggest it to anybody.
Certainly, HiddenCore-Module will work for you.
HiddenCore Module | Xposed Module Repository
repo.xposed.info
HemanthJabalpuri said:
I have also tried that, but failed. But some modules like Busybox are working. But it does not work along with MagiskHideProps.
@VD171 suggested to use HiddenCore module from Xposed to pass SafetyNet. I didn't tested it. May or may not work. Give it a try.
Thanks
Click to expand...
Click to collapse
Oh ok.
abt the exposed doesn't it just show that safetynet is passed and not actually fix the safetynet right?
rushi12565 said:
Oh ok.
abt the exposed doesn't it just show that safetynet is passed and not actually fix the safetynet right?
Click to expand...
Click to collapse
If the app see that safetynet is passed, what does matter if it is fixed or not?
If you've rooted your device, your safetynet will be broken forever, until you unroot it.
That's simple.
Just fake it and everything will works perfectly.
Umm i'll try then
rushi12565 said:
Umm ill's try then
Click to expand...
Click to collapse
Don't forget to share result after trying.
Yea so i was trying to see if by passing saftey net on emulator I could play pokemon go on it (was just curious) and i failed xposed doesn't help. it's shown that safetynet is passed but it isn't i guesss.
rushi12565 said:
Yea so i was trying to see if by passing saftey net on emulator I could play pokemon go on it (was just curious) and i failed xposed doesn't help. it's shown that safetynet is passed but it isn't i guesss.
Click to expand...
Click to collapse
Did you try to check safetynet on magisk app?
Can you try on others app too?
Are you sure xposed is properly working?
Are you sure hiddencore is activated in modules tab?
Try checking logs too
VD171 said:
Did you try to check safetynet on magisk app?
Can you try on others app too?
Are you sure xposed is properly working?
Are you sure hiddencore is activated in modules tab?
Try checking logs too
Click to expand...
Click to collapse
Yea i've checked that hidden core is activated in the modules tab
The safteynet test in magisk is passed but it couldn't pass the test from a normal safteynet test app
this one https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettest&hl=en_IN&gl=US
rushi12565 said:
Yea i've checked that hidden core is activated in the modules tab
The safteynet test in magisk is passed but it couldn't pass the test from a normal safteynet test app
this one https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettest&hl=en_IN&gl=US
Click to expand...
Click to collapse
Did you rename magisk app?
Did you enable magisk hide?
Did you select the desired app for hiding by magisk hide?
There are many steps for hiding root, magisk, xposed or anything on android.
You need to try everything you can.
VD171 said:
Did you rename magisk app?
Did you enable magisk hide?
Did you select the desired app for hiding by magisk hide?
There are many steps for hiding root, magisk, xposed or anything on android.
You need to try everything you can.
Click to expand...
Click to collapse
Hided magisk
Enabled magisk hide when I tried to hit the reboot the emulator just struck so I had to close and restart the emulator itself and when I checked the modules in magisk the magisk hide props was toggled(was shown working)
The thing is when I did this the safety net was not passed, xposed hidden core module was not activated. so now I will try and see if activating both hidden core module and magisk hide will help or not
Yea I have tried it and the results are the same
Safety net is shown passed in magisk but in the actual test it fails
Xposed and magisk modules are activated
(logs in the next msg)
SYSTEM DIALOG ERROR DISABLER V2.0
SUPPORT: TELEGRAM CHANNEL - TELEGRAM GROUP - SUPPORT ME
ABOUT THIS:Magisk module to disable system alerts on every boot forever, based on Dynamic Installer
Features:
Disabling alerts includes the most common "There is an internal problem with the device, contact the manufacturer for more information"
HOW DO I USE IT?
Code:
1. Simply install the module by Magisk app
2. The process requires the recompilation of a .JAR so be patient!
CREDITS TO:
Me @BlassGO (Developer of System Dialog Error Disabler and Dynamic Installer)
System Dialog Error Disabler 2.0
WARNING: In case of any ERROR, delete the module: /data/adb/modules/dialog-error-disabler
Reserved
Will be testing as soon as I do a full backup. Fiddling with stuff last night threw me into an unexpected bootloop and I hadn't backed up, so I just got things back in order.
Edit: installed, warning still appears
Jason Hugg said:
Will be testing as soon as I do a full backup. Fiddling with stuff last night threw me into an unexpected bootloop and I hadn't backed up, so I just got things back in order.
Edit: installed, warning still appears
Click to expand...
Click to collapse
Hi, in what version of android and can u send me ur stock services.jar? The magisk module installation log would also be helpful.
Moto G Power (2021} A11 LOS 18 gsi, stock recovery, stock kernel magisk patched boot.img, verity off, system r/w
Jason Hugg said:
Moto G Power (2021} A11 LOS 18 gsi, stock recovery, stock kernel magisk patched boot.img, verity off, system r/w
Click to expand...
Click to collapse
Okay, also send me the installation log (there is a save button at the top after installation in the magisk app)
Jason Hugg said:
Moto G Power (2021} A11 LOS 18 gsi, stock recovery, stock kernel magisk patched boot.img, verity off, system r/w
Click to expand...
Click to collapse
Thx for the services.jar, I found the problem, I will release a more generic update soon
Jason Hugg said:
Moto G Power (2021} A11 LOS 18 gsi, stock recovery, stock kernel magisk patched boot.img, verity off, system r/w
Click to expand...
Click to collapse
Done, u can try the new version
Can we get additionals info about this module?? What can be done if bootloop?? What about OEM? Samsung or other, Which Android it supports?
Is there for example a hard force uninstaller to recover?
Thx
Can you put this on your github repo?
Just for some clarification...this removes the message after boot or while on the bootscreen regarding an unlocked bootloader?
Personally I'm looking for it to remove the message while on the bootscreen as I get none after boot.
kevinco1 said:
Just for some clarification...this removes the message after boot or while on the bootscreen regarding an unlocked bootloader?
Personally I'm looking for it to remove the message while on the bootscreen as I get none after boot.
Click to expand...
Click to collapse
im looking for the same thing