Is there a root method for the PL1?
Thanks in advance.
Not afaik.
If you want rooted stock(-ish) PL1 though, a workaround is to:
A) roll back to OF1 stock (w/Odin),
B) root w/ one of the Yemen tools*
C) unlock the bootloader again (CID is already changed on a previously unlocked phone but the Odin stock flash in step (A) re-locks the bootloader)
D) install a custom recovery
E) flash my PL1 ".zip flashable" stock ROM in the recovery (thread in General forum)
F) take the recovery's offer to root the rom, or explicitly flash a SuperSU .zip bundle of your choosing.
G,H) start making twrp/nandroid backups and debloating as desired.
* I've never tried/used these; my Note3 still is on the NC4 bootloader (but w/ updated modem), so I can still flash stock NC4 and root w/ towelroot if I lose everything accidentally. Odin-flashable modems are also provided in that thread.
good luck
Simple
Is there a better method or a tutorial that might make it easier for someone that is more of a layman?
Thanks
I managed to root PL1 using kingroot, although doing so is quite risky in more ways than one. After rooting I found a guide for replacing kingroot with supersu. Id recommend flashing a custom recovery prior to replacing root should you decide to do so. I believe I used an app called TWRP manager for that. Of course if youre going to do that you also need to unlock your boot loader....Not really sure how i did that but I vaguely remember it wreaking havoc on my sd card
I just did this, FYI to all. Kingroot for PL1 on verizon S4, then super-sume to remove it and install superSU. Works great. Kingroot is very shady so hopefully that supersume removed all of it's dirty claws
Related
Hi,
Ok guys so a friend of mine wanted root on his S4 Gt-i9500, which I got for him using towelroot, no problems there and for a while he was happy with the root access and getting his phone debloated and a few other bits and bobs. However now he wants to try a couple of AOSP roms, and has asked me to help, which Im happy to do.
If it was my phone I'd take my chances and see what happens but with someone elses device I feel like I should be a bit more responsible, although I have made the dangers clear.
So what I want to do Is add a custom recovery, I've done a bit of googling and I can find out how to do it easy enough when rooted the traditional way, but my concern would be will I run into any problems with the Bootloader still being locked if I just flash a twrp .img with Flashify?
Maybe I should do a full unroot, and root via CF-Root Method and then find a TWRP .tar and flash with Odin.
Not used to having the Bootloader Locked issues as I use a HTC so is an easy unlock.
Any advice people can give would be helpful, hopefully I can just use Flashify and keep it as simple as possible
Ok, just to make things crystal clear, there is a big difference between a locked (i.e. encrypted) bootloader as found on AT&T and Verizon phones, and a SEAndroid Enforcing (aka Knox) bootloader. With the former you cannot customize the firmware that came with the phone, but developers have found workarounds. With Knox, you're still able to root and install custom ROMs if desired. You simply lose the ability to use Knox, which most of the userbase doesn't care about. In HTC speak, all Galaxy S4 bootloaders except the AT&T and Verizon models are equivalent to S-Off.
For installing TWRP, downloading an image and installing through Odin will work. TWRP Manager from the Play Store can also do the job, and do it without you being connected to the PC. Once you have TWRP installed, installing a custom ROM is quick, easy, and painless. Custom ROMs are usually pre-rooted, i.e. including SuperSU or Clockworkmod Superuser. This means you won't have to root again.
Has anyone tried simply flashing a custom recovery, then using the recovery to flash SuperSU as a way to gain root access?
Or do i need to find a rootable kernel somewhere?? I google this issue alot recently, and just want to find out if someone has done this successfully. Odin is killing me because no matter what i DO try to flash using it, fails... other than the Stock Android 5.0.1 firmware. Am i missing something, or can someone give me directions to the simplest instructions possible to gain root on it. I know this has been asked alot, but most solutions i have found have only been for other carriers, and lower builds of the firmware. I would be willing to downgrade to KitKat if necessary... but also that seems impossible because the bootloader blocks downgrades... Please Help
Worked Like A Charm
So its done!! Simple and easy... Three steps! (make sure to copy the newest SuperSU file to your sdcard first)
***Boot into ODIN Download Mode***
1. Using ODIN flash TWRP 2.8.4.0 (dont let it reboot on its own afterwards!... YOU MUST BOOT INTO RECOVERY ON YOUR OWN THE FIRST TIME TO LET TWRP PATCH THE ROM)
2. While in TWRP recovery, then install SuperSU zip file from your SDcard
3. Select reset and perform the "Factory Reset" option.
!!! Success... !!! you now have a rooted Sprint S4 with the OF1 build of lollipop...
*********Credit to "bilgerryan"
For the proper process to use!
:laugh:
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.....
I just got my Moto G4 Plus and want to root it. Does somebody have a good guide for rooting it?
I found this guide on youtube, can I just follow this?: https://www.youtube.com/watch?v=g3bhXe3msxU&t=3s
What stock OS are you running on your device, Marshmallow or Nougat?
echo92 said:
What stock OS are you running on your device, Marshmallow or Nougat?
Click to expand...
Click to collapse
I just updated to Android 6.0.1 Marshmallow
If you're on Marshmallow (6.0.1), then the guide you linked should work, you may wish to keep the stock kernel (and not flash ElementalX). Also, instead of phh superuser, you could choose to flash SuperSU or magisk.
Here's a guide for rooting on Marshmallow 6.0.1 as well https://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772 You may wish to use a newer build of SuperSU than mentioned in the guide - the latest build currently is 2.82 SR1.
echo92 said:
If you're on Marshmallow (6.0.1), then the guide you linked should work, you may wish to keep the stock kernel (and not flash ElementalX). Also, instead of phh superuser, you could choose to flash SuperSU or magisk.
Here's a guide for rooting on Marshmallow 6.0.1 as well https://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772 You may wish to use a newer build of SuperSU than mentioned in the guide - the latest build currently is 2.82 SR1.
Click to expand...
Click to collapse
I found a video that showed how to unlock bootloader, and uses SuperSU when rooting. Can I use this guide insted, or is it to old you think?: https://www.youtube.com/watch?v=dK2uacpjGwc&t=119s
Thank you so much for all the help btw
skismas said:
I found a video that showed how to unlock bootloader, and uses SuperSU when rooting. Can I use this guide insted, or is it to old you think?: https://www.youtube.com/watch?v=dK2uacpjGwc&t=119s
Thank you so much for all the help btw
Click to expand...
Click to collapse
Looking through that video, I think it should work for 6.0.1 - as an aside for anyone reading this, the root procedure for Nougat is different. Though the resources linked in the video may work (I have not tested them), you may, as I mentioned above, wish to flash newer versions of TWRP and SuperSU than that linked in the video:
TWRP - (official): https://dl.twrp.me/athene/
I personally use shreps' TWRP: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
SuperSU v2.82: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703 Ideally, you'll want to use v2.79 SR3 or newer as they're systemless root.
EDIT: this guide linked to in the video has a nice description of some of the steps you'll need: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584
One thing I'd add to those guides is before you flash SuperSU, make a backup of all of the partitions in TWRP (on the TWRP main menu, you'll see 'Backup'). If SuperSU fails to root or causes instabilty, you'll have a backup to fall back to.
Additionally, when flashing TWRP, you'll see the 'Image not signed or corrupted' warning, that's normal. As long as [OKAY] comes up in fastboot after flashing and you reboot to recovery afterwards (so TWRP is set as your recovery), then TWRP should stick.
You may also receive OTA messages - do not accept these whilst rooted and with TWRP. if you wish to turn them off, have a look here: https://forum.xda-developers.com/showpost.php?p=72373828&postcount=12
Don't FLASH TWRP, just BOOT it up, do whatever you need to do and... keep your stock bootloader. The TWRP is useful mostly for CM/Lineage ROM's, for stock it's just a headache waiting to happen.
echo92 said:
Looking through that video, I think it should work for 6.0.1 - as an aside for anyone reading this, the root procedure for Nougat is different. Though the resources linked in the video may work (I have not tested them), you may, as I mentioned above, wish to flash newer versions of TWRP and SuperSU than that linked in the video:
TWRP - (official): https://dl.twrp.me/athene/
I personally use shreps' TWRP: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
SuperSU v2.82: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703 Ideally, you'll want to use v2.79 SR3 or newer as they're systemless root.
EDIT: this guide linked to in the video has a nice description of some of the steps you'll need: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584
One thing I'd add to those guides is before you flash SuperSU, make a backup of all of the partitions in TWRP (on the TWRP main menu, you'll see 'Backup'). If SuperSU fails to root or causes instabilty, you'll have a backup to fall back to.
Additionally, when flashing TWRP, you'll see the 'Image not signed or corrupted' warning, that's normal. As long as [OKAY] comes up in fastboot after flashing and you reboot to recovery afterwards (so TWRP is set as your recovery), then TWRP should stick.
You may also receive OTA messages - do not accept these whilst rooted and with TWRP. if you wish to turn them off, have a look here: https://forum.xda-developers.com/showpost.php?p=72373828&postcount=12
Click to expand...
Click to collapse
I managed to root my phone without bricking it! I think......
SuperSU was not on the phone when I rebooted the phone like in the video. I had to download it through play store. But since it says its rooted on root checker, and I could grant it permission, im pretty sure I done it right.
Thanks for the help I really appreciate it
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.