S5 rooted, now what? - Verizon Galaxy S 5 Q&A, Help & Troubleshooting

I have never run a stock OS rooted. Always AOKP or CM. What should we do now?
-How to we protect it to make sure VZW doesn't somehow patch it?
-Tethering without Foxfi now possible. See below.
-SuperSu info - see below.
-What will we need to do about updates?
-What else?
Read below. I'm adding helpful info as it is collected.
GeoHot (and others), you are the man (men). Thanks guys. All bounty pledgers, pay up!
If you need to root your S5, go here. Donate as well! http://towelroot.com/
** No, Root does not allow us to unlock the bootloader. They are entirely different. I personally have not heard of anyone working on that. Most knowledgeable people I have heard say it would require a leak of the keys from Verizon. **
***Below are apps and/or tweaks (not obvious ones) known to work by me or someone else that has tested***
-Xposed Framework
----X Tether (Free tethering)!
----Wanam Xposed - Free tethering option does NOT work for me. Others report it does.
-Super SU 2.0 in Play store now works. Link below no longer needed.
----use this version http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip

mkitchin said:
I have never run a stock OS rooted. Always AOKP or CM. What should we do now?
-How to we protect it to make sure VZW doesn't somehow patch it?
-I assume we can enable native tethering without FoxFi?
-I know there is some chatter about SuperSu. It fails to update. Need a new version from Chainfire?
-What will we need to do about updates?
-What else?
GeoHot (and others), you are the man (men). Thanks guys. All bounty pledgers, pay up!
Click to expand...
Click to collapse
Did you install SU before or after rooting? Or had that problem, stupid me in the antisapation of having root I installed SU last night and after rooting just now could not for the life of me get it to update SU, after multiple reboots I finally uninstalled it after clearing the cache and app settings in app manager, rebooted then reinstalled, then ran root checker, it failed then it asked for root, granted, rechecked, and it passed!

mkitchin said:
I have never run a stock OS rooted. Always AOKP or CM. What should we do now?
-How to we protect it to make sure VZW doesn't somehow patch it?
-I assume we can enable native tethering without FoxFi?
-I know there is some chatter about SuperSu. It fails to update. Need a new version from Chainfire?
-What will we need to do about updates?
-What else?
GeoHot (and others), you are the man (men). Thanks guys. All bounty pledgers, pay up!
Click to expand...
Click to collapse
logically, you should avoid any vzw updates. SU may fail, but it still works. try running a rooted app. it will ask you to grant permission. I just removed over 12 apps that vzw forced on my phone.
Sent from my SM-G900V using Tapatalk

GlitchMob said:
logically, you should avoid any vzw updates. SU may fail, but it still works. try running a rooted app. it will ask you to grant permission. I just removed over 12 apps that vzw forced on my phone.
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
can you share what was safe to remove so far without messing up any framework dependencies?
Sent from my SM-G900V using Tapatalk

chainfire needs to update app before well b able to update it.. it still has root and works so be patient.. we cant keep vzw/samsung from patching it on future devices but it will take them a bit of time so id imagine later updates and newer phones yet to come out would be patched.. now we enjoy root until someone down the road (hopefully) gets us custom recovery for custom roms but lets not jump the gun here, we just got root so let the devs enjoy that feat lol
Sent from my SM-G900V using XDA Premium HD app

Disable OTA
elliwigy said:
chainfire needs to update app before well b able to update it.. it still has root and works so be patient.. we cant keep vzw/samsung from patching it on future devices but it will take them a bit of time so id imagine later updates and newer phones yet to come out would be patched.. now we enjoy root until someone down the road (hopefully) gets us custom recovery for custom roms but lets not jump the gun here, we just got root so let the devs enjoy that feat lol
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
Rename SDM.apk and SDM.odex. to .bak files and VZW can't use the OTA updater anymore. The software updater in settings will be gone too. You will need a file explorer like fx and the root add on for this, it's free.
EDIT: SDM.apk is in the system/app driectory.

Safestrap is next: you'll be able to run custom ROMs but not custom kernels, so TW builds but not AOSP (unless the S5 GPE is built on a TW kernel, as the original 4.2.2 S4 GPE ROM was). I wouldn't actually delete any APKs from your device; just freeze them with Titanium.

Backwardsblade said:
can you share what was safe to remove so far without messing up any framework dependencies?
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Sure, but I cannot guarantee you won't have any issues. I managed to remove a decent amount of bloat apps and rebooted successfully. I will list them below.
- Google +
- Google Books
- Google Play Music
- Audible
- VZW protection
- Messaging +
- Amazon
- Kindle
- Amazon Appstore
- IMDB
- VZW ringtones
- VZW protection and support
- Isis Wallet
and a few more that I cannot remember. I hope this helps.
---------- Post added at 07:28 PM ---------- Previous post was at 07:28 PM ----------
s44 said:
Safestrap is next: you'll be able to run custom ROMs but not custom kernels, so TW builds but not AOSP (unless the S5 GPE is built on a TW kernel, as the original 4.2.2 S4 GPE ROM was). I wouldn't actually delete any APKs from your device; just freeze them with Titanium.
Click to expand...
Click to collapse
Wouldn't the bootloader need to be unlocked first?

GlitchMob said:
Sure, but I cannot guarantee you won't have any issues. I managed to remove a decent amount of bloat apps and rebooted successfully. I will list them below.
- Google +
- Google Books
- Google Play Music
- Audible
- VZW protection
- Messaging +
- Amazon
- Kindle
- Amazon Appstore
- IMDB
- VZW ringtones
- VZW protection and support
- Isis Wallet
and a few more that I cannot remember. I hope this helps.
---------- Post added at 07:28 PM ---------- Previous post was at 07:28 PM ----------
Wouldn't the bootloader need to be unlocked first?
Click to expand...
Click to collapse
no.. safestrap doesnt change or effect bootloader which is why youd only be able to install roms compatible with the locked bootloader
Sent from my SM-G900V using XDA Premium HD app

elliwigy said:
chainfire needs to update app before well b able to update it.. it still has root and works so be patient.. we cant keep vzw/samsung from patching it on future devices but it will take them a bit of time so id imagine later updates and newer phones yet to come out would be patched.. now we enjoy root until someone down the road (hopefully) gets us custom recovery for custom roms but lets not jump the gun here, we just got root so let the devs enjoy that feat lol
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
He already updated SU HERE: http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
---------- Post added at 12:31 PM ---------- Previous post was at 12:30 PM ----------
elliwigy said:
chainfire needs to update app before well b able to update it.. it still has root and works so be patient.. we cant keep vzw/samsung from patching it on future devices but it will take them a bit of time so id imagine later updates and newer phones yet to come out would be patched.. now we enjoy root until someone down the road (hopefully) gets us custom recovery for custom roms but lets not jump the gun here, we just got root so let the devs enjoy that feat lol
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
mkitchin said:
I have never run a stock OS rooted. Always AOKP or CM. What should we do now?
-How to we protect it to make sure VZW doesn't somehow patch it?
-I assume we can enable native tethering without FoxFi?
-I know there is some chatter about SuperSu. It fails to update. Need a new version from Chainfire?
-What will we need to do about updates?
-What else?
GeoHot (and others), you are the man (men). Thanks guys. All bounty pledgers, pay up!
Click to expand...
Click to collapse
SU updated here: http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip

elliwigy said:
no.. safestrap doesnt change or effect bootloader which is why youd only be able to install roms compatible with the locked bootloader
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
Would love to see safe strap soon!

Two of the more useful features (I believe) are:
1) native tethering -- http://forum.xda-developers.com/showthread.php?t=2768837
2) download booster -- http://forum.xda-developers.com/showthread.php?t=2719582
There's no concept of recovery, so it would involve uploading the files via adb or some other means and running the scripts via terminal emulator/adb
(1) involves replacing framework-res.apk with the packaged copy -- last time I tried to attempt something like that with a live filesystem I ended up with a bootloop I couldn't resolve and had to reflash the stock ODIN, which I don't want to do at this time.
You can also enable the hidden menus via the phone dialer after root -- change /efs/carrier/HiddenMenu to ON

vacaloca said:
Two of the more useful features (I believe) are:
1) native tethering -- http://forum.xda-developers.com/showthread.php?t=2768837
2) download booster -- http://forum.xda-developers.com/showthread.php?t=2719582
There's no concept of recovery, so it would involve uploading the files via adb or some other means and running the scripts via terminal emulator/adb
(1) involves replacing framework-res.apk with the packaged copy -- last time I tried to attempt something like that with a live filesystem I ended up with a bootloop I couldn't resolve and had to reflash the stock ODIN, which I don't want to do at this time.
You can also enable the hidden menus via the phone dialer after root -- change /efs/carrier/HiddenMenu to ON
Click to expand...
Click to collapse
The custom recovery from this thread: http://forum.xda-developers.com/showthread.php?t=2746586 won't work on ours?

Droid_Evo_8 said:
The custom recovery from this thread: http://forum.xda-developers.com/showthread.php?t=2746586 won't work on ours?
Click to expand...
Click to collapse
Bootloader is still locked on the consumer edition. Cannot flash a recovery.

vacaloca said:
Bootloader is still locked on the consumer edition. Cannot flash a recovery.
Click to expand...
Click to collapse
Gotcha. Too bad, I'm not good on replacing those framework stuff in other for me to have the native tethering and download booster to work.

vacaloca said:
Two of the more useful features (I believe) are:
1) native tethering -- http://forum.xda-developers.com/showthread.php?t=2768837
2) download booster -- http://forum.xda-developers.com/showthread.php?t=2719582
There's no concept of recovery, so it would involve uploading the files via adb or some other means and running the scripts via terminal emulator/adb
(1) involves replacing framework-res.apk with the packaged copy -- last time I tried to attempt something like that with a live filesystem I ended up with a bootloop I couldn't resolve and had to reflash the stock ODIN, which I don't want to do at this time.
You can also enable the hidden menus via the phone dialer after root -- change /efs/carrier/HiddenMenu to ON
Click to expand...
Click to collapse
Have you personally tried the dl booster on the S5?

GlitchMob said:
Have you personally tried the dl booster on the S5?
Click to expand...
Click to collapse
I have not. From the updater script on the 2.1 ODEX zip file on that thread it's replacing these files:
/system/framework/services.jar
/system/framework/services.odex
/system/priv-app/SecSettings.apk
/system/priv-app/SecSettings.odex
I briefly looked through the thread and I don't believe the author of the mod specifically mentioned what the changes he did are. I'd prefer getting the original files from my own phone, extracting/decompiling the contents, making the relevant changes, packaging them back up and replacing them on the phone (after making backups). I'm also lazy, so i'll probably leave that to someone else.

vacaloca said:
I have not. From the updater script on the 2.1 ODEX zip file on that thread it's replacing these files:
/system/framework/services.jar
/system/framework/services.odex
/system/priv-app/SecSettings.apk
/system/priv-app/SecSettings.odex
I briefly looked through the thread and I don't believe the author of the mod specifically mentioned what the changes he did are. I'd prefer getting the original files from my own phone, extracting/decompiling the contents, making the relevant changes, packaging them back up and replacing them on the phone (after making backups). I'm also lazy, so i'll probably leave that to someone else.
Click to expand...
Click to collapse
lol same here. I'll wait till I hear more from people who actually try it.

mkitchin said:
I have never run a stock OS rooted. Always AOKP or CM. What should we do now?
-How to we protect it to make sure VZW doesn't somehow patch it?
-I assume we can enable native tethering without FoxFi?
-I know there is some chatter about SuperSu. It fails to update. Need a new version from Chainfire?
-What will we need to do about updates?
-What else?
GeoHot (and others), you are the man (men). Thanks guys. All bounty pledgers, pay up!
Click to expand...
Click to collapse
Does anyone have a good method for enabling the native hotspot app for free? On my old Motorola RAZR all I had to do was flip the entitlement check with a sql editor. Obviously it's not that easy anymore...

ryanpm939 said:
Does anyone have a good method for enabling the native hotspot app for free? On my old Motorola RAZR all I had to do was flip the entitlement check with a sql editor. Obviously it's not that easy anymore...
Click to expand...
Click to collapse
Apparently xposed framework with X Tether module will do it, according to some replies on the thread I linked to above in post #12.
Edit: Here is the native way to do it:
http://forum.xda-developers.com/showthread.php?t=2759119

Related

[Q] For those of us that didn't update but made modification

I have a straightforward question but I haven't been able to piece together a complete answer from the various threads. I held out doing the AT&T update. In the meantime I have:
Rooted
Updated my stock Email apk to bypass security
Replaced my system.ui to get custom icons on the pull-down menu
Run xPosed Framework with APP settings (to adjust DPI) and Nottach's module.
Can't recall what else
I'm quite happy with everything but I wanted to get updated and prepare to install recovery and all other goodies that are to come with Loki. So, what is the best way for me to get up to date, keep root, and my mods so I can follow along with the progress that will be happening very fast now? Do I have to start over?
I'm sure others have this question also so I appreciate any feedback.
hamzer11 said:
I have a straightforward question but I haven't been able to piece together a complete answer from the various threads. I held out doing the AT&T update. In the meantime I have:
Rooted
Updated my stock Email apk to bypass security
Replaced my system.ui to get custom icons on the pull-down menu
Run xPosed Framework with APP settings (to adjust DPI) and Nottach's module.
Can't recall what else
I'm quite happy with everything but I wanted to get updated and prepare to install recovery and all other goodies that are to come with Loki. So, what is the best way for me to get up to date, keep root, and my mods so I can follow along with the progress that will be happening very fast now? Do I have to start over?
I'm sure others have this question also so I appreciate any feedback.
Click to expand...
Click to collapse
Go to the TWRP thread and do EXACTLY as they thread says to install the recovery, or use goo, it is there now. I was rooted on the MDB stock, and I had root after I installed the recovery. no issues. Did a successful backup, did get a error that required me to delete or rename the KNOX apk files. You will have to that also. Answering your question, I did some minor mods and they were still there perfectly.
Good luck sir.
TheAxman said:
Go to the TWRP thread and do EXACTLY as they thread says to install the recovery, or use goo, it is there now. I was rooted on the MDB stock, and I had root after I installed the recovery. no issues. Did a successful backup, did get a error that required me to delete or rename the KNOX apk files. You will have to that also. Answering your question, I did some minor mods and they were still there perfectly.
Good luck sir.
Click to expand...
Click to collapse
Thanks for replying. I will go that route of it's best. What's the drawback of removing KNOX, if any? What about updating to MDL?
hamzer11 said:
Thanks for replying. I will go that route of it's best. What's the drawback of removing KNOX, if any? What about updating to MDL?
Click to expand...
Click to collapse
You have Knox??
AMDL updating instructions and information should be found in one of the links included in the "Root" sticky in the general forum or in the "motochopper" post in the Original Android development forum.
hamzer11 said:
Thanks for replying. I will go that route of it's best. What's the drawback of removing KNOX, if any? What about updating to MDL?
Click to expand...
Click to collapse
KNOX doesn't work yet, but the APKs are there and cause issues - I'd freeze in TiBu rather than deleting - threads are out there on what to freeze.
And I strongly recommend that you open up a note app and list what you did so you know what you might need to back out or re-do if needed. On the GS3 I have a notepad file with over 60 lines of things to do if I want to full wipe and put everything back JUST the way I had it (including hex codes for colors, ringtones, etc.).
---------- Post added at 08:58 PM ---------- Previous post was at 08:57 PM ----------
scott14719 said:
You have Knox??
AMDL updating instructions and information should be found in one of the links included in the "Root" sticky in the general forum or in the "motochopper" post in the Original Android development forum.
Click to expand...
Click to collapse
Knox is in the system, but not implemented yet - they're aiming for July based on the last new release. But the hooks and APKs are still there.
alacrify said:
KNOX doesn't work yet, but the APKs are there and cause issues - I'd freeze in TiBu rather than deleting - threads are out there on what to freeze.
And I strongly recommend that you open up a note app and list what you did so you know what you might need to back out or re-do if needed. On the GS3 I have a notepad file with over 60 lines of things to do if I want to full wipe and put everything back JUST the way I had it (including hex codes for colors, ringtones, etc.).
---------- Post added at 08:58 PM ---------- Previous post was at 08:57 PM ----------
Knox is in the system, but not implemented yet - they're aiming for July based on the last new release. But the hooks and APKs are still there.
Click to expand...
Click to collapse
Wow I never thought of that. That's very thorough of you.
@TheAxman or anyone that knows, I was able to use Goo manager and load TWRP. Made a backup too and rebooted without issue. Where would I run into the KNOX issue? I haven't had any issues.

NEW OTA UPDATE- MF9.. Questions thread.

Who knew a MONDAY would be such an awesome day! New OTA Update MF9 as 1st reported HERE by @jonathanhtc . Any questions can go here guys....
I'll start off with a question I have: Does this mean that all of our mods will have to be re-done to be able to be flashed on the new update? ie: Hotspot mod, 4 in 1 reboot mod, etc. all have to be re-done to be able to work on the new software update?!
Question that's on everyones mind is:
Are the bootloaders locked? That "Secure boot status: Samsung" thing was not there before if I remember correctly.
xonone said:
Question that's on everyones mind is:
Are the bootloaders locked? That "Secure boot status: Samsung" thing was not there before if I remember correctly.
Click to expand...
Click to collapse
That's why I'm definitely waiting till the devs take a look at it before I download it. It definitely wasn't there with MDC and MDL.
Sent from my SPH-L720 using xda app-developers app
Yes same here. BUT some new things that were reported are: Transparent notification bar with any wallpaper, new smart pause toggle, smoother UI (less lag), move apps to SD card, and KNOX is finally deployed along with Briefing and SPDclient.
First things first. Let's see what partitions got an update.
And someone should put a bug in Agat's ear to patch his kernel with the latest updates.
garwynn said:
First things first. Let's see what partitions got an update.
And someone should put a bug in Agat's ear to patch his kernel with the latest updates.
Click to expand...
Click to collapse
I already posted in his thread about an hour ago that source is up
Sent from my SPH-L720 using Tapatalk 4 Beta
I wonder if this is basically the same update that the international version got. Hopefully it is, and it fixes the "smearing issue" and also we get the HDR video recording!
I heard people were unable to unlock to use internationally. Some said sprint unlocked but software restrictions remained. Do you think this update might fix that? And im not talking for use withing the U.S. mainly outside (Europe)
Sent from my SPH-L720 using Tapatalk 2
Okay, new bootloader, modem, kernel.
2 secondary bootloaders updated as well as rpm and tz.
Interesting that everything backs up to mmcblk0p22 before writing the new one.
Don't recall seeing that in updates for other devices.
New Fingerprint is just swap out MDL with MF9.
As mentioned, Knox is there. Makes me wonder what else was locked down with it.
Updated OCR among many updated binaries.
A lot of the binaries - in particular, vendor blobs - have an update.
I'll need someone to dump the system partition once it's patched for the new vendor files.
Hopefully good news for AOSP builds.
I'm asking to see if the previous sources have any info - but they've already stated not to expect anything.
There are a few questions that need to be figured out:
1) What is in the new bootloader? Are we locked like most of the others?
2) Can we revert bootloaders after flashing - and if so, what does it take to do so?
3) Root on new build?
All of this is going to require a test device, which sadly at the moment I am now without.
All the problems with the N2 left me with a Spare N2 and now without an S4.
xonone said:
Question that's on everyones mind is:
Are the bootloaders locked? That "Secure boot status: Samsung" thing was not there before if I remember correctly.
Click to expand...
Click to collapse
bootloader isnt locked, mine is already back to rooted with twrp. that secured by samsung is the new knox stuff, so you can assign your own bootloader chain etc. i dont know all the details nor do i pretend to, but what i do know is its for companies to lock their phones down and not a concern to us
shabbypenguin said:
bootloader isnt locked, mine is already back to rooted with twrp. that secured by samsung is the new knox stuff, so you can assign your own bootloader chain etc. i dont know all the details nor do i pretend to, but what i do know is its for companies to lock their phones down and not a concern to us
Click to expand...
Click to collapse
Could you post the steps you used to update & restore root please?
illdini said:
Could you post the steps you used to update & restore root please?
Click to expand...
Click to collapse
you apply the ota, flash recovery via odin and then flash supersu. if youd rather skip a step im pretty sure you can use ota root keeper
shabbypenguin said:
you apply the ota, flash recovery via odin and then flash supersu. if youd rather skip a step im pretty sure you can use ota root keeper
Click to expand...
Click to collapse
When applying the OTA, were you rooted and flashed with a Custom Recovery (i.e.-CWM or TWRP)? Or were you completely stock?
chenry944 said:
When applying the OTA, were you rooted and flashed with a Custom Recovery (i.e.-CWM or TWRP)? Or were you completely stock?
Click to expand...
Click to collapse
Judging by his earlier post I'm guessing custom recovery is probably not the best way to flash.
I have the same question BTW I'm rooted, with TWRP recovery, but stock ROM. Have installed a few mods (hotspot, camera shutter sound disabled. Had XPosed framework installed with a couple of mods, but removed those later).
What would be the safe way for me to install the new update? I actually like some of the features that Samsung added, so not looking to switch away from stock ROM for now.
I'm hoping that knowledgeable developers will provide guidance in the next few days
jj14 said:
Judging by his earlier post I'm guessing custom recovery is probably not the best way to flash
Click to expand...
Click to collapse
Yea I read that post I am just trying to get clarification for myself and everyone else in which way he did flash it.
shabbypenguin said:
bootloader isnt locked, mine is already back to rooted with twrp. that secured by samsung is the new knox stuff, so you can assign your own bootloader chain etc. i dont know all the details nor do i pretend to, but what i do know is its for companies to lock their phones down and not a concern to us
Click to expand...
Click to collapse
Best news of this thread! Thanks for taking the chance!
Sent from my SPH-L720 using Tapatalk 4 Beta
yea i was stock odex from crawj and i hit errors while flashing it twrp, i flashed stock kernel and stock recovery and tried and it still failed so i modded teh zip to forcibly install, i now have no mobile data and my modem isnt updated. so my suggestion, dont follow my lead
im currently flashing MDC stock tar to fully update all the way.
Got the Modem Updated to MF9 using Odin without going back to Stock, uploading the odin package now, and will be updating the thread here -> http://forum.xda-developers.com/showthread.php?t=2338919
Does this include the security update Google announced would be coming to OEMs?
Now if i update to mf9, will it affect custom roms that are built around MDL, or AOSP?

What root method have you tried?

I want to get a list of root methods people have tried and which ones have been successful.
Kingo Root seems to be the most discussed method, but various reports have raised questions about whether it steals data. Looks as though the official policy on XDA is that it's in limbo until deemed safe:
http://forum.xda-developers.com/showpost.php?p=47111019&postcount=65
Someone else suggested OneClickRoot.com:
http://www.oneclickroot.com/phone/lg-g-pad-8-3/
This method is widely used and from my research, considered safe by most people, but I don't know if anybody has used it successfully on a G Pad.
Please report in this thread what method you've tried and what worked.
I have tried Framaroot 1.7 but it did not work.
Sent from my SCH-I815 using Tapatalk 4
woody1 said:
I want to get a list of root methods people have tried and which ones have been successful.
Kingo Root seems to be the most discussed method, but various reports have raised questions about whether it steals data. Looks as though the official policy on XDA is that it's in limbo until deemed safe:
http://forum.xda-developers.com/showpost.php?p=47111019&postcount=65
Someone else suggested OneClickRoot.com:
http://www.oneclickroot.com/phone/lg-g-pad-8-3/
This method is widely used and from my research, considered safe by most people, but I don't know if anybody has used it successfully on a G Pad.
Please report in this thread what method you've tried and what worked.
Click to expand...
Click to collapse
I rooted following this link. Worked for me.
http://forum.xda-developers.com/showthread.php?p=48083981
After rooting I replaced superuser with supersu from play store since this is best for GMD to work. I am happy?
Sent from my LG-V500 using XDA Premium 4 mobile app
abdulm said:
I rooted following this link. Worked for me.
http://forum.xda-developers.com/showthread.php?p=48083981
After rooting I replaced superuser with supersu from play store since this is best for GMD to work. I am happy?
Click to expand...
Click to collapse
I used the same method and also replaced Superuser with Supersu. And I installed Busybox from Google Play. The script works great! I would recommend that everbody who has not yet rooted use this method and not Kingo.
woody1 said:
The script works great! I would recommend that everbody who has not yet rooted use this method and not Kingo.
Click to expand...
Click to collapse
+1
what are the advantages of replacing superuser with supersu? Is it an easy procedure to replace it?
katsika said:
+1
what are the advantages of replacing superuser with supersu? Is it an easy procedure to replace it?
Click to expand...
Click to collapse
I think the two apps are pretty similar. I read reviews that said that SuperSU was better for later versions of Android and Superuser was better for older versions. I've been using SuperSU on my phone for a while, so I'm more familiar with it. Probably doesn't matter much which one you use.
As far as switching the apps, just uninstall Superuser and install SuperSU.
woody1 said:
I think the two apps are pretty similar. I read reviews that said that SuperSU was better for later versions of Android and Superuser was better for older versions. I've been using SuperSU on my phone for a while, so I'm more familiar with it. Probably doesn't matter much which one you use.
As far as switching the apps, just uninstall Superuser and install SuperSU.
Click to expand...
Click to collapse
Agree. Supersu is faster in granting permissions on every boot and is considered better suitable for OS JB and above
Sent from my LG-V500 using XDA Premium 4 mobile app
abdulm said:
I rooted following this link. Worked for me.
http://forum.xda-developers.com/showthread.php?p=48083981
After rooting I replaced superuser with supersu from play store since this is best for GMD to work. I am happy?
Sent from my LG-V500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I also just rooted using this method - works as advertised. Simple. All set for custom ROMs now.
abdulm said:
Agree. Supersu is faster in granting permissions on every boot and is considered better suitable for OS JB and above
Sent from my LG-V500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I deleted super user and downloaded supersu and it says im no longer rooted.
Faded_329 said:
I deleted super user and downloaded supersu and it says im no longer rooted.
Click to expand...
Click to collapse
Can you root again as per the link in my previous post and then install supersu from playstore. Supersu will detect superuser and it will ask to delete it. This is how I did.
Faded_329 said:
I deleted super user and downloaded supersu and it says im no longer rooted.
Click to expand...
Click to collapse
Open up a terminal app (say, Connectbot), Connect to local. When you get a $ prompt, type 'su'. If you get a # prompt, you're rooted.
abdulm said:
Can you root again as per the link in my previous post and then install supersu from playstore. Supersu will detect superuser and it will ask to delete it. This is how I did.
Click to expand...
Click to collapse
thanks just did that, now i want to add a recovery which one do you think is better.
abdulm said:
Can you root again as per the link in my previous post and then install supersu from playstore. Supersu will detect superuser and it will ask to delete it. This is how I did.
Click to expand...
Click to collapse
about the apps that require root, should i uninstall them and reinstall them?
Faded_329 said:
thanks just did that, now i want to add a recovery which one do you think is better.
Click to expand...
Click to collapse
Glad it worked I haven't tried changing recovery yet, sorry not in a position to comment.
I am experimenting with root apps now, will wait for sometime to try mods...
downloaded twrp
You can use SuperSU and there's nothing wrong with that but there's also nothing wrong with Superuser.
It works fine for new versions of Android, in fact it is what is built into CM11.
I think people are confusing the Superuser I included with the old Superuser made by ChainsDD. I included Superuser by Koush/Clockwork Mod because it is open source and used by CyanogenMod.
When it comes to an app that is so important to maintaining security then I stick with open source.
dalingrin said:
You can use SuperSU and there's nothing wrong with that but there's also nothing wrong with Superuser.
It works fine for new versions of Android, in fact it is what is built into CM11.
I think people are confusing the Superuser I included with the old Superuser made by ChainsDD. I included Superuser by Koush/Clockwork Mod because it is open source and used by CyanogenMod.
When it comes to an app that is so important to maintaining security then I stick with open source.
Click to expand...
Click to collapse
This is exactly what I was thinking while reading through this thread. Can't wait to see CM11 on the G-Pad, even though mine won't come in until Monday. Damn winter weather.
dalingrin said:
You can use SuperSU and there's nothing wrong with that but there's also nothing wrong with Superuser.
It works fine for new versions of Android, in fact it is what is built into CM11.
I think people are confusing the Superuser I included with the old Superuser made by ChainsDD. I included Superuser by Koush/Clockwork Mod because it is open source and used by CyanogenMod.
When it comes to an app that is so important to maintaining security then I stick with open source.
Click to expand...
Click to collapse
Fair enough, i have cyanogen in my samsung tab 2 and i never experienced any issues about it, and neither in my gpad. Thnx for clarifying this!

Double check before I root

I just acquired a GS4 from ATT today. it is:
Android 4.4.2 (which I upgraded myself)
Baseband V: I337UCUFNC1
I found this thread http://forum.xda-developers.com/showthread.php?t=2663545 But I wanted to make sure there is not anything newer or different since then. I wasn't able to find anything else by searching. I'm trying to root this phone to use CyanogenMod. Unfortunately, my phone is not supported in their list of easy installs.
Can someone verify the steps for me to root and flash Cyan to this model phone before I pull the trigger? Thanks!
burgertime78 said:
I just acquired a GS4 from ATT today. it is:
Android 4.4.2 (which I upgraded myself)
Baseband V: I337UCUFNC1
I found this thread http://forum.xda-developers.com/showthread.php?t=2663545 But I wanted to make sure there is not anything newer or different since then. I wasn't able to find anything else by searching. I'm trying to root this phone to use CyanogenMod. Unfortunately, my phone is not supported in their list of easy installs.
Can someone verify the steps for me to root and flash Cyan to this model phone before I pull the trigger? Thanks!
Click to expand...
Click to collapse
You can't flash anything other than Touch Wiz Roms. That guide and ones like The Ultimate All in one Guide will be a starting place. No custom recoveries either.
Sent from my GT-I9505G using Tapatalk
rugmankc said:
You can't flash anything other than Touch Wiz Roms. That guide and ones like The Ultimate All in one Guide will be a starting place. No custom recoveries either.
Sent from my GT-I9505G using Tapatalk
Click to expand...
Click to collapse
So what's the problem? ATT? too new a hardware version? I have the worst luck with this stuff - if I buy a router to flash a custom firmware like Tomato, it's the ONLY version that isn't supported. crazy.
I'm not sure what a custom recovery is unfortunately. That said, can I root this phone at all? I guess if I can't flash the rom I want to use, can I at least install titanium and freeze all the crapware that I don't want running?
btw - thanks for the response.
burgertime78 said:
So what's the problem? ATT? too new a hardware version? I have the worst luck with this stuff - if I buy a router to flash a custom firmware like Tomato, it's the ONLY version that isn't supported. crazy.
I'm not sure what a custom recovery is unfortunately. That said, can I root this phone at all? I guess if I can't flash the rom I want to use, can I at least install titanium and freeze all the crapware that I don't want running?
btw - thanks for the response.
Click to expand...
Click to collapse
Any build after mdl has the bootloader locked down. If you read thru those two threads OP pages you get an idea. You will also need to get familiar with SafeStrap. I am on the old build and can use an exploit called loki-doki to bypass Sammy's security check and allow kernel to flash.
There may be some new stuff on rooting NC1, but I don't keep up. Basically you had to go back to mk2 to root then go back NC1 and use SafeStrap to flash only TW roms. The SafeStrap thread will explain that. But, it creates slots on the System partition again fooling Sammy. More or less--
Like I said not an expert as I don't have the issue you have with bootloader. But that is the gist of it. Just need to read up so you don't brick--good luck.
rugmankc said:
Any build after mdl has the bootloader locked down. If you read thru those two threads OP pages you get an idea. You will also need to get familiar with SafeStrap. I am on the old build and can use an exploit called loki-doki to bypass Sammy's security check and allow kernel to flash.
There may be some new stuff on rooting NC1, but I don't keep up. Basically you had to go back to mk2 to root then go back NC1 and use SafeStrap to flash only TW roms. The SafeStrap thread will explain that. But, it creates slots on the System partition again fooling Sammy. More or less--
Like I said not an expert as I don't have the issue you have with bootloader. But that is the gist of it. Just need to read up so you don't brick--good luck.
Click to expand...
Click to collapse
DAMN! Thanks!
burgertime78 said:
DAMN! Thanks!
Click to expand...
Click to collapse
Good Luck
There are plenty of folks here to help with specifics like jd and tedusa--:good:
burgertime78 said:
I just acquired a GS4 from ATT today. it is:
Android 4.4.2 (which I upgraded myself)
Baseband V: I337UCUFNC1
I found this thread http://forum.xda-developers.com/showthread.php?t=2663545 But I wanted to make sure there is not anything newer or different since then. I wasn't able to find anything else by searching. I'm trying to root this phone to use CyanogenMod. Unfortunately, my phone is not supported in their list of easy installs.
Can someone verify the steps for me to root and flash Cyan to this model phone before I pull the trigger? Thanks!
Click to expand...
Click to collapse
New way to root is call towelroot. Google it or search for it around here the link is everywhere. It's an apk file made by geohot (same guy that jail broke the iphone and ps3). Once you root you can install safestrap. If you've ever owned an droid device they have something identical called boot strap. Think of it as a dual boot of sorts. Definitely keep your eyes on these threads as well as the sgs5 thread. If an exploit is discovered it'll probably be for the s5 and will be compatible with our s4 (towel root was made for the s5 but works for a whole bunch of devices)
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
burgertime78 said:
DAMN! Thanks!
Click to expand...
Click to collapse
Link: http://forum.xda-developers.com/showpost.php?p=52167774&postcount=3&nocache=1&z=8413408249616623
I was in the same boat as you 2 weeks ago, bought a NC1 and wanted CM, and used this to root. I currently use the Google Edition ROM that has been modified to work on locked bootloader phones, though it does have it's fallbacks. For someone new I'd recommend GoldenEye, just click the link on my signature to download it.
Good luck!
Oh, btw--check out GEOHOT's Towelroot thread in General for NC1. I knew I forgot one. That was the recent method I was thinking of. Not sure which of threads are best for you--depends what you want to do.
---------- Post added at 10:38 PM ---------- Previous post was at 10:37 PM ----------
HaHa posted at same time.
You all are AWESOME! Thank you so much! I'll look into this and keep you posted.
rugmankc said:
Oh, btw--check out GEOHOT's Towelroot thread in General for NC1. I knew I forgot one. That was the recent method I was thinking of. Not sure which of threads are best for you--depends what you want to do.
---------- Post added at 10:38 PM ---------- Previous post was at 10:37 PM ----------
HaHa posted at same time.
Click to expand...
Click to collapse
I just towelrooted. It worked! I was watching this video http://gs5.wonderhowto.com/how-to/r...nt-even-at-t-verizon-20-seconds-flat-0155617/ and I did it while I Was watching the video. On my device, it did not even reboot - i just said "should be rooted" so I loaded a root checker and sure enough, it is rooted! took all of about 8 seconds.
Now, on to a rom.
I'm confused now. Why can I not use CM? I read about SafeStrap and I understand it's sort of a dual boot setup - I get that. So, in a sense, I'm not really installing FRESH, a new rom - at least not in the sense that you format your hard disk and install a new OS. However, what ARE my choices in roms? I know the whiz touch, and now the golden eye, plus the google modified - but what else? I want something cut down, simple and battery friendly. I'm not a super power user and I don't require much. Actually, battery life is the most important thing to me.
This is my business phone - I use Gmail, SMS, maybe take a few pictures - and I listen to podcasts. very basic user. Advice?
burgertime78 said:
I just towelrooted. It worked! I was watching this video http://gs5.wonderhowto.com/how-to/r...nt-even-at-t-verizon-20-seconds-flat-0155617/ and I did it while I Was watching the video. On my device, it did not even reboot - i just said "should be rooted" so I loaded a root checker and sure enough, it is rooted! took all of about 8 seconds.
Now, on to a rom.
I'm confused now. Why can I not use CM? I read about SafeStrap and I understand it's sort of a dual boot setup - I get that. So, in a sense, I'm not really installing FRESH, a new rom - at least not in the sense that you format your hard disk and install a new OS. However, what ARE my choices in roms? I know the whiz touch, and now the golden eye, plus the google modified - but what else? I want something cut down, simple and battery friendly. I'm not a super power user and I don't require much. Actually, battery life is the most important thing to me.
This is my business phone - I use Gmail, SMS, maybe take a few pictures - and I listen to podcasts. very basic user. Advice?
Click to expand...
Click to collapse
MDL builds have an exploit that allows the kernel to flash. That is loki-doki. Bypasses the Sammy security check to allow this. There is no exploit yet for post MDL builds. Hence you can only flash stock Touch Wiz kernels, thus only roms that have them. So, no aosp based roms. In one of the threads in General that talk about MK2/NC1 etc is a list of roms for you. I forget the technical coding side of SafeStrap. But, it puts roms in System bypassing the bootloader. But, no way of doing that with aosp roms yet.
I am old and don't retain things much anymore if they are not very important to me. So, although I have read up on this stuff, and have a "45 year old" Engineering Degree, I don't need SafeStrap having the MDL bootloader. So, don't remember all that I have read. But, what I said is the basics of it.
Your roms need to have SafeStrap option in the rom thread's OP page. If not listed, it won't work. Having said all that things like Towelroot are new and more options may come along. :good:

Any interest in an unrooted insanely debloated ROM?

The ENG kernel used for root is great in a sense that it has aided in giving us root access, but it is nowhere near as refined as the factory kernel. @psouza4 has done a TON to make this kernel awesome, but there are a lot of people who have reverted back to stock because of the limitations.
I'm considering making an insanely debloated ROM that will hopefully run on the factory PE1 kernel. Root access would be needed to do the initial install with FlashFire, but afterwards there would be no root access. This might be what a few of you guys are looking for, a blazing fast ROM that runs forever on a charge, without getting hot. Once the ROM is flashed, there will be NO ability to modify unless the ENG kernel is flashed and rooted again. This ROM would NOT be for anyone interested in running Xposed framework in anyway.
If there is enough interest, I'll start working on something FAST!
Definitely interested in this
Extremely interested.
Could you throw in a modified hosts file for ad blocking? Or, should I mod it first then unroot? Also, would bypassing the checks for tethering be an option before going back to original kernel?
Illogi.xbone said:
Could you throw in a modified hosts file for ad blocking? Or, should I mod it first then unroot? Also, would bypassing the checks for tethering be an option before going back to original kernel?
Click to expand...
Click to collapse
I'm hoping to include some mods like this. I believe I'll be able to modify the host file, but you would not be able to update the hosts once the ROM is installed.
CVertigo1 said:
I'm hoping to include some mods like this. I believe I'll be able to modify the host file, but you would not be able to update the hosts once the ROM is installed.
Click to expand...
Click to collapse
Great! I was thinking of trying something along this route. I will make a flashfire backup of internal first then could give it a go.
I'll keep you posted when I have something worthy of flashing.
Wont future updates just re-bloat the rom?
CVertigo1 said:
I'll keep you posted when I have something worthy of flashing.
Click to expand...
Click to collapse
Thank you! Mostly root for adaway anyways lol
freak69ize said:
Wont future updates just re-bloat the rom?
Click to expand...
Click to collapse
The ROM would prevent future updates, so all updates would be done via re-root and flash.
CVertigo1 said:
The ROM would prevent future updates, so all updates would be done via re-root and flash.
Click to expand...
Click to collapse
Yeah.. very interested then... as long as you keep theme store in it
Awesome
This is exactly what I was looking for! I'd be eternally grateful if you did it.
I would love to see something like this!
My question is, since I can always at least disable bloat, can I make some changes (provisioning for tethering, modified hosts file) then unroot and reflash stock kernel?
The only reason I wanted root is for viper4android/audio mods. Would an unrooted rom be able to include that?
Sent from my SM-G930V using Tapatalk
fronc01 said:
The only reason I wanted root is for viper4android/audio mods. Would an unrooted rom be able to include that?
Sent from my SM-G930V using Tapatalk
Click to expand...
Click to collapse
That's an interesting question. Some optimizations like that could be added. But that app wouldn't work since it requires root privileges.
Sent from my SM-G930V using XDA-Developers mobile app
This will be great. An insanely debloated stock VZR 935U ROM with non-provisioned tethering, HD calling, and VVM is all that that's needed to make this the ultimate phone. Everything else that's need for full VZW functionality can be installed from the Play Store.
However, how would you go back to the stock kernel after installing this ROM? Just by flashing the stock AP in Odin?
I'd be stoked if this phone had stock mm status bar icons that's the only thing I've honestly really used root for and it still doesn't say LTE but instead the ugly 4G icon.. I'd even be alright with Verizons icon if it wasn't persistent on WiFi but then they're still ics looking signal bars. My s7 runs rather warm and battery drain rather sucks with the eng. Kernel starting to think it's not quite worth being able to themeish my status bar. I'd be interested in a debloated stock rom with HD calling if you can throw in the status bar that's icing on the cake.
Sorry for not checking the thread lately. I'm still trying to figure out how to make this work. I have some ideas, but nothing concrete yet.
This isn't going to work. DM-Verity checks will cause the phone not to boot once the original kernel is flashed back. If there is even a byte changed in the system partition it will make the hash invalid and cause the DM-Verity check to fail. The only debloating you can possibly do is simply disabling packages. (In the event of not wanting the Engineering kernel/root.)

Categories

Resources