Hey! So I'm trying to root my device. I already ran an old rooting method using Odin, but when I tried to use it afterwards Knox was tripped. This led to finding Saferoot.
I've tried it a few times, only for it to get stuck at trying to disable Knox.
Code:
--- Samsung Galaxy S4 Android 4.3 Root ---
--- Based on the CVE-2013-6282 exploit by cubeundcube ---
[*] Testing adb usability
Plug in your phone and Press any key to continue . . .
[*] Waiting for your phone to appear
[*] Your phone is detected and ready for rooting.
[*] Sending files to your device...
[*] Starting rooting program.
ro.build.product=t03g
ro.build.id=JSS15J
search kallsyms...
1
(kallsyms_addresses=c082efb0)
(kallsyms_num_syms=0000ef10)
kernel dump...
1 2 3 4 5 6 7 8 9
prepare_kernel_cred=c00c04c4
commit_creds=c00bfcb0
ptmx_fops=c0bda36c
ptmx_open=c02bb450
tty_init_dev=c02b3ff0
tty_release=c02b3a4c
tty_fasync=c02b117c
ptm_driver=00000000
Succeeded in getroot!
Remount success!
Copying files..
Done.. reboot to enable root!
[COLOR="Red"](I don't actually need to reboot here, it just goes on to the next step)[/COLOR]
[*] Checking if rooting succeeded
[*] Removing temporary files...
[*] Trying to disable Knox...
Usually the program just hangs here indefinitely, but one time it rebooted my phone and tried to run SuperSU, only for it to be blocked by Knox. My phone seems to be rooted according to Simple Root Checker - it says Application Superuser found, Terminal Rooted, Busybox installed, and Busybox v1.21.1 - so I guess that the old method of rooting did work, but Knox remains.
Any ideas?
[edit] The additional text which shows after a reboot. Obviously I was unable to actually start SuperSU to update it.
Code:
[*] Checking if rooting succeeded
[*] Removing temporary files...
[*] Trying to disable Knox...
[*] Rebooting... Please wait.
[*] Waiting for device to re-appear...
Wait until your phone reboots,then unlock it and Press any key to continue . . .
On your phone, open SuperSU and let it update if it asks.
When SuperSU is done updating, Press any key to continue . . .
On your phone, watch for the SuperSU permission popup and give
permission for ADB Shell to gain root permissions.
I have to quit it manually thereafter.
Just to note, Knox is tripped every time saferoot tries to disable it.
Tuppence_ said:
Hey! So I'm trying to root my device. I already ran an old rooting method using Odin, but when I tried to use it afterwards Knox was tripped. This led to finding Saferoot.
I've tried it a few times, only for it to get stuck at trying to disable Knox.
Code:
--- Samsung Galaxy S4 Android 4.3 Root ---
--- Based on the CVE-2013-6282 exploit by cubeundcube ---
[*] Testing adb usability
Plug in your phone and Press any key to continue . . .
[*] Waiting for your phone to appear
[*] Your phone is detected and ready for rooting.
[*] Sending files to your device...
[*] Starting rooting program.
ro.build.product=t03g
ro.build.id=JSS15J
search kallsyms...
1
(kallsyms_addresses=c082efb0)
(kallsyms_num_syms=0000ef10)
kernel dump...
1 2 3 4 5 6 7 8 9
prepare_kernel_cred=c00c04c4
commit_creds=c00bfcb0
ptmx_fops=c0bda36c
ptmx_open=c02bb450
tty_init_dev=c02b3ff0
tty_release=c02b3a4c
tty_fasync=c02b117c
ptm_driver=00000000
Succeeded in getroot!
Remount success!
Copying files..
Done.. reboot to enable root!
[COLOR="Red"](I don't actually need to reboot here, it just goes on to the next step)[/COLOR]
[*] Checking if rooting succeeded
[*] Removing temporary files...
[*] Trying to disable Knox...
Usually the program just hangs here indefinitely, but one time it rebooted my phone and tried to run SuperSU, only for it to be blocked by Knox. My phone seems to be rooted according to Simple Root Checker - it says Application Superuser found, Terminal Rooted, Busybox installed, and Busybox v1.21.1 - so I guess that the old method of rooting did work, but Knox remains.
Any ideas?
[edit] The additional text which shows after a reboot. Obviously I was unable to actually start SuperSU to update it.
Code:
[*] Checking if rooting succeeded
[*] Removing temporary files...
[*] Trying to disable Knox...
[*] Rebooting... Please wait.
[*] Waiting for device to re-appear...
Wait until your phone reboots,then unlock it and Press any key to continue . . .
On your phone, open SuperSU and let it update if it asks.
When SuperSU is done updating, Press any key to continue . . .
On your phone, watch for the SuperSU permission popup and give
permission for ADB Shell to gain root permissions.
I have to quit it manually thereafter.
Just to note, Knox is tripped every time saferoot tries to disable it.
Click to expand...
Click to collapse
First try to update SuperSu manually it'd probably works.
Have you installed Knox full application which is around 150 Mbs? Then uninstall tha app and repeat the procedure.
If SuperSU is not working. Go to Application manager and try to uninstall. If u can not then re-flash 4.3 from Computer Odin to get rid of Corrpt SpuerSU.
Downgrade from 4.3 to 4.1.2. I have done this with 100% Success
BACKUP everything. (Important)
Turn ON USB Debugging mode and Unknown sources.
First ROOT your phone.
Open Playstore and Update SuperSU. Open SuperSU and it will give a message to disable KNOX. Click YES/Ok.
Then install Titanium backup root from Playstore. Open it, go to backup/restore tab.
Find,
1.com.sec.enterprise.knox.attestation
2.com.sec.knox.eventsmanager
3.KLMS Agent
4.KNOX
5.Knox Notification Manager
6.KNOX Store
Go to each one of it and Uninstall them.
Next restart your phone.
*VERY IMPORTANT* Now Backup your efs folder by using EFS Professional on you computer (Link: http://d-h.st/Gfo ). Because your imei number will be changed after downgrading. You can easily restore it later.
Now install Mobile Odin Pro from Playstore on your phone. Here is the link.
https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro
*IMPORTANT* DO NOT flash firmware for downgrading with Computer Odin as it will NOT work and it will FAIL. *ONLY Mobile Odin Pro from Playstore will work.
Copy your 4.1.2 firmware to your phone. Next Open Mobile Odin Pro on your phone and let it download some necessary files from internet.
When done, click on Open file and select the firmware. After loading the firmware scroll down and UNCHECK EverRoot(because it cause problems). Then click on FLASH Firmware.
*IMPORTANT* If your phone get stuck on samsung logo. Go into recovery mode by pressing Home+Power+Volume UP keys together for 15 seconds. Click Factory wipe/data and then Wipe Cache. Then Reboot.
Now check your imei by *#06#. If imei is changed then restore it from EFS Professional.
Baller231 said:
Downgrade from 4.3 to 4.1.2. I have done this with 100% Success
Click to expand...
Click to collapse
That would be awesome, but I am not sure if it will work for everybody. What phone/carrier did you use?
I am afraid to try it out, because I heard some attempt will results in a hard brick that can only be fixed using Jtag.
Thanks!
Related
!!This is ONLY for Elocity A7!!!
This Mod is based on Elocity Stock with additions from Nvidia SDK, to make a better functioning stock rom with google apps.
You can also follow updates on Twitter now: Dexter Picard (DexterPicard) on Twitter or
for the continued support or you can visit my homepage at Dexter's mods
I Thought this demo deserved to be posted with my Mod for ElocityA7
I get some creds here too , thanks!
Installation Instructions:
ALWAYS HAVE CHARGER CONNECTED WHEN UPDATING A FIRMWARE
Download ElocityMod v1.42 patch update
Download ElocityMod v1.41
It will require Wipe/factory reset as well. as reports on the update seems to report some problems if not, so its your own if it does FC alot, if you do not wipe
PATCHES
installs like regular full updates: rename to Update.zip and run recovery.
- v1.xx Adhoc patch here if you need connecting to mobile teetering app, it will not autostart wifi after sleep.
Previous releases
Download ElocityMod v1.3
Download ElocityMod v1.2
Install using recovery menu.
copy the file to the root of your sdcard and rename to Update.zip.
Enter "Recovery menu" by pressing power for 2seconds, release
then hold power button until "hold power 5sec...." appear and wait until it says booting recovery kernel..and release power button.
Press "HOME" button to see menu, use SEARCH/BACK button to navigate.
select "Wipe/factory reset" - press MENU key to activate
then select "apply sdcard:update.zip" - press MENU to activate
after the small install process - press "reboot" to finalize and wait for the upgrade to take place on second screen that appear.
[/INDENT]
ISSUES
- Files manager app does FC too much, use the OI filemanager for local filehandling.
CHANGELOG
v1.42
- added latest 17-04 update from ElocityA7 update.
- Fixed sdcard problem, you can now eject/insert as much as wanted.
alternate patch is now removed.
v1.41
- build.prop (ro.kernel.android.checkjni=false) enables Skype to function (and maybe other apps)
- usb stick support added.
- changed sdcard handler to stock, but with exception it only work until you eject sdcard/usb , and a reboot is only way to remount (or restart vold daemon which is from a shell)
- honeycomb bootanimation added.
- Files app added (for copying network files to tablet) is buggy with pictures handling in folders. (might be removed again)
- VPN (script + vpn settings enabled/added)
- HDMI resolution changer added in settings (480p -> 1080p output available)v1.4
- Based on latest 24-02 update from Elocity.
- Cracked the sdcard issue, and its fully working now..
- Added patched hulu Flashplayer 10.2 (uninstall this one first, if you download it from market)
- New calendar appv1.3
- finally latest Market app included (2.2.7 will be upgraded to 2.2.11 when you enter market the first time)
- Added Gsensor fix, so screen rotation works, if playing games that need sensor like SpeedX or racing games..
- Added DSP audio manager with EQU function (does help increasing volume a little too)
- re-arranged process, so installers do not keep trying to install apps.v1.2
- Updated to latest stock of Feb-04 .
- removed wifi Settings again, solution did not work (im told)
- Fixed Calendar app FC.
- Updated Market to the latest release.
THANKS to all who donated up to now! its appreciated, and shows that people like the extras added...
WARNING: Use this image at your own risk and i take no responsibility if you brick your tablet..
Reserved for future use..
This will be very helpful for a lot people. Great of you to put this together for everyone!
Just curious, what's the advantage of having the superuser app when the device is rooted out of the box?
I look forward to seeing what else can happen with this device, and would be happy to test if needed.
DroidxRage said:
Just curious, what's the advantage of having the superuser app when the device is rooted out of the box?
Click to expand...
Click to collapse
although its already in non-secure mode, the apps that run "su" dont recognise it, so the root app is required together with its "su" command.
and it actually also have the advantage of you being in control of which apps get root access..
although your "adb shell" is in a root shell, the apps running still has non-su rights to the system, otherwise its would be pretty open as well and without much security.
I went ahead and applied version 1.0a over 1.0. I didn't take the time to do a backup so I didn't wipe/factory reset first. Everything went well, but calendar still gets a force close upon launch (not a problem for me, I don't need it). I may go ahead and wipe it and reinstall 1.0a, but I'm very happy with it as is for now.
Thanks again for making this rom! I'll hit that donate button for sure.
Thanks Dexter, tossed a donation your way.
I couldn't get root access back so I'm rerunning the update after a full wipe of data and cache. I will let you know how it goes.
rich_e said:
I went ahead and applied version 1.0a over 1.0. I didn't take the time to do a backup so I didn't wipe/factory reset first. Everything went well, but calendar still gets a force close upon launch (not a problem for me, I don't need it). I may go ahead and wipe it and reinstall 1.0a, but I'm very happy with it as is for now.
Thanks again for making this rom! I'll hit that donate button for sure.
Click to expand...
Click to collapse
rich_e said:
I couldn't get root access back so I'm rerunning the update after a full wipe of data and cache. I will let you know how it goes.
Click to expand...
Click to collapse
I lost root access loading this rom too. It tried to update su but couldn't.
DroidxRage said:
I lost root access loading this rom too. It tried to update su but couldn't.
Click to expand...
Click to collapse
Couldnt install the su zip file it put on my sd either..
I couldn't get SU to update either (placed on SD card as update.zip, but no joy). Just for grins I tried Z4root too, it went through the motions but no root. I tried to use Titanium Backup to install busybox. It downloaded the binaries but nothing changed.
DroidxRage said:
I lost root access loading this rom too. It tried to update su but couldn't.
Click to expand...
Click to collapse
rich_e said:
I couldn't get SU to update either (placed on SD card as update.zip, but no joy). Just for grins I tried Z4root too, it went through the motions but no root. I tried to use Titanium Backup to install busybox. It downloaded the binaries but nothing changed.
Click to expand...
Click to collapse
I cant see what the problem is... dex any ideas?
I may flash the offocial update, reinstall the modified build.prop, and reinstall market.
The was a post somewhere in the BJ's 299 thread about busybox not installing correctly due to differences in the directory structure on this device, which caused loss of root.
rich_e said:
The was a post somewhere in the BJ's 299 thread about busybox not installing correctly due to differences in the directory structure on this device, which caused loss of root.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=10097888&postcount=750
Gonna try that now
DroidxRage said:
http://forum.xda-developers.com/showpost.php?p=10097888&postcount=750
Gonna try that now
Click to expand...
Click to collapse
This didn't work... other than this superuser permissions being messed up everything else works stellar!
If we don't have anything soon, I'll flash back and poke around with the modified build.prop on the official build.
Edit: Reinstalled the official elocity update and got my root back, installed gapps, now updating build.prop. Hopefully this gets me all the market fixes minus that Su thing. Superuser app is available in the market too. Report back soon.
So you're basically just using the build prop settings out of this rom with the factory update? I went back to version 1.0 for now.
rich_e said:
So you're basically just using the build prop settings out of this rom with the factory update? I went back to version 1.0 for now.
Click to expand...
Click to collapse
Yeah pretty much!... did you not have the SU issues with version 1.0? If not I'll just update to that. I can't get Bank of America or Tasker to install even using the build.prop from the ROM, there's something other than the fingerprint in this ROM making the magic happen.
Titanium back up reports root access with V1.0 and I can get the # at the prompt in terminal. Lots of other apps that wouldn't install with the eLocity update install just fine with it too.
im a little confused..
i added the "su" command to the build, it never was there...
i added Superuser.apk as well.. and if you're trying to add those on top , you might corrupt it, and also,
VERY IMPORTANT filesystem has 0 bytes free, so any copying will probably corrupt the su command or other copied files..
Does this rom support ad-hoc wifi tether?
Device and OS: SGS3 AT&T (SGH-I747) 4.1.2.
Goal : Cancel the pending OTA update and its notification; prevent future OTA updates and notifications.
Assumptions: You've seen galaxys3root.com how-to-root-u-s-and-canada-galaxy fail-proofnoob-proof (Newbie here so can't yet post the outside link.)
This companion post simply collects the information into one place and optimizes the sequence of steps, instead of reading a whole disjointed thread, which I could not even find again anyway.
Phase 0 - Prep.
- Back up your data.
- Download the necessary files.
Phase 1 - Root the device.
- Connect via USB.
- Use Windows to copy SuperUser.ZIP onto device.
- Boot into download mode (Vulcan death grip with volume down).
- Use Odin to copy RecoveryGalaxyS3USCanada.TAR onto device.
- Disconnect USB.
- Boot into recovery mode (Vulcan death grip with volume up); the new loader launches.
- Install Chainfire's SuperSU (it's inside SuperUser.ZIP).
- Reboot normally.
Phase 2 - Stop OTA updates.
- Using Root Browser:
- Delete the one file in /cache/fota/.
- Rename /etc/security/otacerts.zip to otacerts-zip.bak.
- Add write-permissions on /system and /system/app (really not sure this is necessary).
- Copy FOTAKill.apk to /system/app.
- Rename /system/app/FWUpgrade.apk to FWUpgrade-apk.bak
- Reboot.
- Notification page may still say "New update postponed" (it does not swipe away).
- WAIT until the current postponement expires.
Now the notification is gone!
I feel like there may be one rename that I forgot, but it's listed around here somewhere.
Seemingly spurious information:
- Titanium Backup requiring Lucky Patcher requiring BusyBox; that whole stack failed so not used.
- Remounting /system using a terminal failed.
Wow.
A much easier way if you' ve obtained root would be to uninstall and reinstall titanium backup, click on backup/restore, then go down to where it says AT&T software update (or whatever it's called) click on it, then click uninstall. You will never receive any update notifications again.
Also, if you've already installed the recovery, the update will fail if you let one go through, so you don't need to do anything else to block updates after flashing that .tar file.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
uninstall and reinstall titanium backup, then uninstall AT&T software update (or whatever it's called). You will never receive any update notifications again.
Click to expand...
Click to collapse
I first tried using TiBu to freeze AT&T software update, but it was failing for some reason, so I scrapped that approach.
I want to be able to accept OTA later, just not now, so not ready to completely uninstall anything.
if you've installed the recovery, the update will fail if you let one go through
Click to expand...
Click to collapse
Looks like that's what happened this morning.
Thanks for the clarify, this makes sense now that I have been through the process by overdoing it :fingers-crossed:
1.Get utoo root.zip file
2.Go into settings>backup & reset>recovery mode.
3.Once in recovery mode find utoo root.zip file whether it is in the ext storage or internal storage. You can navigate using the volume up button and select using the power button
4. Select the utoo root.zip file.
5.Wait for utoo root file to complete installation
6.After installation reboot system.
7.After reboot open up supersu and update binary.
8.Update supersu using playstore.
9.Open supersu and if you have not bought supersu pro (you should btw), click enable pro features and because chainfire is awesome he basically gave everyone pro features and stuff.
10.Enjoy Root
I did this, it worked, mostly.
I did this method.
It worked, sort of...
I was able to get root on my tiny Kurio 4s.
There were some problems though.
Several apps stopped working properly.
The keyboard kept stopping and restarting.
The loader did as well, but did not restart.
I could not use the keyboard to input.
Lucky for me I still had the stock upgrade apk in my system.
I was able to restart in recovery mode and run the upgrade.
That reset everything to factory new.
Then I had to go through the whole catalog of updates...
That took forever.
So, what I want to know is...
Has anyone else done this?
And it's there a more up to date root method I can use on my K4s?
All the other posts on this device are old.
P.s. towelroot does not work on 4.2.2
P.p.s framaroot does not work either.
tried again...
Ok, I tried the utoo zip again.
This time (so far) I have not had any issues with misbehaving apps.
At first root checker kept saying that I did not have root.
But after I rebooted, I changed some SU settings and now root check reports that I have root!
ES3 File explorer has root access as does ES startup manager..
Hooray! Successful root on my Kurio 4s touch!
Thank you.
First of all, I have no idea where should this be posted as I am a total noobie to this forum and there is way too many categories.
I have a big problem. I installed Framaroot, used the first option (Boromir?) and have rooted my phone successfully. I tried to use *#*#supersu#*#* but nothing came up, the digits just disappeared, so I installed SuperSU from the market. I didn't do much on it, just changed the theme and hid it from my apps. I were rooted and happy for about a month, then however I got angered by SuperSU because I had to restart Hex Editor every time to get the root permissions (I were editing Terraria save files). The anger made me want to uninstall SuperSU, hoping it would just grant all the perms to the editor. First of all I disabled SuperSU, and when I realised it actually disabled the whole root, I enabled it again (unsure if it worked), I assumed everything is working, but I still wanted to get rid of the permission thing, so I pressed something like 'clean up to switch to a different superuser', and restarted my phone. I come back, and I have no root, so I went into Framaroot and used all the options, each returning that SuperSU and superuser binaries were installed. I restarted my phone, grabbed SuperSU from the Play store, just to find out that 'SuperSU binaries were not installed and SuperSU cannot install them, this is a problem!'. I then went on Framaroot, uninstalled root with all 3 options, restarted, then installed all, restarded, and the problem is still occuring. I am running Android Jelly Bean on Alcatel 4030X.
I have completely no PC access, so any USB roots or things like that are a no go. Please help!
Hi
since no-one has replied it may be because you have no paragraphs so it shows a disorganised mind....giggles
#########
Since you claim you used framaroot to install we now try to get root again
system settings security enable unknown sources
install framaroot ....if you lost it....to sdcard
install it
run it
choose first root exploit as you say that worked
if success you must reboot
###########
What you need to do if you have chainfire's superuser installed next time
go to app drawer
click on the red and yellow su icon
click on settings
change the default from .....ask each time to grant
reboot phone to test permission for apps is now auto granted. Especially test Hex Editor
###########
Altho you don't ask....there are 2 ways of updating chainfire's app
playstore ....click on update for app
open it
it will give you a dialog box to update
choose normal............it attempts to autoupdate
b) install a custom recovery and choose TWRP or CWM or CTR etc and try to update thru custom recovery
good luck
[Tut]How To Systemless Root+Root+More!
This was fully tested on SM-G928A;Baseband:UCU2AOJ1 on 5.1.1
Just in case needed //SM-G928A\\ **Full Odin Restore G928AATT2AOJ1**
$<Download Mode & Odin Systemless Root Flash>
Requirements:
1.A Windows Computer
2.Your Phone Device SM-G92-0/5/8A
3.Odin 3.10.7
4.Kernel_Root_Android_5.1.1_AT&T_SamFirm.NET
5.USB Drivers(Most of the time if connect the phone to the computer using the usb cord that comes with the device it will install all of the drivers if your computer is connected to the internet.
____________________
Okay now assuming that everything has been required, we can begin.
Turn off your phone and open Odin with admin rights on the computer & connect your phone to the computer using the usb cable that comes with the phone.
On the phone now hold all of these following buttons down, Volume Down+Home Key+Power Soon after once you see the blue screen release those buttons and press the Volume Up key to enter Downloading Mode.
Now in Odin on the computer, it should have recognized your device now press the "AP" button and open up for example, "G928A_Kernel_Root_5.1.1_SamFirm.NET.tar.MD5" now just press start and sit back and relax and soon you will have Systemless Root!(Note your phone will reboot which is normal after the flash.
--------------------
#<Obtaining Root Access>
Requirements:
1.A Windows Computer
2.Your Phone Device SM-G92-0/5/8A
3.USB Drivers(Most of the time if connect the phone to the computer using the usb cord that comes with the device it will install all of the drivers if your computer is connected to the internet.
4.Flashed The Systemless Root
5.Kingo Root
6.Root Checker Cost $FREE
7.SuperSU Cost $FREE
8.BusyBox Cost $FREE
9.Developer Options (USB Debug)
____________________
Okay now assuming that everything has been required, we can begin.
Go into Settings>System>About Device & Enable Developer Options.(Keep tapping the "Build Number" category until it says Developer options have been enabled.
Connect your device with your usb that which comes with the phone on the computer. Open "Kingo ROOT" on your computer with admin rights, and once the program asks you to turn USB Debug on, go on your phone into Settings>System>Developer options and make sure it is enabled as well as usb debugging. Wait for kingo root to find your device and once found, it will ask you to either "Reroot,Root, or Remove Root, click "Reroot" then wait for it to start.(After it starts you should see on your phone the kingo root usb app pop-up and show the same thing you see on your computer)
After it is done it should confirm you have been rooted and will ask to donate.
Now you may exit out of the program on the computer and the phone and once out of the app and back on your phone, you will want to look in your app drawer for the kingo root "Superuser" and uninstall this. Then head on over to the playstore if haven't all ready and install "SuperSU" & "Busybox" if want to. Once have the SuperSU app open it and install the su binary updates with the "Normal" option not the recovery one since we don't have that.... & once done just press OK DO NOT REBOOT or you will bootloop and will have to use Odin to reflash your system of your phone to get it back working out of the box "state"
UPDATE Have a pc around and can still boot with root:
Yamaha169 said:
You can restart the device while rooted... but you have to have ADB to do so...
When you reboot ... you will get stuck at the ATT logo... at this point... plug your phone in to your pc...
Open up ADB (COMMAND WINDOW)
type in
ADB devices
until your device # appears in adb... (this can take a minute for your pc to find your phone) so don't panic
This means the phone is found...
From this point... type
ADB ROOT
ADB SHELL
YOU will now be inside the shell of the device with root permissions
Now type
setenforce 0
(MAKE SURE LOWERCASE just like seen. "setenforce 0" if do Setenforce 0 it won't be found.....)
This will set selinux to permissive ... allowing the phone to boot...
Someone with enough experience could probably create a selinux permissive stock kernel ... but I've contacted several developers with no response ...
Click to expand...
Click to collapse
Now open up the root checker app & click verify to see if you truly do have root.(You must grant root access so allow once it pops up.) Enjoy your root but never ever reboot.
UPDATE: How to Root If Possibly not allowing you to root!!!
Step one you will need to of downloaded "Android Studio
Step two you will now need to install all of the updates(Well that's what I did) inside the studio program.
Step three now locate 'program tools" which for me was located here: C:\Users\NameofComputer\AppData\Local\Android\android-sdk\platform-tools
Step four make a cmd.exe file to go in the platform-tools simply just clicking on the "start button" on windows and searching "cmd" then dragging the cmd file to the folder.(Rename it to something like ADB Root or something different than just cmd)
Step FIVE download the su binary which can be located HERE and place it in the "platform-tools" folder.
Step SIX now almost there. Open the cmd file(ADB Root.exe) and once opened, plug the phone into the computer with the cable that came with your phone.
Step Seven:^.^ now with the phone plugged in and the program start, type this command to make sure your device is found:
Code:
adb devices
and if found you will see your attached devices and if more than one or can't see your device, you can do
Code:
adb kill-server
command and it will restart adb.
Step Eight: MAGIC time lol now that your phone is connected and you can see it is indeed listed, type these commands as followed:
Code:
adb root
adb remount
adb push su /system/bin/su
adb shell
chown 0:0 /system/bin/su
chmod 6755 /system/bin/su
You don't really have to do the other commands after pushing su it's just for pre-caution.
Step Nine: Now do the following at the top and try to use the Kingo root once more and click root or reroot.
If this doesn't work try to press unroot and restart phone then try this again.
Also like down below I talk about if you did reboot before you unrooted, you can still unroot but sometimes it's tricky and it needs you to do the adb remount before will work so just remember that...
--------------------
$#$<UnRooting & Keeping Systemless Root So You Can Reboot & Reroot>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.Root Access(Superuser rights)
3.SuperSU Cost $FREE
4.Root Checker Cost $FREE
____________________
This is very simple and easy to do, all you must do after every root and before every reboot is to go into "SuperSU" and go into the settings and scroll down until you see "Fully Unroot" and click that and once done verify with the root checker that you are indeed unrooted but still have adb shell and once done that you may freely reboot with no bootloop and then if want root once more just use "Kingo Root" on the computer to reroot once more.(I'm hoping someone will come out with an app that does the same thing and works so we don't need the computer anymore which would make it much easier..)
Edit/Update:
I found that if you maybe forgot to unroot before a reboot that you can still unroot without the need of going into odin and reflashing stock system just by connecting your phone to the computer via the usb that which comes with your phone and opening up Kingo Root and waiting for it to find your phone then click unroot and wait for it after you have unrooted and you will hear a sound which means it's fixed! So just force shutdown the device with pressing both: Volume Down+Home Button+Power then it will boot back up as normal!
-------------------- ____________________ -------------------- ____________________
~My Findings Through Long Research & Errors~:
<How to Fix Wifi Bug That Comes With Flashing Systemless Root>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.Root Access(Superuser rights)
3.SuperSU Cost $FREE
4.BuildProp Editor Cost $FREE
____________________
On your phone open up the "BuildProp Editor".
click on the search button and search for "ro.securestorage.support=true" now once found change the =true to =false and save. Now you must reboot for it to take place but remember to UNROOT before you reboot.
Now doing this your wifi will stay connected and you no longer have to enter your password millions of times so it will be nicer to keep systemless root.
--------------------
<How to Enable AT&T Hotspot System FULLYApp>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.Root Access(Superuser rights & .SuperSU Cost $FREE)
3.Root Explorer Cost $3.99
4.NEW Modded TetheringProvision .apk Cost $FREE(Also can be found in this thread in attachments.
5.ADB Root cmd knowledge or Download SQLite Editor Cost $2.99
6.BuildProp Editor Cost $FREE
____________________
Okay my fellow members that stayed on 5.1.1 with me, this tut did once work but then at&t blocked me and it stopped working but now rejoice becase there is a bypass once more!!!
NEW WAY:
I'm not sure which worked so I'm gonna just tell you everything that I did...
1.I first rooted obviously
2.I found a new TetheringProvision.apk which I have uploaded down in the attachment and at the top.
3.I used adb root for this but this can also be done with sqlite editior so I'll explain both ways, first way will be the easy way the adb root...>>>
Step 1: Ensure you have the correct OEM drivers installed for your handset on the computer
Step 2: Download and install the necessary ADB drivers (v1.4.2)
Step 3: Enable USB debugging on your Android handset:
Go to Settings > About Device, and tap the build number 7 times or until you see 'You're now a developer' message.
Return to Settings > Developer options and use the toggle button to turn on USB debugging. Then tap OK button to accept the warning and continue.
Step 4:Connect your device to PC with original USB cable.
Step 5: Launch a command window on your Windows PC.
Step 6: Access ADB shell and run the following command:
adb shell now just type " settings put global tether_dun_required 0 " and enter.
________----------Now the sqlite way
Step 1:Go into sqlite editor and allow root rights...
Step 2: Locate "Settings Storage" and click on "Settings.db then click on "global"
Step 3:Locate tether_dun_required 0 and if not there add by clicking on the +
then fill out name as " tether_dun_required " >>And value as " 0 " and then save file and unroot then reboot.
Now then after all of that I downloaded the build.prop which I know you don't have to but it makes it easier for me to do so and probably for you too...
Step 1:Get build.prop editor from the playstore and open it to grant root rights.
Step 2:Click on the pencil icon on the top right where the search icon is.
Step 3: Scroll all the way down to an open line.(If not one make one.)
and put this in the line....>>> " net.tethering.noprovisioning=true " and then click the save button at the top right and then save it and unroot then reboot.
Then replacing the Tetherprovision.apk . >>>
Step 1: Download the NEW modded TetherProvision.apk at top or at bottom.
Step 2: get a root explorer and go to System/App/TetheringProvision
Step 3: Rename the actual TetheringProvision.apk to TetheringProvision.apk.bak
Step 4: in the same location, go into "arm64" and rename the TetheringProvision.odex to TetheringProvision.odex.bak
Step 5: Now locate the modded TetheringProvision.apk you've just downloaded and place it in System/App/TetheringProvision/ now should be two TetheringProvision, the TetheringProvision.apk.bak and the modded one, TetheringProvision.apk.
Step 6: change the property promissions of the tetheringprovision.apk to give it root rights by changing the promissions to look just like the actual one which is " rw-r--r-- "
Step 7: save and unroot then reboot!
Now youre wifi tether and usb should work!!! enjoy!
--------------------
<How to disable OTA & Security Notification>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.Root Access(Superuser rights & .SuperSU Cost $FREE)
3.Titanium Backup & Titanium Backup Pro License Cost $Free | $5.99
____________________
Open up titanium back with pro license and freeze these following apps:
1.SecurityLogAgent(This is that annoying notification that which comes with the systemless flash root that keeps annoying you to reboot and undo what you done.)
AT&T Software Update(This will make it so AT&T won't push any updates to your device anymore so no need to worry about installing an update ota and losing your root or something else like bootlooping.
And again, all of this sticks after you unroot and reboot!
___________________________________________
<How to Get Youtube RED (Sort of) FREE!>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.OGYoutube Cost $Free
Basically all you do here is download the modded sort of youtube app(OGYoutube) and install it then done! You now can download videos/music on the app and have access to run audio in the background plus NO ADS!!! (if there are I haven't seen any yet...)
Best part of this too since can't be used fttb, no need for XPOSED apk!
_____________________________
<How To Install Viper4android>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.Root Access(Superuser rights & .SuperSU Cost $FREE)
3.Fast Reboot
4.Soft Reboot
5.Viper4Android V2.3.4.0
6.Audio_Effect.Config
7.Titanium Backup & Titanium Backup Pro License Cost $Free | $5.99
8.IRS Impulse Response Sample files
9.Root Explorer Cost $3.99
~~~~~~~~~~~~~
To Read the tuts yourself than rather follow my tut, you may do so by following This Link & This Link
~~~~~~~~~~~~~~~~~~
Alright, I decided to do my own detail tut to make it much easier so follow me and you'll have viper4android in no time : )
So let's get begin, download if not already, the busybox,SuperSU,TitaniumBackup,Fast reboot,Soft Reboot, & Root explorer. Now having all that done open up Busybox and allow it root rights and you may wait for it to research for a smart intall, or just press install. Once you installed it in the default location System/xbin, click on the will be installed to location and choose System/bin and install it there too.(Not sure why but that's what the tut called for.)
Now let's download the folders for viper4android, go ahead and download Audio_Effect.Config.zip file,IRS Impulse Response Sample files, & the Viper4Android V2.3.4.0 folder.
Now open up the root explorer and unzip all that which is zipped up.(Which is all of the files;Audio_Effect.Config.zip file,IRS Impulse Response Sample files.zip, & the Viper4Android V2.3.4.0 folder.zip
)
Now once all are extracted, we will begin putting what is needed where.
Let's start off with the ViPER4Android_FX_A4.x (The actual name of the folder) you're gonna want to long press it and copy this folder. Once done, you're gonna want to paste this folder in System>Priv-app and make sure to change the permission of the .apk to 0644 rw-r--r-- & the FOLDER to 0755 rwxr-xr-x(The folder should have the same permissions as the other folders in that location.) which is inside the folder to give it root access which is 0644;rw-r--r-- and if not sure what root permission should look like, refer to this link Or Google what it looks like, then save/press ok.
Now go back to where you extracted your folders, and this time copy the "audio_effects.conf and go to System>etc and find and rename the actual audio_effects.conf to audio_effects.conf.bak and then paste the copied modded audio_effects.conf here & DONT FORGET change the permissions to give it root rights.
Now after all is done, open the app "Titanium Backup Pro" and look for and freeze these following applications: 1.Adapt Sound 4.0 & SoundAlive 3.0 now open the app "Soft Reboot (Root) and click yes you want to do a soft reboot. Then once back up(If want you can click the "Fast reboot app" to quickly refresh the system) and running you should see the viper app inside your app drawer. Open it and install the update/software when ask you to and once done it should ask for you to reboot just click on ok and then go out and back to the "Soft Reboot (Root) then do another soft reboot.
Now almost DONE!!! Once back up and running again, go to your root explorer again where you extracted the folders and grab the folder of "ViPER4Android and move it to your device storage ex; Storage/emulated/0 (It's where the download folder is and dcim folder is.. Then finally, go toSettings>Device>Sounds and notifications>Sound quality and effects and toggle on all of the listings[NOTE YOU MUST PUT EARPHONES IN FOR THESE TOGGLES TO SHOW]; UHQ Upscaler|SoundAlive+|Tube Amp Pro now you're done enjoy viper4android via editing the settings in the app.
Edit
You need to download SELinux Mode Changer and give root rights and just click on permissive mode and all done. Also might need to use compatible mode in the Viper4Android settings.
I found that this mod works with Pandora and Youtube app but not with google music or the default music app and not sure how to fix that....
__________________________________0
This is some more quick finds which you don't need a tut for just information I'd like to share so you all know.
I found out that you can use Titanium Backup Pro Cost $5.99 and freeze anything you want such as bloatware and that annoying notification that appears every time you reboot if have systemless root installed "SecurityLogAgent" and as long as you UNROOT before you reboot, it is safe and everything you froze stays frozen.
Now I haven't tried uninstalling any system apps so I wouldn't advise doing that unless you wanted to but I don't see the point except to free space up since you can just freeze anything and does the same thing except for freeing space....
I haven't been able to unlock the bootloader in my research and errors which probably never gonna happen anytime soon....
I also never found an app that could root the device yet without a computer....
And yeah that's it! I just was so happy to find out all of this and just had to share it with xda members which are on the same boat as me that has been wanting some "freedom" which now can have a piece of it. : )
If found these tuts to be helpful, feel free to hit thanks button and if want donate.
AngelRyu said:
Just gonna get right to it and be fast.
Odin Flash Kernel for systemless root.
obtain root
Download SuperSU
After rooted download some sort of buildprop editor and search for " ro.securestorage.support=true" Now change =true to =false. and save!
Now go into the superSU app and fully unroot then reboot and also keep adb shell root!
So you fix the wifi bug plus keep the adb shell so you can obtain root once more! Now we just need some app that can give root access with 1 click without needing a pc and this would work for me until we can actually reboot with root without it bootlooping anyways.... I still can't find a wifi tether app or a method that works for the at&t hotspot app though...
Click to expand...
Click to collapse
Question for clarification.
So current method for rooting g928a is this systemless root.
Question 1, will it brick my phone with this root if i reboot, because i read somewhere on here that the phone will just keep on rebooting.
You mention using superSU app to unroot to reboot. So basically I have to unroot with superSU whenever I want to reboot then reflash again to get root?
fuzmik said:
Question for clarification.
So current method for rooting g928a is this systemless root.
Question 1, will it brick my phone with this root if i reboot, because i read somewhere on here that the phone will just keep on rebooting.
You mention using superSU app to unroot to reboot. So basically I have to unroot with superSU whenever I want to reboot then reflash again to get root?
Click to expand...
Click to collapse
Yes you must unroot to remove the su binary so the system acts like nothing has happen. I use kingo root for windows and it works every time with root all you need to do is hit "root" or it may say "reroot" and works every time. I have been playing with this a lot trying to do things to get it to reboot with root but have failed so far.... I wish someone with more experience would approach this so we could have an app to use at least so we not have to use pc every time to reroot until we get the ability to keep root and reboot.
Kingo root can be found here : https://www.kingoapp.com/android-root.htm
and this works after flashing the kernel from odin. This was the only way I actually found to be able to get root was with this because manually pushing su just didn't work for me....
Thanks for being much clearer on the instructions and idoit proof. I was worried about the bootloop and I thought there was no exit strategy on this expensive phone until you mention reflash. With your extensive tinkering on this, did your knox security trip up?
If this is the only possible way, maybe the community could make some sort of app that if we have to shutdown or reboot the phone specifically for g928a, it will safely unroot it for us.
TASKER?!
Anyone know if this still works after taking the latest OTA a few days ago?
The problem is this isn't root. I restart my phone several times a day. There is no point especially if I can't get a custom OS. However, thanks for making the instructions clear. And for anyone who doesn't understand systemless root, it's temp root. When you reboot dmverity sees the false file structure and tries to rewrite and reverse the changes, effectively removing root. On the Note 5 AT&T for temp root you didn't have to unroot before reboot as it wouldn't boot loop, it would just remove root and let you continue on. So something in this version must be getting farther in breaking past dmverity if it's causing the OS to bootloop.
tonys.94 said:
The problem is this isn't root. I restart my phone several times a day. There is no point especially if I can't get a custom OS. However, thanks for making the instructions clear. And for anyone who doesn't understand systemless root, it's temp root. When you reboot dmverity sees the false file structure and tries to rewrite and reverse the changes, effectively removing root. On the Note 5 AT&T for temp root you didn't have to unroot before reboot as it wouldn't boot loop, it would just remove root and let you continue on. So something in this version must be getting farther in breaking past dmverity if it's causing the OS to bootloop.
Click to expand...
Click to collapse
I was wondering if maybe we could place SU somewhere else so we might could trick it to reboot with root but haven't done it yet and or maybe keep SU on the sdcard/storage and use the terminal on the phone to push su to xbin every reboot but just hoping maybe can get root working without making the stupid thing bootloop.... Like I said I been doing a lot of dumb stuff with my phone because I have been so disappointed in this phone with not having wifi tether at the most really but now that got that I'm much happier but I'm still on the research of keeping root and being able to reboot.
I won't be updating until something maybe for sure comes along with 6.0 I can wait because my galaxy s4 I had stayed on stock version forever because was able to do everything so was no need to update really.... Anyways yeah lol maybe someone greater or maybe my playing around will work. WE can only hope...
Oh yeah, to the other guy NO it did not trip knox doing any of the things I've done. which I wouldn't care if could unlock the bootloader lol...
Edit:
I've done all I can think of and didn't work to keep root on a reboot except it did keep root without bootloop with a soft reboot...
I found out to maybe later will add tut up top but for now I'd like to tell you or whoever, if you do bootloop due to not being able to access the su unroot in time, you can still connect your device with Kingo Root in that bootloop and can unroot to save you from having to reflash every time... Might have to reboot as soon as you hear the found from the unroot though.
Oh and on a factory reset everything sticks excepts what was frozen becomes unfrozen just fyi...
Yeah, that's all I can find so I'm done with it hope someone can help later on but I'm just happy with wifi tether so much : )
So what all can we do with this root
Thank you for your hard work. it's very much appreciated!!!
Will pay part of my bounty which is 50 dollars pay day!!
But, please reply. what all can we do with this root!?
O0Gjulian said:
So what all can we do with this root
Thank you for your hard work. it's very much appreciated!!!
Will pay part of my bounty which is 50 dollars pay day!!
But, please reply. what all can we do with this root!?
Click to expand...
Click to collapse
Hi, I didn't come up with anything but the fix for wifi bug and hotspot app.
I just made a very detail tut to help others, but thanks.
I would wait on the bounty to be paid to someone who can make it possible to keep root on and still be able to reboot.
So in theory with this method I can root, install a modified tetheringprovisions, unroot (as hotspot is the only feature I actually desire), and go about my business without worrying about bootlooping or knox being tripped? Feels too good to be true, but I want to believe.
Just a reminder that Android 6.0.1 is right around the corner. If you don't fully go back to stock before the upgrade it will not flash and could possibly wipe the data partition. Both the system and boot images need to be 100% stock.
antizombie said:
So in theory with this method I can root, install a modified tetheringprovisions, unroot (as hotspot is the only feature I actually desire), and go about my business without worrying about bootlooping or knox being tripped? Feels too good to be true, but I want to believe.
Click to expand...
Click to collapse
It's true, that's how my phone is rolling with frozen apps and the modded hotspot without root, but still the systemless root remains in the system but doesn't do anything with out a computer or applying the kingo root to true root it.
I haven't tested the adaway yet so idk if will work or not.... and I been wanting xpose to work to disable youtube ads but haven't tried that either. . I might root tonight and try out adway tho.
But yeah to your question you are 100% safe and will not change anything or trip anything; phone can reboot all it wants with no bootloops with the modded tether is what I'm trying to say lol .. .
Edit:
Yeah adaway works after unroot and reboot. . . But I decided not to use it because a lot of people us adfly and it wouldn't let me access the link so yeah.....
On another note I froze a lot of stuff and done a lot of things not sure which part caused it but it doesn't bother me because I don't use samsung pay but in the end I had to freeze samsung framework for samsung pay because it kept saying force closed but which again Idc about that app so no biggy to me : )
Was Samsung Pay crashing before you started freezing apps? I have yet to use Pay but I'd prefer to keep my options open if possible.
antizombie said:
Was Samsung Pay crashing before you started freezing apps? I have yet to use Pay but I'd prefer to keep my options open if possible.
Click to expand...
Click to collapse
Honestly, I'm not sure but it had to be either the freezing at&t update or securityagent because it seemed to happen after that... Or could be the hotspot mod but I didn't get any crashes until i froze those 2 apps so idk...
Package Disabler in play store freezes apps so what's the point?
Can you fully remove with TiBu and be safe unrooted?
---------- Post added at 03:55 PM ---------- Previous post was at 03:40 PM ----------
navalynt said:
Just a reminder that Android 6.0.1 is right around the corner. If you don't fully go back to stock before the upgrade it will not flash and could possibly wipe the data partition. Both the system and boot images need to be 100% stock.
Click to expand...
Click to collapse
Yeah and from what I've seen of the nightmares people have been having with their Note 5's on Marshmallow, I'm staying FAR away from it!
I can confirm this works. Sorta a pain to have to reroot but hey, It's progress. We may never have a custom ROM option or recovery, But this is the next big thing. If we can find a app that'll just reroot us. it's perfect. (somewhat) Just rooted a few minutes ago. Going to play around. More than likely I'll re flash stock and make a youtube video for anyone needing questions or wanting to see it be done.
And I lied.. So, My experience was weird. Lagging constantly and weird download issues with a fresh wipe.
I'm sadly gonna have to unroot and hope that a better method would come out.
):
O0Gjulian said:
I can confirm this works. Sorta a pain to have to reroot but hey, It's progress. We may never have a custom ROM option or recovery, But this is the next big thing. If we can find a app that'll just reroot us. it's perfect. (somewhat) Just rooted a few minutes ago. Going to play around. More than likely I'll re flash stock and make a youtube video for anyone needing questions or wanting to see it be done.
And I lied.. So, My experience was weird. Lagging constantly and weird download issues with a fresh wipe.
I'm sadly gonna have to unroot and hope that a better method would come out.
):
Click to expand...
Click to collapse
I'm not sure why you would experience "lag" because I have no lag what so ever. Maybe try going to settings>system>developer options and change both transition animation scale and window animation scale to 0.5x
I've reflashed stock many of times due to to trying to find everything there is to find and I've had no "lag" but also you could download the soft reboot and fast reboot from market. Fast reboot frees up memory via closing and restarting certain apps, and soft reboot kills zygote and does a "hot reboot" without going through whole start up process .
Please reply I'm gonna try and help you : )
Also @
joe3681 said:
Package Disabler in play store freezes apps so what's the point?
Can you fully remove with TiBu and be safe unrooted?
---------- Post added at 03:55 PM ---------- Previous post was at 03:40 PM ----------
Yeah and from what I've seen of the nightmares people have been having with their Note 5's on Marshmallow, I'm staying FAR away from it!
Click to expand...
Click to collapse
I can confirm freezing anything won't harm the system on a reboot after unrooting but not sure about removing the apps would be safe. I have however remove the youtube app and reinstalled it in play store and it didn't harm anything.
AngelRyu said:
I'm not sure why you would experience "lag" because I have no lag what so ever. Maybe try going to settings>system>developer options and change both transition animation scale and window animation scale to 0.5x
I've reflashed stock many of times due to to trying to find everything there is to find and I've had no "lag" but also you could download the soft reboot and fast reboot from market. Fast reboot frees up memory via closing and restarting certain apps, and soft reboot kills zygote and does a "hot reboot" without going through whole start up process .
Please reply I'm gonna try and help you : )
Thanks for helping me! I went ahead and flashed stock and followed your steps!
Working great now!
NOW, My next question... What difference would it make if I used package disabler pro VS TBU?
Wouldn't both of these apps freeze the processes? Or would it make a difference with root and SU access?
Click to expand...
Click to collapse
O0Gjulian said:
AngelRyu said:
I'm not sure why you would experience "lag" because I have no lag what so ever. Maybe try going to settings>system>developer options and change both transition animation scale and window animation scale to 0.5x
I've reflashed stock many of times due to to trying to find everything there is to find and I've had no "lag" but also you could download the soft reboot and fast reboot from market. Fast reboot frees up memory via closing and restarting certain apps, and soft reboot kills zygote and does a "hot reboot" without going through whole start up process .
Please reply I'm gonna try and help you : )
Thanks for helping me! I went ahead and flashed stock and followed your steps!
Working great now!
NOW, My next question... What difference would it make if I used package disabler pro VS TBU?
Wouldn't both of these apps freeze the processes? Or would it make a difference with root and SU access?
Click to expand...
Click to collapse
I'm not sure because I've never heard of that program, but I did buy it just now for about $1.89 and the activation keeps failing so I can't test it to see the difference but with titanium you can do everything not just freeze stuff but back up apps and their data and much more.
Titanium backup has been around for ages which is why I recommend it.
Click to expand...
Click to collapse
I use package Disabler. Works like TiBu without root. Only reason to root would be to fully remove apps but would it boot okay after?