[HELP] Having problem installing custom recovery - Galaxy S 5 Q&A, Help & Troubleshooting

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

Related

[Q] GALAXY S5 - SM-G900F unable to boot TWRP or CWM

Hello. I have GALAXY S5 - SM-G900F Lollipop. I wanted to root it and i used Kingo. It said that root was successful i even had superSU app, but i couldn't open it and when i installed app that i know needs root access i didn't get prompted to allow it. So after some checking i concluded that root was not successful and wanted to revert it with kingo again. It said that S5 was not rooted and i couldn't root it again (was getting failed this time).
Then i wanted to do factory reset to 4.4.2 via mobile but each time i would select that option phone would just freeze. I booted into recovery TWRP that i installed previously and did hard wipe. After that i was without ROM, and installed lollipop using this tutorial (/watch?v=r_ifFnj9tbo). Everything was fine but i lost TWRP and was with stock recovery.
I wanted to root phone again using different method (/watch?v=iBNGeppOzGI) but when i installed TWRP via odin (i got success and phone rebooted as last time i installed it) and tried to boot into TWRP using button combinations phone would just load standard recovery instead. I also tried to install CWM, same results. Success message, phone reboots and it still loads stock recovery so i'm stuck now. Anyone has any idea how to install TWRP now?
Anyone got any idea, don't know what to do here. Any help appreciated.
Could you paragraph your post please, it hurts my brain trying to read it like that
*Detection* said:
Could you paragraph your post please, it hurts my brain trying to read it like that
Click to expand...
Click to collapse
Just for you any ideas to why i can't get into twrp or cwm?
Anyone?

I Don't Know What I'm Doing Anymore!

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.....

Installing custom recovery on sm-n900v with stock lollipop rom

Hello all, I've been doing a lot of searching today to figure out if I can, and how to, install any custom recovery onto my Verizon Samsung Galaxy Note 3 on Android 5.0. I want to do this so I can either install a custom rom, or use xposed. But now that I'm on 5.0 I'm not sure what's possible anymore. I can root just fine, but installing TWRP with Flashify, or CWM with ROM Manager just puts my phone in a soft lock when I power it up. Giving me an error because it recognizes that I've installed a custom recovery, so it just locks my phone. I've gotten out of this twice now but using Odin to install the Lollipop rom again. To reiterate, is there any way I can install custom recovery on this phone now? I've seen some conflicting things in my searches so I have no idea what the case is.
Thanks
If the phone has a locked bootloader, a custom recovery can't be installed.

Can't Unroot S4?

So, i tried to Root my GF's I9506 with CF-Autoroot.
Safteynet fails and PokemonGo doesn't work, login problems.
I Unrooted trough SuperSU, restarted the phone a couple of times but PoGo still wont login.
She's on Stock Samsung Rom with Stock Recovery.
What can i do?
I was able to Re-Root with SuperSU for some reason. Had to update the binary tho. That's strange...
Shouldnt work if SuperSU unrooted in the first place?
Maybe it leaves files behind. If you're interested, there are ways to hide root from the game.
Anyway, the only sure way to remove root would probably be the flashing of a stock ROM.
Pwnycorn said:
Maybe it leaves files behind. If you're interested, there are ways to hide root from the game.
Anyway, the only sure way to remove root would probably be the flashing of a stock ROM.
Click to expand...
Click to collapse
Hmm. She really dosen't want to do a factory reset. so i guess i have to hide it then..
I think there are a few options i think all of them needs another recovery though:
Magisk + Magiskhide + phh
SuperSu, Suhide
Something called iSu.
Might it help to root again, remove anu "Su" files and folders trough ES Filexplorer? Then unroot from SuperSu?
If the phone is running a stock ROM, flashing a stock ROM usually leaves all of the data intact.
Dallebull85 said:
Hmm. She really dosen't want to do a factory reset. so i guess i have to hide it then..
I think there are a few options i think all of them needs another recovery though:
Magisk + Magiskhide + phh
SuperSu, Suhide
Something called iSu.
Might it help to root again, remove anu "Su" files and folders trough ES Filexplorer? Then unroot from SuperSu?
Click to expand...
Click to collapse
Removing any root file live might break root, which in turn won't let you remove any of the other files left.
Besides, you don't even know what files to look for.
Having a custom recovery won't affect her usage of the phone, nor the game. Besides, it gives you the benefit of making a Nandroid backup.
Ty for all the answers. So a custom Recovery doesn't trigger Saftynet?
Might as well install TWRP, backup and try to reflash stock rom from there.
Samsung Galaxy S4 International Qualcomm (jfltexx)
Samsung Galaxy S4 LTE Advanced i9506 (ks01lte)
Which one? i suppose its the 9506, flashhing my old CF-autoroot for my 9505(jfltexx) didn't work.
To flash a stock ROM, you need Odin, Samsung phone drivers, and the stock ROM from sammobile.com.
OK. But i'll do a backup on twrp first. Ty ty
Fixed it! Reflashed stock Rom with Odin and now Pogo works again!
Ty a lot for all the help. you guys are the best!

How to prevent bootloop on j3 2016 after rooting

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

Categories

Resources