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
Related
Hello,
I'm having problems installing custom recovery (both CWM and TWRP). I've already been installing custom recoveries before and then I decided to go fully stock. So, now I've been fully stock for quite a while and today I tried installing custom recovery. In Odin it says "Pass" but no custom recovery installed. I've disabled Reactivation lock and enabled USB debugging. I really don't know what's wrong.
If anybody knows what's the problem, I would really appreciate the help!!!
EDIT: The problem was in official TouchWiz build version. That version (in my case) couldn't been rooted and didn't allow another recovery being installed. I downgraded to BNL9 version, before I was on BOA3 version. You can easily find earlier version on sammobile.com
If you're rooted, use TWRP manager from Play store, few people have this issue, myself included
I just said I went fully stock. So, no. I`m not rooted. But thanks for the advice. Might need it in the future!
AlwaysAndroid said:
Hello,
I'm having problems installing custom recovery (both CWM and TWRP). I've already been installing custom recoveries before and then I decided to go fully stock. So, now I've been fully stock for quite a while and today I tried installing custom recovery. In Odin it says "Pass" but no custom recovery installed. I've disabled Reactivation lock and enabled USB debugging. I really don't know what's wrong.
If anybody knows what's the problem, I would really appreciate the help!!!
Click to expand...
Click to collapse
This happened to me a while back when I had a Galaxy S3, i found a solution, unfortunately, you must be rooted to do this solution.
In this post http://forum.xda-developers.com/showpost.php?p=27597756&postcount=1 you'll find a section that states "Stock Recovery being reflashed after a reboot?" and there is the one solution that worked for me.
If you manage to find any of this files through a file explorer, it means that your ROM is flashing stock recovery on every boot. So you would need root access to rename them.
Thank you very much. I will certainly dig into this and search for it.
U need Root
You'll need root for that project.
I had the same problem.
I took CF-Autoroot and flashed it. Right afterwards I booted again manual into stock recovery mode and wiped cash and dalvik cash. After that -without reboot-
removed the battery for a minute. I reinserted the battery and I booted into download mode and flashed recovery-cwmtouch-6.0.4.7-kgsm.tar.
Finally, to stay off of KNOX, which always is going to bother, you should install an app, called: Knox-Disabler. It doesnt clean the phone from Knox, but it keeps Knox inactive.- :good:
Good luck
Hello everyone,
this is my first time posting on the XDA forums after doing a lot of research, so please bear with me if I've missed something painfully obvious. My issue I'm looking to get help with is my AT&T GS4 i337.
Here goes the problem, initially I had the FNJ4 (4.4.4) baseband and build number. I was really excited to try custom ROM's like CM11 or 12. I ended up reflashing the phone via odin with baseband and build number FNB1 with a rootable kernel (titled I337UCUFNB1_TWRootable_Full_Odin.tar 4.4.2). This successfully worked as did using TowelRoot (v3) to root. Since the reflash, I cannot seem to load CWM or TWRP much less access even the factory recovery mode on startup (it goes to the "unable to boot into normal mode" screen). And today, I was messing around with the "Disable Service" app and accidentally unchecked the box to turn off the service for SuperSu (even though I re-checked the box, I still lost root). And now I cant even run the tr.apk file to successfully root again - what I mean is the tr.apk installs and says I have root, but then when I check the root with root checker basic it says the phone has not been successfully rooted.
On a side note, I did find a flashable recovery .zip version of SuperSu (2.46) app to get the app back except now, shortly after startup, the app service turns itself off and I loose SuperSu again. I really don't know what to do.
I have tried messing with Terminal Emulator, Flashify, TWRP manager, ROM manager, ODIN and Titanium Backup to try and get SuperSU (to get root) and the factory recovery mode back (I also tried using Safetrap to install CWM and TWRP without success). The only program I haven't messed with is flashing with Heimdall. Oh yeah, I also tried using SELinux Mode Changer (changed mode to permissive) without any success.
I know this is getting super long, but my initial intent was just to be able to run CM11 or CM12 and customize the phone the way I want it. Any help would be greatly appreciated as I'm not sure how to prioritize these problems.
The bootloader of the AT&T S4 SGH-I337 is locked. This means you can not install a custom kernel or a custom recovery, and thus you are limited to touchwiz based firmware. You can have custom firmware based on touchwiz, however, you will not be able to have CyanogenMod or any other aosp based firmware.
I would suggest that you repeat the process: flash stock NB1, the rootable kernel, root with towelroot, and install SuperSU as you did before, and then depending on where you want to end up, install safestrap or upgrade to Lollipop with the keeproot method. Look in the general forum for threads by guut13 and muniz_ri.
creepyncrawly said:
The bootloader of the AT&T S4 SGH-I337 is locked. This means you can not install a custom kernel or a custom recovery, and thus you are limited to touchwiz based firmware. You can have custom firmware based on touchwiz, however, you will not be able to have CyanogenMod or any other aosp based firmware.
I would suggest that you repeat the process: flash stock NB1, the rootable kernel, root with towelroot, and install SuperSU as you did before, and then depending on where you want to end up, install safestrap or upgrade to Lollipop with the keeproot method. Look in the general forum for threads by guut13 and muniz_ri.
Click to expand...
Click to collapse
Got it. Thank you very much for responding so quickly! I'm new to this whole thing (the world of installing custom ROM's and the like) and I'm finding that so many details (Root/firmware/baseband/kernel/ROM compatibility) are so much more dependent on carrier and model number than I ever imagined. Thank you for pointing me in the right direction by helping me understand my limitations. Now its time to do a little more research.....
First off thanks to the community for actively helping strangers on the internet. We appreciate it.
Now, I rooted my phone while on 5.0.1 using chainfire's root technique without issue. Then I flashed with Odin Sammobile's 5.1.1 update successfully. However in doing so I lost root.
When I attempt to re-root using the same technique that worked before it goes into a bootloop. So I re-flashed the 5.1.1 update and then flashed TWRP. I granted TWRP the right to install root and the same problem occured. It just continues to loop at the samsung logo.
Does anyone have any ideas on what I'm doing wrong?
Thanks in advance.
Just search the forum, there are many thread about the solution here
I've tried searching the forums without any luck. If anyone could link a thread with an answer it would be great. Unfortunately I have about 20 minutes a day to try to get this resolved and I'm on day 4.
Thanks
Chain fire's root file which is made for android 5.0 won't work on android 5.1. To root android 5.1 you will need to flash a root file made for your device of that version. Also note that you must flash only those files that are made for your phone's model number. For example, exynos root file may or may not work on snapdragon.
Hey people
I have a Samsung sm-j320f 2016, OS android 5.1.1 and im trying to root it.
I flashed trwp recovery mode uaing odin and i tried several times rooting the phone with superSU or magisk. Cut to the chase, i rooted my phone...after hours it powered itself off and kept bootlooping
I flashed the firmware using oding and its working again now
I tried again rooting it with magisk...same happened but this time o restored it.
I found out it was because of stock rom and touchwiz ui that causes bootlooping
I really want to root my phone and i dont know how should i prevent bootloop
Can you help me?
AminNadery said:
Hey people
I have a Samsung sm-j320f 2016, OS android 5.1.1 and im trying to root it.
I flashed trwp recovery mode uaing odin and i tried several times rooting the phone with superSU or magisk. Cut to the chase, i rooted my phone...after hours it powered itself off and kept bootlooping
I flashed the firmware using oding and its working again now
I tried again rooting it with magisk...same happened but this time o restored it.
I found out it was because of stock rom and touchwiz ui that causes bootlooping
I really want to root my phone and i dont know how should i prevent bootloop
Can you help me?
Click to expand...
Click to collapse
first thing, go back to the stock of your device, activate OEM unlock, download the latest version of twrp and install by DOWNLOAD mode, rom stock only supports SuperSu, if you want to use magisk, just use a custom rom (I recommend Viper )
G0K4LT3 said:
first thing, go back to the stock of your device, activate OEM unlock, download the latest version of twrp and install by DOWNLOAD mode, rom stock only supports SuperSu, if you want to use magisk, just use a custom rom (I recommend Viper )
Click to expand...
Click to collapse
I realizd i shouldn't use 2 root apps.
Im using magisk now
Without any problems
Thanks tho
Hey! haven't seen anyone in this section for a while....
Why I am making this thread
So lately, I was looking through my old phones only only to find my old dusty Samsung Galaxy Note 2 lying around. It had already been rooted with kingroot... Needless to say, it's a spyware and my phone was drastically slow probably because of it.
Long story short, kingroot messed up all the files. Trying to install a working version of SuperSU gave me a headache. Finally, Magisk(v22.1) was supposed to work on the phone as it stated that it's the last version to support v4.4.2 but it doesn't actually work. It keeps on showing N/A whenever I launch it and a million different permutations that I had done in the process of rooting it using Magisk never worked.
This took me days, just jumping from one rabbit hole into another, finding old dead links which really made me so frustrated that at some point I wanted to throw the whole phone away.
That's why I'm creating this thread, so that I save the hassle for myself in the future and hopefully anyone who comes across this.
Updated rooting guide
This guide worked for my GT N7100 android version 4.4.2. It'd also probably work on other devices on other old phones which have an android version less than 5
Just make sure to backup everything before trying it.
Step 1. Flashing TWRP
Download the files from the following link
[TWRP]N7100 TWRP v3.3.1-0 ODIN FLASHABLE [23/05/2019]
Ok there we go this recovery is the latest 3.2.3-2 for t03g only don't flash this on t0lte(N7105). UPDATE: 12/04/2019: official support: https://dl.twrp.me/t03g TWRP 3.2.3-2 for N7100. Bugs: Format as F2FS doesn't work because the option isn't...
forum.xda-developers.com
Download ODIN
https://samfw.com/Odin/Odin3_v3.13.3.zip
Boot the phone into download mode(VOLUME DOWN + POWER KEY + HOME KEY)
Open ODIN and in BL choose the file that you've downloaded whose extension is or is similar to ".tar"
Click start
Step 2. Downloading and flashing Magisk
In here, you need to download a very specific version of Magisk, because anything above this version won't work.
NOTE: If you have installed any later versions of Magisk then make sure to uninstall them first, you can find out how to uninstall it from here(https://topjohnwu.github.io/Magisk/install.html#uninstallation)
Download THESE VERY SPECIFIC VERSIONS of Magisk and Magisk Manager from here
https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-v21.4.zip
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Get into TWRP recovery mode and then flash Magisk-v21.4.zip
Reboot back into the device and install MagiskManager-v8.0.7.apk
That's the end of it, your device is rooted now
HOWEVER, once MagiskManager has been installed, it would say that there's an update available(a newer version) available that you could upgrade to.
NEVER EVER UPDATE!! Updating your Magisk version to ANYTHING above v21.4 will cause it not to detect root. This is a bug with Magisk and it would probably never get fixed because support for android <5 had been discontinued a long time ago.
In case you ever do accidentally update Magisk, you will have to uninstall the Magisk app and then install MagiskManager-v8.0.7.apk again.
To uninstall and unroot your device, download this file and flash it with TWRP
https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-uninstaller-20210117.zip
Where I got the links above from
https://github.com/topjohnwu/Magisk/releases/download/v21.4/
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/
Magisk v22.1
This release is focused on fixing regressions and bugs. Check the v22.0 release notes if coming from older releases.
Note: Magisk v22 is the last major version to support Jellybean and Kitkat. Magisk v23 will only support Android 5.0 and higher.
ze7zez said:
Magisk v22.1
This release is focused on fixing regressions and bugs. Check the v22.0 release notes if coming from older releases.
Note: Magisk v22 is the last major version to support Jellybean and Kitkat. Magisk v23 will only support Android 5.0 and higher.
Click to expand...
Click to collapse
Nope doesn't work as it wont be able to detect root at all, this is what had initially caused my headache to begin with
The last version of magisk that actually works on GT N7100 and probably any other old phone is the one that I linked in the thread
EDllT said:
(...)
Get into TWRP recovery mode and flash Magisk-v21.4.zip
Reboot back into the device and install MagiskManager-v8.0.7.apk
(...)
Click to expand...
Click to collapse
Thank you for the information.
I checked on Samsung Galaxy S4 Mini LTE i9195 (stock KK 4.4.2) and it works indeed at most version 21.4.
It is not possible to install MagiskManager-v8.0.7.apk because it is installed together with Magisk-v21.4.zip.