I just rooted my tablet and phone, they're on the following
Note 10.1 2014 p600 - 5.1.1
Note 3 n9005 - 5.0
I really don't know what files to grab for them, I understand wanam xposed and xposed installer. However, can anyone be kind enough to link me to the right files please
rirawin said:
I just rooted my tablet and phone, they're on the following
Note 10.1 2014 p600 - 5.1.1
Note 3 n9005 - 5.0
I really don't know what files to grab for them, I understand wanam xposed and xposed installer. However, can anyone be kind enough to link me to the right files please
Click to expand...
Click to collapse
You need two files:
the Xposed framework (a .zip file which has to be flashed through custom recovery (TWRP recommended))
and
the Xposed Installer (an .apk file that can be installed like any other app).
Download both files, put them onto your device's SD card (or storage) and boot into recovery. Flash the Xposed framework (the .zip file), wipe cache&dalvik and reboot. Afterwards, install the Xposed Installer (the .apk file) and you are done.
To identify the correct SDK version:
SDK21 = Android 5.0.x
SDK22 = Android 5.1.x
SDK23 = Android 6.0.x
To identify the correct CPU version (arm, arm64, x86) search for your device's specifications and identify the CPU type (for example Snapdragon). Then head over to the Qualcomm Snapdragon Wiki and check for your device's CPU and check the "CPU instruction set".
ARMv7 = arm
ARMv8 = arm64
Most likely you don't have an Intel CPU architecture (x86), otherwise it is explicitly shown in your device's stats.
I am currently using rooted Huawei Mate 9 using this guide.
Before proceeding to install Magisk, may I confirm:
1. is it possible for me to install Magisk with the current setup?
2. will I be able to do OTA update after installing Magisk?
3. Is there anything I have to take note?
Thanks in advanced for the reply.
A user in the main discussion thread noted that installation failed on his Mate 9.
jash1412 said:
I am currently using rooted Huawei Mate 9 using this guide.
Before proceeding to install Magisk, may I confirm:
1. is it possible for me to install Magisk with the current setup?
2. will I be able to do OTA update after installing Magisk?
3. Is there anything I have to take note?
Thanks in advanced for the reply.
Click to expand...
Click to collapse
Were you ever successful in getting Magisk on your Mate 9 (I have a Mate 9 Pro coming next week)
jash1412 said:
I am currently using rooted Huawei Mate 9 using this guide.
Before proceeding to install Magisk, may I confirm:
1. is it possible for me to install Magisk with the current setup?
2. will I be able to do OTA update after installing Magisk?
3. Is there anything I have to take note?
Thanks in advanced for the reply.
Click to expand...
Click to collapse
I too would like to know if you got this working. Found an article online that seems to say it's possible, but I'm dubious.
Bumping this. I tried to install Magisk via TWRP and it didn't work. Anyone have any luck?
allen099 said:
Bumping this. I tried to install Magisk via TWRP and it didn't work. Anyone have any luck?
Click to expand...
Click to collapse
What does the recovery log from the installation say?
There's been a lot of work on compatibility lately, so if there's an issue like that you might have better luck with the next release. Meanwhile it could be worth trying the unofficial build snapshots to see if it installs: https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
Didgeridoohan said:
What does the recovery log from the installation say?
There's been a lot of work on compatibility lately, so if there's an issue like that you might have better luck with the next release. Meanwhile it could be worth trying the unofficial build snapshots to see if it installs: https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
Click to expand...
Click to collapse
The installation of Magisk crashes when loop mounting /data/magisk.img. It does something like
Code:
make_ext4fs ... /data/magisk.img
losetup /dev/block/loop0 /data/magisk.img
mount -t ext4 -o loop /dev/block/loop0 /magisk
But that's not an issue that Magisk can solve.
It seems that the current TWRP implementations for the Mate 9 cannot handle loop mounts.
st_voss said:
The installation of Magisk crashes when loop mounting /data/magisk.img. It does something like
Code:
make_ext4fs ... /data/magisk.img
losetup /dev/block/loop0 /data/magisk.img
mount -t ext4 -o loop /dev/block/loop0 /magisk
But that's not an issue that Magisk can solve.
It seems that the current TWRP implementations for the Mate 9 cannot handle loop mounts.
Click to expand...
Click to collapse
I read that the setup works but the mounts fails. Stock kernel problem.
Confirm the same. Does not install the zip. i wonder if we temp flash a custom kernel, then install, and reflash will that work? or perhaps manually place files from the zip in place and set perms?
---------- Post added at 05:12 AM ---------- Previous post was at 05:11 AM ----------
what files would be needed to overcome this hurdle?
Not sure if this helps, but with the superroot script, someone mentioned adding a boot line to fix the install... or maybe it was supersu...
https://forum.xda-developers.com/mate-9/development/root-supersu-2-79-t3573155
seems the build 170416 installs, but the manager still says to install the zip.
wrecklesswun said:
Confirm the same. Does not install the zip. i wonder if we temp flash a custom kernel, then install, and reflash will that work? or perhaps manually place files from the zip in place and set perms?
---------- Post added at 05:12 AM ---------- Previous post was at 05:11 AM ----------
what files would be needed to overcome this hurdle?
Click to expand...
Click to collapse
Of course a custom kernel would help a lot. But Huawei so far hasn't released the kernel sources for its Kirin 960 devices. So currently we have no custom kernel for Mate 9 etc.
I don't think that manually placing/copying files from the zip would help.
IMO the main purpose of Magisk is to avoid any modifications of /system. To reach that goal it uses loop mounts so that certain files/binaries that normally would be placed somewhere into /system can be placed in /data or elsewhere.
Tikerz said:
I read that the setup works but the mounts fails. Stock kernel problem.
Click to expand...
Click to collapse
Some update:
Looks like with newer EMUI builds loop mounting works with the stock kernel. I'm on currently on MHA-L29C432B182.
This is the kernel version:
Code:
> adb shell uname -a
Linux localhost 4.1.18-g0ad0fb3 #1 SMP PREEMPT Tue Apr 11 12:25:26 CST 2017 aarch64
st_voss said:
Some update:
Looks like with newer EMUI builds loop mounting works with the stock kernel. I'm on currently on MHA-L29C432B182.
This is the kernel version:
Code:
> adb shell uname -a
Linux localhost 4.1.18-g0ad0fb3 #1 SMP PREEMPT Tue Apr 11 12:25:26 CST 2017 aarch64
Click to expand...
Click to collapse
Did you manage to install magisk?
Andy4Shurr said:
Did you manage to install magisk?
Click to expand...
Click to collapse
Yes, please see https://forum.xda-developers.com/showpost.php?p=72070388&postcount=692
Do not reboot with Magisk Hide activated
Just a warning when using Magisk Hide on the Mate 9!
Avoid rebooting with Hide activated. You won't be able to unlock your device. Neither with fingerprint nor with PIN.
Seems that Hide conflicts with some Trusted Execution Environment of the device.
Download the firmware for the Galaxy J7 Prime SM-G610M with product code TTT from Trinidad and Tobago. This firmware has version number PDA G610MUBU1BQI3 and CSC G610MUUB1BQI3. The operating system of this firmware is Android 7.0, with build date Fri, 18 Mar 1549 14:06:53 +0000. Security patch date is 2017-08-01, with changelist 12149057.
- Model ... SM-G610M - G610M/DS
- Model name ... Galaxy J7 Prime
- Country ... Trinidad and Tobago
- Version ... Android 7.0
- Changelist ... 12149057
- Build date ... Fri, 18 Mar 1549 14:06:53 +0000
- Security Patch Level ... 2017-08-01
- Product code ... TTT
- PDA ... G610MUBU1BQI3
- CSC ... G610MUUB1BQI3
Download Firmware ... Sammobile
https://www.sammobile.com/firmwares/galaxy-j7-prime/SM-G610M/TTT/download/G610MUBU1BQI3/192883/
Download Firmware ... SamFirm
https://mega.nz/#!1mAGhBiJ!JGbmNMCRoTZ7JPowTAIdlzHjsPePkfVB4rE5kgeKF_8
Download Firmware ... Mega
https://mega.nz/#!I7Zn1CTb!S1mRc2g64iHz0bXwCCcsQQ331qacz9Lrqk_2C51blKo
Download Firmware ... Mediafire
http://www.mediafire.com/file/wzx4xgdujuxh277/Android_7_Nougat_Stock_J7_Prime_SM-G610M-DS_%5BTTT_-_B1%5D_By_JHAM2005.rar
Odin 3.13.1 ... Mega
https://mega.nz/#!x2ozABDT!a7niSl_kW2djb37SvvYhYC9JUqqxx6fu1gL6-l_km54
Odin 3.13.1 ... Mediafire
http://www.mediafire.com/file/b31gmzgmx9hn4l8/Odin3-v3.13.1.zip
Samsung USB Driver
https://mega.nz/#!FyogVZ5I!-tiS_hscFEu1Qbg2V1rl1V_f1-IoGGQAdXZorAQPZjA
NOTE:
1.- IT IS NECESSARY TO GO TO: Settings -> Developer Options -> OEM unlocking AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
2.- KNOX will be tripped once you flashed custom binaries to your phone.
3.- Samsung Firmware System Updates will no longer work once you flashed custom binaries.
How to Install
1.- Install the Stock Firmware with Odin
2.- Install TWRP
3.- It is necessary to have the files to release the memory and the root file in the Pendrive (USB) to use them by OTG
4.-Enter the advanced recovery and install the... zip ...to unlock memory, need a OTG adapter + USB Pendrive
5.- Then Format Data ... YES ...
6.- Restart the mobile
7.- Configure the mobile to suit the user
8.- Turn off the mobile and enter the Recovery
9.- Install the root zip to use ... SuperSU or Magisk
Restart the mobile
Enjoy :fingers-crossed:
Free Internal Memory + Root + TWRP 3.2.1 ... Thanks to DarkLord1731
https://mega.nz/#!MiYFySqY!-xKp6ZCfpLmxEe9s2xXN_EWbvMMtcDJppPKxyTTdBoE
MOUNT INTERNAL STORAGE
- To mount internal storage you need to remove forced encryption by flashing this zip in TWRP
no-verity-opt-encrypt.zip
- Then you may need to format/data to boot properly.
Xposed Installer 3.1.5 + Xposed Framework 89 ... Thanks to rovo89
https://mega.nz/#!RzwxTbRB!F7kiHmdMz-6NG93rWx2p5-LEJ5FEihdA6ZDPyPgrnE8
Magisk 16.0 + Magisk Manager 5.6.3 ... Thanks to topjohnwu
https://mega.nz/#!875GgbJJ!V9cCd9vbZE-nAg4ne8MnjIGQFAAlWBRuo7P9KZekZdw
Xposed Systemless 89.2 Nougat 7 [Magisk] Thanks to topjohnwu
https://mega.nz/#!N7RgTDZQ!8pFVszDmTXwelvPzVAUYvI2jMBL_san6PhAGh-iu-j0
Added more firmware download options Stock ...
Works on Argentina??
Thanks
IgnacioAlleg said:
Works on Argentina??
Thanks
Click to expand...
Click to collapse
It works in any country, as it is an operator-free firmware, it can be installed in the M and M/DS version.
Would this work on my phone?
Thanks!!
Click to expand...
Click to collapse
billy_silva said:
Would this work on my phone?
Thanks!!
Click to expand...
Click to collapse
It works in any country, as it is an operator-free firmware, it can be installed in the M and M/DS version
Downloaded this file and its corrupt file. Failed extracting on both phone and pc
---------- Post added at 12:20 PM ---------- Previous post was at 12:20 PM ----------
Its corrupt
https://mega.nz/#!I7Zn1CTb!S1mRc2g64iHz0bXwCCcsQQ331qacz9Lrqk_2C51blKo
I am not having success installing Magisk v25.2 on my Samsung Galaxy Tab S MT-800. This used to run Android 6.0 OS. I updated the OS to Android 7.0 Nougat. I have installed Magisk and followed the instructions to create a patched boot.img file. I have copied the patched file on my PC. I have ODIN on my PC and TWRP on Tab S.
i can get ADB to recognize my device but fastboot simply returns <waiting for device> on my PC. Am assuming fastboot does not work with Samsung TAB S running Android 7 Nougat.
I tried flashing the patched boot.img via TWRP with no success.
Tried ODIN with no success :
AP: boot.img.tar (patched boot file)
ODIN ran successfully.
Reboot and open Magisk i still see the following:
Magisk
Installed N/A
Zygisk: No
Ramdisk Yes
App
Latest 25.2 (25200) (33)
Installed 25.2
Package com.topjohnwu.magisk
looking for guidance. I do not see the Superuser or any other capability available to hide root for apps.
Device: Samsung Galaxy A23
Android version: 12
Magisk version name: 26.1
Magisk version code: 26100
Hello everyone, I am a new member of this forum and I have a problem with Magisk. I want to downgrade the application from version 26.1 to version 24.2, I specify an external source of updates, install everything from the Magisk main screen, and then a system window of Android appears asking for confirmation to update. I click on it, but nothing happens. Do you have any ideas on how to fix this or downgrade Magisk differently without resetting data?
Just download the Magisk 24.2 zip file or any version of zip file you want to downgrade. Then goto Magisk module install screen. And select the downloaded zip and install and then reboot. Magisk is effectively downgraded. Keep in mind that the version you install must compatible with your device and also uninstall all installed modules before downgrade.