I rooted my S4 awhile back but never put a rom on it well I got the 4.4.4 update and didn't really care but now I am having a serious battery drain by the Android System and need to run so apps that require root access. Since I was already rooted is there a different process to Re-Root the device or do I just follow the standard rooting procedure for the 4.4.4 NJ4. Will I have to wipe everything also to do it or will I be able to keep my phone in tacked. Could you point me to the best method for my situation it would be greatly appreciated.
Thanks in advance for you help.
If you have custom recovery, flash the update super su zip.
If not, you might have to go through the rooting process.
Related
Hey, so my root checker is failing, and I have no idea why. I'm using TWRP and have flashed Illusion mod, however, I don't have any root access to kind of tinker with my CPU levels.
I'm basically thinking I have to re-root my device. MY question is, I spent a lot of time customizing my phone exactly to how I'd want it and I just found this out. If I back up my custom flash, and reroot my device, can I go back into TWRP and restore my backup? Will that mess anything up?
OR most importantly, does anyone know how to give full root access to an already rooted device?
Thanks! I'm almost there with my 100% customized phone, I'm VERY eager and have been having a BLAST learning all this.
ahendowski said:
Hey, so my root checker is failing, and I have no idea why. I'm using TWRP and have flashed Illusion mod, however, I don't have any root access to kind of tinker with my CPU levels.
I'm basically thinking I have to re-root my device. MY question is, I spent a lot of time customizing my phone exactly to how I'd want it and I just found this out. If I back up my custom flash, and reroot my device, can I go back into TWRP and restore my backup? Will that mess anything up?
OR most importantly, does anyone know how to give full root access to an already rooted device?
Thanks! I'm almost there with my 100% customized phone, I'm VERY eager and have been having a BLAST learning all this.
Click to expand...
Click to collapse
You won't lose anything if you reroot your device. You don't have to wipe data. Have you tried downloading supersu from the play store and letting it install the binaries? Or flashing supersu through recovery?
cruise350 said:
You won't lose anything if you reroot your device. You don't have to wipe data. Have you tried downloading supersu from the play store and letting it install the binaries? Or flashing supersu through recovery?
Click to expand...
Click to collapse
Yeah, I have tried downloading supersu from the play store... but it says it cannot update the binaries. Not sure why.
I'll try flashing supersu from recovery though. Might be a better idea. If I flash supersu through recovery, will it install all the latest binaries as well? Or will I still have to update it later?
edit: flashing the SuperSU worked perfectly!!! I only tried installing it via playstore, not actually flashing it. Thanks a ton!!
Hello!
I had previously rooted my AT&T Samsung Galaxy S4 using towelroot and everything was fine. However, I recently received an alert from AT&T stating that a new update was available. I currently have 4.4.2 and from this forum, it sounds like the update was for 4.4.4.
I went to download and install the update, but when I did so, the update failed and my root was removed. I cannot reroot using towelroot nor can I get the update to complete, it just resets at about 25%.
I'd like to install the update successfully and possibly reroot, although root is a lesser priority. Does anyone have any ideas on how I can fix this problem?
Thank you.
Do you have a recovery installed? Just flash the SuperSU from recovery, reboot and install binaries. Problem solved.
HORiZUN said:
Do you have a recovery installed? Just flash the SuperSU from recovery, reboot and install binaries. Problem solved.
Click to expand...
Click to collapse
What are binaries and how do you install them? thanks
Deep_Blue_9 said:
Hello!
I had previously rooted my AT&T Samsung Galaxy S4 using towelroot and everything was fine. However, I recently received an alert from AT&T stating that a new update was available. I currently have 4.4.2 and from this forum, it sounds like the update was for 4.4.4.
I went to download and install the update, but when I did so, the update failed and my root was removed. I cannot reroot using towelroot nor can I get the update to complete, it just resets at about 25%.
I'd like to install the update successfully and possibly reroot, although root is a lesser priority. Does anyone have any ideas on how I can fix this problem?
Thank you.
Click to expand...
Click to collapse
The process is lil bit costly. I was all afternoon looking for it . I think this is the solution:
1. There is no official firmware file for NC1. You will have to flash the NB1 file first then apply the update to NC1: HERE
2. You can root your phone and have the latest update for your device. How? Follow this GUIDE.
3. Enjoy
It's easier for my device, I guess. If I flash a rom that doesn't have root access, I just flash the SuperSU zip in recovery and reboot. Unlocked bootloaders make it sooo easy to mess with the phone
Joku1981 said:
The process is lil bit costly. I was all afternoon looking for it . I think this is the solution:
1. There is no official firmware file for NC1. You will have to flash the NB1 file first then apply the update to NC1: HERE
2. You can root your phone and have the latest update for your device. How? Follow this GUIDE.
3. Enjoy
Click to expand...
Click to collapse
Thanks, things are good now!
I followed the instructions for your step Step 1 spelled out in detail at
http://forum.xda-developers.com/showthread.php?t=2616221
http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
http://forum.xda-developers.com/showthread.php?t=2674223
and I was able to update to 4.4.4 successfully. I haven't tried to root my phone but I'm not sure if I really want to so everything seems resolved.
Hi I have been running with a rooted Note 2 for two years now and it is time for a change.
I just bought a phone Rooted Running Android 4.4.2 rooted with Safestrap on swappa.
I don't really understand what I can and cant do with this phone, like can I install a lollipop rom? Cyanogenmod Rom? do I have to stay on 4.4.2 ?
Also, can you tell me what NOT to do so to lose root, this phone seem a bit locked down, more so than my note 2.
The seller sent me this not today:
"Hi Plainbum. I will be shipping the phone out in a few hours during my lunch break. I have wiped it clean and installed a fresh copy of 4.4.2 with root and safestrap. I went ahead and renamed the 2 files in the file system that are known to force a system software update by renaming the files to .bak, so you shouldn't have to worry about the phone trying to update itself. I have included all the files you would need to re-install a clean copy of 4.4.2 unrooted, plus root and safestrap on a 4gb sd card at no extra charge. Please refer to XDA forums should you need steps on how to do this, and take note newer versions of android may not be rootable on this phone. Thanks!"
Can I never run a rooted phone with a lollipop or MM ROM?
Thanks for any advice
If you install a stock lollipop or mm rom then you will lose root and even if you downgrade from them root it lost. Cm and aosp roms also won't work because of the locked bootloader. I think the only 5.x type rom is JasmineRom if i remember correctly
Thanks! Let's say I successfully INSTALL jasmine, do I have to stay there to keep root or can I safely go back to kitkat?
Is there a root procedure for the galaxy s4 that's on the newest lollipop update ? I was able to root with kingroot but read its not safe to use kingroot and try install a custom rom ?
dpmeeks said:
Is there a root procedure for the galaxy s4 that's on the newest lollipop update ? I was able to root with kingroot but read its not safe to use kingroot and try install a custom rom ?
Click to expand...
Click to collapse
CF-autoroot or flash TWRP then in TWRP flash SuperSU
Kingroot and SuperSU_me method works also... Watch the entire process in 2 parts... https://www.youtube.com/watch?v=IWnYFDQ1Vio
K94U said:
Kingroot and SuperSU_me method works also... Watch the entire process in 2 parts... https://www.youtube.com/watch?v=IWnYFDQ1Vio
Click to expand...
Click to collapse
Have you lost root since? I've read a lot about people loosing root after a few hours to a couple of days. Any other issues, like random crashes / freezes / reboots?
Ezintn said:
Have you lost root since? I've read a lot about people loosing root after a few hours to a couple of days. Any other issues, like random crashes / freezes / reboots?
Click to expand...
Click to collapse
That's why flashing TWRP and SuperSU is the safest/easiest way to root, it's about as straightforward as it gets
mattzeller said:
That's why flashing TWRP and SuperSU is the safest/easiest way to root, it's about as straightforward as it gets
Click to expand...
Click to collapse
Wasn't aware I could flash a custom recovery on a stock unrooted phone. I don't use the s4, that's why both of the ones I own aren't rooted already, my personal phones are often rooted before I even get home from the store! I need root and su without tripping knox or making any significant changes to the current set-up on either phone. I would prefer the recovery was stock on at least one of 'em. So how should I go about this? One is a tri band and the other isn't. The dual band one needs to be as stealth as possible. Losing root really won't matter as long as the system permissions remain as is prior to losing root.
Ezintn said:
Wasn't aware I could flash a custom recovery on a stock unrooted phone. I don't use the s4, that's why both of the ones I own aren't rooted already, my personal phones are often rooted before I even get home from the store! I need root and su without tripping knox or making any significant changes to the current set-up on either phone. I would prefer the recovery was stock on at least one of 'em. So how should I go about this? One is a tri band and the other isn't. The dual band one needs to be as stealth as possible. Losing root really won't matter as long as the system permissions remain as is prior to losing root.
Click to expand...
Click to collapse
Flashing a custom recovery is going to trip knox. Why do you care about knox? Triband or not flashing TWRP and SuperSU is the same. If you lose root and have things that require root to operate, you will lose the function of those things, unless it's a one off type of thing
mattzeller said:
Flashing a custom recovery is going to trip knox. Why do you care about knox? Triband or not flashing TWRP and SuperSU is the same. If you lose root and have things that require root to operate, you will lose the function of those things, unless it's a one off type of thing[/QU
It's imperative that root is stealth. Just need to give one app already running su permissions. On one device knox is monitored, that's why I care. I wouldn't care on my s5, but I never tripped it anyway - rooted with modified stock recovery, flashed MOAR, flashed TWRP. Been using MAOR and TWRP since each was first released. Been rooted on my personal devices since 3 days after the Hero was released. I've just never rooted the s4 or "stealth rooted" any device. That's why Kingroot / SSM looks promising. Any help would be appreciated.
Click to expand...
Click to collapse
There are a few threads that deal with upgrading lollipop to marshmallow, but they seem to raise as many questions as they answer - mainly since they were usually written before rooted images were distributed.
Basically, I am on an unlocked, rooted stock XT1575 with TWRP 2.8.7.0. It sounds like it's less efficient and has lots of potential problems to go back to stock, unroot, install OTA, do new system root, and re-add TWRP.
Instead, it sounds like the simplest method to get to stock rooted MM, with least steps and potential problems, should be this:
Update TWRP to 2.8.7.1 using IMG file here from within TWRP Recovery (TWRP Manager did not install it when I tried via Android proper - I was still at 2.8.7.0)
Do a full TWRP backup of my current Lollipop stock rooted installation (I assume this means I can restore without problems if the MM install goes awry)
*Optional: Use Titanium Backup to backup settings of important apps, and text messages/MMS.
In TWRP, Wipe->Swipe to Factory Reset
Transfer to phone and Flash via TWRP the stock rooted odexed ROM from this thread (not sure if there is a good argument for deodexed? I've never gotten a clear answer why one should be better, but would stick with odexed just because I believe it is "stock" so maybe less problems?)
Install SuperSU 2.62 from this thread by simply flashing it as normal in TWRP 2.8.7.1.
Reinstall all programs on initial setup. [*Optional: Reinstall via Titanium backup]
I assume if I do this I will: have marshmallow; have root; have working TWRP.
Does anyone see any obvious problems with this method? Thanks, I really appreciate any comments.
EDIT: Yes, I tried this method. It all worked, except I've added SuperSU installation steps that worked for me, since the "Stock Rooted" ROM is NOT actually rooted when I flash it. Also, used Titanium Backup successfully for some programs, so added that as an option.
Sorry to bump, but any response from someone with experience would be very helpful. I just want to make sure I don't have to go through the whole unroot/OTA/reinstall TWRP/reinstall root procedure that every thread says seems to cause problems...
Answered my own question - edited the main post to show the method used successfully.
Thank you for this answer thread. I was looking for the simplest answer for upgrading to MM without having to unroot and reflash everything. Looks like this is the easiest for now (I have having to reinstall everything, since some games I play to NOT react nicely to data being restored via titanium).
Have a brand new XT1575 with 5.1.1, Does the MM Update break root ability. I primarily want it for xposed, adaway. No ROMing
Should I update and then root? or root and then update?
I personally have found that following this method breaks root possibilities. MM is rooted, but when I got to the point of installing SuperSU via these steps, it broke EVERYTHING (settings stopped working, Motorola Services stopped working, etc).
I have to start from scratch again now.