This is SuperSU that installs always in System-Mode.
Instructions
1 - Download zip
2 - Go in recovery & make a backup (optional, but recommended)
3 - Flash zip
Changelogs here & here
Special thanks to @aufarxda (the original creator of this thread) @Chainfire @CCMT
binaries failed to update
Just installed the lastest security update (6.01) from google on my nexus 6. Flashed v2.66 and binaries will not update. Any suggestions?
Thanks My Brother ?
Reflash the kernel.
Unroot.
Reroot.
Should work.
Hope that helps.
aufarxda said:
Reflash the kernel.
Unroot.
Reroot.
Should work.
Hope that helps.
Click to expand...
Click to collapse
I am on CM13 1/6/2016 nightly on angler, and this is causing a bootloop now. Before this newest nightly, I was able to install with no problem. Systemless also still works.
fpqc said:
I am on CM13 1/6/2016 nightly on angler, and this is causing a bootloop now. Before this newest nightly, I was able to install with no problem. Systemless also still works.
Click to expand...
Click to collapse
Nightly comes with problems.Look Angler's XDA thread and ask others which nightly is the most stable build.
Hope that helps.
aufarxda said:
Nightly comes with problems.Look Angler's XDA thread and ask others which nightly is the most stable build.
Hope that helps.
Click to expand...
Click to collapse
The reason I think is that this is the first update with the newest vendor.img. That's the only thing that seems out of the ordinary.
fpqc said:
The reason I think is that this is the first update with the newest vendor.img. That's the only thing that seems out of the ordinary.
Click to expand...
Click to collapse
Well, just reflash last update before this one.
Or, just wait another update with the fix.
I have the Verizon SCH-I545, MDK bootloader, and am running JDC Team's AOSP 6.0.
I am unable to install any version of SU above 2.52. TWRP 2.8.7.0 and 2.8.7.2 by Antaresone and the official 2.8.7.0 all fail with the same message.
Recovery.log
https://www.dropbox.com/s/kmc3bafuvlfq20v/recovery.log?dl=0
FernBch said:
I have the Verizon SCH-I545, MDK bootloader, and am running JDC Team's AOSP 6.0.
I am unable to install any version of SU above 2.52. TWRP 2.8.7.0 and 2.8.7.2 by Antaresone and the official 2.8.7.0 all fail with the same message.
Recovery.log
https://www.dropbox.com/s/kmc3bafuvlfq20v/recovery.log?dl=0
Click to expand...
Click to collapse
Solution 1(Tricky, and may not work) :
Try to mount data and system using mount option and remove mounting script on the updater-binary.
Then, use TWRP file manager to remove /supersu manually.
At last, install the zip again.
Solution 2 (not really a solution) :
If you really cant mount data or system, ask the rom dev or someone on your phone's forum for solution.
Solution 3 (1% chance of working) :
Dont bother about the bootloader.
Check your boot image instead.
Solution 4 :
Check if you have chcon on system/bin.
If not download this file and move it into system/bin.
Link :Drive
Hi,
Thanks! This version finally works for secondary roms in Multrirom!!!
Droidphilev said:
Hi,
Thanks! This version finally works for secondary roms in Multrirom!!!
Click to expand...
Click to collapse
Nice to know.
Can this be flashed over systemless root to convert to system root or will I have to flash my system.img backup then this. I'm running systemless root on Htc M9 Marshmallow dev edition
Sent from my HTC One M9 using Tapatalk
I installed 2.64 beta via TWRP. It installed successfully however upon reboot it shows i still have 2.52. Is that normal?
slick97477 said:
I installed 2.64 beta via TWRP. It installed successfully however upon reboot it shows i still have 2.52. Is that normal?
Click to expand...
Click to collapse
Don't know. Maybe install the app on the zip manually. Update the binary and if updating fails, full unroot and re-root with the new zip.
krazyace35 said:
Can this be flashed over systemless root to convert to system root or will I have to flash my system.img backup then this. I'm running systemless root on Htc M9 Marshmallow dev edition
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
No, full unroot first.
Then, remove /su
Replace the kernel with new custom one.
And then, flash the system mode zip.
aufarxda said:
No, full unroot first.
Then, remove /su
Replace the kernel with new custom one.
And then, flash the system mode zip.
Click to expand...
Click to collapse
Cool thanks for the info
Sent from my HTC One M9 using Tapatalk
---------- Post added at 06:00 PM ---------- Previous post was at 05:30 PM ----------
@aufarxda I'm guessing there are no custom kernels yet for Marshmallow? I can't find one I also noticed flar2 said the kernel source hasn't been released yet
Sent from my HTC One M9 using Tapatalk
krazyace35 said:
@aufarxda I'm guessing there are no custom kernels yet for Marshmallow? I can't find one I also noticed flar2 said the kernel source hasn't been released yet
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Maybe not avaiable for your phone.
But most Marshmallow phone devs already made custom kernels for their phones.
Thanks for this, @aufarxda. Can you tell us what you did and made it always install in System mode?
KreAch3R said:
Thanks for this, @aufarxda. Can you tell us what you did and made it always install in System mode?
Click to expand...
Click to collapse
I moved v2.52 script with little modifications (aside from the ui_print).
Related
Now that you installed TWRP or another custom recovery, here is a working GAPPS for Xiaomi Note Pro, this one so far works
perfectly, do not rely on manual install version as they are missing key lib and framework files.
http://www.slimdevs.com/Gapps/Lollipop-arm64/
lorinkundert said:
Now that you installed TWRP or another custom recovery, here is a working GAPPS for Xiaomi Note Pro, this one so far works
perfectly, do not rely on manual install version as they are missing key lib and framework files.
http://www.slimdevs.com/Gapps/Lollipop-arm64/
Click to expand...
Click to collapse
So just flash over the top of existing or is there more to it?
Thanks
Flashed. All working fine.
jazz452 said:
So just flash over the top of existing or is there more to it?
Thanks
Click to expand...
Click to collapse
You should if you already manually installed GAPPS, with my phone it was flash the ROM, flash TWRP, flash SU, and GAPPS
lorinkundert said:
You should if you already manually installed GAPPS, with my phone it was flash the ROM, flash TWRP, flash SU, and GAPPS
Click to expand...
Click to collapse
Installed over existing Gapps no problem except while rebooting and updating my phone was that hot I could hardly touch it. Sat it on a cool damp sponge, once it finished it cooled back to normal.
jazz452 said:
So just flash over the top of existing or is there more to it?
Thanks
Click to expand...
Click to collapse
Not Found
The requested URL /Gapps/Lollipop-arm64/ was not found on this server.
Can u reupload to mega? thx
FxJohnnyEng said:
Not Found
The requested URL /Gapps/Lollipop-arm64/ was not found on this server.
Can u reupload to mega? thx
Click to expand...
Click to collapse
Hi,
Uploaded to mega for you here's the link
https://mega.co.nz/#!iRkgxAYS!hIJFpAQ1SUjlkCq3Syr8v1iTz-lRnRMj5LRl-oIiqAo
Kahun said:
Hi,
Uploaded to mega for you here's the link
https://mega.co.nz/#!iRkgxAYS!hIJFpAQ1SUjlkCq3Syr8v1iTz-lRnRMj5LRl-oIiqAo
Click to expand...
Click to collapse
Thanks for your kindness
For root, need you guys clarify bit,
As i can see from this forum link: http://en.miui.com/download-262.html
Xiao mi note pro stable rom is V6.5.4.0.KXECNCD, can i use this root tutorial to activate root for my mi note pro instead of installing developer rom?
Thanks
FxJohnnyEng said:
Thanks for your kindness
For root, need you guys clarify bit,
As i can see from this forum link: http://en.miui.com/download-262.html
Xiao mi note pro stable rom is V6.5.4.0.KXECNCD, can i use this root tutorial to activate root for my mi note pro instead of installing developer rom?
Thanks
Click to expand...
Click to collapse
There is no root method released yet apart from installing the developer rom
Kahun said:
There is no root method released yet apart from installing the developer rom
Click to expand...
Click to collapse
Most important question to ask, i new to xiao mi environment,
Let say i install the developer rom, anytime i can download the stable rom and update over? While installing do i need clean data or the rom?
Do i need like use twrp to backup the stock rom first or something?
need your advice bro, and how about the recovery? as i know use flashify to backup and restore, as stock rom doesnt not have root yet, so cant backup as well.
Thanks if you can give me assurance
FxJohnnyEng said:
Most important question to ask, i new to xiao mi environment,
Let say i install the developer rom, anytime i can download the stable rom and update over? While installing do i need clean data or the rom?
Do i need like use twrp to backup the stock rom first or something?
need your advice bro, and how about the recovery? as i know use flashify to backup and restore, as stock rom doesnt not have root yet, so cant backup as well.
Thanks if you can give me assurance
Click to expand...
Click to collapse
You won't get TWRP on without developer rom first as it fails through fastboot. The only method is using Flashify. Best thing is staying with developer rom as it is stable, had no problem at all with it. You will also receive weekly updates. Just don't flash TWRP because the updates will brake it needs to be stock recovery. You can install the developer rom by downloading it onto your phone and installing it using the Updater app on your phone. Once you have activated it the root permissions a bit strange. First what you have to do is open app that required root permissions, close the app then go to Security App>Permissions>Root Access and select the app. Yes you can flash the stock rom back at any time but you will loose root. I'm waiting for Xiaomi to release the Kernel Source, when that happens we will have custom roms such as Cyaongen mod, root methods etc..
Kahun said:
You won't get TWRP on without developer rom first as it fails through fastboot. The only method is using Flashify. Best thing is staying with developer rom as it is stable, had no problem at all with it. You will also receive weekly updates. Just don't flash TWRP because the updates will brake it needs to be stock recovery. You can install the developer rom by downloading it onto your phone and installing it using the Updater app on your phone. Once you have activated it the root permissions a bit strange. First what you have to do is open app that required root permissions, close the app then go to Security App>Permissions>Root Access and select the app. Yes you can flash the stock rom back at any time but you will loose root. I'm waiting for Xiaomi to release the Kernel Source, when that happens we will have custom roms such as Cyaongen mod, root methods etc..
Click to expand...
Click to collapse
I've been updating weekly and I'm using TWRP as my recovery with no issues...
Kahun said:
You won't get TWRP on without developer rom first as it fails through fastboot. The only method is using Flashify. Best thing is staying with developer rom as it is stable, had no problem at all with it. You will also receive weekly updates. Just don't flash TWRP because the updates will brake it needs to be stock recovery. You can install the developer rom by downloading it onto your phone and installing it using the Updater app on your phone. Once you have activated it the root permissions a bit strange. First what you have to do is open app that required root permissions, close the app then go to Security App>Permissions>Root Access and select the app. Yes you can flash the stock rom back at any time but you will loose root. I'm waiting for Xiaomi to release the Kernel Source, when that happens we will have custom roms such as Cyaongen mod, root methods etc..
Click to expand...
Click to collapse
TWRP works fine on the stable ROM, you just have to hold the vol up and power button at first boot as you would if you want to go into
recovery mode
skw5115 said:
I've been updating weekly and I'm using TWRP as my recovery with no issues...
Click to expand...
Click to collapse
lorinkundert said:
TWRP works fine on the stable ROM, you just have to hold the vol up and power button at first boot as you would if you want to go into
recovery mode
Click to expand...
Click to collapse
Strangely enough I have 2 mi note pros and both of them can't update through TWRP. Yes TWRP will work fine in stable rom but u ll need root perm to flash it first. That's what I had to do as it failed through fastboot
Kahun said:
You won't get TWRP on without developer rom first as it fails through fastboot. The only method is using Flashify. Best thing is staying with developer rom as it is stable, had no problem at all with it. You will also receive weekly updates. Just don't flash TWRP because the updates will brake it needs to be stock recovery. You can install the developer rom by downloading it onto your phone and installing it using the Updater app on your phone. Once you have activated it the root permissions a bit strange. First what you have to do is open app that required root permissions, close the app then go to Security App>Permissions>Root Access and select the app. Yes you can flash the stock rom back at any time but you will loose root. I'm waiting for Xiaomi to release the Kernel Source, when that happens we will have custom roms such as Cyaongen mod, root methods etc..
Click to expand...
Click to collapse
So if i flash developer rom, recovery will remain stock and will have root access right? so i update developer rom and go back stock anytime without issue right?
Thanks for explanation, not feeling good to update twrp yet , later GG
Yup that's correct.
Kahun said:
Yup that's correct.
Click to expand...
Click to collapse
Dear Professor kahun,
Just to confirm, is this http://en.miui.com/download-262.html rom for Mi Note Pro? Just in case before i update it.
Thanks
FxJohnnyEng said:
Dear Professor kahun,
Just to confirm, is this http://en.miui.com/download-262.html rom for Mi Note Pro? Just in case before i update it.
Thanks
Click to expand...
Click to collapse
No that's MI Note. The download for MI Note Pro is here: http://en.miui.com/download-273.html
skw5115 said:
No that's MI Note. The download for MI Note Pro is here: http://en.miui.com/download-273.html
Click to expand...
Click to collapse
Thanks bro, lucky i download but haven update XD
FxJohnnyEng said:
Thanks bro, lucky i download but haven update XD
Click to expand...
Click to collapse
It would have failed anyway without editing the build.prop xD
Has anyone rooted and installed xposed and adaway on the recent update for the XT1095?
I've tried. Thus far, I get crashes galore using the latest systemless root. Have not gone farther than that yet. Anyone have any success?
Adaway and Root - but don't use Systemless, it just gives me fits.
I used this: forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
worked perfectly fine! Xposed is next up
iletired said:
Adaway and Root - but don't use Systemless, it just gives me fits.
I used this: forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
worked perfectly fine! Xposed is next up
Click to expand...
Click to collapse
Just to confirm - you flashed the kernel meant for the XT1097 (Brazilian BR-PT) on the US Pure Edition XT1095 Pure (TMO)?
lordloki77 said:
Just to confirm - you flashed the kernel meant for the XT1097 (Brazilian BR-PT) on the US Pure Edition XT1095 Pure (TMO)?
Click to expand...
Click to collapse
Yes, it works without a hitch. Not sure why, but it did. I tried Seamless, then it didn't work, so I used the .bat file and everything worked fine.
I did install xposed - see below
forum.xda-developers.com/showthread.php?t=3034811
File Type: zip xposed-v79-sdk23-arm.zip
AMP+ for the power menu was just updated for Marshmallow the other day and works
iletired said:
Yes, it works without a hitch. Not sure why, but it did. I tried Seamless, then it didn't work, so I used the .bat file and everything worked fine.
I did install xposed - see below
forum.xda-developers.com/showthread.php?t=3034811
File Type: zip xposed-v79-sdk23-arm.zip
AMP+ for the power menu was just updated for Marshmallow the other day and works
Click to expand...
Click to collapse
Didn't expect that to work. Thanks for confirming - I'll definitely try out at some point.
iletired said:
Yes, it works without a hitch. Not sure why, but it did. I tried Seamless, then it didn't work, so I used the .bat file and everything worked fine.
I did install xposed - see below
forum.xda-developers.com/showthread.php?t=3034811
File Type: zip xposed-v79-sdk23-arm.zip
AMP+ for the power menu was just updated for Marshmallow the other day and works
Click to expand...
Click to collapse
nomadism said:
Didn't expect that to work. Thanks for confirming - I'll definitely try out at some point.
Click to expand...
Click to collapse
nomadism - if you have not yet flashed the brazilian kernel, but have upgraded to 6.0 and have TWRP flashed, can you capture the kernel first? Junior has said he would create a modified kernel for us using the chainfire WIP method.
lordloki77 said:
nomadism - if you have not yet flashed the brazilian kernel, but have upgraded to 6.0 and have TWRP flashed, can you capture the kernel first? Junior has said he would create a modified kernel for us using the chainfire WIP method.
Click to expand...
Click to collapse
I have the untouched kernel, and I can easily boot to TWRP. Can you tell me how to capture the untouched kernel? Do I simply back the kernel from TWRP - backup?
nomadism said:
I have the untouched kernel, and I can easily boot to TWRP. Can you tell me how to capture the untouched kernel? Do I simply back the kernel from TWRP - backup?
Click to expand...
Click to collapse
brilliant. the kernel is the boot.img partition. so you should be able to just do a normal backup (or only the boot partition). This will create a file named boot.emmc.win -> just change the filename to boot.img (make sure if you are using windows that you have unchecked the option to hide known filetype extensions (probably overkill, but in case you need to change the setting: http://www.howtohaven.com/system/show-file-extensions-in-windows-explorer.shtml). let me know when you've created it (you should zip the file, and then upload to this post as boot.zip or similar).
XT1095 can unlock bootloader, right? can install TWRP, right ? And can flash supersu from TWRP??
very easy to root XT1095
md07 said:
XT1095 can unlock bootloader, right? can install TWRP, right ? And can flash supersu from TWRP??
very easy to root XT1095
Click to expand...
Click to collapse
if you aren't on marshmallow, please don't comment. No, it is no longer as simple as it was to just root, even with unlocked bootloader. I can send you some links if you are curious to learn. but please try not to troll.
Thanks for the data!! Let's keep sharing what we find out.
lordloki77 said:
brilliant. the kernel is the boot.img partition. so you should be able to just do a normal backup (or only the boot partition). This will create a file named boot.emmc.win -> just change the filename to boot.img (make sure if you are using windows that you have unchecked the option to hide known filetype extensions (probably overkill, but in case you need to change the setting: http://www.howtohaven.com/system/show-file-extensions-in-windows-explorer.shtml). let me know when you've created it (you should zip the file, and then upload to this post as boot.zip or similar).
Click to expand...
Click to collapse
Done and uploaded as an attachment to this post
Also available here in dropbox
https://dl.dropboxusercontent.com/u/52727/boot.img.zip
I can confirm @Chainfire's system-less root works fine on XT1095 running the latest marshmallow. Just boot into TWRP then flash the BETA-Supersu-2.62.zip. If you use 2.64 zip , don't use the default system mode, it causes FC errors. System-less mode maybe works fine, but i didn't test. If you want to, you can echo 'SYSTEMLESS=TRUE' to /data/.supersu before flashing the 2.64 zip.
来自我的 XT1095 上的 Tapatalk
Add root for XT1092 and XT1095
http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
nomadism said:
Done and uploaded as an attachment to this post
Also available here in dropbox
https://dl.dropboxusercontent.com/u/52727/boot.img.zip
Click to expand...
Click to collapse
Junior did it. See here: http://forum.xda-developers.com/showpost.php?p=63826996&postcount=1
---------- Post added at 08:15 AM ---------- Previous post was at 08:11 AM ----------
purejoy said:
I can confirm @Chainfire's system-less root works fine on XT1095 running the latest marshmallow. Just boot into TWRP then flash the BETA-Supersu-2.62.zip. If you use 2.64 zip , don't use the default system mode, it causes FC errors. System-less mode maybe works fine, but i didn't test. If you want to, you can echo 'SYSTEMLESS=TRUE' to /data/.supersu before flashing the 2.64 zip.
来自我的 XT1095 上的 Tapatalk
Click to expand...
Click to collapse
Pure/junior, I think this is a stupid question, but is there any benefit to system less root if you're planning to use xposed framework anyway? Wouldn't you still need junior's root kernels? Because xposed clearly modifies /system, which is the point of the modified kernel, no?
It's late. I may be talking crazy.
lordloki77 said:
Junior did it. See here: http://forum.xda-developers.com/showpost.php?p=63826996&postcount=1
---------- Post added at 08:15 AM ---------- Previous post was at 08:11 AM ----------
Pure/junior, I think this is a stupid question, but is there any benefit to system less root if you're planning to use xposed framework anyway? Wouldn't you still need junior's root kernels? Because xposed clearly modifies /system, which is the point of the modified kernel, no?
It's late. I may be talking crazy.
Click to expand...
Click to collapse
What I've heard is that using the system less root with some minor modifications allows you to use android pay (originally not possible on rooted devices). I also root mostly for xposed, but for some they might not need it and would prefer an minimal amount of modifications I guess.
lordloki77 said:
Junior did it. See here: http://forum.xda-developers.com/showpost.php?p=63826996&postcount=1
---------- Post added at 08:15 AM ---------- Previous post was at 08:11 AM ----------
Pure/junior, I think this is a stupid question, but is there any benefit to system less root if you're planning to use xposed framework anyway? Wouldn't you still need junior's root kernels? Because xposed clearly modifies /system, which is the point of the modified kernel, no?
It's late. I may be talking crazy.
Click to expand...
Click to collapse
The benefits of system-less root over the traditional way can be found here: http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
Junior's work is appreciated and the system-less root's script actually doing the same thing to patch the kernel.
As the Xposed Framework, you can easily revert to stock by Rovo89's uninstaller script.
hi,
i flashed the 5.1 ROM (RETDEALL) -> get the two OTA-updates to 6.0 -> boot into twrp -> install SuperSu v2.62-3. -> rooted
I also try the v2.64 before, but unfortunately all app's keep force closing^^
Works fine with my XT1092 (RETDEALL) and unlocked bootloader.
https://goo.gl/photos/h5QqfVa6JpvF8qPr6
I just followed the instructions here to flash the modified kernel > flashed twrp > install SuperSu 2.52 through the new recovery and was able to root but ended up losing wifi and network connectivity. Any suggestions to fix this despite restoring to 5.1 stock and going through all the OTA updates?
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases.
All information, including troubleshoot guides and notes, are in the Announcement Thread
Oh wowww. Thanks!!
Error in the thread title: 2015.8.4
Yay it's finally here!
I'm already using it and I must say it works fine
Man, this "universal MultiROM support" left me full of hope. I hope it works out. And it was time for a mods manager on Android, thanks topjohnwu
Working great on my N6!
topjohnwu has my vote for President!
(and a well deserved donation)
AMAZING!, now to be sure, if i have a rom and want to integrate Magisk, the correct order of flashing is:
1-rom
2-magisk
3-modded su (magisk compatible)
it's that the way?
topjohnwu said:
....Magisk Is A Magic Mask to Alter System Systemless-ly.
If you are running custom roms, dirty flash the rom again to remove all possible issues. If the rom includes SuperSU, unzip the boot image from the rom zip, and flash it through TWRP, flashify, fastboot etc. to restore to stock ramdisk......
....... you can now download Magisk and flash to your device.
To remove Magisk, restore your boot image back (Magisk will backup your boot image automatically in /data/stock_boot(md5).img.gz), then delete /data/magisk.img.
Click to expand...
Click to collapse
is the following still applicable in the case of custom roms?
smohanv said:
1. Boot in to TWRP
2. go to Advanced / File Manager and delete folder named supersu
3. go to Advanced / Terminal and enter these two commandsecho SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersuThe first one forces systemless, the second prevents /su/xbin_bind from existing.4. Flashed Beta SuperSu 2.74-2 (we can notice while flashing this zip after the above script, we will not see the line saying "Disabling OTA". Also, end of flashing it warns that it takes longer time to boot.
5. Reboot device and enjoy systemless
6. To check if we have achieved systemless root, go to system/xbin folder and we should not see the file named "su".
7. I rebooted in to TWRP and flashed xposed 85.1 (also updated with 85.2 later) and installed the apk (Material design apk from this thread)
8. All done and my xposed works.....
Click to expand...
Click to collapse
Awesome....
Sent from my AO5510 using Tapatalk
Stuck at boot screen on the S7 Exynos variant, is this just for stock Android or did i do something wrong? I flashed the Magisk v1 then the phh root zip now im stuck at the boot screen ?
So wait, before i get excited this means things like viper4android can be installed without messing with system?
swipp3r said:
Stuck at boot screen on the S7 Exynos variant, is this just for stock Android or did i do something wrong? I flashed the Magisk v1 then the phh root zip now im stuck at the boot screen ?
Click to expand...
Click to collapse
Sure you probably did something wrong.
For starters you gave way to little information.
Did you follow the procedure from the OP exactly ?
What rom do you have, custom recovery if any, custom kernel if any ?
How did you flash ?
Come on people give this information by yourself please, don't let us pull it out of you everytime.
You know you are the one needing help than please try to give detailed information about your problem.
Sent from my Nexus 5 using XDA-Developers mobile app
grep_i said:
Sure you probably did something wrong.
For starters you gave way to little information.
Did you follow the procedure from the OP exactly ?
What rom do you have, custom recovery if any, custom kernel if any ?
How did you flash ?
Come on people give this information by yourself please, don't let us pull it out of you everytime.
You know you are the one needing help than please try to give detailed information about your problem.
Sent from my Nexus 5 using XDA-Developers mobile app
Click to expand...
Click to collapse
Stock marshmallow, flashed via twrp, and yes i followed the op correctly. No custom kernel.
swipp3r said:
Stuck at boot screen on the S7 Exynos variant, is this just for stock Android or did i do something wrong? I flashed the Magisk v1 then the phh root zip now im stuck at the boot screen ��
Click to expand...
Click to collapse
Did you flash phh's root zip from this thread's Downloads section or from original phh's thread? If the latter, then that's probably the culprit.
Nezorflame said:
[/COLOR]
Did you flash phh's root zip from this thread's Downloads section or from original phh's thread? If the latter, then that's probably the culprit.
Click to expand...
Click to collapse
The threads download section. Should i have downloaded from phhs thread?
swipp3r said:
The threads download section. Should i have downloaded from phhs thread?
Click to expand...
Click to collapse
Nah, you did right, I checked just in case, because thought of it myself. Need the developer's help then.
Nezorflame said:
Nah, you did right, I checked just in case, because thought of it myself. Need the developer's help then.
Click to expand...
Click to collapse
Thanks for trying bro.....
@topjohnwu this new "magisk" method. It doesn't allow Android Pay to work on custom roms like CyanogenMod does it? If I remove SU from CyanogenMod and use your root.
Magisk on (Yu Yureka) ARM64 device
i did a full clean wipe and then flashed rom, magisk and 'Magisk Compatible phh's SuperUser' - in that order. magisk manager app does not open.
Holy crap.. everything universal with support for extensions. This platform could be the beginning of a new era in mods. @topjohnwu amazing work. Don't want to be rude, but personally I think the name of the project is not as awesome as the project itself. "Magisk" sounds a bit cheesy.. :silly:
great work, will try it out soon! one little thing i noticed in the thread title...i guess it should be 2016
I can't seem to find the answer to this.
I've just flashed the Nougat Factory image for Nexus 6 and want root. Can anyone confirm is the latest SuperSU is compatible? I've flashed TWRP and downloaded the latest SuperSU but just a little hesitant to flash it in case of issues.
Thanks a lot.
Yep I rooted just fine. works ok.
Nucleotide said:
I can't seem to find the answer to this.
I've just flashed the Nougat Factory image for Nexus 6 and want root. Can anyone confirm is the latest SuperSU is compatible? I've flashed TWRP and downloaded the latest SuperSU but just a little hesitant to flash it in case of issues.
Thanks a lot.
Click to expand...
Click to collapse
I had no problems with the latest version, which I installed last night (downloaded factory image, extracted to PC and fastboot flashed through bootloader, rebooted to recovery and flashed SuperSU 2.78-SR1).
yudumcan said:
Yep I rooted just fine. works ok.
Click to expand...
Click to collapse
pkgnex said:
I had no problems with the latest version, which I installed last night (downloaded factory image, extracted to PC and fastboot flashed through bootloader, rebooted to recovery and flashed SuperSU 2.78-SR1).
Click to expand...
Click to collapse
Perfect. Flashed and working great. Thank you! :good:
If you enjoy having an unknown organization having absolute godlike control over your phone, then sure, use stupidsu.
But if you like to have auditable and sane control over your own device, I would very VERY much suggest that you instead use https://github.com/seSuperuser/AOSP-SU-PATCH
Nucleotide said:
I can't seem to find the answer to this.
I've just flashed the Nougat Factory image for Nexus 6 and want root. Can anyone confirm is the latest SuperSU is compatible? I've flashed TWRP and downloaded the latest SuperSU but just a little hesitant to flash it in case of issues.
Thanks a lot.
Click to expand...
Click to collapse
I flashed factory image today and went to Nexus Root Toolkit to root and flash recovery. It went well.
new to Nexus 6, just got Nougat OTA, whats the best way to root and have double tap to wake (will it drain battery big time?) and notification led? pls help, tia
btw I use Mac
Isn't the nexus 6 supposed to be 100% stock Android and with that being able to be rooted by any root method? I know I've read many times that if you want to get into root and hacking to pick up a nexus device as they were easily recoverable and weren't root blocked by any means
Sent from my Z988 using Tapatalk
gabe.ulrickson said:
Isn't the nexus 6 supposed to be 100% stock Android and with that being able to be rooted by any root method? I know I've read many times that if you want to get into root and hacking to pick up a nexus device as they were easily recoverable and weren't root blocked by any means
Sent from my Z988 using Tapatalk
Click to expand...
Click to collapse
Not sure what exactly you're asking but the Nexus 6 is easily rooted when using the proper methods. Unlock the bootloader, fastboot flash TWRP recovery and then flash SuperSU or Magisk in TWRP.
Hey,
I bought my phone 2 days ago, after charging it I updated to OOS4.0 through the system updates using VPN, when I got home I unlocked the bootloader but did nothing else afterwards. I'm seeing a lot of threads with people having issues with TWRP and encryption, considering my last device was the OPO and I was running Lollipop (was too lazy to update it ) I'm kinda out of the loop.
How can I root it now that it's running Nougat ? simply flashing the twrp img using fastboot and then flashing the SuperSU zip or is there a different method ?
Any kind of help is greatly appreciated.
Also, one more question, is Xposed working on Nougat ? I had quite a few useful modules on my OPO, wanted to know if that's possible on the 3T as well.
The beta builds of the TWRP which are compatible with the OOS 4.0.0 are available. You can find them from the thread.
If you want to use the Xposed modules, you should downgrade to 3.5.4.
WeirdSoup said:
The beta builds of the TWRP which are compatible with the OOS 4.0.0 are available. You can find them from the thread.
If you want to use the Xposed modules, you should downgrade to 3.5.4.
Click to expand...
Click to collapse
And where should I download SuperSU from ? Heard the project is being taken over or smth like that
B00steed said:
And where should I download SuperSU from ? Heard the project is being taken over or smth like that
Click to expand...
Click to collapse
http://www.supersu.com/download
Actually, I'm using the Magisk instead. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
WeirdSoup said:
http://www.supersu.com/download
Actually, I'm using the Magisk instead. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Is it better to install this instead of SuperSU ?
If you are interested in using apps which detect root or a modified system/bootloader (Android Pay, Pokémon Go, some banking apps) then yes. Otherwise, no benefit of Magisk (v10.2) for you and may as well use SuperSU which is simpler to install.
B00steed said:
Is it better to install this instead of SuperSU ?
Click to expand...
Click to collapse
It's case by case, and I don't know which one is good for you. Do some research and figure out yourself.
---------- Post added at 11:30 AM ---------- Previous post was at 11:24 AM ----------
23Six said:
If you are interested in using apps which detect root or a modified system/bootloader (Android Pay, Pokémon Go, some banking apps) then yes. Otherwise, no benefit of Magisk (v10.2) for you and may as well use SuperSU which is simpler to install.
Click to expand...
Click to collapse
Magisk is open source, and it is also easy to install. You can also install the Magisk modules. It's not a simple root-hide app as many people still misunderstand.
So, with oxygen 4.0.1 the procedure will be the same?
TWRP Stuck Mount password
Greetings guys..
Yesterday I got my 3T and upgraded OTA latest OxygenOS 4.0.1. I was able to unlock bootloader and install TWRP 3.0.3 but when I access bootloader the first screen ask me to provide "Decrypt password" to mount, and if I ignore and slide to start modification I don't have access to internal card (assume its READ-ONLY), just folders are visible but unable to find or install SU package.
I check all the forums but didn't find any relevant information how to get out of TWRP "Decrypt password" issue. I don't want my phone to be encrypted, so I would appreciate if you can please help me to root my 3T.
Cheers
junostik said:
Greetings guys..
Yesterday I got my 3T and upgraded OTA latest OxygenOS 4.0.1. I was able to unlock bootloader and install TWRP 3.0.3 but when I access bootloader the first screen ask me to provide "Decrypt password" to mount, and if I ignore and slide to start modification I don't have access to internal card (assume its READ-ONLY), just folders are visible but unable to find or install SU package.
I check all the forums but didn't find any relevant information how to get out of TWRP "Decrypt password" issue. I don't want my phone to be encrypted, so I would appreciate if you can please help me to root my 3T.
Cheers
Click to expand...
Click to collapse
I think you need latest twrp beta 1, it should be in twrp tread, look in last pages or here https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
bertozzi243 said:
I think you need latest twrp beta 1, it should be in twrp tread, look in last pages or here https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
Click to expand...
Click to collapse
Thanks for quick reply, I'll check it.
bertozzi243 said:
I think you need latest twrp beta 1, it should be in twrp tread, look in last pages or here https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
Click to expand...
Click to collapse
Installed TWRP 3.0.3.1 BETA .... How long does it really take to decrypt new phone without any apps? Just to have an idea. When I started TWRP it asked for password and I used the PIN assigned to login to screen ... now going on for 5 minutes now.
Following on the screen:
Mount
Try Decryption
Updating partition details...
....done
Unable to mount storage
Full SELinux support present
---------blue animation-----------
junostik said:
Installed TWRP 3.0.3.1 BETA .... How long does it really take to decrypt new phone without any apps? Just to have an idea. When I started TWRP it asked for password and I used the PIN assigned to login to screen ... now going on for 5 minutes now.
Following on the screen:
Mount
Try Decryption
Updating partition details...
....done
Unable to mount storage
Full SELinux support present
---------blue animation-----------
Click to expand...
Click to collapse
I read that it takes some minutes if you are f2s and encrypted but I don't know how to proceed since I haven't flashed twrp and root yet.
Sorry but you may have to wait someone who has already done it