Related
Root. A word so simple, yet so complexed.
Every android user on XDA should know what it is, but people only know what they can do with it, not how and why.
There are already a ton of threads describing what root is, but here's something most of those threads forget:
To obtain root access, you need a 'su' binary inside /system/bin .
Also, you need an app to control apps that gain root privileges. The two you're most likely to hear about are SuperUser (SU) and SuperSuperUser (SuperSU).
So, if you have a recovery, you can flash a zip file that puts a su binary inside /system/bin , and installs the controller app (SuperUser and SuperSU). -- That way you don't need a PC to root your phone. Also, you don't lose any data and there's no risk of bricking your phone.
But, as I can see, people here aren't aware that they don't need PCs for rooting.
They flash kernels from all sorts of stock FW releases, use a billion programs, and finally, they get root after a good amount of time and flashing, usually with a lot of risk of bricks.
So, a quick step-by-step guide on how to do root like a pro:
1. You need a phone with a recovery and internet (be it WiFi or mobile data).
2. Go here: http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip and save the file to your phone. Remember where you saved it!
3. Boot into recovery and flash the zip.
4. Reboot back into Android
Optional:
5. Realize that this process is far better than the ones that need a PC, because it's simpler. Thank me.
6. Tell it to your friends, so they don't mess around with huge downloads and flashing kernels.
someone755 said:
Root. A word so simple, yet so complexed.
Every android user on XDA should know what it is, but people only know what they can do with it, not how and why.
There are already a ton of threads describing what root is, but here's something most of those threads forget:
To obtain root access, you need a 'su' binary inside /system/bin .
Also, you need an app to control apps that gain root privileges. The two you're most likely to hear about are SuperUser (SU) and SuperSuperUser (SuperSU).
So, if you have a recovery, you can flash a zip file that puts a su binary inside /system/bin , and installs the controller app (SuperUser and SuperSU). -- That way you don't need a PC to root your phone. Also, you don't lose any data and there's no risk of bricking your phone.
But, as I can see, people here aren't aware that they don't need PCs for rooting.
They flash kernels from all sorts of stock FW releases, use a billion programs, and finally, they get root after a good amount of time and flashing, usually with a lot of risk of bricks.
So, a quick step-by-step guide on how to do root like a pro:
1. You need a phone with a recovery and internet (be it WiFi or mobile data).
2. Go here: http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip and save the file to your phone. Remember where you saved it!
3. Boot into recovery and flash the zip.
4. Reboot back into Android
Optional:
5. Realize that this process is far better than the ones that need a PC, because it's simpler. Thank me.
6. Tell it to your friends, so they don't mess around with huge downloads and flashing kernels.
Click to expand...
Click to collapse
A Simple question, how can i get recovery, if for get it, i need first a root phone?
SteBanVe said:
A Simple question, how can i get recovery, if for get it, i need first a root phone?
Click to expand...
Click to collapse
I think u need an unlocked bootloader. U can root using bin4ry method without unlocking bootloader but it works upto 6.1.a.2.50 only.
Sent from my LT26i using xda app-developers app
bluechelsea said:
I think u need an unlocked bootloader. U can root using bin4ry method without unlocking bootloader but it works upto 6.1.a.2.50 only.
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
i have Xperia S 2.55, and bin4ry method doest work. To apply this method, i repeat my question how can i get recovery, if for get it, i need first a rooted phone?
someone755 said:
1. You need a phone with a recovery...
Click to expand...
Click to collapse
How do you suppose we get a custom recovery without using different tools or unlocking bootloader?
Yes great guide, but only for UB ... for LB you need root BEFORE you install CWM...
al with .55 FW i recomend - flash any older rootable FW, root it, install CWM ... via CWM flash stockbased rom ( KA, XTX ) and thats all... or you an flash prerooted .55 FW ....
Okay, fine, schratch that!
Use goo.im manager from the play store and install the TWRP recovery!
Problem solved, but the main point is that people don't need PCs for root!!
someone755 said:
Okay, fine, schratch that!
Use goo.im manager from the play store and install the TWRP recovery!
Problem solved, but the main point is that people don't need PCs for root!!
Click to expand...
Click to collapse
I installed the app now how do i install recovery and boot into it?
Sent from my LT26i using xda app-developers app
I prefer an open source alternative. We have no idea what supersu actually is doing if the source is not availible without a lot of work. So is it possible?
if you're already rooted you can just install superuser from the play store, then go into SuperSu Settings, scroll down, select "Switch superuser app," and follow the instructions SuperSu tells you.
If not you can just follow the rooting steps from any tutorial here on the Nexus 7 forums and just flash the appropriate zip from http://androidsu.com/superuser/ instead of the SuperSu zip.
TheAltruistic said:
if you're already rooted you can just install superuser from the play store, then go into SuperSu Settings, scroll down, select "Switch superuser app," and follow the instructions SuperSu tells you.
If not you can just follow the rooting steps from any tutorial here on the Nexus 7 forums and just flash the appropriate zip from http://androidsu.com/superuser/ instead of the SuperSu zip.
Click to expand...
Click to collapse
Does chainsdd superuser work with the security changes in 4.3?
sfhub said:
Does chainsdd superuser work with the security changes in 4.3?
Click to expand...
Click to collapse
Aaaa.... Not sure to be honest. I use and like SuperSu myself. You should shoot an email to the dev and see if they can answer that for you. Sorry I can't give you a better answer mate
TheAltruistic said:
Aaaa.... Not sure to be honest. I use and like SuperSu myself. You should shoot an email to the dev and see if they can answer that for you. Sorry I can't give you a better answer mate
Click to expand...
Click to collapse
Last I heard superuser didn't support 4.3, which is why I asked.
Everyone on 4.3 switched to SuperSU because they put in a daemon mode to workaround the 4.3 security changes.
Since you mentioned how to use superuser, I just was wondering if they had addressed the issue. I didn't see a newer version on the play store so I assumed they didn't but there could always be newer information available, hence the question.
Yeah that would be good info for the OP. :good: Thank you!
|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.
sooo i was stock i took the OTA update to 4.3 mk6
i decided i didn't care about the knox counter so i rooted and custom recovery (this is the rom location http://forum.xda-developers.com/showthread.php?t=2589891) and this is the recovery location http://forum.xda-developers.com/showthread.php?t=2159652
now every thing is working (SU, Titanium Back up, and so on)
however when i try certain apps (game killer, game chi) it says i don't have root
i have searched everywhere but i am not seeing any posts about this
any help would be greatly appreciated
You could flash superSU from recovery to system...
That often corrects the issue...
Did you download superSU from the market and update it ??
Try that first....and if no change....flash this....g
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
gregsarg said:
You could flash superSU from recovery to system...
That often corrects the issue...
Did you download superSU from the market and update it ??
Try that first....and if no change....flash this....g
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
Click to expand...
Click to collapse
thanks for the help i will try this now
gregsarg said:
You could flash superSU from recovery to system...
That often corrects the issue...
Did you download superSU from the market and update it ??
Try that first....and if no change....flash this....g
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
Click to expand...
Click to collapse
i uninstalled superSU then went to the market and downloaded and updated that didn't work it was still the same
no i have downloaded and installed from customer recovery and when i open superSU it says i need to manually re-root my phone so i guess i need to re flash my rom from original post?
Try installing the current version of SuperSU via Odin.. you shouldn't have to reinstall the rom...
Once SuperSU is installed, boot phone, check Play Store for updates for SuperSU and install if any. Then run SuperSU, update the binary if prompted, then when asked to disable Knox, answer yes. You should be good to go.
Zen Arcade said:
Try installing the current version of SuperSU via Odin.. you shouldn't have to reinstall the rom...
Once SuperSU is installed, boot phone, check Play Store for updates for SuperSU and install if any. Then run SuperSU, update the binary if prompted, then when asked to disable Knox, answer yes. You should be good to go.
Click to expand...
Click to collapse
okay i found it and did it and now i am back where i started most things work but the 2 app's i use most still say root permission denied (granted permission in superSU)
mrnewspaper said:
okay i found it and did it and now i am back where i started most things work but the 2 app's i use most still say root permission denied (granted permission in superSU)
Click to expand...
Click to collapse
Remove them from SU list. Restart app and approve the SU request again.....
dicksteele said:
Remove them from SU list. Restart app and approve the SU request again.....
Click to expand...
Click to collapse
okay done and no change
mrnewspaper said:
okay i found it and did it and now i am back where i started most things work but the 2 app's i use most still say root permission denied (granted permission in superSU)
Click to expand...
Click to collapse
Which apps?
Zen Arcade said:
Which apps?
Click to expand...
Click to collapse
the apps that wont work are game chi and game killer
the apps that are working looks like all of my apps that require root other then those 2
even root checker says i do have root
mrnewspaper said:
the apps that wont work are game chi and game killer
the apps that are working looks like all of my apps that require root other then those 2
even root checker says i do have root
Click to expand...
Click to collapse
Game Killer - Comments on Play Store show that this is a known issue with 4.3 and SuperSU with this app.
GameCIH - (I assume this is what you meant) Comments on Play Store also show a known issue with 4.3. Some comments from dev about enabling USB debugging, but it appears to be a 4.3 issue.
Looks like you are out of luck for now unless you step back to 4.2 or below.
Zen Arcade said:
Game Killer - Comments on Play Store show that this is a known issue with 4.3 and SuperSU with this app.
GameCIH - (I assume this is what you meant) Comments on Play Store also show a known issue with 4.3. Some comments from dev about enabling USB debugging, but it appears to be a 4.3 issue.
Looks like you are out of luck for now unless you step back to 4.2 or below.
Click to expand...
Click to collapse
i didn't see those notes but thanks to everyone for all the help and i will look in to stepping back again (i bricked the first time)
If you have the MK6 bootloader, avoid the MA4 stock package. You'll need the LJ2 stock package (which does not have a bootloader in it). See this guide... you can follow it up to the point where you have MH3 on your phone and then stop:
http://forum.xda-developers.com/showthread.php?t=2618447
Zen Arcade said:
If you have the MK6 bootloader, avoid the MA4 stock package. You'll need the LJ2 stock package (which does not have a bootloader in it). See this guide... you can follow it up to the point where you have MH3 on your phone and then stop:
http://forum.xda-developers.com/showthread.php?t=2618447
Click to expand...
Click to collapse
awesome thank you
Hello people,
I have a Note 2 (SGH-i317m) running the MVLUCMK5 Official Android 4.3 rom. I flashed the cf-autoroot from chainfire's website using odin and download mode, updated super SU as soon as the device booted, disabled Knox and got the device rooted. Root was working fine. Titanium backup could restore the app backup and everything.
However, when I restarted the phone, the root was gone. Any idea what's going on? I will have to flash CF again and it will work. But the flash counter keeps counting every flash. Is there a permanent root method for 4.3?
PS: Sorry to hijack this thread. I figured there was a relevant discussion going on, why clutter the section with a new thread. Also, since my post count is low, I couldn't post in CF's thread.
pavanchirmade said:
Hello people,
I have a Note 2 (SGH-i317m) running the MVLUCMK5 Official Android 4.3 rom. I flashed the cf-autoroot from chainfire's website using odin and download mode, updated super SU as soon as the device booted, disabled Knox and got the device rooted. Root was working fine. Titanium backup could restore the app backup and everything.
However, when I restarted the phone, the root was gone. Any idea what's going on? I will have to flash CF again and it will work. But the flash counter keeps counting every flash. Is there a permanent root method for 4.3?
PS: Sorry to hijack this thread. I figured there was a relevant discussion going on, why clutter the section with a new thread. Also, since my post count is low, I couldn't post in CF's thread.
Click to expand...
Click to collapse
Sounds like you may be using an older version of cf-auto-root? Try this one via Odin:
main - http://autoroot.chainfire.eu/
i317m - http://download.chainfire.eu/279/CF-Root/CF-Auto-Root/CF-Auto-Root-t0ltecan-t0ltevl-sghi317m.zip
Zen Arcade said:
Sounds like you may be using an older version of cf-auto-root? Try this one via Odin:
main - http://autoroot.chainfire.eu/
i317m - http://download.chainfire.eu/279/CF-Root/CF-Auto-Root/CF-Auto-Root-t0ltecan-t0ltevl-sghi317m.zip
Click to expand...
Click to collapse
I flashed the same one.
Are you running the stock kernel?
After you flash cf-auto-root and boot phone, what do the contents of this file look like?
/system/etc/install-recovery.sh
Does it reference SuperSU and run daemonsu or does it reference recovery-from-boot.p ?
Zen Arcade said:
Are you running the stock kernel?
After you flash cf-auto-root and boot phone, what do the contents of this file look like?
/system/etc/install-recovery.sh
Does it reference SuperSU and run daemonsu or does it reference recovery-from-boot.p ?
Click to expand...
Click to collapse
Here's a screenshot.
That's the correct file...
A deeper dive would involve looking at the permissions and properties of su and daemonsu in /system/xbin as well as a few other SuperSU related files in /system and subdirectories.
If you are running a custom kernel it's possible that it is pushing an older version of SuperSU (or other superuser app).
Do you have only the SuperSU app installed (i.e. no SuperUser or other app in the app drawer)?
Reaching at this point as it's not typical for the current versions of SuperSU to lose root.
One thing you can try is root with current, boot phone, immediately run SuperSU, choose "Full Unroot", reboot boot phone, then shutdown and reflash cf-auto-root and see if it sticks.
As for flash counter, once you get root to stick, you can use Triangle Away to reset that to zero - works for everything but the knox warranty counter.
It seems there would be a problem in flashing normal downloaded SU and have to go through the long process of flashing systemless SU after which have to upgrade it.
Is it normal for you guys too?
How come 1+3 bricks after installing normal SU?
b.t.w. personal note: thanks to one of the oneplus rep that was in the euro tour in Rome the TWRP recovery fix worked (sorry forgot your name ). Really appreciate the chat and help out!
No, i downloaded normal su (SuperSU) and then flashed it through TWRP. I don't know which su you are using, but there are loads of us who have installed SuperSU without an issue.
nemexs said:
It seems there would be a problem in flashing normal downloaded SU and have to go through the long process of flashing systemless SU after which have to upgrade it.
Is it normal for you guys too?
How come 1+3 bricks after installing normal SU?
b.t.w. personal note: thanks to one of the oneplus rep that was in the euro tour in Rome the TWRP recovery fix worked (sorry forgot your name ). Really appreciate the chat and help out!
Click to expand...
Click to collapse
You may have the wrong flashable, flashing supersu on the OP3 for me is very quick and painless. Make sure you have the latest from chainfire's website v2.76 at the time of me posting this. : http://download.chainfire.eu/supersu-stable
PS: regular supersu is both systemless and "normal" root it makes a decision during installation determining whether your device can support normal root and if not then it does a systemless boot.img patch.
StykerB said:
You may have the wrong flashable, flashing supersu on the OP3 for me is very quick and painless. Make sure you have the latest from chainfire's website v2.76 at the time of me posting this. : http://download.chainfire.eu/supersu-stable
Click to expand...
Click to collapse
You beat me to pointing him to it. If I can add, there's a dedicated SuperSU thread to seek help if SuperSU causes an issue:
http://forum.xda-developers.com/showthread.php?t=1538053
Highly unlikely but just in case. If you are not sure, there are sufficient number of toolkits out there that can simplify the job for you.
@tropicanapure @StykerB
Have tried them the only way I can flash SU is downloading @ahmed_radaideh 's oneplus3 toolkit and then flashing his SU. Tried the normal version and the problem seems to be present (brick), yes chainfire's su. If I don't want to do full wipe I'd have wipe system and just reflash stock and then systemless su
nemexs said:
@tropicanapure @StykerB
Have tried them the only way I can flash SU is downloading @ahmed_radaideh 's oneplus3 toolkit and then flashing his SU. Tried the normal version and the problem seems to be present (brick), yes chainfire's su. If I don't want to do full wipe I'd have wipe system and just reflash stock and then systemless su
Click to expand...
Click to collapse
Then you may want to check the process y you are using for this.
If I can ask what exactly are you trying to fix? Do you already have SuperSU installed? And you are trying to move to systemless?
Or are you unable to install SuperSU itself? If yes, then you may want to post to the SuperSU thread too.
tropicanapure said:
Then you may want to check the process y you are using for this.
If I can ask what exactly are you trying to fix? Do you already have SuperSU installed? And you are trying to move to systemless?
Or are you unable to install SuperSU itself? If yes, then you may want to post to the SuperSU thread too.
Click to expand...
Click to collapse
I had no problem in installing it systemless, however just wanted to see if everyone else had to go through the same process. It seems not, now I'm trying to find out how come I can't install normally.
nemexs said:
I had no problem in installing it systemless, however just wanted to see if everyone else had to go through the same process. It seems not, now I'm trying to find out how come I can't install normally.
Click to expand...
Click to collapse
You still haven't mentioned the process you use[emoji6]
The process most commonly used via TWRP is to download the zip from the link above and flash it. That's all there is to it.
tropicanapure said:
You still haven't mentioned the process you use[emoji6]
The process most commonly used via TWRP is to download the zip from the link above and flash it. That's all there is to it.
Click to expand...
Click to collapse
my bad, yes I use twrp method 3.0.2 the most recent one, flash stock rom and then flash su
nemexs said:
my bad, yes I use twrp method 3.0.2 the most recent one, flash stock rom and then flash su
Click to expand...
Click to collapse
Assuming your bootloader is already unlocked beforehand, the straight answer to your question is yes, that's how most of us do it.
No problem with flashing SU whatsoever,
and i rather not to use any toolkit to flash either recovery or anything,
fastboot for recovery and recovery for anything else,
Simple, straight and safe
otonieru said:
No problem with flashing SU whatsoever,
and i rather not to use any toolkit to flash either recovery or anything,
fastboot for recovery and recovery for anything else,
Simple, straight and safe
Click to expand...
Click to collapse
doesn't work for me.