Related
How do I root my Galaxy Nexus on firmware 4.0.4 and a GSM model
thomaswackers said:
How do I root my Galaxy Nexus on firmware 4.0.4 and a GSM model
Click to expand...
Click to collapse
Flash Superuser (Link)
I tried flashing su.zip and it works, however apps are not asking for root permission anymore. Instead they just freeze or say they can't run privileged commands
EDIT: adfree for example will just run as if nothing was wrong, but it doesn't actually update the hostfile, and Superuser doesn't show AdFree in the list of apps
It just seems as if none of the apps are asking for superuser permissions anymore.
veinripper said:
I tried flashing su.zip and it works, however apps are not asking for root permission anymore. Instead they just freeze or say they can't run privileged commands
EDIT: adfree for example will just run as if nothing was wrong, but it doesn't actually update the hostfile, and Superuser doesn't show AdFree in the list of apps
It just seems as if none of the apps are asking for superuser permissions anymore.
Click to expand...
Click to collapse
Try to clear data and cache from SU. Are you sure you flashed the latest version? See link? If that does not help maybe delete and reinstall.
Sent from my Galaxy Nexus using xda premium
Diger36 said:
Try to clear data and cache from SU. Are you sure you flashed the latest version? See link? If that does not help maybe delete and reinstall.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I finally fixed, you were right, it was an older version. I went on the superuser website and got this version: Superuser-3.0.7-efghi-signed.zip
I would post a link but I don't have enough posts.
Flashed in recovery and it works now.
thanks
veinripper said:
I finally fixed, you were right, it was an older version. I went on the superuser website and got this version: Superuser-3.0.7-efghi-signed.zip
I would post a link but I don't have enough posts.
Flashed in recovery and it works now.
thanks
Click to expand...
Click to collapse
No problem mate, and the link was in the second post
Sent from my Galaxy Nexus using xda premium
When you say flash, do you mean through CWM? And if so could I flash a temp CWM so I can just flash this?
jonnyg1097 said:
When you say flash, do you mean through CWM? And if so could I flash a temp CWM so I can just flash this?
Click to expand...
Click to collapse
Yes and Yes (although I didn't try the last one but it should work)
Diger36 said:
Yes and Yes (although I didn't try the last one but it should work)
Click to expand...
Click to collapse
Cool thanks!
Diger36 said:
Yes and Yes (although I didn't try the last one but it should work)
Click to expand...
Click to collapse
How do I 'flash'
with Clockworkmod recovery
I tried to flash through cwm su.zip and gave an error, something with 0 . How do I do it manually?
I tried to install latest version of Super user, but i get error status 0 in CWM.. Help please
How to install cwm recovery? I just flashed my nexus with stock 4.0.4 and flash this kernel..
Check my sig, kids.
Make sure to follow gsm/cdma downloads and you'll be butter.
OK I'm not sure which update broke my root, but I am on IMM67I
I noticed too that in the superuser app there were no requests, and when going into a terminal and typing su I get 'permission denied'.
First port of call was superboot v4.. that hung at the google screen. Then I temp booted CWM and flashed su_ICS_GN.zip...
Once booted still no access in terminal (permission denied), so I deleted su and superuser.apk (how? Surely I need su to delete these?), then flashed again.. exactly the same.
Downloaded the linked file above and got:
Error in Superuser-3.0.7-efghi-signed.zip
(status 0)
installation aborted
Incidentally, this is the same version of su that is in su_ICS_GN.zip
When going into superuser and trying to update the binary, it says 'cant get root'..
Downloaded just the binary only and get exactly the same as above (installation aborted). Looked at the update_script and cannot see anything wrong....
I've just tried to boot an unsecure image so I can push the new su binary.... stuck at the Google screen...
Very confused...
---------- Post added at 10:59 AM ---------- Previous post was at 10:45 AM ----------
OK I used the 'Galaxy Nexus Toolkit' which must have an updated insecure image I guess to push the right su binary..
I had to manually get it into bootloader mode as it didnt reboot (even though it detected the phone at adb).... and then the script continued OK..
i have unlocked Sir G nexus , unlocked with odin method by chainfire (after install 4.0.4 my phone get unlcoked fortunately )
i have andoid system recovery <3e> and there is apply update from cache !
and when i go into it there isnt any file i can update .
i can not root my device now , some giude tells me use some command prompt to flash , that i can not find it either !
i had been through so much **** to buy this phone and dont want to ruin in with ignorance , due to this can any one that root his device tell me how to do it . i really appreciate anyone one read this message
another question is about boot loader unlocking .
my boot loader unlocked by odin method installing 4.0.4 (chainfire)
is there any different between the toolkit unlocked phone and my locked phone , i said above
afraaa said:
i have unlocked Sir G nexus , unlocked with odin method by chainfire (after install 4.0.4 my phone get unlcoked fortunately )
i have andoid system recovery <3e> and there is apply update from cache !
and when i go into it there isnt any file i can update .
i can not root my device now , some giude tells me use some command prompt to flash , that i can not find it either !
i had been through so much **** to buy this phone and dont want to ruin in with ignorance , due to this can any one that root his device tell me how to do it . i really appreciate anyone one read this message
Click to expand...
Click to collapse
fount it myself no need to answer this
---------- Post added at 09:06 PM ---------- Previous post was at 09:03 PM ----------
afraaa said:
another question is about boot loader unlocking .
my boot loader unlocked by odin method installing 4.0.4 (chainfire)
is there any different between the toolkit unlocked phone and my locked phone , i said above
Click to expand...
Click to collapse
found it my selft ,,,, no need to answer this
Wth are you talking about? Unlock bootloader with odin?
Only way i know is with fastboot.
sent from my i9250
I am new with rooting my phone. I have used Rooted phones before, I followed http://forum.xda-developers.com/showthread.php?t=2258633 Motochopper how to. I ran into a problem. I click the superuser app that was installed onto my phone, and it tells me that "The Superuser binary (su) must be updated. Please choose an installation method. Recovery mode installation is recommended for HTC devices." I click install and it tells me there was an error. I would like to root my phone along with potentially installing CWM so that I can easily install Cyanogenmod when they release a stable verison for the S4. Also would love to install titanium backup along with some Adfree apps.
Any help would be very much appreciated.
OK, so it looks like you already have it rooted.
When super SU asks that question, dont install via CWM, tell it to just install normally.
Once you have SuperSU working, Download Rom Manager from the play store and install CWM Recovery right from within the ROM Manager app.
It will give you the option to pick between two types of CWM(ClockWorkMod). The Touch version, like its name gives you the ability to use the touch screen and not only the volume up/down + Power button.
Telling it to install normally causes it to just tell me there was an error, it also tells me it is out of date as well. Titanium Backup tells me that it cant get root access and I was never asked about it.
OK, so your phone is not rooted then.
Your going to have to try rooting it again or flashing an already rooted rom with Odin.
I just tried it again, this time it said failure after the install of the superuser.apk. I just read that one of the later updates by samsung can make it harder to root. I just got my phone and i was fully updated. What Roms, are already rooted for the S4. I am actually enjoying some of the default apps that came with the phone.
Wicked (and most ROMs that don't include the [STOCK] tag) are pre-rooted...but you'll need to ODIN a custom recovery first then flash the ROM.
If you want to stay on rooted stock, follow the steps in the "root May 7 MDL" thread to ODIN a rooted kernel, and you'll be good to go.
(You don't need root access to get a custom recovery flashed)
Basically, any of your options are pretty straightforward, but they're going to involve Odin-ing stuff.
So there isn't really a way to just root my phone without installing a custom rom?
There was before the second update, with the second update rooting got just a little bit more steps
Sent from my SGH-M919 using xda premium
movieaddict said:
There was before the second update, with the second update rooting got just a little bit more steps
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
So is there a way to keep it stock but root it? What are the other steps I would have to take. Why does Samsung not like people rooting their phones, I thought carriers were the ones that hated people rooting their phones
Spud37 said:
So is there a way to keep it stock but root it? What are the other steps I would have to take. Why does Samsung not like people rooting their phones, I thought carriers were the ones that hated people rooting their phones
Click to expand...
Click to collapse
Are you still on the MDB firmware or have you done any over the air updates? Specifically the May 7 update which is MDL. Motochopper is specifically for then older firmware (MDB) and it won't work if you are already on the updated. MDL firmware. In which case you would have to follow these instructions to acquire root.
http://forum.xda-developers.com/showthread.php?p=41162041
I usually use a market app called root checker to quickly check if I do have root.
And yes you can be rooted on stock.
Sent from my SGH-M919
lazaro17 said:
Are you still on the MDB firmware or have you done any over the air updates? Specifically the May 7 update which is MDL. Motochopper is specifically for then older firmware (MDB) and it won't work if you are already on the updated. MDL firmware. In which case you would have to follow these instructions to acquire root.
http://forum.xda-developers.com/showthread.php?p=41162041
I usually use a market app called root checker to quickly check if I do have root.
And yes you can be rooted on stock.
Sent from my SGH-M919
Click to expand...
Click to collapse
Root checker says no root. I believe it does have that over the air update installed. T Mobile updated it when they gave me the phone, because they thought I didn't really know anything about phones. I assume this means I have to follow another method to root my phone?
If you have the MDL update you have to root using the steps listed here:
http://forum.xda-developers.com/showthread.php?t=2268880
Easily done, just a few more steps.
ronin4740 said:
If you have the MDL update you have to root using the steps listed here:
http://forum.xda-developers.com/showthread.php?t=2268880
Easily done, just a few more steps.
Click to expand...
Click to collapse
This is going to sound like a dumb question but from reading all of that I need to use ODIN to install the ROOT_M919?UVUAMDL onto the phone? that should root the phone and allow me to install ROM Manager and install CWM from there right?
Also would doing this delete everything I have on my phone right now?
Spud37 said:
This is going to sound like a dumb question but from reading all of that I need to use ODIN to install the ROOT_M919?UVUAMDL onto the phone? that should root the phone and allow me to install ROM Manager and install CWM from there right?
Also would doing this delete everything I have on my phone right now?
Click to expand...
Click to collapse
No, you use Odin to install one of the recoveries. You use the recovery to install the zip ROOT_M919?UVUAMD. Personally I didn't use that file. I installed the kernel in recovery and SuperSU in recovery. And no, it won't delete things on your phone.
Atmazzz said:
No, you use Odin to install one of the recoveries. You use the recovery to install the zip ROOT_M919?UVUAMD. Personally I didn't use that file. I installed the kernel in recovery and SuperSU in recovery. And no, it won't delete things on your phone.
Click to expand...
Click to collapse
Thank you so much, I am about to go and do this. I will use the kernel you suggested since that looks like a better option, after flashing the kernal should i reboot and just use it normally for a bit and then go to recovery and flash SuperSU?
EDIT: The steps on the thread for ODIN are for installing a rooted ROM, I am assuming its still the same steps for installing a recovery instead of a rooted ROM
Spud37 said:
after flashing the kernal should i reboot and just use it normally for a bit and then go to recovery and flash SuperSU?
Click to expand...
Click to collapse
If I remember right I just flashed them both at the same time. Just make sure you do the kernel first.
---------- Post added at 02:01 PM ---------- Previous post was at 01:59 PM ----------
Spud37 said:
EDIT: The steps on the thread for ODIN are for installing a rooted ROM, I am assuming its still the same steps for installing a recovery instead of a rooted ROM
Click to expand...
Click to collapse
The steps for Odin are for the stock rom, but yes, you use it the same way for a recovery.
Atmazzz said:
If I remember right I just flashed them both at the same time. Just make sure you do the kernel first.
---------- Post added at 02:01 PM ---------- Previous post was at 01:59 PM ----------
The steps for Odin are for the stock rom, but yes, you use it the same way for a recovery.
Click to expand...
Click to collapse
Okay I didn't get any error using ODIN, however when I try and boot into CWM using Volume Up + Power it just goes to android recovery. Which doesn't have any of the options I need. Am I just booting up the wrong way, or did I do something wrong. I tried both the touch version and the non-touch version
Spud37 said:
Okay I didn't get any error using ODIN, however when I try and boot into CWM using Volume Up + Power it just goes to android recovery. Which doesn't have any of the options I need. Am I just booting up the wrong way, or did I do something wrong. I tried both the touch version and the non-touch version
Click to expand...
Click to collapse
2 options. uncheck auto reboot in Odin. When Odin is done, unplug your phone, pull your battery, then boot into recovery. Or .. when Odin is done and it reboots your phone, keep holding volume up to get to recovery.
Atmazzz said:
2 options. uncheck auto reboot in Odin. When Odin is done, unplug your phone, pull your battery, then boot into recovery. Or .. when Odin is done and it reboots your phone, keep holding volume up to get to recovery.
Click to expand...
Click to collapse
Thank You so much. However it now seems like I have both Super User and SuperSU installed.
How did you root? Did you install the ROOT_M919?UVUAMDL zip and install SuperSU?
|Guide|How-To| Root & Install Custom Recovery for 4.3 / 4.4 Update |16 July 2014 |
Warning: Following any of these instructions will void your warranty, and could possibly cause irreparable harm to your device (i.e. bricked). If you do not understand these risks, stop here and do not proceed. If you do not know how to use Odin, stop here and do not proceed. I am not responsible for anything that happens to your device. YOU chose to follow this guide.
If you have not updated to 4.3, go here.
If you have not updated to 4.4, go here.
Finally, there is no guarantee that either method will work for you.
Root Method #1:
The first thing you should try is CF-Autoroot since this has worked for many users.
If you successfully root with this method, you can simply install Goo Manager or ROM Manager and install recovery.
This method failed for me after many attempts.
Edit:
Here is some potentially useful info for root method #1 from ansonantonym.
Root Method #2:
1) Reboot in to download mode
2) Flash TWRP with Odin via PDA
3) Reboot to recovery then flash SuperSu and the Knox Remover
4) Reboot
5) Download SuperSu from the Play Store
6) Open SuperSu and update the binary when prompted
7) Reboot
8) Enjoy rooted 4.3/4/4
Downloads:
Odin
TWRP (Odin flashable tar)
SuperSu (v1.65)
SuperSu (v2.01)
DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V1.0
If you found another method that worked for you, please post here so that others may benefit.
If you are uncertain about any of the steps above, please ask your questions here before proceeding.
Please be sure to thank Chainfire, Dees_Troy, and Kaito95.
*****
Noob here, first off I unrooted a while ago, then took the ota 4.3, is the bootloader locked? Cause according to the cf auto root site if your bootloader is locked you'll probably brick your phone if you flash the auto root? Also do these steps have to be in order? I tried rooting by other means and installing supersu first, wouldn't work so I removed knox with the script, and then updated supersu in the play store and still nothing, can I try to flash cf auto root now and then update supersu in the play store? Thanks a million, need this thing rooted
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
jeremyds45 said:
Noob here, first off I unrooted a while ago, then took the ota 4.3, is the bootloader locked? Cause according to the cf auto root site if your bootloader is locked you'll probably brick your phone if you flash the auto root? Also do these steps have to be in order? I tried rooting by other means and installing supersu first, wouldn't work so I removed knox with the script, and then updated supersu in the play store and still nothing, can I try to flash cf auto root now and then update supersu in the play store? Thanks a million, need this thing rooted
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Well, I'm not bricked, so I think that answers your question about the bootloader.
Do you have a custom recovery installed? I assume so since you say you flashed the Knox remover script. If you do have a custom recovery installed, just flash the SuperSu zip, then update in the Play Store.
upndwn4par said:
Well, I'm not bricked, so I think that answers your question about the bootloader.
Do you have a custom recovery installed? I assume so since you say you flashed the Knox remover script. If you do have a custom recovery installed, just flash the SuperSu zip, then update in the Play Store.
Click to expand...
Click to collapse
Ah it is so nice to have root again... Thank you so much for putting up with a noob.
Crazy events of a noob that lead me to root
Installed ota 4.3
Tried to root and install superuser by odin and then custom recovery to flash
Root didn't happen because of knox
Could only get to CWM custom recovery if it was right after odin and battery pull?...
Flashed the script to remove knox, which did remove knox
Tried the same root method as above and no root access
Tried supersu and then updating in play with no success
Changed security update settings etc nothing
Reset delvik, cache, permissions, etc nothing
Different root method and files for odin, and custom recovery stuck
Used files from this thread, went into custom recovery and flashed supersu
Installed supersu from play store...
Updated the binary using custom recovery
Rebooted...
ROOT access, all root applications work fine and root sticks even after reboots
I never messed with cf auto root method
THANK you guys for your time effort and sharing, helps noobs out like me a lot!
Sweet! I've missed root since I upgraded using the OTA file you provided. Looking forward to much other great things coming from you
Thank You
upndwn4par said:
Warning: Following any of these instructions will void your warranty, and could possibly cause irreparable harm to your device (i.e. bricked). If you do not understand these risks, stop here and do not proceed. If you do not know how to use Odin, stop here and do not proceed. I am not responsible for anything that happens to your device. YOU chose to follow this guide.
If you have not updated to 4.3, go here. Make sure you understand the risks and uncertainties described in the OP.
Finally, there is no guarantee that either method will work for you.
Root Method #1:
The first thing you should try is CF-Autoroot since this has worked for many users.
If you successfully root with this method, you can simply install Goo Manager or ROM Manager and install recovery.
This method failed for me after many attempts.
Root Method #2:
1) Reboot in to download mode
2) Flash TWRP with Odin via PDA
3) Reboot to recovery and flash SuperSu.
4) Flash the Knox Remover
5) Reboot
6) Download SuperSu from the Play Store
7) Update the binary when prompted
8) Reboot
8) Enjoy 4.3
Downloads:
Odin
TWRP (Odin flashable tar)
UpdateSuperSu
If you found another method that worked for you, please post here so that others may benefit.
If you are uncertain about any of the steps above, please ask your questions here before proceeding.
*****
Click to expand...
Click to collapse
Method two absolutely worked. Thank you so much. I was scared to flash TWRP but knowing you did it gave me the courage. Have full root and happy
questions about this root
Hi, I'm a little nervous with this root but I need the root as the phone is useless without it.
I have the [email protected] galaxy s3 I747 will all these files work with it im just double checking.
Also do you flash the knox remover the same way as you flash other things with the pda button?
Will I still be able to do factory restores?
Also I saw that knox remover removes a lot of apps, Can you install these deleted apps from the market if you need too?
THanks please let me know asap.
THANKS!!!! your a lifesaver didn't know how much longer i could take without root
Dunno where you guys got your 4.3 update from and how you got it working but I did the OTA and Root just does not want to stick. I used knox remover and Cf auto root but it loses root after a restart. SuperSu never opens and crashes as soon as you open it. I have a feeling Cf auto root is just not compatible for the ota 4.3 i747??
bkong said:
Dunno where you guys got your 4.3 update from and how you got it working but I did the OTA and Root just does not want to stick. I used knox remover and Cf auto root but it loses root after a restart. SuperSu never opens and crashes as soon as you open it. I have a feeling Cf auto root is just not compatible for the ota 4.3 i747??
Click to expand...
Click to collapse
use the TWRP method worked perfected for me
Thanks
PimpMyPC said:
Hi, I'm a little nervous with this root but I need the root as the phone is useless without it.
I have the [email protected] galaxy s3 I747 will all these files work with it im just double checking.
Also do you flash the knox remover the same way as you flash other things with the pda button?
Will I still be able to do factory restores?
Also I saw that knox remover removes a lot of apps, Can you install these deleted apps from the market if you need too?
THanks please let me know asap.
Click to expand...
Click to collapse
The second method worked great. I believe (and the way that worked for me) that you use your custom recovery to flash the knox script, not using Odin and pda. I don't think it removed anything other than knox, there is a different script for removing knox and att bloatware. Should still be able to factory reset... But can't guarantee that.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Root & Knox
When you go to Settings/More tab/Security/Device Administrators, You have KNOX and Android Device Manage. Both are unchecked on mine. So does that mean Knox is not working if unchecked and safe to try to Root?????
tailgunner9 said:
When you go to Settings/More tab/Security/Device Administrators, You have KNOX and Android Device Manage. Both are unchecked on mine. So does that mean Knox is not working if unchecked and safe to try to Root?????
Click to expand...
Click to collapse
Those settings are just for granting device administrator privileges. If unchecked, Knox is still doing it's thing, just not at an administrative level.
Yes, it is safe to try and root.
I have Android Device Manager as admin. That way if I ever lose my device I can just log in to the Play Store and locate and / or wipe the device.
To do this just flash the recovery.img file using odin and clicking the pda button correct?
Is there a way to freeze Knox instead of deleting it in the event I would want to go back to full stock?
After you are rooted, use an app like Titanium Backup(pro) or My Backup pro. Both will freeze it.
Root
If some of you out there use Root Method #2 and it works well and No problems, Please post and let us all know. Thanks
tailgunner9 said:
If some of you out there use Root Method #2 and it works well and No problems, Please post and let us all know. Thanks
Click to expand...
Click to collapse
I tried method 1 and failed.
Then tried method 2, but using a CMW tar that was posted yesterday.
I seem to be rooted!
So far no issues.. Just need to get everything setup as I had it in the leak.
indymx said:
I tried method 1 and failed.
Then tried method 2, but using a CMW tar that was posted yesterday.
I seem to be rooted!
So far no issues.. Just need to get everything setup as I had it in the leak.
Click to expand...
Click to collapse
Thanks indymx, may get the nerve up to try it on my AT&T S3. Let me know if you run into any problems. Guess Rom Manager and other programs that require Root are working Ok and you have rebooted few times to be sure it keeps Root?? Have Happy Thanksgiving.
Hello, I've tried to root my phone by various method available but in vain..
After I did it with CF root and Odin, I got security message on the phone when trying to open superSU (unrespond close).
Also, when verify the root access through rood checker, it says wasn't root properly..
Please help..anyone able to do it?
I've already increase my binary count to 2 and knox to 1. :/
See my phone details attached..
Thanks
Cypher_SGN2 said:
Hello, I've tried to root my phone by various method available but in vain..
After I did it with CF root and Odin, I got security message on the phone when trying to open superSU (unrespond close).
Also, when verify the root access through rood checker, it says wasn't root properly..
Please help..anyone able to do it?
I've already increase my binary count to 2 and knox to 1. :/
See my phone details attached..
Thanks
Click to expand...
Click to collapse
As far as it goes I think after rooting it with CFroot you should update the SuperSU from the Playstore.
Success
hagba said:
As far as it goes I think after rooting it with CFroot you should update the SuperSU from the Playstore.
Click to expand...
Click to collapse
nice..I finally succeeded to root my phone!
Going for DN3 rom..
Thanks!
Fail to intall DN3
hagba said:
As far as it goes I think after rooting it with CFroot you should update the SuperSU from the Playstore.
Click to expand...
Click to collapse
Hello, I was trying to update my note 2 with DN3 kitkat rom today.. But didn't work! :/
I rooted the phone. I got correct root access.
Then followed the instruction to flash the ROM.
After reboot, I could hear the welcome sound(new) and saw the samsung animated logo..then it stuck there. I waited for some 15mins, but nothing happened, only the animated samsung logo.
I saw an issue in TWRP.. saying there was a problem with permission. I don't know what was it. I tried to fix permission, but it failed.
After nothing worked, now I am in the process of recovery from kies.
Perhaps I didn't have the right step by step guide; from rooting the phone to flashing it. :/
If someone could please help, would be great!.. I really want to flash my phone for the DN3 custom rom.
Thanks.
Why do you need to root when flashing custom rom? It is already prerooted. You only need recovery.
madman_cro said:
Why do you need to root when flashing custom rom? It is already prerooted. You only need recovery.
Click to expand...
Click to collapse
As per rooting instruction, it is mentioned that the device must be rooted before flashing a custom rom from stock rom.
While installing the recovery the device is rooted or another way that I tried was to root by CFroot first, which was successfully done then I got the super user access to install a recovery like TWRP,,
Cypher_SGN2 said:
As per rooting instruction, it is mentioned that the device must be rooted before flashing a custom rom from stock rom.
While installing the recovery the device is rooted or another way that I tried was to root by CFroot first, which was successfully done then I got the super user access to install a recovery like TWRP,,
Click to expand...
Click to collapse
+1
Sent from my GT-N7100 using XDA Premium 4 mobile app
As far as i know for latest 4.4.2 stock roms,
Try to flash philz advance recovery(md5.tar) through odin & then flash su.zip from recovery.
Done.
Sent from my GT-N7100 using XDA Premium 4 mobile app
**IGNORE POST #1 ONLY FOLLOW POST #2-#4!!!**
Info and DL on SuperSU v2.6x and Systemless Root
1. MUST flash a 100% stock (Odin) firmware.
2. DL SuperSU v2.6x
3. Install custom recovery
4. Install new SuperSU zip
5. Let it run through the process then reboot.
Hey Joe, your link about the info is broken. Also your 'click source' on #2. is not a link.
balistic2 said:
Hey Joe, your link about the info is broken. Also your 'click source' on #2. is not a link.
Click to expand...
Click to collapse
I think that this is the link: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
If I read Chainfire's notes correctly, this is only for systems running Marshmallow, which would let us out for a while. But....
Once Samsung updates our OS to Marshmallow or they get CM 13 working on our phones (currently a work in progress) this could allow us to use Android Pay on a rooted phone.
balistic2 said:
Hey Joe, your link about the info is broken. Also your 'click source' on #2. is not a link.
Click to expand...
Click to collapse
Fixed!
koop1955 said:
I think that this is the link: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
If I read Chainfire's notes correctly, this is only for systems running Marshmallow, which would let us out for a while. But....
Once Samsung updates our OS to Marshmallow or they get CM 13 working on our phones (currently a work in progress) this could allow us to use Android Pay on a rooted phone.
Click to expand...
Click to collapse
I do not believe it is MM only bc it's posted in the international S6 general forum too (and they obviously aren't on MM yet either).
JoeFCaputo113 said:
I do not believe it is MM only bc it's posted in the international S6 general forum too (and they obviously aren't on MM yet either).
Click to expand...
Click to collapse
I wasn't sure if CM13 is already working on International phones.
I only know what I read....
From Chainfire's post:
Rooting procedure:
- flash/upgrade to Marshmellow
- flash modified boot.img
- flash/boot TWRP and sideload latest...
Joe, be careful if you try this. Looks like you need to Odin back to stock.
Does this still void knox?
1619415 said:
Does this still void knox?
Click to expand...
Click to collapse
That is the key question. Also, would Google detect the phone as being rooted.
For the Knox part, someone with a "virgin" phone would need to test. Both Joe and I have already rooted using the current method, so Knox is already tripped.
koop1955 said:
That is the key question. Also, would Google detect the phone as being rooted.
For the Knox part, someone with a "virgin" phone would need to test. Both Joe and I have already rooted using the current method, so Knox is already tripped.
Click to expand...
Click to collapse
Seems to work on Note 5, just flashed TWRP with ODIN and then flashed SuperSu and there is no text while booting
---------- Post added at 09:19 PM ---------- Previous post was at 08:29 PM ----------
Thank you for posting this, now we have a method of rooting that A: Does not require custom kernels #Marshmallow and B: May not trip Knox
1619415 said:
Seems to work on Note 5, just flashed TWRP with ODIN and then flashed SuperSu and there is no text while booting
---------- Post added at 09:19 PM ---------- Previous post was at 08:29 PM ----------
Thank you for posting this, now we have a method of rooting that A: Does not require custom kernels #Marshmallow and B: May not trip Knox
Click to expand...
Click to collapse
Well Merry Christmas!
JoeFCaputo113 said:
Well Merry Christmas!
Click to expand...
Click to collapse
You to
---------- Post added at 01:52 PM ---------- Previous post was at 01:01 PM ----------
Has anyone tried rooting with this method and trying samsumg pay?
Decided to give this a try. Odin flashed OL1. Booted OL1 with no problem. Odin flashed TWRP, without reboot. Rebooted directly into TWRP and flashed SU beta 2.65. It booted without problem with root access. When I go into SU, it says there is an update available, but I just cancel out.
I was hoping android pay would work as I could never get it to work except stock unrooted. I started android pay and got the message "android pay cannot be used." I realized I needed to unroot in SU. I did that and still get the same message.
EDIT: Tried it again. Odined OL1, rebooted and android pay worked fine. Odined TWRP, booted into TWRP, fine. Rebooted into rom, bootlooped at Samsung logo, over and over. Rebooted into recovery and flashed SU 2.65. Rebooted into rom with no problem. Android Pay no longer works.
todivefor said:
Decided to give this a try. Odin flashed OL1. Booted OL1 with no problem. Odin flashed TWRP, without reboot. Rebooted directly into TWRP and flashed SU beta 2.65. It booted without problem with root access. When I go into SU, it says there is an update available, but I just cancel out.
I was hoping android pay would work as I could never get it to work except stock unrooted. I started android pay and got the message "android pay cannot be used." I realized I needed to unroot in SU. I did that and still get the same message.
EDIT: Tried it again. Odined OL1, rebooted and android pay worked fine. Odined TWRP, booted into TWRP, fine. Rebooted into rom, bootlooped at Samsung logo, over and over. Rebooted into recovery and flashed SU 2.65. Rebooted into rom with no problem. Android Pay no longer works.
Click to expand...
Click to collapse
Try Number 15
1619415 said:
Try Number 15
Click to expand...
Click to collapse
Thanks. Been there done that.
Sent from my SM-T710 using Tapatalk
For those asking about whether this root method trips knox or not. Yes this will trip knox. Anytime you use odin to flash non official Samsung firmware/software then it forever trips knox. Therefore flashing any custom recovery will absolutely trip knox... forever.
Samsung and Android pay apps will not work on rooted devices. Period. The pay apps are intended for official factory software for obvious reasons. Security is the main focus with these types of apps that deal with your personal banking/credit card information. Hence a rooted device is not considered "secure".
using this method and my S6 is rooted without custom kernel which i prefer.
however, it seems like i cant use titanium backup to restore any backed up apps. Titanium app just runs endlessly.
yaibakt said:
using this method and my S6 is rooted without custom kernel which i prefer.
however, it seems like i cant use titanium backup to restore any backed up apps. Titanium app just runs endlessly.
Click to expand...
Click to collapse
Try installing/updating busybox and try removing titanium backups root access them regrant it
JoeFCaputo113 said:
**IGNORE POST #1 ONLY FOLLOW POST #2-#4!!!**
Info and DL on SuperSU v2.6x and Systemless Root
1. MUST flash a 100% stock (Odin) firmware.
2. DL SuperSU v2.6x
3. Install custom recovery
4. Install new SuperSU zip
5. Let it run through the process then reboot.
Click to expand...
Click to collapse
Nice work will give this a go soon.
1619415 said:
Try installing/updating busybox and try removing titanium backups root access them regrant it
Click to expand...
Click to collapse
thank you. ill give it a try. :good:
This may be a weird question, but we don't have a stock kernel to flash. Would there be a way to make a zip of a stock kernel and then use this to get root? I'd like to have a custom ROM but with the stability of a stock Kernel. This is the first phone I can think of that I've owned that didn't have a stock kernel with root.