I've searched the forums and only found recoveries for Sprint. I'm afraid to do anything with my G900V until I have a backup. I have rooted already but that's about it. I assume I'd have to use SafeStrap because of the locked bootloader, but SafeStrap doesn't seem to install correctly. I do have busybox and SS installed already so that isn't the problem. Any help will be very much appreciated! Thanks.
treyonator56 said:
I've searched the forums and only found recoveries for Sprint. I'm afraid to do anything with my G900V until I have a backup. I have rooted already but that's about it. I assume I'd have to use SafeStrap because of the locked bootloader, but SafeStrap doesn't seem to install correctly. I do have busybox and SS installed already so that isn't the problem. Any help will be very much appreciated! Thanks.
Click to expand...
Click to collapse
No recovery for lollipop.
Make sure you have busybox installed correctly. You will have to be on 4.4.2 or 4.4.4 for safestrap to install. Use this one. You can also use flashfire for backing up your system but it isn't a custom recovery.
Thanks. Very much appreciated.
Related
I've been away from modding since I mistakenly bought the verizon gs5 (G900V) and saw that there wasn't even a way to root it. I started looking around again and saw that towelroot now works for the G900V. Now that I've rooted, I can't seem to find one unified thread to installing a good recovery, and flashing a ROM. Ideally, I'd like a step-by-step on how to install CWM-Touch and then CyanogenMod CM12.
Would anyone be able to give me that step-by-step?
Install Busybox first
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en_GB
Run it, and install as directed.
Then use this to install TWRP Recovery
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en_GB
You'll remember the flashing custom steps once you have a custom recovery Im sure, if not, reply here
This is probably outside the scope of my original question, but will the cm12 kltevsw nightlies flash to my G900V correctly after installing TWRP?
I'm not asking about stability, just that whether it would install properly.
You'd have to check compatibility of any custom ROM for your model S5, in that ROMs thread
Fair enough. I guess a better question I should've started with is this: Does the busybox and TWRP install allow me to use AOSP Roms?
dobber92 said:
Fair enough. I guess a better question I should've started with is this: Does the busybox and TWRP install allow me to use AOSP Roms?
Click to expand...
Click to collapse
So long as your device is supported for the custom ROM you want to flash, then yes, TWRP will allow you to flash anything custom
Busybox is only needed for TWRP manager app, in order to flash TWRP in the first place, you can remove it once you have TWRP if you want
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.....
Ok, so I got an AT&T Galaxy S4 running OC3, and I want to put a custom ROM on. I've been reading so many threads over the past few days, and want to make sure that I have everything ready to go before I brick my phone (the volume up button is stuck so I can't get into download mode if I brick it, will that be a problem?)
1. I have rooted using Kingroot. Root check app says I have root
2. I installed busybox
3. I installed safestrap 3.72 (I tried uninstalling 3.72, and installing 3.75, but it says old version installed. Will this be a problem?)
4. Downloaded and installed the NC1 flasher spk, but have not flashed yet because I want to make sure I'm doing everything ok
5. This is where I really want to make sure I have everything in order... I'm going to list the zip I have that I think I need to flash, in the order that I think I need to flash them:
a. Goldeneye ROM v.53 (unless someone has a better ROM they think I should use)
b. 5.0 nano Gapps
c. SuperSU (unless I don't need to)
d. OC3 Stock Kernel
e. OC3 modules
f. 0C3 Modem
g. xposed
6. Reboot (then install xposed installer apk, reinstall busybox/safestrap apk/nc1 flasher apk, other apps, etc)
Please let me know if this is the right path. And is not being able to get into download mode going to be a problem?
I don't know where you got the 5.0 nano Gapps step from, but you shouldn't need those. SuperSU never hurts to flash so that's fine. Just make sure you have the recovery flashable zip for the OC3 kernel since you can't get into download, but you should be able to reboot to download from Safestrap anyway if necessary. You may also want to boot into the ROM once before flashing xposed.
DeadlySin9 said:
I don't know where you got the 5.0 nano Gapps step from, but you shouldn't need those. SuperSU never hurts to flash so that's fine. Just make sure you have the recovery flashable zip for the OC3 kernel since you can't get into download, but you should be able to reboot to download from Safestrap anyway if necessary. You may also want to boot into the ROM once before flashing xposed.
Click to expand...
Click to collapse
Thanks for the quick reply. I guess I'm just used to flashing gapps from every other device I have flashed haha. So you don't need to in this method?
And does it matter that I can't update to safestrap 3.75? Will 3.72 work?
And thanks for the heads up on flashing xposed. When I boot the ROM, do I need to reinstall safestrap/NC1 flasher to get back so I can flash xposed?
One more question (sorry for all the questions ), do you have any opinion on the Goldeneye ROM vs any other compatible lollipop ROMs? And are there any Marshmallow ROMs that would be compatible?
jicrunk said:
Thanks for the quick reply. I guess I'm just used to flashing gapps from every other device I have flashed haha. So you don't need to in this method?
And does it matter that I can't update to safestrap 3.75? Will 3.72 work?
And thanks for the heads up on flashing xposed. When I boot the ROM, do I need to reinstall safestrap/NC1 flasher to get back so I can flash xposed?
One more question (sorry for all the questions ), do you have any opinion on the Goldeneye ROM vs any other compatible lollipop ROMs? And are there any Marshmallow ROMs that would be compatible?
Click to expand...
Click to collapse
Apologies for being away from XDA for a bit. You don't need Gapps since it's not an AOSP ROM. Either Safestrap should work once you flash the NC1 kernel I believe. You will need NC1 Flasher, Safestrap should still be installed though (the recovery, not the app though) or you should also be able to use Flashfire if you have it. No MM Roms are compatible, and Goldeneye was a good ROM when I used it. Personally I just rooted stock and customized it myself, but Goldeneye is good.
If you've already gone and flashed, then I hope all has gone well and whatnot.
Greetings. Has anyone had any luck installing installing Magisk to hide root? I have tried a variety of things, and they ultimately lead to bootloops or "unauthorized" software detected by ATT. I am running a rooted deodexed stock OC4 rom on an i337. I have followed the major guides to get to that point, and have tried to flash the Magisk zip in numerous ways.
Things I have tried:
*Flashing in safestrap (used the NC1 flasher) with and without supersu. I can't recall the precise error message (I think it is unable to be unpacked), but either way it does not work. I have also had no luck getting back to my rom after reflashing the OC4 modules and kernal, but that is a different thread.
*Installing from the Magisk from the root rom with and without supersu managing root.
*Flashing the zip from normal recovery, which of course creates an error for the zip being unverified or whatever it says
Any advice would be greatly appreciated.
It's only on unlocked bootloaders
safwanz1 said:
It's only on unlocked bootloaders
Click to expand...
Click to collapse
Thanks for the reply. I don't think I read that anywhere, but I assume you're probably right about that given the state of the S4.
Although TWRP is *supposed* to be lokied, it turns out that all the 3.x versions are not properly lokied. This has been reported in the last couple of pages of this thread, and it's been reported in their bug tracker (although they seem to be ignoring it for now).
One of the users in that xda thread was kind enough to loki a few TWRP releases, but the latest one he did was v3.1.1.0, and he hasn't done any more since.
Can someone else be kind enough to Loki the latest version of TWRP for jflteatt, located here? (Preferably both IMG and TAR, so people can use it with whichever installation method they prefer/need)
My guide tells you how to Loki CWM recovery, it should work the same for TWRP (should is the keyword here).
https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
StoneyJSG said:
My guide tells you how to Loki CWM recovery, it should work the same for TWRP (should is the keyword here).
https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
Click to expand...
Click to collapse
Thank you. However, the method described requires root.
I had root on CyanogenMod 11, but ever since I flashed LineageOS 14.1, I haven't been able to root my phone without bricking it - so this method won't work for me.
How are you on lineage OS without having root? You need root to install a custom recovery which then in turn allows a custom ROM. I know lineage OS hides or does sometimes with superSU, so it might be hiding root as well (unless I am thinking of Oct OS).
Your phone is probably rooted, use the root checker app from the play store to check. If by chance somehow it's not, then use towel root, king root, one click root, safe root, CF auto root, or kingo root to root it. If all else fails you might have to ODIN back to stock, then root, then install the latest TWRP then Loki it using my guide then install lineage OS.
StoneyJSG said:
How are you on lineage OS without having root? You need root to install a custom recovery which then in turn allows a custom ROM. I know lineage OS hides or does sometimes with superSU, so it might be hiding root as well (unless I am thinking of Oct OS).
Your phone is probably rooted, use the root checker app from the play store to check. If by chance somehow it's not, then use towel root, king root, one click root, or kingo root to root it.
Click to expand...
Click to collapse
No, my phone is definitely not rooted. It *previously* had root under CyanogenMod 11. That's how I had a custom recovery installed. So I was able to use TWRP to flash LineageOS 14.1 just fine. However, here are the results of my trying to root this phone under LOS 14.1:
1. Magisk: Bricked on Samsung Logo.
2. SuperSU (normal systemless): Not installed properly. Seems to fail on patching the boot image.
3. SuperSU (system mode): Bricked on Lineage boot screen.
4. LineageOS addonsu: Installs fine, but doesn't seem to do anything. I still don't have root.
I've tried posting about this in a few places on xda, but so far, I haven't had any luck.
So *maybe* if I revert back to an older version of Android, I might be able to get a working root. But in order to be recent, it's looking like I have little choice but to finally retire this phone and get something newer. Which is unfortunate, because there's nothing wrong with the phone hardware-wise.
Perhaps I'll try one of the other root options you mentioned and hope it doesn't brick my phone as well.
That's really odd that you have a custom recovery and ROM without root. You might have to ODIN back to stock Android 4.2.2 jelly bean using the MDL firmware .tar file. Can you revert back to a TWRP that is Loki?
StoneyJSG said:
That's really odd that you have a custom recovery and ROM without root. You might have to ODIN back to stock Android 4.2.2 jelly bean using the MDL firmware .tar file. Can you revert back to a TWRP that is Loki?
Click to expand...
Click to collapse
I have a Lokied version of TWRP (3.1.1.0), which is working fine. But with all of the problems I've been having trying to get root, I was wondering if perhaps a newer version of TWRP might make the difference. That's why I was trying to get a Lokied version of the latest TWRP.
Ah so you're trying to gain root by flashing TWRP. No idea why lineage OS removed root, unless the people who made it built it that way. The only thing I can think of is either try all the root apps I mentioned before and if that doesn't work then ODIN back to MDL stock and use towel root to root. If lineage OS is anything like Oct OS, you will have to root using a root .zip file.
I wish I could be more help, but I haven't ever used lineage OS before due to liking touchwiz. I run golden eye ROM on my at&t Loki phone.
StoneyJSG said:
My guide tells you how to Loki CWM recovery, it should work the same for TWRP (should is the keyword here).
https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
Click to expand...
Click to collapse
Unfortunately it does not work:
Code:
1|[email protected]:/data/local/tmp # ./loki_flash recovery twrp.img
[+] loki_flash v1.1
[-] Input file is not a Loki image.
1|[email protected]:/data/local/tmp #
jabulon said:
Unfortunately it does not work:
Code:
1|[email protected]:/data/local/tmp # ./loki_flash recovery twrp.img
[+] loki_flash v1.1
[-] Input file is not a Loki image.
1|[email protected]:/data/local/tmp #
Click to expand...
Click to collapse
Thanks for trying it! It's now confirmed my guide is only for CWM recovery.
Not sure if you've already searched it out, but HERE is my thread with the latest Loki patched twrp. I lokied jfltexx 3.2.3-0 which works on the i337 (ATT) s4.
There's also this:
https://forum.xda-developers.com/galaxy-s4-att/general/lokid-jfltexx-twrp-att-vzw-s4-t3869503
StoneyJSG said:
There's also this:
https://forum.xda-developers.com/galaxy-s4-att/general/lokid-jfltexx-twrp-att-vzw-s4-t3869503
Click to expand...
Click to collapse
Your link IS my link from the post directly above yours
Oh crap haha so it is. Oops brain fart there, my fault.
StoneyJSG said:
Oh crap haha so it is. Oops brain fart there, my fault.
Click to expand...
Click to collapse
You're good ? I had it in a separate post, and I just created that thread the other day to give it a permanent home more easily found.