Related
Background info:
1) Rooted my Xperia Z lollipop 5.0.2 with king root
2)phone is unlocked bootloader(or what ever it's called, I checked with the service config)
3) Got no idea about rooting aha
Problem 1: Can't change kingroot to SuperSU. I followed the method I thread used but it said something about not being mounted properly on the terminal and before it said I have to install busy box
Problem 2: I'm trying to enter recovery mode so I can install the zip file for xposed frameworks. I'm using XZrecovery and it says to install busybox. I did that(I downloaded busynox and busybox installer) for busybox, I tried the smart install but it said it wouldn't install. I tried busybox installer and I still didn't install (said something like its compatitable for this edition ). This is for TWRP recovery that I saw on youtube
3) Problem 3
I can't enter recovery mode normally by pressing the power and volume up . it just vibrates 4 times and doesn't turn on
So yeah I need help with those problems. I tried looking through the forums but they are all so weird and complicated
Sorry I'm really new to all of this
What was the version of Kingroot that you used?
herophuong93 said:
What was the version of Kingroot that you used?
Click to expand...
Click to collapse
I loaded kingroot and on the loading screen it said 4.0.5
try this method ( if you haven't already) and use the kingroot apk on the attachment ( version 4.1.0)...and remember uninstall the one you already have 1st
http://forum.xda-developers.com/xperia-z/general/super-su-xperia-device-lollipop-easy-t3119006
i think you should've asked on the Original thread, question are supposed to be on the Q & A section not the genral section i think.
theduke7 said:
try this method ( if you haven't already) and use the kingroot apk on the attachment ( version 4.1.0)...and remember uninstall the one you already have 1st
http://forum.xda-developers.com/xperia-z/general/super-su-xperia-device-lollipop-easy-t3119006
i think you should've asked on the Original thread, question are supposed to be on the Q & A section not the genral section i think.
Click to expand...
Click to collapse
I did that method but SuperSU doesn't open it just says u unfortunately SuperSU has stopped
curryitors said:
I did that method but SuperSU doesn't open it just says u unfortunately SuperSU has stopped
Click to expand...
Click to collapse
i replied to you on the original thread
Hey guys! So I read around about rooting Android 6.0.1 and I only see systemless root. I am rooted right now using systemless root and it works fine, but my question is, is there a way to root 6.0.1 with traditional system root? Or is systemless the only way? Just curious really. Will systemless most likely be the future of rooting and the way it's going to have to be done from now on to keep Android Pay working?
Sent from my Nexus 6
I don't know of anyone who's made the kernel mods required for traditional root. I'd say that systemless root is probably going to be the only way to root from now on at least on nexus devices. Chainfire outlines things that don't work with systemless root on the supersu forums.
StykerB said:
I don't know of anyone who's made the kernel mods required for traditional root. I'd say that systemless root is probably going to be the only way to root from now on at least on nexus devices. Chainfire outlines things that don't work with systemless root on the supersu forums.
Click to expand...
Click to collapse
Thanks for the response! And I wonder if it will be what it is for now! It's the only way to keep Android Pay working while the device is rooted correct? Android Pay refuses to work with a traditionally rooted device?
Sent from my Nexus 6
StykerB said:
I don't know of anyone who's made the kernel mods required for traditional root. I'd say that systemless root is probably going to be the only way to root from now on at least on nexus devices. Chainfire outlines things that don't work with systemless root on the supersu forums.
Click to expand...
Click to collapse
I did. I still use SU2.52. But only until this weekend. I'm switching to systemless too.
Actually building a permissive kernel is really straightforward, needs one line of code added. The build is about five minuters then with abootimg you can just replace the existing with the newly buil kernel in the boot.img, and flash it.
I can give you details if you're interested.
Hi
I have a serious problem with ES File Explorer. This app (and maybe other Apps) says device isn't root, since I cant use ES in root explorer mode.
I heard Titanium Backup has the same issue with this future root!
now I back to 6.0 and waiting for a solution.
kamkar said:
Hi
I have a serious problem with ES File Explorer. This app (and maybe other Apps) says device isn't root, since I cant use ES in root explorer mode.
I heard Titanium Backup has the same issue with this future root!
now I back to 6.0 and waiting for a solution.
Click to expand...
Click to collapse
Mine works perfectly.
kamkar said:
Hi
I have a serious problem with ES File Explorer. This app (and maybe other Apps) says device isn't root, since I cant use ES in root explorer mode.
I heard Titanium Backup has the same issue with this future root!
now I back to 6.0 and waiting for a solution.
Click to expand...
Click to collapse
The first systemless root did that, go back to that thread and get the newest version and flash that, fixed that issue.
Sent from my Nexus 6
Krzysiek_CK said:
Mine works perfectly.
Click to expand...
Click to collapse
How? I pass this steps to install and root 6.0.1:
First of all, I have a clean install of 6.0.1
then flash TWRP
In TWRP, install SuperSU 2.61 that flash a custom boot.img automatically. after dalvik/cash wipe, reboot to OS
After that, reboot to recovery again and flash a custom kernel
but supersu doesn't work and ES file explorer says device doesn't have root permission.
however, I need read/write permission in /system folder to delete some useless apks
H4X0R46 said:
The first systemless root did that, go back to that thread and get the newest version and flash that, fixed that issue.
Sent from my Nexus 6
Click to expand...
Click to collapse
I tested 2.61, is problem fixed in 2.62.3? because I must flash 6.0.1 and setup phone again!
i rooted the old fashioned way, there's no difference except you also have to flash a custom kernel when flashing supersu.
simms22 said:
i rooted the old fashioned way, there's no difference except you also have to flash a custom kernel when flashing supersu.
Click to expand...
Click to collapse
Same way it was with 6.0 right? And Android Pay doesn't work with traditional root? Does it break anything else besides Android Pay?
Sent from my Nexus 6
H4X0R46 said:
Same way it was with 6.0 right? And Android Pay doesn't work with traditional root? Does it break anything else besides Android Pay?
Sent from my Nexus 6
Click to expand...
Click to collapse
ive no use for pay, so never tried. i assume its broken..
Sorry,
I have a Nexus 6 with 6.0.
I am trying to find how to update to 6.0.1 with no-enforced-encryption and then do a systemless rooting but I cannot find the instructions to do this
Seems that just flashing stock, TWRP and the flashing supersu 2.61 from there is enough to have systemless root, right?
but what about no-force-encrypt?
Probably I am changing the discussion but have not found a good thread, apologies.
Thanks in advance.
carmatana said:
Sorry,
I have a Nexus 6 with 6.0.
I am trying to find how to update to 6.0.1 with no-enforced-encryption and then do a systemless rooting but I cannot find the instructions to do this
Seems that just flashing stock, TWRP and the flashing supersu 2.61 from there is enough to have systemless root, right?
but what about no-force-encrypt?
Probably I am changing the discussion but have not found a good thread, apologies.
Thanks in advance.
Click to expand...
Click to collapse
What you probably wanna do is go for a custom kernel that doesn't force encryption. Most if not all don't force it! Elementalx is a good one, maybe elite kernel, and so many others! I use ElementalX on mine, my favorite kernel. www.elementalx.org if you wanna try that one! Others are found here on XDA!
EDIT: Looks like elementalx says to use SuperSU 2.61 or later, which is systemless, I would try another. Maybe elite or another one.
H4X0R46 said:
What you probably wanna do is go for a custom kernel that doesn't force encryption. Most if not all don't force it! Elementalx is a good one, maybe elite kernel, and so many others! I use ElementalX on mine, my favorite kernel. www.elementalx.org if you wanna try that one! Others are found here on XDA!
EDIT: Looks like elementalx says to use SuperSU 2.61 or later, which is systemless, I would try another. Maybe elite or another one.
Click to expand...
Click to collapse
Thanks !!! I will check them, I always have tried to be as close to stock as possible but I think it is time to try something new.
One question: Do Custom Kernels interfere with OTA updates?, this is one of the advertised advantages of systemless rooting and is one of my favorites.
Thanks again
carmatana said:
Thanks !!! I will check them, I always have tried to be as close to stock as possible but I think it is time to try something new.
One question: Do Custom Kernels interfere with OTA updates?, this is one of the advertised advantages of systemless rooting and is one of my favorites.
Thanks again
Click to expand...
Click to collapse
I would say yes, I'm 90% sure but could be wrong. I would flash the a new update with fastboot.
carmatana said:
Thanks !!! I will check them, I always have tried to be as close to stock as possible but I think it is time to try something new.
One question: Do Custom Kernels interfere with OTA updates?, this is one of the advertised advantages of systemless rooting and is one of my favorites.
Thanks again
Click to expand...
Click to collapse
Any mod stops ota's. Root, kernels....You will have to flash full images to get updates. You can skip the userdata part and save your apps and data. But you will have to flash.
Not a big deal, it an extra couple of commands just like the kernel you want to flash.
Thanks!
kamkar said:
How? I pass this steps to install and root 6.0.1:
First of all, I have a clean install of 6.0.1
then flash TWRP
In TWRP, install SuperSU 2.61 that flash a custom boot.img automatically. after dalvik/cash wipe, reboot to OS
After that, reboot to recovery again and flash a custom kernel
but supersu doesn't work and ES file explorer says device doesn't have root permission.
however, I need read/write permission in /system folder to delete some useless apks
Click to expand...
Click to collapse
Clean 6.0.1 followed by systemless root installation as expained in the Root done right thread.
Hi there fellows ! ^^
First of all, I want you all to know that I really am sorry if this is something that has been asked before. I tried, but couldn't find an answer by myself and I don't want to damage my phone again (I may have been waaaaay too hasty in the past...). So here goes.
I have a Honor 5C NEM-L51 (European variant) which I rooted a while ago (two or three months ago maybe ? Can't remember for sure) by unlocking the bootloader, installing TWRP from ADB, flashing the SuperSU zip file... You know, the usual thing. After that I went ahead and installed Xposed Framework, Busybox and several applications and modules which needed root like many of you I guess. Everything went fine. And still is, for the record.
Now I realize that I may have been living under a rock because I discovered very recently that not only SuperSU can be downloaded from the Play Store but also that there is Magisk, an open-source alternative with more functionnalities. Guess what ? I want it.
Soooo I did some research and read this https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 along with other articles here and there on the web and it seems that I'd just have to install some Magisk Manager app' from the Play Store... Is that really all there is to do ?!
I'm worried because it says "If you're already rooted with MagiskSU or Latest Official Systemless SuperSU". Yep, the "Systemless" part get me worried. While I do understand what it means, I can't help but wonder : since I installed SuperSU from a flashable zip file, is it Systemless ? How can I tell ?
Plus the whole thing is kinda confusing to me. If I do that, will Magisk remove SuperSU ? But if so, won't there be a problem with Xposed and other apps that need root ? Same question applies if I first manually remove SuperSU (assuming I can actually do that) before installing anything else.
In short, how should I proceed ? Do I have to remove anything ? Can I do anything ?
Again, sorry if things had been told already. I really want to take my shot, but I don't wanna soft brick my device again by being too carefree one more time.
Thank you for your time and your help.
When super su is installed magisk will make it automatically systemless. But it can't guarantee that it can always hide it. If super su isn't installed /you are unrooted then magisk will install and use magisk su.
Also since you mentioned them: soft bricks can be resolved by just reflashing your Rom, no need to wipe (lose your data) in most cases
Gesendet von meinem SM-G925F mit Tapatalk
ken2802 said:
When super su is installed magisk will make it automatically systemless. But it can't guarantee that it can always hide it. If super su isn't installed /you are unrooted then magisk will install and use magisk su.
Click to expand...
Click to collapse
Thank you for your answer. Can I uninstall SuperSU to install Magisk su instead then ? Do I need to remove Xposed module and my root apps too ?
ken2802 said:
Also since you mentioned them: soft bricks can be resolved by just reflashing your Rom, no need to wipe (lose your data) in most cases
Gesendet von meinem SM-G925F mit Tapatalk
Click to expand...
Click to collapse
Yeah, I do know that, but I really do need my phone at the moment, so I'd kinda be in a world of pain if I brick it.
You can Uninstall super su if you want but it isn't a must if you don't care magisk su. I would remove xposed before installing magisk and after having installed magisk you can install the systemless version. As for your apps that use root, you don't need do deinstall them
ken2802 said:
You can Uninstall super su if you want but it isn't a must if you don't care magisk su. I would remove xposed before installing magisk and after having installed magisk you can install the systemless version. As for your apps that use root, you don't need do deinstall them
Click to expand...
Click to collapse
Sorry for the late reply.
I do want to use Magisksu instead of SuperSU. So basically, what I have to do is :
1 - Uninstall Xposed by flashing the uninstaller from TWRP
2 - Uninstall SuperSu (by the app menu ? Is it enough to remove root ?
3 - Install Magisk from the store
4 - Install systemless Xposed from the store
And I'll be all set, correct ? Nothing should go wrong ?
Zarou said:
Sorry for the late reply.
I do want to use Magisksu instead of SuperSU. So basically, what I have to do is :
1 - Uninstall Xposed by flashing the uninstaller from TWRP
2 - Uninstall SuperSu (by the app menu ? Is it enough to remove root ?
3 - Install Magisk from the store
4 - Install systemless Xposed from the store
And I'll be all set, correct ? Nothing should go wrong ?
Click to expand...
Click to collapse
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.
Didgeridoohan said:
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.
Click to expand...
Click to collapse
Thank you for this clarification. Can you also tell me how can I restore the stock boot image only ? Or Do I have no choice but to re-flash the whole ROM in order to do so ?
Zarou said:
Thank you for this clarification. Can you also tell me how can I restore the stock boot image only ? Or Do I have no choice but to re-flash the whole ROM in order to do so ?
Click to expand...
Click to collapse
Just flash the boot image from an near stock custom Rom. You can flash it through a recovery menu
ken2802 said:
Just flash the boot image from an near stock custom Rom. You can flash it through a recovery menu
Click to expand...
Click to collapse
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?
Zarou said:
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?
Click to expand...
Click to collapse
You can try but if magisk complain while instalation you need to flash a fresh boot image/Rom
Gesendet von meinem SM-G925F mit Tapatalk
Zarou said:
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?
Click to expand...
Click to collapse
It can be a bit of a bother getting the boot image from inside a Huawei factory image...
SuperSU can restore your boot image when you do the full unroot. That was actually what I was referring to with my 2.5.
Didgeridoohan said:
It can be a bit of a bother getting the boot image from inside a Huawei factory image...
SuperSU can restore your boot image when you do the full unroot. That was actually what I was referring to with my 2.5.
Click to expand...
Click to collapse
Thank you, I managed to get by the whole thing with no issue. Problem solved !
Didgeridoohan said:
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.
Click to expand...
Click to collapse
Hi all,
Yesterday I've unlocked my Oneplus 3T bootloader and installed TWRP.
After that I flashed Lineage 14.1, Open Gapps, addonsu-14.1-arm64-signed.zip and finally Magisk. Reboot and install SuperSu.
But I'm wondering if I still need to flash the Lineage addonsu and SuperSu.
tutabeier said:
Hi all,
Yesterday I've unlocked my Oneplus 3T bootloader and installed TWRP.
After that I flashed Lineage 14.1, Open Gapps, addonsu-14.1-arm64-signed.zip and finally Magisk. Reboot and install SuperSu.
But I'm wondering if I still need to flash the Lineage addonsu and SuperSu.
Click to expand...
Click to collapse
What are you doing mixing all those root solutions? Pick one... If you want Magisk, you do not need the other two.
Didgeridoohan said:
What are you doing mixing all those root solutions? Pick one... If you want Magisk, you do not need the other two.
Click to expand...
Click to collapse
Thanks. I probably missed something when reading the threads. I understood Magisk can root my devices, but didn't understood that simply installing it would root my device. So that's why I was flashing su binary and using SuperSU app.
Thanks a lot.
First of all I'm sorry for answering this post so late but I needed to do it.
Well, according to all I've seen about magisk, and obviously with this post, everything I must do to use magisk is:
1. Unlock Bootloader
2. Flash Official Stock ROM
3. Flash Magisk.zip
4. Install Magisk Manager
Is it all? Really? Shouldn't I do anything else, because I'm too worried about it. I've ever used SuperSU until now, and this things of MagiskSU, Magisk Manager and Magisk Hide option are really new for me.
If someone could answer me, including the owner of this post it'd be VERY APPRECIATED and I would thank you all a lot!
Thanks haha
xdaVTU said:
First of all I'm sorry for answering this post so late but I needed to do it.
Well, according to all I've seen about magisk, and obviously with this post, everything I must do to use magisk is:
1. Unlock Bootloader
2. Flash Official Stock ROM
3. Flash Magisk.zip
4. Install Magisk Manager
Is it all? Really? Shouldn't I do anything else, because I'm too worried about it. I've ever used SuperSU until now, and this things of MagiskSU, Magisk Manager and Magisk Hide option are really new for me.
If someone could answer me, including the owner of this post it'd be VERY APPRECIATED and I would thank you all a lot!
Thanks haha
Click to expand...
Click to collapse
It's not quite apparent from your post if you have rooted with SuperSU already and now want to use Magisk instead. But, considering that you're posting in a thread that deals with moving from SuperSU I'm gonna go with that... Kind of...
You will need an unlocked bootloader, yes.
If you've rooted with SuperSU you can reflash your ROM, or use something like @osm0sis unSU zip and then flash the stock boot image only. Depends on your setup which option is easier. If you're not already rooted, this step is unnecessary.
Installing Magisk is just as easy as that, yes.
The Manager is also installed when flashing the Magisk zip, so this step is unnecessary. However... In rare cases the Manager doesn't install with the zip. If that happens you just have to install it manually.
The only step I'd like to add is to have a backup of all important data and files on your device. That's always good practice when tinkering with your device...
The release thread and the installation/troubleshooting thread (I'm hoping to have time to update it for Magisk v15.2 tonight) are good resources when setting everything up and if you encounter issues. Searching through the general support thread is also a good idea if issues arise. Most questions have been answered numerous times already.
I'm new to Magisk but have a couple of questions. I have a pixel XL running Dirty UNICORNS rooted with SuperSU. If I want to use Magisk can I just flash my dirty UNICORNS rom, gapps and then the magisk.zip?
Sent from my Pixel XL using Tapatalk
Hi ..I am using Nexus 6 stock rom , super su, and with all kind root apps Xposed modules .
My questions is do I need to uninstall all the root apps first before flashing the UN su zip ?? Pls help sir
jc1266 said:
Hi ..I am using Nexus 6 stock rom , super su, and with all kind root apps Xposed modules .
My questions is do I need to uninstall all the root apps first before flashing the UN su zip ?? Pls help sir
Click to expand...
Click to collapse
No. You merely need to uninstall SuperSU, either through the SuperSU app (complete uninstall) or by using the unSU zip. You'll also have to make sure that you restore the stock unpatched boot image.
After that you can flash Magisk and you'll be good to go.
Hello i'm new in the forum :fingers-crossed: i have an xperia m5 E5603 and i try to install magisk so i can use apps that i can't use with a custom ROM my device is already rooted with super su and twrp recovery is installed any help please
Hello and welcome to XDA.
There's a lot of information about how to install Magisk (and how to replace SuperSU with MagiskSU) in this forum already. If you look around you'll find it. Number one rule on XDA is to search before posting (I'm not kidding, look at the rules).
To start you off I can tell you that you need to first uninstall SuperSU. You can do that through the SuperSU app (full unroot, select to restore boot image if you have systemless root), or with the unSU script and then manually flash a stock boot image (you can do this in TWRP). After that you should be able to install Magisk by flashing the zip in TWRP. Since you're new, I'd recommend to stick to the stable v12 release for now.
If you encounter issues, here's a troubleshooting guide for you:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Didgeridoohan said:
Hello and welcome to XDA.
There's a lot of information about how to install Magisk (and how to replace SuperSU with MagiskSU) in this forum already. If you look around you'll find it. Number one rule on XDA is to search before posting (I'm not kidding, look at the rules).
To start you off I can tell you that you need to first uninstall SuperSU. You can do that through the SuperSU app (full unroot, select to restore boot image if you have systemless root), or with the unSU script and then manually flash a stock boot image (you can do this in TWRP). After that you should be able to install Magisk by flashing the zip in TWRP. Since you're new, I'd recommend to stick to the stable v12 release for now.
If you encounter issues, here's a troubleshooting guide for you:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Click to expand...
Click to collapse
thank you fo reply after removing super su and install magisk do i need to install super su again for my device to be rooted again ? and is there any recommended version of magisc for my xperia?
Limoneytoo said:
thank you fo reply after removing super su and install magisk do i need to install super su again for my device to be rooted again ? and is there any recommended version of magisc for my xperia?
Click to expand...
Click to collapse
Magisk comes with it's own root, MagiskSU, no need for SuperSU (and for what you seem to want it for, SuperSU isn't compatible). You should probably start by reading through the release thread (the whole thing, it's not that long).
Some Sony devices have issues installing Magisk. This is known... If Magisk v12 doesn't work, you could give the v13.0 beta a go and pay close attention to the info in the TWRP output when flashing. If you do decide to go for the beta, please read through the first post carefully and follow any directions to gather logs to troubleshoot issues.
If you've read through all the info available (I've given you a few good links) and are still having issues, search the support thread for your issue (pretty much everything has already been covered). If you still can't get it going, make sure you post all possible details about your issue and lots of logs (there's also a section about "Asking for help" in the troubleshooting guide I posted earlier).
Didgeridoohan said:
Magisk comes with it's own root, MagiskSU, no need for SuperSU (and for what you seem to want it for, SuperSU isn't compatible). You should probably start by reading through the release thread (the whole thing, it's not that long).
Some Sony devices have issues installing Magisk. This is known... If Magisk v12 doesn't work, you could give the v13.0 beta a go and pay close attention to the info in the TWRP output when flashing. If you do decide to go for the beta, please read through the first post carefully and follow any directions to gather logs to troubleshoot issues.
If you've read through all the info available (I've given you a few good links) and are still having issues, search the support thread for your issue (pretty much everything has already been covered). If you still can't get it going, make sure you post all possible details about your issue and lots of logs (there's also a section about "Asking for help" in the troubleshooting guide I posted earlier).
Click to expand...
Click to collapse
After lot of attemps i always got the same result a bootloop :/ thats happened before when i was trying to install the latest version of super then i release that i can only install an old version of super su but i dont know what version of magisk is recommended for my sony m5
Today I was having Chromecast issues with Netflix, so I factory reset my Chromecast and then had some issues getting it set back up. I had to point the Fire 7's WIFI towards the Chromecast because it couldn't find it otherwise.
After this strange series of events, I rebooted and decided maybe I would remove Netflix and install the last good version I used. I opened Titanium Backup and was told that it could not acquire root. Then a notification for SuperSU popped-up saying "The SU binary needs to be updated!". When I click on it, SuperSU opens and says "SU Binary occupied". When I click "how to solve", I'm taken to a blank WIKI page.
I rebooted. Turned on "Root access" (for apps) in "Developer options". I then rebooted again. I am still unable to achieve Root access!
My tablet was originally running Fire OS v5.1.3 and I downgraded it to v5.1.2. I Rooted v5.1.2 using Root Junkie's tools and then installed CM 12.1 using the guide from the developer's thread.
Firstly, why did this happen or how did this happen?
Secondly, what can I do to gain Root again?
Blastyrant said:
Today I was having Chromecast issues with Netflix, so I factory reset my Chromecast and then had some issues getting it set back up. I had to point the Fire 7's WIFI towards the Chromecast because it couldn't find it otherwise.
After this strange series of events, I rebooted and decided maybe I would remove Netflix and install the last good version I used. I opened Titanium Backup and was told that it could not acquire root. Then a notification for SuperSU popped-up saying "The SU binary needs to be updated!". When I click on it, SuperSU opens and says "SU Binary occupied". When I click "how to solve", I'm taken to a blank WIKI page.
I rebooted. Turned on "Root access" (for apps) in "Developer options". I then rebooted again. I am still unable to achieve Root access!
My tablet was originally running Fire OS v5.1.3 and I downgraded it to v5.1.2. I Rooted v5.1.2 using Root Junkie's tools and then installed CM 12.1 using the guide from the developer's thread.
Firstly, why did this happen or how did this happen?
Secondly, what can I do to gain Root again?
Click to expand...
Click to collapse
Lol. Unlock bootloader and flash latest lineage:
UNLOCK: https://forum.xda-developers.com/amazon-fire/development/unlock-fire-t3899860
LINEAGE: https://forum.xda-developers.com/amazon-fire/orig-development/rom-lineage-12-1-t3639447
Hello. Thank you for that reply. Both threads were very interesting! I would like Lineage on here... Unfortunately, I do not have access to Linux and fear that a lot of those steps to unlock the bootloader are beyond my current understanding.
I'll have to keep reading.
Beyond this.... is my only alternative to flash back the stock ROM, downgrade again, root, and install CM 12.1?
From the error message I am guessing that you are on SuperSU 2.82. I would try uninstalling the SuperSU apk (just the apk, don't unroot) and install version 2.79 of the apk. Sometimes I have seen that error message (on 2.82) when the su binary has somehow been deleted. It tries to replace the binary but fails. If 'daemonsu' is still present in xbin it may be possible for SuperSU to fix the installation but this works better on 2.79 than it does on 2.82.
Blastyrant said:
Hello. Thank you for that reply. Both threads were very interesting! I would like Lineage on here... Unfortunately, I do not have access to Linux and fear that a lot of those steps to unlock the bootloader are beyond my current understanding.
I'll have to keep reading.
Beyond this.... is my only alternative to flash back the stock ROM, downgrade again, root, and install CM 12.1?
Click to expand...
Click to collapse
If you have lost root your only practical options are: 1) restore FireOS and start from scratch; or 2) follow the links suggested by @Rortiz2 (here).
MontysEvilTwin said:
From the error message I am guessing that you are on SuperSU 2.82. I would try uninstalling the SuperSU apk (just the apk, don't unroot) and install version 2.79 of the apk. Sometimes I have seen that error message (on 2.82) when the su binary has somehow been deleted. It tries to replace the binary but fails. If 'daemonsu' is still present in xbin it may be possible for SuperSU to fix the installation but this works better on 2.79 than it does on 2.82.
Click to expand...
Click to collapse
Hello thank you. I like this idea, it will be pretty easy give it a try! Is there a safe source for old SuperSU .apks that you can recommend to me?
Blastyrant said:
Hello thank you. I like this idea, it will be pretty easy give it a try! Is there a safe source for old SuperSU .apks that you can recommend to me?
Click to expand...
Click to collapse
The best place is Chainfire's blog. A link to the page with 2.79 SR3 (bug fix update) is here: https://chainfire.eu/articles/970/SuperSU_v2.79_SR3
Download the zip file: the superuser apk is in the 'common' folder. Click on the apk file from a file browser to install. You will have to enable the option to 'install apps from unknown sources' but you will be prompted to do this if you have not already done so.
Blastyrant said:
Hello. Thank you for that reply. Both threads were very interesting! I would like Lineage on here... Unfortunately, I do not have access to Linux and fear that a lot of those steps to unlock the bootloader are beyond my current understanding.
I'll have to keep reading.
Beyond this.... is my only alternative to flash back the stock ROM, downgrade again, root, and install CM 12.1?
Click to expand...
Click to collapse
No need to install linux. Just use VirtualBox or bootable USB!
Rortiz2 said:
No need to install linux. Just use VirtualBox or bootable USB!
Click to expand...
Click to collapse
Hi. Thank you for those suggestions. I Googled quickly but am still afraid using both options is not something I'll be able to dive right into. I'm also a little confused that the guide for unlocking the bootloader mentions "Install python3, PySerial, adb and fastboot." I'm unsure how to do this for a virtual install or a bootable USB. My Linux usage dates back to a 1 month course in the mid 2000's. =P
Am I making this out to be more difficult than it actually will be?
MontysEvilTwin said:
The best place is Chainfire's blog. A link to the page with 2.79 SR3 (bug fix update) is here: https://chainfire.eu/articles/970/SuperSU_v2.79_SR3
Download the zip file: the superuser apk is in the 'common' folder. Click on the apk file from a file browser to install. You will have to enable the option to 'install apps from unknown sources' but you will be prompted to do this if you have not already done so.
Click to expand...
Click to collapse
Thank you! I bookmarked it and grabbed the file. I've just reinstalled it and am being told "no root detected". =(
Still, it was worth a try!
Blastyrant said:
Hi. Thank you for those suggestions. I Googled quickly but am still afraid using both options is not something I'll be able to dive right into. I'm also a little confused that the guide for unlocking the bootloader mentions "Install python3, PySerial, adb and fastboot." I'm unsure how to do this for a virtual install or a bootable USB. My Linux usage dates back to a 1 month course in the mid 2000's. =P
Am I making this out to be more difficult than it actually will be?
Click to expand...
Click to collapse
Yes. It's very easy. The difficult part is short the pins but since you have 5th gen you don't need to do that.
Enviado desde mi Mi A2 mediante Tapatalk
Rortiz2 said:
Yes. It's very easy. The difficult part is short the pins but since you have 5th gen you don't need to do that.
Click to expand...
Click to collapse
That said, you have to decide if the benefit is worth the effort/hassle. In the US $64 scores a very serviceable 8" tablet at Walmart running the latest version of Android that runs circles around all Amazon offerings except the HD10.