Hey guys,
I unlocked the bootloader and rooted my phone using the toolkit and all was well. I installed the Cataclysm ROM and everything was too. However, one day randomly I checked and Super SU and BusyBox was missing and Root checker said my device isn't rooted. However, my phone does boot into recovery (TWRP) and it IS running Cataclysm ROM. I downloaded Super SU from Playstore and it says "There is no SU binary installed and Super SU cannot install it". Some forums for other devices say just flash the latest version of Super SU but the marshmallow pages say go back to stock or something, I don't get it since I'm a Noob. If someone could tell me what I need to do to fix this the right way I would be really grateful. Thanks in advance. :angel:
holydevil27 said:
Hey guys,
I unlocked the bootloader and rooted my phone using the toolkit and all was well. I installed the Cataclysm ROM and everything was too. However, one day randomly I checked and Super SU and BusyBox was missing and Root checker said my device isn't rooted. However, my phone does boot into recovery (TWRP) and it IS running Cataclysm ROM. I downloaded Super SU from Playstore and it says "There is no SU binary installed and Super SU cannot install it". Some forums for other devices say just flash the latest version of Super SU but the marshmallow pages say go back to stock or something, I don't get it since I'm a Noob. If someone could tell me what I need to do to fix this the right way I would be really grateful. Thanks in advance. :angel:
Click to expand...
Click to collapse
It really depends on what you're trying to do. If you flash the older beta 2.52 super su, for the 'old style' system root, you should be able to flash the zip and be well on your way. You need to go back to the stock and follow the flash instructions if you're going to use the newer / experimental systemless root. If you don't know what you're doing exactly, I'd recommend the old system root, but flashing super su 2.52.
It sounds pretty messed up for Super SU just to disappear and root access to just be gone. Although like teh roxxorz said it depends on what type of root you are doing. I think system root is much easier and cleaner personally. If I was you I would probably flash back to stock, flash TWRP, install SuperSU 2.65. Then flash back which ever ROM you want. Since you are having issues with root I would not restore your ROM from a back up either, just start fresh.
teh roxxorz said:
It really depends on what you're trying to do. If you flash the older beta 2.52 super su, for the 'old style' system root, you should be able to flash the zip and be well on your way. You need to go back to the stock and follow the flash instructions if you're going to use the newer / experimental systemless root. If you don't know what you're doing exactly, I'd recommend the old system root, but flashing super su 2.52.
Click to expand...
Click to collapse
If I want to do the old system root, do I just download Super SU and flash it with TWRP? Or do I format my phone and do it? Or do I have to flash stock firmware first?
AndroidPurity said:
It sounds pretty messed up for Super SU just to disappear and root access to just be gone. Although like teh roxxorz said it depends on what type of root you are doing. I think system root is much easier and cleaner personally. If I was you I would probably flash back to stock, flash TWRP, install SuperSU 2.65. Then flash back which ever ROM you want. Since you are having issues with root I would not restore your ROM from a back up either, just start fresh.
Click to expand...
Click to collapse
Can you guide me as to how to flash back to stock? A link would be great, and I apologize for the lack of knowledge, the last rooted Android phone I had was Samsung s3! Things have really changed since then xD
holydevil27 said:
Can you guide me as to how to flash back to stock? A link would be great, and I apologize for the lack of knowledge, the last rooted Android phone I had was Samsung s3! Things have really changed since then xD
Click to expand...
Click to collapse
No worries man. Even tough I been rooting phones and playing around for over a year I still have lots to learn myself. What helped me the most when I wanted to know how to do something was watching a you tube tutorial on it. Here is a good detailed tutorial how to flash back to stock right here.
Once you do that, to do a systemless root, you can watch this short little video tutorial right here. The newest SuperSU 2.65 you can find on Chainfire's thread at the bottom of this page right here.
If you have any questions going through either of those 2 video tutorials feel free to ask.
holydevil27 said:
Can you guide me as to how to flash back to stock? A link would be great, and I apologize for the lack of knowledge, the last rooted Android phone I had was Samsung s3! Things have really changed since then xD
Click to expand...
Click to collapse
No need to be sorry; we all have to start somewhere..
AndroidPurity said:
No worries man. Even tough I been rooting phones and playing around for over a year I still have lots to learn myself. What helped me the most when I wanted to know how to do something was watching a you tube tutorial on it. Here is a good detailed tutorial how to flash back to stock right here.
Once you do that, to do a systemless root, you can watch this short little video tutorial right here. The newest SuperSU 2.65 you can find on Chainfire's thread at the bottom of this page right here.
If you have any questions going through either of those 2 video tutorials feel free to ask.
Click to expand...
Click to collapse
Good look. Though I still think the system root might be a good pace, and it's 100% working; still some quirks with certain root apps on systemless root. SuperSu 2.52
---------- Post added at 05:52 PM ---------- Previous post was at 05:50 PM ----------
holydevil27 said:
If I want to do the old system root, do I just download Super SU and flash it with TWRP? Or do I format my phone and do it? Or do I have to flash stock firmware first?
Click to expand...
Click to collapse
Correct, you would just download the zip and flash in TWRP; I linked it in an above post.
teh roxxorz said:
Good look. Though I still think the system root might be a good pace, and it's 100% working; still some quirks with certain root apps on systemless root. SuperSu 2.52
Click to expand...
Click to collapse
Thanks! Just curious, what are a couple of the most known/popular root apps that don't work with system less root? I haven't found a thread yet on that. Also on the other hand Android pay don't work with the 'old' system root method right? And I think wallet no longer works with it too, correct?
AndroidPurity said:
Thanks! Just curious, what are a couple of the most known/popular root apps that don't work with system less root? I haven't found a thread yet on that. Also on the other hand Android pay don't work with the 'old' system root method right? And I think wallet no longer works with it too, correct?
Click to expand...
Click to collapse
No problem. And the one I know that comes to mind that doesn't work with systemless root is Es File Explorer - though any root app where it is hardcoded tot he path for supersu won't work, additionally, apparently some kernels won't work with systemless root, though I haven't seen it on our end.
Wallet still works with the system root, but as you said, Android Pay does not - though the Chroma ROM apparently has it working, but I've yet to use the ROM, as it isn't a deal breaker for me.
teh roxxorz said:
No need to be sorry; we all have to start somewhere..
Good look. Though I still think the system root might be a good pace, and it's 100% working; still some quirks with certain root apps on systemless root. SuperSu 2.52
---------- Post added at 05:52 PM ---------- Previous post was at 05:50 PM ----------
Correct, you would just download the zip and flash in TWRP; I linked it in an above post.
Click to expand...
Click to collapse
Thanks guys,
I just went into TWRP and flashed 2.64 Super SU (since that's the one I got with the tool kit and what I had installed before) and Root came back! I hope it stays! Thanks again folks!
Related
Hey all, I'm fairly new to rooting an android device, this is actually the first time I'm rooting my phone. I used Wugs Nexus root toolkit to root my device and everything went well until the last step where I had to go open superSU app. I would get a popup stating "There is no SU binary installed, and SuperSu cannot install it. This is a problem! If you just upgraded to Android 4.3, you will need to manually re-root counsult the relevant forums for your device!"
What does this mean exactly? and where did i go wrong? I honestly don't have an idea on how to manually re-root.
Through the toolkit I've unrooted, flashed stocked and did the OEM lock again, and tried the whole rooting process again and I still get that same error. I think I need some guidance if you guys can help me a bit. Sorry to be a big noob about all this.
Thanks!
knicks20828 said:
Hey all, I'm fairly new to rooting an android device, this is actually the first time I'm rooting my phone. I used Wugs Nexus root toolkit to root my device and everything went well until the last step where I had to go open superSU app. I would get a popup stating "There is no SU binary installed, and SuperSu cannot install it. This is a problem! If you just upgraded to Android 4.3, you will need to manually re-root counsult the relevant forums for your device!"
What does this mean exactly? and where did i go wrong? I honestly don't have an idea on how to manually re-root.
Through the toolkit I've unrooted, flashed stocked and did the OEM lock again, and tried the whole rooting process again and I still get that same error. I think I need some guidance if you guys can help me a bit. Sorry to be a big noob about all this.
Thanks!
Click to expand...
Click to collapse
1. Read this if you haven't already, just so you know what you are doing.
http://forum.xda-developers.com/showthread.php?t=2367406
2. Install the SuperSU zip from recovery:
http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
abaaaabbbb63 said:
1. Read this if you haven't already, just so you know what you are doing.
http://forum.xda-developers.com/showthread.php?t=2367406
2. Install the SuperSU zip from recovery:
http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
Click to expand...
Click to collapse
thanks for that man, actually read all of it. that helped a little, I guess with time and the more i flash and stuff i'll just get better. So unroot and try rooting again and then zip supersu?
knicks20828 said:
thanks for that man, actually read all of it. that helped a little, I guess with time and the more i flash and stuff i'll just get better. So unroot and try rooting again and then zip supersu?
Click to expand...
Click to collapse
No need for "unroot". Just flash the supersu zip, and it will install the binaries.
abaaaabbbb63 said:
No need for "unroot". Just flash the supersu zip, and it will install the binaries.
Click to expand...
Click to collapse
Thanks man it worked! I feel so relieved now, So I'm trying to flash cyanogenmod 10.1.3 and I have the zip flie downloaded but I cant seem to find gapps that supports this cyanogen version and android 4.3 . is it not released yet? or something?
Sorry to be so annoying with this but I am getting better I can say that much.
knicks20828 said:
Thanks man it worked! I feel so relieved now, So I'm trying to flash cyanogenmod 10.1.3 and I have the zip flie downloaded but I cant seem to find gapps that supports this cyanogen version and android 4.3 . is it not released yet? or something?
Sorry to be so annoying with this but I am getting better I can say that much.
Click to expand...
Click to collapse
Flash the regular 4.2.2 Gapps. They will work.
http://goo.im/gapps/gapps-jb-20130812-signed.zip
I was running Adaway on my rooted/soff M7 and would like to run it on my now rooted/soff 10. I tried downloading v3.3.1 from @mrRobinson thread here but each time I tried to open the program it said something about a SuperSU error. I'm guessing that it didn't like the modified SuperSU we used rooting the 10 to keep forceencrypt? Any one have an idea or see something I did wrong?
Edit:
Looking through my apps list I can't find SuperSU, but I know it's on here cause it ran when sunshine requested root access and I had to side load it through TWRP for root. Why wouldn't it show up in my app list?
use this, then adaway works fine: http://forum.xda-developers.com/htc-10/development/root-supersu-2-71-forceencrypt-verity-t3373258
Load this app: jRummy Root Check
It should work if the SuperSU process was successful. I used jcase's guide Root-optionally-s-off-radio
After that, I loaded the XDA Labs App, then loaded AdAway. Everything working as it should.
You may want to retrace your steps to jcase's quide, and see what might have been missed.
HTH.
I followed jcases method for root and soff and had to side load the modified SuperSU that @starbase64 linked to in that process. That jRummy app says I do not have root. Can I just flash the modified SuperSU in TWRP? I'm definitely soff, so how would I be able to get soff without root? So weird
yes, but restore stock boot.img first
Yes that should work.
Root these days is in the boot.img so if you reflashed that at any point you are back at stock.
Adaway is working fine here!
The only thing I did after jcases root/soff procedure was flash the Verizon radio from @dottat. Not sure how I would have messed with the boot.img
Light1984 said:
The only thing I did after jcases root/soff procedure was flash the Verizon radio from @dottat. Not sure how I would have messed with the boot.img
Click to expand...
Click to collapse
starbase64 said:
use this, then adaway works fine: http://forum.xda-developers.com/htc-10/development/root-supersu-2-71-forceencrypt-verity-t3373258
Click to expand...
Click to collapse
Did you flash this file in twrp yet? That should be all you need to do.
Light1984 said:
The only thing I did after jcases root/soff procedure was flash the Verizon radio from @dottat. Not sure how I would have messed with the boot.img
Click to expand...
Click to collapse
Oh well
If SuperSU isn't in the app tray and you haven't hidden it manually, flashing back SuperSU (preferably topjohnwu version) should bring it back.
10-4 brb. Thanks
Edit: yes, I checked with jcase too. Just reflashed the zip in TWRP. Although when it was going through its process it said it already found the files and over wrote them anyways, maybe something got corrupted at some point. All is well now, thanks for the help all.
May also be something in /data/ somewhere which will be lost as S-Off forces data to be reset -- but again a TWRP install of SuperSU should cover it.
Tried everything flashing every supersu via twrp and just gets stuck at the moto logo. Tried systemless root and did the same thing. So thinking it was my kernel and flashed elementalx moto kernel ( frankenclark ) then tried to flash supersu once again with the same fail and noticed with that kernel I lost my wifi connection but ran it anyways but failed. After much forum browsing and that supersu just isn't for the MXPE I even went as far as kingroot to achieve root then slap supersu to keep root like I did with my kindle fire. I'm pretty lost for words here. I'm previously running resurection remix and works flawless but I do really like the original setup. Ps tried the stock rooted roms and they was a lil off and kept trying to ota update but failed because my bootloader is unlocked so I had to uninstall it. Just looking to root the original rom so I can keep all the moto apps. Looking forward to hearing the ideas. Thanks in advance.
Wow... So I assume you flashed back to pure stock?
Rooting is not difficult, there is only 2 ways to do it, either flash SuperSU 2.62-3 beta or the latest stable version with the "echo" command for systemless installations. Look at this thread (note the pictures in the OP are of my XT1575, I fudged a little) but the method is identical. If it doesn't work, no offense, but your not doing something right.
I have both pure stock in a restore and resurection remix in a restore which is pretty much my daily because the active display drives me nuts. And supersu 2.6.2 I haven't tried yet but the SR supersu I've flashed via twrp with the stock kernel and ( frankenclark ) kernel and it responded the same stuck at moto. I've flashed it via windroid toolkit also it shows it's installing without any failure but on boot up she says no way. And I've updated the toolkit to it's newest version and still ends up stuck at moto. I'm sure I'll figure it out and get it. And no offense on doing something wrong it's been known to happen. Some lg double tap to wake the screen would be nice over the active display.
fastjohnson said:
I have both pure stock in a restore and resurection remix in a restore which is pretty much my daily because the active display drives me nuts. And supersu 2.6.2 I haven't tried yet but the SR supersu I've flashed via twrp with the stock kernel and ( frankenclark ) kernel and it responded the same stuck at moto. I've flashed it via windroid toolkit also it shows it's installing without any failure but on boot up she says no way. And I've updated the toolkit to it's newest version and still ends up stuck at moto. I'm sure I'll figure it out and get it. And no offense on doing something wrong it's been known to happen. Some lg double tap to wake the screen would be nice over the active display.
Click to expand...
Click to collapse
It sounds like the install script for SuperSU is not doing a systemless install...
So you are flashing stock, booting at least once (this is required), the open TWRP and allow changes to system (In mounts make sure Mount System Read-Only is NOT checked), go to Advanced - Terminal and enter "echo SYSTEMLESS=true>>/data/.supersu" and press enter, then go to Install and select the SuperSU zip file and install it. It should clearly say it is doing a system-less install, patching boot image, etc. as shown in the first post of the link I shared a couple posts previous.
OK I tried this info word for word and tried multiple times and its still gets stuck on the moto logo, I don't get it.
I don't know... it's a puzzler.
2.62-3 and stop using toolkits.
lafester said:
2.62-3 and stop using toolkits.
Click to expand...
Click to collapse
I'm using twrp to obtain the root like specified. But I'll try adb commands and see if the version you mentioned will do it. I appreciate the help.
fastjohnson said:
I'm using twrp to obtain the root like specified. But I'll try adb commands and see if the version you mentioned will do it. I appreciate the help.
Click to expand...
Click to collapse
Well that worked perfectly the first try I used those terminal commands with that version SuperSU it rooted and booted right up like normal and started asking the SuperSU adb shell permission banners. Perfect guys maybe this thread will help some other poor soul to get root. Awesome advice that works. Thank you.
fastjohnson said:
Well that worked perfectly the first try I used those terminal commands with that version SuperSU it rooted and booted right up like normal and started asking the SuperSU adb shell permission banners. Perfect guys maybe this thread will help some other poor soul to get root. Awesome advice that works. Thank you.
Click to expand...
Click to collapse
Yeah, glad it's working... Did you read through the link I posted earlier? The 2.62-3 method was clearly described in the second post under Alternative Methods.
acejavelin said:
Yeah, glad it's working... Did you read through the link I posted earlier? The 2.62-3 method was clearly described in the second post under Alternative Methods.
Click to expand...
Click to collapse
No actually I didn't see it, lol probably would have helped made me not look dumb. Buy who am I kidding you guys love flexing you rooting muscles..
Deleted.
Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you
The axon7 has had its EDL programmer released and a leaked ZTE signed TWRP since shortly after the device went on sale. Anything is possible.
I would recommend nuking it... wipe the phone data and then install the latest full official firmware over whatever you have now. Then you can go back and start modding.
Jay_Nz said:
Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you
Click to expand...
Click to collapse
Thanks for replying. Just a thought is it possible to flash twrp on top of the existing set up..? And keep the root as it is.?
Should be, but it's not safe since you do not know the current root method.
Odds are fairly high that you have malware on the device. Be safe, nuke it.
Jay_Nz said:
Thanks for replying. Just a thought is it possible to flash twrp on top of the existing set up..? And keep the root as it is.?
Click to expand...
Click to collapse
Ok thanks for replying. Anti-virus shows device is clean. I'll do a clean one then as recommended . Flash official firmware first then flash twrp and probably will go for magisk root. Wish me luck as power button is mushed in and have to poke it real hard. I don't even know if bootloader is unlocked or not.. Haha
tdm said:
The axon7 has had its EDL programmer released and a leaked ZTE signed TWRP since shortly after the device went on sale. Anything is possible.
Click to expand...
Click to collapse
where to find these solutions??
Check for posts by tenfar for the signed twrp.
The firehose was included in one of the leaked update packages. I don't remember which one. I got my copy by running tcpdump while running tenfar"s twrp flasher.
Druboo666 said:
where to find these solutions??
Click to expand...
Click to collapse
tdm said:
Check for posts by tenfar for the signed twrp.
The firehose was included in one of the leaked update packages. I don't remember which one. I got my copy by running tcpdump while running tenfar"s twrp flasher.
Click to expand...
Click to collapse
also works in B32??i am on b32 and i am stuck with stock recovery as bootloader as been striped from b32 so this will give me TWRP back on B32??
Druboo666 said:
also works in B32??i am on b32 and i am stuck with stock recovery as bootloader as been striped from b32 so this will give me TWRP back on B32??
Click to expand...
Click to collapse
I don't know, you can try.
Jay_Nz said:
Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you
Click to expand...
Click to collapse
I just posted some huge verbose $hit on your previous post, just sayin
Hi, Thank you for your guidance so far. Question - if the previous owner just flashed stock rom then shouldn't g that get rid of root. As you can see from this 2nd post I checked on some root apps and it said it is rooted and su is phh so I downloaded phh su from play store and now rooted apps work fine. Some one pointed out chances of my phone having a malware are quite high so I just want to clean all up and have nandroid g back up. It is an awesome phone. As per your recommendation should I flash using miflash.? Would updating from sd card in phone settings not put it back to complete stock and get rid of root and everything.? When I restart I don't get that device can't be checked for corruption message. I'm on marshmallow at the moment so flashing nougat be ok whether it if from miflash or SD card firmware update.? Appreciate your assistance. Thank you
Yes, if the previous owner flashed stock only, you would not have root. He either flashed a malicious package or "helpfully" pre-rooted it for you. So you have untrusted and unknown, and regardless of what it may seem, not stock software.
There are several "return to stock" threads. I would study a couple to get a feel for how the procedure works and then follow one of them. Here's one I pulled up in a search:
https://forum.xda-developers.com/axon-7/development/rom-guide-how-to-restore-stock-a2017u-t3549227
I can't vouch for it, it's just the first one that popped up. However, it does seem to be very complete both in instructions and flashing everything from the boot stack on up to boot and system.
Note that b20 is rather old now -- I believe it's the first firmware that shipped on the device. You could make an effort to find newer files. But it's not really necessary, as you should get an OTA update notification after you boot into the stock system.
Good luck!
Jay_Nz said:
Hi, Thank you for your guidance so far. Question - if the previous owner just flashed stock rom then shouldn't g that get rid of root. As you can see from this 2nd post I checked on some root apps and it said it is rooted and su is phh so I downloaded phh su from play store and now rooted apps work fine. Some one pointed out chances of my phone having a malware are quite high so I just want to clean all up and have nandroid g back up. It is an awesome phone. As per your recommendation should I flash using miflash.? Would updating from sd card in phone settings not put it back to complete stock and get rid of root and everything.? When I restart I don't get that device can't be checked for corruption message. I'm on marshmallow at the moment so flashing nougat be ok whether it if from miflash or SD card firmware update.? Appreciate your assistance. Thank you
Click to expand...
Click to collapse
Hi thanks for the reply. I downloaded zip from zte and did an update from phone settings, it pumped me to marshmallow but next release version of zte up. Then another Ota and now I'm on nougat. Checked and root access is gone as expected but funnily enough app shows no root access but busy box binary yes.. Don't know if that's normal. Did a full factory reset too. Now I'm on full Chinese variant stock rom unrooted hence getting Ota. I pressed volume and power button together and managed to get to the screen with start in green and text screen. Other options included restart, power off, reboot to recovery and bootloader and it did show bootloader is locked. I'm thinking of unlocking bootloader, installing TWRP, then root through magisk and perhaps change to A2017U (usa firmware)... Fingers crossed. Thanks again..
tdm said:
Yes, if the previous owner flashed stock only, you would not have root. He either flashed a malicious package or "helpfully" pre-rooted it for you. So you have untrusted and unknown, and regardless of what it may seem, not stock software.
There are several "return to stock" threads. I would study a couple to get a feel for how the procedure works and then follow one of them. Here's one I pulled up in a search:
https://forum.xda-developers.com/axon-7/development/rom-guide-how-to-restore-stock-a2017u-t3549227
I can't vouch for it, it's just the first one that popped up. However, it does seem to be very complete both in instructions and flashing everything from the boot stack on up to boot and system.
Note that b20 is rather old now -- I believe it's the first firmware that shipped on the device. You could make an effort to find newer files. But it's not really necessary, as you should get an OTA update notification after you boot into the stock system.
Good luck!
Click to expand...
Click to collapse
But that's for the A2017U... Be careful with that, he can brick his phone or lose signal
Hi, just got around to rooting my Kindle. Currently using SuperSu, curious if anyone has used Magisk with this tablet? Any reason not to do so?.
Thanks in advance.
I've debated doing this as well, as I don't like having to default grant everything root access.
As far as I understand though, none of your root apps/su requests can modify the system partition, so I haven't tried it yet.
@diplomatic is this true for the bootless root method without dm-verity?
No, you can modify /system if there's no dm-verity, @Kctucka
diplomatic said:
No, you can modify /system if there's no dm-verity, @Kctucka
Click to expand...
Click to collapse
Oh wow that's pretty awesome.
Sounds like there's no downside to Magisk on the 2017 HD 8 then.
Kctucka said:
Oh wow that's pretty awesome.
Sounds like there's no downside to Magisk on the 2017 HD 8 then.
Click to expand...
Click to collapse
Thanks, guys!
SuperSU access workaround
Kctucka said:
I've debated doing this as well, as I don't like having to default grant everything root access.
.....
Click to expand...
Click to collapse
There is a SuperSU access workaround without having to default grant everything root access:
https://forum.xda-developers.com/hd8-hd10/general/supersu-access-workaround-fire-devices-t3738269
Maybe I am mistaken, but how does one install Magisk on 2017 HD8 without TWRP ?
Dan_firehd said:
There is a SuperSU access workaround without having to default grant everything root access:
https://forum.xda-developers.com/hd8-hd10/general/supersu-access-workaround-fire-devices-t3738269
Maybe I am mistaken, but how does one install Magisk on 2017 HD8 without TWRP ?
Click to expand...
Click to collapse
Yeah I've seen that method, but didn't wanna redo it for every root app I add.
And this is the Bootless Root Magisk method:
https://forum.xda-developers.com/showpost.php?p=79626434&postcount=135
I think I'm gonna try this method when I get some free time.
Kctucka said:
Yeah I've seen that method, but didn't wanna redo it for every root app I add.
And this is the Bootless Root Magisk method:
https://forum.xda-developers.com/showpost.php?p=79626434&postcount=135
I think I'm gonna try this method when I get some free time.
Click to expand...
Click to collapse
@Kctucka would you let me know if that method works for you? I tried grabbing the stock boot image and modifying it with the latest version of Magisk, Could not get that to work either via ADB or Flashify because of the locked bootloader - stupid of me not to realize that from the start. I let my excitement get the best of me.
I am out of time today, but it seems like a modified BIN file might be an option.
koop1955 said:
@Kctucka would you let me know if that method works for you? I tried grabbing the stock boot image and modifying it with the latest version of Magisk, Could not get that to work either via ADB or Flashify because of the locked bootloader - stupid of me not to realize that from the start. I let my excitement get the best of me.
I am out of time today, but it seems like a modified BIN file might be an option.
Click to expand...
Click to collapse
Yeah will do! I'll probably try it tomorrow or the day after.
koop1955 said:
@Kctucka would you let me know if that method works for you? I tried grabbing the stock boot image and modifying it with the latest version of Magisk, Could not get that to work either via ADB or Flashify because of the locked bootloader - stupid of me not to realize that from the start. I let my excitement get the best of me.
I am out of time today, but it seems like a modified BIN file might be an option.
Click to expand...
Click to collapse
Ok so I successfully have Magisk working, and have been playing around with it for a bit now. I am running the latest version of Magisk Manager. To get it up and running, I chose the option in SuperSu to clean up binaries for different su method.
So far, all of my root apps detect root, except for titanium backup. I've messed around with it for a bit but haven't been able to figure it out. I'm guessing it has something to do with the location of the su binaries.
Also of note, FlashFire did not work at first. I realized that this is because the timebomb method we used along with the older app version, was from before Magisk existed. I grabbed the latest version of FlashFire from apk mirror, and it started without issues. I haven't tested by flashing anything yet though.
Lastly, the one minor inconvenience is that my kernel tweaks I enable at boot, do not work, as there is no root at boot. So I have to manually add zram every reboot. Perhaps there's a better way to do this.
All in all, this is a pretty solid root method, but obviously non ideal due to the locked bootloader.
I've also not tested how easy it is to switch back to SuperSu if desired, but I assume it's as simple as disabling the start up script, and updating su binaries in SuperSu.
@diplomatic is this the case? Or would you also need to delete the created files in the data partition? Thanks again for the awesome method!
Kctucka said:
Ok so I successfully have Magisk working, and have been playing around with it for a bit now. I am running the latest version of Magisk Manager. To get it up and running, I chose the option in SuperSu to clean up binaries for different su method.
Click to expand...
Click to collapse
Was that all that you did? That option and then install? And how did you change the time in your Kindle to get Flashify to work or just the latest APK?
And thanks for everything! Getting back into this after so long I feel like a n00b again.
koop1955 said:
Was that all that you did? That option and then install? And how did you change the time in your Kindle to get Flashify to work or just the latest APK?
And thanks for everything! Getting back into thhis after so long I feel like a n00b again.
Click to expand...
Click to collapse
That option was all I did to remove SuperSu. Then I followed the instructions here:
https://forum.xda-developers.com/showpost.php?p=79626434&postcount=135
Didn't take long to get it working.
And the time change was to get the version of FlashFire working that was compatible with the version of SuperSu we could run. See this post for more info if you're curious:
https://forum.xda-developers.com/hd8-hd10/general/hd-10-2017-xposed-t3722252
But with this new method, the most recent version of FlashFire works, as it's compatible with Magisk. The older version of FlashFire I had is not.
Also, I'm a noob myself. That's why I tagged diplomatic again, to correct the dumb things I might have said
Well, I am busy adding to your "Thanks" quotient, something seems to have fallen by the wayside today. Glad t have you around.
I think ultimately we are going to end up with a custom BIN file with Magisk and Xposed integrated.
Cheers.
koop1955 said:
Well, I am busy adding to your "Thanks" quotient, something seems to have fallen by the wayside today. Glad t have you around.
I think ultimately we are going to end up with a custom BIN file with Magisk and Xposed integrated.
Cheers.
Click to expand...
Click to collapse
That's awesome! Would that pass signature verification? Or would it be through hacked fastboot?
Also, that'd make it much easier to set up the device after a softbrick. FlashFire would be good to flash backups right away.
Kctucka said:
.....
Lastly, the one minor inconvenience is that my kernel tweaks I enable at boot, do not work, as there is no root at boot. So I have to manually add zram every reboot. Perhaps there's a better way to do this.
.....
Click to expand...
Click to collapse
Would you please let us know how did you do your "kernel tweaks" to add zram for a rooted 2017 HD8?
Thanks.
Dan_firehd said:
Would you please let us know how did you do your "kernel tweaks" to add zram for a rooted 2017 HD8?
Thanks.
Click to expand...
Click to collapse
My kernel tweaks were done with KA Mod Reborn, using the "apply on boot" setting:
https://forum.xda-developers.com/android/apps-games/approot4-0-ka-mod-reborn-v18-t3714105
I added 260 MB ZRAM with a swapiness of 10. You can also tweak low memory killer, laptop mode, and a whole bunch of other dials that I don't mess with as I don't fully understand what they do.
Kernel changes could also be done with a number of different apps that do similar things.
Unfortunately, the bootless root method doesn't give root on boot, so it and also most Magisk modules won't work. Can't think of a workaround currently.
Kctucka said:
I've also not tested how easy it is to switch back to SuperSu if desired, but I assume it's as simple as disabling the start up script, and updating su binaries in SuperSu.
@diplomatic is this the case? Or would you also need to delete the created files in the data partition? Thanks again for the awesome method!
Click to expand...
Click to collapse
Yeah, pretty much. The activation of root depends only the init.d app running the script. The su binaries don't really exist in storage. You can delete all the stuff under /data/adb if you want to wipe everything Magisk. In theory, it should be possible to install Magisk on the system partition. It probably doesn't support that method officially anymore. But if the bootless method works, then a similar script can be added to /system....
diplomatic said:
Yeah, pretty much. The activation of root depends only the init.d app running the script. The su binaries don't really exist in storage. You can delete all the stuff under /data/adb if you want to wipe everything Magisk. In theory, it should be possible to install Magisk on the system partition. It probably doesn't support that method officially anymore. But if the bootless method works, then a similar script can be added to /system....
Click to expand...
Click to collapse
That's super beneficial then, you can swap back and forth easily depending on what you need.
diplomatic said:
Yeah, pretty much. The activation of root depends only the init.d app running the script. The su binaries don't really exist in storage. You can delete all the stuff under /data/adb if you want to wipe everything Magisk. In theory, it should be possible to install Magisk on the system partition. It probably doesn't support that method officially anymore. But if the bootless method works, then a similar script can be added to /system....
Click to expand...
Click to collapse
How about just swapping the install-recovery.sh script for suboot.sh on devices that don't have dm-verity?
I think that's pretty much what SuperSU does as well.
That would give root much earlier during boot and not depend on the extra App.
Probably doesn't even need to run mtk-su each boot then either.
Yeah, that's on the right track, @k4y0z. What you can probably use is a modified SU_MINISCRIPT section of suboot.sh, at least as a starting point. That is the code that needs to be run as root. What should be changed is the path to the magiskinit & magisk binaries. Those could be placed somewhere on /system. You would only need mtk-su if selinux needs to be permissive. But I suspect it does for the 'magiskpolicy --live' call. (But then how does SuperSU handle it with enforcing?)