Database Users

[HELP] Having problem installing custom recovery

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

Xposed framework SM-G530T1?

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

Doing a system-less root on s4 using magisk possible?

alright im thinking of doing system-less root with xposed using magisk (yes im a pokemon goer thats ticked off from its new update) just wanting to know what would be the best way to go about this. If it is possible. currently im running GoldenEYE rom android 5.0.1 dont have fastboot so i already know i have alot of work in Odin to do. would love to have CM12.1 running with a systemless root but last time i tried to even get CM12.1 loaded it never worked.
So anyidea if this is possible or not. (yes i do have stock roms at the ready from when i put on my current rom along with root methods)

You don't have to do anything in Odin.
All you need is TWRP.
Then follow the Magisk instructions.
Unroot, uninstall Xposed (if present), flash Magisk zip, flash phh root zip, download phh superuser app and Magisk manager app.

well that sucked. now have the dreaded unauthorized soft ware. found a way around it to get phone booted. going into download mode then cancel out restarting phone from there.

So I tried this exact thing two days ago because I have an S4 with the Goldeneye rom installed, and unfortunately got these results
I opened up superSU and did a full unroot, after
I deleted the xposed that was installed (v86 by dlc) using the uninstaller through TWRP.
Next I flashed magisk v6 zip along with the phh superuser zip, and ended up in a bootloop..
The phone wouldnt pass the boot animation, so i uninstalled magisk, and reflashed superSU
On my end its not working, mate.

Mrcastle25 said:
So I tried this exact thing two days ago because I have an S4 with the Goldeneye rom installed, and unfortunately got these results
I opened up superSU and did a full unroot, after
I deleted the xposed that was installed (v86 by dlc) using the uninstaller through TWRP.
Next I flashed magisk v6 zip along with the phh superuser zip, and ended up in a bootloop..
The phone wouldnt pass the boot animation, so i uninstalled magisk, and reflashed superSU
On my end its not working, mate.
Click to expand...
Click to collapse
As far as I know, systemless stuff works only on Android 6 and above.
Goldeneye is a TouchWiz ROM, therefor it's android 5.

Magisk works on Touchwiz 5.0
Magisk works on android 5.0 touchwiz. Im using lenny bard stock HPG1 rom and PoGo works perfectly

Sure you can do it. i have gt-i9500 variant with 5.1.1 port tw android. magisk work when i want to play pokemon go. the only problem i have now is the systemless xposed not working as expected.

I am under the impression I am not able to get TWRP on mine because its the later version with locked bootloader.. what options are there.. Currently Download Graded to 4.4.4 to use towel root and installed Flashfire so i can install Safestrap
Really want to use Magisk

Dragnous said:
I am under the impression I am not able to get TWRP on mine because its the later version with locked bootloader.. what options are there.. Currently Download Graded to 4.4.4 to use towel root and installed Flashfire so i can install Safestrap
Really want to use Magisk
Click to expand...
Click to collapse
Magisk does not work on devices with locked bootloaders.

GDReaper said:
Magisk does not work on devices with locked bootloaders.
Click to expand...
Click to collapse
yea had that feeling guess root for me gone yay.. ****ing niantic lol ahahah

Dragnous said:
yea had that feeling guess root for me gone yay.. ****ing niantic lol ahahah
Click to expand...
Click to collapse
I know this is pretty old but just a headsup if you have the latest bootloader that is locked you can just download firmware for your region with an older bootloader and flash the entire thing with odin. I had the locked bootloader issue and odin fixed it.

Cryptonite26 said:
I know this is pretty old but just a headsup if you have the latest bootloader that is locked you can just download firmware for your region with an older bootloader and flash the entire thing with odin. I had the locked bootloader issue and odin fixed it.
Click to expand...
Click to collapse
Which version of Odin did flash with bro?

Cryptonite26 said:
I know this is pretty old but just a headsup if you have the latest bootloader that is locked you can just download firmware for your region with an older bootloader and flash the entire thing with odin. I had the locked bootloader issue and odin fixed it.
Click to expand...
Click to collapse
Ok so you extracted an older bootloader and swapped it out?

17S update - can't root phone anymore

Hi,
Can anyone help me, please?
I used to have the version 16s installed on my phone but after the forced update, got the official 17s version installed.
Lost root access and got a lot of chinese apps installed.
Now I can't root my phone anymore. I've tried a a lot of methods/twrps and can't get the phone to boot to twrp recovery.
After flashing the recovery.img, phone only reboot again to the chinese rom.
From what I'm reading on a xda topic, it seems the same as this guy:
http://forum.xda-developers.com/leeco-le1-pro/development/letv-x800-ruschrom-1-0-25e-t3224702/page41
Thanks for the reply. My phone used to be rooted, too (Lollipop), but became unrooted during an unwanted OTA update and can not be re-rooted ever since (Marshmallow). None of the King/o/root/etc. apps did the job over ADB from a pc or installed on my phone. Flashing supersu zip from TWRP got my phone into a bootloop last night from which I could only get out by re-locking the bootloader and installing a stock ROM. The bloody 17v update notice keep popping up and I have no choice but to let it install sooner or later. If I ever manage to re-root my device, I'll try your method.

laoki said:
Hi,
Can anyone help me, please?
I used to have the version 16s installed on my phone but after the forced update, got the official 17s version installed.
Lost root access and got a lot of chinese apps installed.
Now I can't root my phone anymore. I've tried a a lot of methods/twrps and can't get the phone to boot to twrp recovery.
After flashing the recovery.img, phone only reboot again to the chinese rom.
From what I'm reading on a xda topic, it seems the same as this guy:
http://forum.xda-developers.com/leeco-le1-pro/development/letv-x800-ruschrom-1-0-25e-t3224702/page41
Thanks for the reply. My phone used to be rooted, too (Lollipop), but became unrooted during an unwanted OTA update and can not be re-rooted ever since (Marshmallow). None of the King/o/root/etc. apps did the job over ADB from a pc or installed on my phone. Flashing supersu zip from TWRP got my phone into a bootloop last night from which I could only get out by re-locking the bootloader and installing a stock ROM. The bloody 17v update notice keep popping up and I have no choice but to let it install sooner or later. If I ever manage to re-root my device, I'll try your method.
Click to expand...
Click to collapse
CN? Or US!?

dieselman6969 said:
CN? Or US!?
Click to expand...
Click to collapse
Thank you for your reply, it is CN version.
I was able to root the phone again, by doing fastboot commands manually.
flash recovery, flash misc
After that, I was able to enter recovery mode.

TWRP and stock Nougat hangs at Samsung logo, trying to root phone

Just installed Nougat stock ROM for my S7 Edge with ODIN, and trying to root.
I installed TWRP latest version 3.01 and immediately after installed supersu 2.79 SR3 from TWRP.
At first I could not boot the phone because it kept saying I used the wrong PIN code for boot. I reflashed stock rom and was able to boot again (same PIN) - disabled PIN on boot, and reflashed TWRP and supersu, but it keeps hanging at the Samsung Logo.
Flashing stock rom solves it, but I still want to root it..
What am I doing wrong?

currently there is no reliable root for nouget roms. It is being worked on.

Cosmic Blue said:
currently there is no reliable root for nouget roms. It is being worked on.
Click to expand...
Click to collapse
Thanks for replying.
In this case - even if the goal is to root - it seems the problem is with TWRP.. Even if I do not root, but just install TWRP, the neverending bootlogo shows up..

Nougat OS has been changed that all the old rooting and twrp need to be updated.
It will be a while till developers can modify the os to allow changes.

Have posted the same question in the TWRP S7 thread that I did not see before posting this one - sorry