Related
Just wondering if anyone was successful in installing xposed framework on the metro version of this phone and making it active? I have looked far and wide and after countless soft bricks and restores I admit defeat. As stated in the title my phone is the metro version of the grand prime android 5.1.1. I am running the trap kernel by Shinyside on this phone along with supersu.
I have followed many tutorials on several different versions of this phone and each one has ended in soft bricking the phone. When you search xposed SM-G530T1 it returns nothing but topics about stock firmware and xposed on the 530H. The only version that didn't soft brick is xposedinstaller 3.0 alpha, yet even after granting root privileges and rebooting I am still greeted with The latest version of Xposed is currently not active.
Edit: Solved using Wanams fix for samsung Link below for his steps to fix
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
Help me Please.
I have been going through this same problem but the other forum doesn't help as much I have the same phone a Samsung Galaxy Grand Prime SM-G530T1 rinning lollipop 5.1.1 the metro version. Um my rom is custom gwiz I think with a trap kernel l.. I had to install that through flash fire app. Because I can't seem to get CWM or TWRP working on my phone... can you let me know exactly what you did starting with rooting your phone to installing xposed ?:crying: :crying: :crying:
dinosrequiem said:
I have been going through this same problem but the other forum doesn't help as much I have the same phone a Samsung Galaxy Grand Prime SM-G530T1 rinning lollipop 5.1.1 the metro version. Um my rom is custom gwiz I think with a trap kernel l.. I had to install that through flash fire app. Because I can't seem to get CWM or TWRP working on my phone... can you let me know exactly what you did starting with rooting your phone to installing xposed ?:crying: :crying: :crying:
Click to expand...
Click to collapse
Well first I flashed the stock rom with odin waited for the phone to reboot then I set it up just like you would a new phone. Once it was completed I shut it down and put it back into download mode and flashed the trap kernel located here:
http://forum.xda-developers.com/grand-prime/development/kernel-root-root-sm-g530t-5-1-1-t3203476
After that was done waited for the phone to reboot then flashed twrp from the g530h with odin . A forum search of TWRP-SMG530H will lead you to the file.
Once I gained root and flashed the recovery I needed to find out what type of cpu this phone was running so I installed droid info from the playstore. The system info shown ARMv7 so I went to the link in my original post and downloaded XposedInstaller_3.0_alpha4.apk but did not install it just yet. First I flashed the framework xposed-v85.1-sdk22-arm-custom-build-by-wanam-20160 with twrp. Once it was done I cleared cache and rebooted. It took the phone about seven mins to boot.
Then installed the apk gave it root permissions rebooted and thats it. Also Note that the twrp version used cant make backups because it was not intended for this phone but it will flash whats needed. After many, I and I mean many failed attempts this was the solution to my problem.
Ok
So you don't have a Custom ROM or is trap Kernel a custom rom... I'm still kind of new to this but I will try
Thank You
Thanks it's now working
Hi Everyone, l have a question about this Magisk Mod and its directed to s7 & s7 edge users. If anyone is using this Mod, may you please tell us how you got it to work, coz l have tried and failed many times. Your help would be kindly appreciated..
King Addies
Root and install xposed.
I have used a stock rom, as it says on the magisk thread and followed all the instuctions and still failed.. lm not really botherd about using the mod anymore, but l made this thread so all the other people who are in my situation can get help or a tutorial on how to install it on s7 & s7 edge. Coz l could not really get much help from the official thread.
King Addies
I'm using sac23's custom Note 7 port ROM. After installing his ROM, I went to SuperSU, clicked the option for cleanup to install different Super User app. Reboot phone. Then I booted into TWRP, flashed Magisk, then flashed Phh's Super User. Reboot system. Then install Magisk Manager or Auto Magisk app. Activate Auto Magisk under accessibility settings. Works like a dream.
Mr. Orange 645 said:
I'm using sac23's custom Note 7 port ROM. After installing his ROM, I went to SuperSU, clicked the option for cleanup to install different Super User app. Reboot phone. Then I booted into TWRP, flashed Magisk, then flashed Phh's Super User. Reboot system. Then install Magisk Manager or Auto Magisk app. Activate Auto Magisk under accessibility settings. Works like a dream.
Click to expand...
Click to collapse
Thanx for your input on this issue mate, hope the info you have provided helps all those that want to use this Mod on their s7 or s7 edge phones..
King Addies
One more step, sorry. You have to also install Phh's SU app from the Google Play store.
Besides Sac23's Note 7 Port Rom, has anyone else tested or used this Mod on any other s7 or s7 edge Rom..
King Addies
Magisk works fine with any ROM. You just need to use a custom kernel or:
Obtain root using CF - Auto Root
Remove root via SuperSU app
Click No when asked about restoring stock boot.img
Go through the normal Magisk/Phh Superuser steps to install
Only thing I've noticed is that banking apps can still detect that I am rooted. Not sure if this is because I did SuperSU/modified boot.img method. I may try flashing back to stock via ODIN then flashing a custom kernel and install Magisk that way and see.
I've already tried all this. Do you think it's because i've got encrypted device?!
I've tried so many combinations as well... In the end, i have to always restore the stock firmware, run CF-autoroot and xposed normally.
Any ideas why? anyone?!
Galactus said:
Magisk works fine with any ROM. You just need to use a custom kernel or:
Obtain root using CF - Auto Root
Remove root via SuperSU app
Click No when asked about restoring stock boot.img
Go through the normal Magisk/Phh Superuser steps to install
Only thing I've noticed is that banking apps can still detect that I am rooted. Not sure if this is because I did SuperSU/modified boot.img method. I may try flashing back to stock via ODIN then flashing a custom kernel and install Magisk that way and see.
Click to expand...
Click to collapse
kevinwu128 said:
I've already tried all this. Do you think it's because i've got encrypted device?!
I've tried so many combinations as well... In the end, i have to always restore the stock firmware, run CF-autoroot and xposed normally.
Any ideas why? anyone?!
Click to expand...
Click to collapse
Encryption isn't the reason, I'm encrypted too.. There isn't really a benefit to it right now anyways. SafetyNet has been updated, you can't pass it with Xposed PERIOD until another bypass is done by the dev.
The key like someone said on a different thread, is to run CF Auto Root, then unroot with SuperSU. Follow the steps from there and you should be good to go but as I've already said, a lot has changed since then. Su-hide isn't working half of the time etc. Better off waiting for them to sort out all the issues first.
Galactus said:
Encryption isn't the reason, I'm encrypted too.. There isn't really a benefit to it right now anyways. SafetyNet has been updated, you can't pass it with Xposed PERIOD until another bypass is done by the dev.
The key like someone said on a different thread, is to run CF Auto Root, then unroot with SuperSU. Follow the steps from there and you should be good to go but as I've already said, a lot has changed since then. Su-hide isn't working half of the time etc. Better off waiting for them to sort out all the issues first.
Click to expand...
Click to collapse
Maybe I did have it working then, the only thing I tested it with Pokemon go and it didn't work.. so I just assumed it wasn't working, so I reverted all changes. I spent way too much time than I had hoped
Cheers Buddy
Hi there, I install superman rom with magisk already installed but cant find the cheekbox to unroot on Magisk Manager.
Still cant use Snapchat & pokemon go on my s7.
Anyone can help ?
Regards.
Devilover said:
Hi there, I install superman rom with magisk already installed but cant find the cheekbox to unroot on Magisk Manager.
Still cant use Snapchat & pokemon go on my s7.
Anyone can help ?
Regards.
Click to expand...
Click to collapse
Magisk is pointless right now. Simply having an unlocked bootloader causes SafetyNet to fail. The latest version of magisk also removed the checkbox to turn root on and off. To use Snapchat YOU MUST login before any modifications. Make a titanium backup of Snapchat logged in, then you can restore it whenever you want.
silverrum said:
Besides Sac23's Note 7 Port Rom, has anyone else tested or used this Mod on any other s7 or s7 edge Rom..
King Addies
Click to expand...
Click to collapse
Im using Darklord S7e PeK port Latest Kernel and successful MagiskSU install on my Galaxy Note 3 N9005
I flashed it on TWRP 2.0.8.0
When rebooting Do Not Check Install SU (Chainfire SU) if you want Magisk
In Regards to Snapchat i used SC staright after Magisk install from twrp and it logged on also SC allows rooted Lineage OS 7.1.1 :/
PoTBrain• said:
Im using Darklord S7e PeK port Latest Kernel and successful MagiskSU install on my Galaxy Note 3 N9005
I flashed it on TWRP 2.0.8.0
When rebooting Do Not Check Install SU (Chainfire SU) if you want Magisk
In Regards to Snapchat i used SC staright after Magisk install from twrp and it logged on also SC allows rooted Lineage OS 7.1.1 :/
Click to expand...
Click to collapse
What part of S7/S7Edge do you fail to understand?
Or, boot into TWRP, format data to unencrypt then flash latest magisk and reboot. Once booted, open magisk manager hit menu button and open settings, check magisk hide. Exit settings, open menu and open magisk hide, there you can check any app you want to hide from root. done.
Hello!
Now after Google seems to be tweaking the hell out of its Safetynet (bootloader check and whatever) I was wondered where this will lead us to. Especially since our devices, at least the Exynos ones come with an unlocked bootloader..
I tried a dozen of combinations from the above named tools without any success, as my mobile banking app seem to rely on that crap now too since it's latest update (I can live without Pokemon go ) it got me all little worried.
What are your experiences, how did you lock out Safetynet, do you guys ignore it? So many questions regarding that topic. Feel free to leave any comment.. :good:
From what I understand all s7 come with bootloader locked by default but on exynos variant, it's unlockable with a "OEM Unlock" toggle in developer option. So normal user who don't root or modified the phone don't affect by new safetynet.
So if you don't need root, you can turn off OEM Unlock and flash back stock rom. But if you need root, there's no known method for now to bypass safetynet.
Sent from my SM-G935F using Tapatalk
I haven't been able to log in PokemonGO with my S7 and on my OnePlus One for the last 24 hours
Samsung Galaxy S7
TWRP 3.0.2-3
Superman ROM v1.14 (SELinux status [kernel]: Permissive)
Supersu v2.78-sr1 systemless
topjohnwu's Xposed v86.2 systemless
Suhide v0.55
06suhide
RootSwitch 1.2.4
Click to expand...
Click to collapse
EDIT: It now works with my OnePlus One (removed the 06suhide fix and ticked the "Stop all SU deamons" option in RootSwitch), but stills doesn't work with my S7
OnePlus One
TWRP 3.0.2.0
Official ROM Cyanogen OS v13.1.2 Android 6.0.1
SELinux Status: Enforcing
Supersu v2.78-sr1 systemless
Suhide v0.55
06suhide
+Added RootSwitch 1.2.4
Click to expand...
Click to collapse
I've heard they can now detect and block Custom Recovery. I don't think it's true.
I tried that Again now, using Hydra Kernel 1.7.1 without that modified Boot stuff. Removed SuperSu and Xposed, flashed the new Root Free Kernel and safetynet i's Not Flagged. The Main Problem for me (and many others) ist, that the Phone wont Boot after installing SuHide 0.5x! I've used the Not Flagged System as testbase, TWRP doesnt Alter it in any Way, but once i install either Magisk v8 or SuperSu 1.78R1 it gets Flagged Again.. So without SuHide, which doesnt Boot the Phone at All its worthless..
Please, can someone help me to replace magisk without any bootloop, I just don't like this magisk thing and prefer good old supersu. Please, nearly all the nought rom for s4 has magisk and I really want su. I tried two to just to flash the zip, and i had to factory reset twice. Thank you . :crying::crying:
Uninstall Magisk, flash SuperSU zip. Done.
Pwnycorn said:
Uninstall Magisk, flash SuperSU zip. Done.
Click to expand...
Click to collapse
Thank you for the reply but how do i uninstall magisk
Nearly all the Android 7.x ROMs are using Magisk because of its ability to bypass SafetyNet for use with banking apps as well as Pokémon Go. Plus, SuperSU just recently had a botched rollout in that some devices bootlooped when it was installed, some devices lost root completely, and some were unable to update the hosts file using AdAway. Couple that with the new owners of SuperSU trying to slip analytics items into the app, not to mention excessive permissions for the bug reporting feature and you have a mess. So, while I have absolutely no idea what issues you're having with Magisk, you're doing far worse in my opinion going back to SuperSU and should instead use phh Superuser. It's as simple to use as SuperSU while not being saddled with SuperSU's excessive permissions and device problems.
With that said, if you really want to go back to SuperSU, dirty flash your custom ROM if using one (uninstalls Magisk), then install SuperSU and reboot.
Horridhenry said:
Thank you for the reply but how do i uninstall magisk
Click to expand...
Click to collapse
Have you looked in the Magisk thread? I'm pretty sure they have some uninstall instructions there.
Strephon Alkhalikoi said:
Nearly all the Android 7.x ROMs are using Magisk because of its ability to bypass SafetyNet for use with banking apps as well as Pokémon Go. Plus, SuperSU just recently had a botched rollout in that some devices bootlooped when it was installed, some devices lost root completely, and some were unable to update the hosts file using AdAway. Couple that with the new owners of SuperSU trying to slip analytics items into the app, not to mention excessive permissions for the bug reporting feature and you have a mess. So, while I have absolutely no idea what issues you're having with Magisk, you're doing far worse in my opinion going back to SuperSU and should instead use phh Superuser. It's as simple to use as SuperSU while not being saddled with SuperSU's excessive permissions and device problems.
With that said, if you really want to go back to SuperSU, dirty flash your custom ROM if using one (uninstalls Magisk), then install SuperSU and reboot.
Click to expand...
Click to collapse
If his ROM comes with Magisk "out-of-the-box", then dirty flashing won't do anything.
@Pwnycorn: LOL...I didn't think that one through, did I?
In any case, the bulk of my post was reasons why NOT to use SuperSU. Personally, there's nothing SuperSU can do that Magisk can't, and I don't miss SuperSU at all. In fact, I ditched SuperSU on MachineX ROM and successfully replaced it with Magisk. I replaced MicroG in that ROM as well, but I digress.
Strephon Alkhalikoi said:
@Pwnycorn: LOL...I didn't think that one through, did I?
In any case, the bulk of my post was reasons why NOT to use SuperSU. Personally, there's nothing SuperSU can do that Magisk can't, and I don't miss SuperSU at all. In fact, I ditched SuperSU on MachineX ROM and successfully replaced it with Magisk. I replaced MicroG in that ROM as well, but I digress.
Click to expand...
Click to collapse
fun fact!
galaxy S2 doesn't support Magisk(outdated boot image format),...i feel sorry for myself right now..LOL
I just got my unlocked G5 Plus (XT1687) today and I've unlocked the bootloader and installed TWRP and SuperSU.
However, SuperSU seems to be randomly losing root access. It works for a little while, but then I'll get an error in SuperSU about root undetected and I have to reboot back into TWRP and reflash SuperSU. This has happened 3 times so far today.
Has anyone seen this issue in the stock rom? Is there some security process stealthily running in the background that deletes the su binary on a regular basis? I'm running build number NPN25.137-33.
Edit: SuperSU is running in systemless mode
I rooted mine using the Toolkit here yesterday and that afternoon it acted like i lost root. Root checker would say i didn't have root and just constantly flash that it was trying to get permission. I restarted it and it's been fine ever since.
I tried rebooting and it restores root temporarily, but I'm still losing it constantly (no set time interval, but I've seen it lost within a few minutes of a restart). Getting really annoying.
Would flashing one of the modified stock kernels potentially help this?
Hi,
I've the same problem. XT1685
Already done:
- reflash stock
- reflash updated stock
- reflash SuperSu 2.82 SR3 and SR4
Ever the same, after some (short) time the root is lost.
Unrooted from SuperSu app and installed Magisk 14.0: loses root after some moments!
Edit: after some reboots now its working. The root is maintained from 2 days. So Magisk 14.0 works.
Hi.
Here another confirmation. My XT1687 loses root rights once in a while. I’d say it’s about every 3rd day or so.. Simple reboot brings root rights back.
Config:
Build: NPN25.137-83
Kernel: 3.18.31-ElementalX
Root: Magigk 14.0
EDIT: When checking Magisk App I found out that Magisk crashed each time I started Superuser. So, I deinstalled Magisk and re-installed again. No problem ever since.
Always remember to un-optimize Magisk- (or SuperU-) App in battery options! "Boeffla-Doze-Control" also helps to avoid apps from falling asleep.
On StokROM + SuperSU 2.82SR5, I also experienced the same situation.
Running the following command no longer causes problems.
Code:
ln -s /su/bin/su /system/bin/su
Hello there.
I actually rooted my Moto G5 Plus according to this instructions. I flashed TWRP 3.2.1.0 and the last stabel SuperSU.
I also uninstalled SuperSU over "apps" on Stock Rom and tried to flash Magisk, but this causes in an error while flashing (It says something about "Error 1" and about the path, where the magisk.zip is, for further information I would try to flash again and tell you the whole error).
The latest thing I tried was running the command from highwaystar2699 over the terminal from TWRP, but still I loose root randomly.
Can anybody help? =(
Thanks in advance
FlatD
No root losses anymore
Just_a_fan said:
Hello there.
I actually rooted my Moto G5 Plus according to this instructions. I flashed TWRP 3.2.1.0 and the last stabel SuperSU.
I also uninstalled SuperSU over "apps" on Stock Rom and tried to flash Magisk, but this causes in an error while flashing (It says something about "Error 1" and about the path, where the magisk.zip is, for further information I would try to flash again and tell you the whole error).
The latest thing I tried was running the command from highwaystar2699 over the terminal from TWRP, but still I loose root randomly.
Can anybody help? =(
Thanks in advance
FlatD
Click to expand...
Click to collapse
Well, I can say, that after some updates of Magisk I don't experience the problem anymore. Neither me nor a friend who has the G5 (not Plus) have ever lost our root since being on Magisk Version 16.0
Maybe you should give Magisk a try...
G5 Plus Mate said:
Well, I can say, that after some updates of Magisk I don't experience the problem anymore. Neither me nor a friend who has the G5 (not Plus) have ever lost our root since being on Magisk Version 16.0
Maybe you should give Magisk a try...
Click to expand...
Click to collapse
Like I said, installing Magisk returns an error.
Nevertheless, after I ran the command from @highwaystar2699 and canceled the battery-optimization of SuperSU I've got still root after already 5 days of using the phone.
So, thanks for your help, for now =)
I have no ideas that you can solve your problem ...
What I got interested in your post(#8) is "I also uninstalled SuperSU over apps on Stock Rom".
If there is no mistake in my memory, SuperSU have an "unroot" menu, which should be used to uninstall SuperSU.
Did you uninstall by using "unroot" menu?
In any case, I am not sure how to recover the state of your g5plus.
I will not be able to help you. sorry.
highwaystar2699 said:
On StokROM + SuperSU 2.82SR5, I also experienced the same situation.
Running the following command no longer causes problems.
Code:
ln -s /su/bin/su /system/bin/su
Click to expand...
Click to collapse
How and where to run this code? Fastboot or adb terminal?
sudiptoc19 said:
How and where to run this code? Fastboot or adb terminal?
Click to expand...
Click to collapse
Just boot into TWRP and open the terminal (you can find it under "advanced" or "tools", not completely sure right now) and run that command. Maybe you should check where the mentioned su-folder is located right now on your phone, 'cause in my case it was at a different location.
@highwaystar2699: Yeah, afterwards I also realized that unroot-option
So maybe I have to unroot with that option and retry to install magisk. I will try that maybe, if I should loose root again. Or when the next update comes. (I'm a little afraid about that. Sounds difficult to OTA-update after rooting your G5 Plus...)
Either way: Thanks for your help! If I try something, I will report about it here
Super SU working for G5 plus. I don't think so. It has some problems. Bootloops are frequent.
Sooooo, hello again all! @highwaystar2699: I lost root again after one hour when I had to reboot the phone so I just thought about: "Why don't give it a try now?"
So I flashed the superSU again in TWRP to get root, startet the SuperSU app and choose "Unroot". I was asked if I want to unroot because of an OTA update, which I answered with "no". The app closed and root was gone.
I rebooted into recovery and tried to install the magisk 16.0 zip aaaaaaannnnd...
...got Error 1 again.
At the point "Unmounting partitions", TWRP says
"Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v16.0.zip'"
Now I'm back to superSU again. Damn, I don't know whats wrong here =(
Short edit for @Yeshu_bablu: Yes, after installing superSU, you've got 2 to 3 bootloops. But only the first time. After it's installed, the phone boots normal.
So, according to you... Which is better? SuperSU or Magisk?
SuperSU is obsolete, twrp you need latest version 3.2.1.0 or higher number if updated.
Once twrp installed you can install the rom of your choice with or without gapps package of your choice.
Then you can install magisk 16.3 for root and modules if wanted.
Yeshu_bablu said:
So, according to you... Which is better? SuperSU or TWRP?
Click to expand...
Click to collapse
SuperSu is root, TWRP is recovery, 2 different things.
[email protected] said:
SuperSu is root, TWRP is recovery, 2 different things.
Click to expand...
Click to collapse
I'm sorry, SuperSu or Magisk?
Short update and big thanks to @highwaystar2699 and @Wolfcity.
After I completely lost root with SuperSU, I tried to install Magisk but failed everytime with already known Error 1.
But finally, after I got a stock boot.img and flashed it and instantly (!) installed Magisk after flashing the boot.img, the phone startet normal and now I've got root without problems.
FIY: When I only flash the boot.img and don't root it in TWRP, the phone keeps bootlooping.
So, to give @Yeshu_bablu an answer: Magisk is better. SuperSu only make problems with Moto G5 Plus. Magisk works like a charm.