Related
Hi!
I have rooted SGSA and update the SuperSU app from Google Play.
I see in options that there is an option "install supersu into /system"
Is unchecked from default.
What it does?? (i search Internet but i didn't find any information...)
It is good to check it? or it isn't necessary?
Thank you.
konstantinos77 said:
Hi!
I have rooted SGSA and update the SuperSU app from Google Play.
I see in options that there is an option "install supersu into /system"
Is unchecked from default.
What it does?? (i search Internet but i didn't find any information...)
It is good to check it? or it isn't necessary?
Thank you.
Click to expand...
Click to collapse
You can't root that way. If you use JB use this: http://forum.xda-developers.com/showthread.php?t=2087424
P.S. Sorry I read it too quickly. You do not need to do that.
Yes but what is the meaning to make SuperSU a system app??
If some one knows please explain...
Thank you!!
Its mean that supersu will install like other system apps and cannot uninstall unless you revert back that setting or delete using file browser or titanium backup
Sent from my GT-I9070 using XDA Premium 4 mobile app
And what is the meaning to do this??
konstantinos77 said:
And what is the meaning to do this??
Click to expand...
Click to collapse
1. That you can't uninstall it like other apps installed from play store
2. Need to remove it from system/app folder
3. Does not mean anything to it functionality
beware
I accidentally ran the script that installed SuperSu in a protected mode and made it a system app. Since then, I can no longer flash CM11 on S3 SGH-i747. Recovery after the install asks if I want to fix root, yes-no....not matter what I answer, the rom just reverts back to stock so beware.
chestboy76 said:
I accidentally ran the script that installed SuperSu in a protected mode and made it a system app. Since then, I can no longer flash CM11 on S3 SGH-i747. Recovery after the install asks if I want to fix root, yes-no....not matter what I answer, the rom just reverts back to stock so beware.
Click to expand...
Click to collapse
Look for S3 SGH-i747 section, this is SGSA I9070 section.
Sorry
shut_down said:
Look for S3 SGH-i747 section, this is SGSA I9070 section.
Click to expand...
Click to collapse
My apologies. I didn't realize I was in the wrong section. I linked here from S3 SGH-i747 section.
shut_down said:
1. That you can't uninstall it like other apps installed from play store
2. Need to remove it from system/app folder
3. Does not mean anything to it functionality
Click to expand...
Click to collapse
If I choose it will it stabilize the system so when I reboot it will keep root?
I had it all set up rooted and SuperSu and went to back it up so I could just use twrp recovery and restore it and still be rooted and just like it is after rooting and all.
I made the back up and did the required reboot and when it finished I lost root.
Will this work?
ronfiveo said:
If I choose it will it stabilize the system so when I reboot it will keep root?
I had it all set up rooted and SuperSu and went to back it up so I could just use twrp recovery and restore it and still be rooted and just like it is after rooting and all.
I made the back up and did the required reboot and when it finished I lost root.
Will this work?
Click to expand...
Click to collapse
On Galaxy S Advance I9070? Check if you have USB debugging ON (when you said you lost root). This will not make it more stable, SuperSU.apk is just a GUI for controling root. And you root with SU file that is pushed to system (can't remember what folder exacly).
shut_down said:
On Galaxy S Advance I9070? Check if you have USB debugging ON (when you said you lost root). This will not make it more stable, SuperSU.apk is just a GUI for controling root. And you root with SU file that is pushed to system (can't remember what folder exacly).
Click to expand...
Click to collapse
The USB debugging has a check mark . Is that the way it's supposed to be to save root during a reboot or do I revoke USB debugging authorization ?
I choose USB debugging it when I did the root process.
And it's a Galaxy S4 SGH-i337Z
ronfiveo said:
The USB debugging has a check mark . Is that the way it's supposed to be to save root during a reboot or do I revoke USB debugging authorization ?
I choose USB debugging it when I did the root process.
And it's a Galaxy S4 SGH-i337Z
Click to expand...
Click to collapse
Why are you asking your question in a Galaxy S Advance forum?
Better go to then S4 section.
ronfiveo said:
The USB debugging has a check mark . Is that the way it's supposed to be to save root during a reboot or do I revoke USB debugging authorization ?
I choose USB debugging it when I did the root process.
And it's a Galaxy S4 SGH-i337Z
Click to expand...
Click to collapse
I am not sure what is root procedure for that device. Better ask someone that has that device, or made a root for it.
shut_down said:
I am not sure what is root procedure for that device. Better ask someone that has that device, or made a root for it.
Click to expand...
Click to collapse
I had it rooted with Kingroot.
As far as I know that's the only way for this model of device.
Then using MrW0lf's method I replaced and removed Kinguser for SuperSU.
I was still rooted.
I wanted to make a backup so when using restore I could retain root and SuperSU in my system.
The setting of choosing to make SuperSU a system app in stead of as it is, I thought would make it possible to keep root.
I have used restore while having root with Kinguser and kept root.
I am not understanding why I loose root when restoring while having SuperSU.
Sent from my SAMSUNG-SGH-I337Z using Tapatalk
ronfiveo said:
I had it rooted with Kingroot.
As far as I know that's the only way for this model of device.
Then using MrW0lf's method I replaced and removed Kinguser for SuperSU.
I was still rooted.
I wanted to make a backup so when using restore I could retain root and SuperSU in my system.
The setting of choosing to make SuperSU a system app in stead of as it is, I thought would make it possible to keep root.
I have used restore while having root with Kinguser and kept root.
I am not understanding why I loose root when restoring while having SuperSU.
Sent from my SAMSUNG-SGH-I337Z using Tapatalk
Click to expand...
Click to collapse
I do not thing that moving SuperSu to System partition would help you. Main file that enables root permissions are not in that apk, you can install SuperSu from the Play store. That is not the problem.
Do you know why I loose root after a restore?
Sent from my SAMSUNG-SGH-I337Z using Tapatalk
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.
2 days ago i rooted my G800F with CF-auto-root through ODIN. (Used the latest CF-auto-root from here , with ODIN v3.10.6)
But after that my device is too laggy!
Much slower as it had 512 RAM. Root success was confirmed with Root Checker
SuperSU was also installed but sometimes i get a message that SU binary isn't installed.
I 've tried with "ROM toolbox" and "System App Remover" to unistall some system apps but i got the message "Failed to Unistall xxxxxxx app". But if i entered again "ROM toolbox" i found out that the xxxxxx app wasn't there. It has been unistalled!
Once Play Store didn't let me upgrade some apps, because it said that i must logged in to my account (which i was already logged in), and others problems like that!
What shall i do now?
Root again the device? Unroot the device and root again? Unistall Knox? (i've read somewhere that Knox is responsible for problems after rooting). Find another version for CF- auto-root? (the latest is for Build ID LMY47X.G800FXXU1BPB2 but mine is LMY47X.G800FXXU1BPC4 if it matters)
Please help!
Yes, if you have root you must disable Knox. If it doesn't help, you can try go back to stock to see if it's a hardware issue (it will still lag), then root again if everything is fine for a day or two...
lfom said:
Yes, if you have root you must disable Knox. If it doesn't help, you can try go back to stock to see if it's a hardware issue (it will still lag), then root again if everything is fine for a day or two...
Click to expand...
Click to collapse
I have this device for about 2 years. These problems have begun just after rooting. So, i believe it is not a hardware problem.
By saying disable Knox you mean delete/unistall or freeze?
And how can i do that?
billphone said:
I have this device for about 2 years. These problems have begun just after rooting. So, i believe it is not a hardware problem.
By saying disable Knox you mean delete/unistall or freeze?
And how can i do that?
Click to expand...
Click to collapse
I would first use Link2SD to freeze all related to Knox and Security log first. If everything went right, backup and delete files.
lfom said:
I would first use Link2SD to freeze all related to Knox and Security log first. If everything went right, backup and delete files.
Click to expand...
Click to collapse
I freezed all apps and having the word Knox in their names. The phone isn't so laggy now but if i open some apps for rooted devices such as Busybox or Rom Toolbox they can't operate and got a message that my device isn't rooted. After that, no others apps for rooted devices are working! The SU doesn't open at all! All will work again after restart (except ofcourse Busy box Rom toolbox)
So what shall i do?
Unroot and root again? Root again over the previous root? What else?
billphone said:
I freezed all apps and having the word Knox in their names. The phone isn't so laggy now but if i open some apps for rooted devices such as Busybox or Rom Toolbox they can't operate and got a message that my device isn't rooted. After that, no others apps for rooted devices are working! The SU doesn't open at all! All will work again after restart (except ofcourse Busy box Rom toolbox)
So what shall i do?
Unroot and root again? Root again over the previous root? What else?
Click to expand...
Click to collapse
I thought that CF-Auto-Root disabled Knox protection when used, but maybe not... I think there is an option in SuperSU to disable it, you must use it as soon as you open it after using CF-Auto-Root and booting again to Android. If it doesn't have this option, it's not only Knox that makes the security system that prevents root, there is SecurityLog too (and on MM I think I've seen Rootpd that probably is a root protection daemon). Probably it removed su when you were disabling Knox. If you can root again over the current state, probably you can try disabling security system completely this time. Check other threads about rooting G800F, probably there is a list of apps you must disable.
lfom said:
I thought that CF-Auto-Root disabled Knox protection when used, but maybe not... I think there is an option in SuperSU to disable it, you must use it as soon as you open it after using CF-Auto-Root and booting again to Android. If it doesn't have this option, it's not only Knox that makes the security system that prevents root, there is SecurityLog too (and on MM I think I've seen Rootpd that probably is a root protection daemon). Probably it removed su when you were disabling Knox. If you can root again over the current state, probably you can try disabling security system completely this time. Check other threads about rooting G800F, probably there is a list of apps you must disable.
Click to expand...
Click to collapse
Thanks for your anwser.
The SU isn't permanently removed but only temporarily, because after restart it is working again
I 'll try to unroot and root again and we 'll see what happens
billphone said:
Thanks for your anwser.
The SU isn't permanently removed but only temporarily, because after restart it is working again
I 'll try to unroot and root again and we 'll see what happens
Click to expand...
Click to collapse
SuperSU is the app, su is the superuser daemon. Good luck.
billphone said:
Thanks for your anwser.
The SU isn't permanently removed but only temporarily, because after restart it is working again
I 'll try to unroot and root again and we 'll see what happens
Click to expand...
Click to collapse
So finally the problems are still here. The device is no longer laggy, but the root sometimes works sometimes doesn't.
I root again over the previous root, again the same. I unroot and again root, the same. I install a custom recovery and flash the SuperSU, the same results.
Initially working fine, giving rights to the applications but later sometime does not. With restart reverts briefly again.
What on earth has gone wrong? I have root many devices and all of them were working perfect!
I would like to avoid factory reset because i don't know how to restore my backup without problems.
Is there another solution?
Knox disables root, it can even revert custom recovery. Did you disable it, as well as Security Log (disable its updates in settings first), as suggested previously?
lfom said:
Knox disables root, it can even revert custom recovery. Did you disable it, as well as Security Log (disable its updates in settings first), as suggested previously?
Click to expand...
Click to collapse
Yes, i disable some apps with the word Knox in them. I don't know if is still a Knox app with a different name. Is there a list with Knox apps?
I didn't disable the Security Log neither its updates. Where can i find them?
So, finally i have a rooted device which randomly unroot itself!
And nothing can be done!
Question:
Is Xposed or any of its modules suppose to give zygote root access? Doesnt Xposed already take care of that?
Yes. What's app extensions module must have zygote/sqlite3 base for work.
Robert342 said:
Yes. What's app extensions module must have zygote/sqlite3 base for work.
Click to expand...
Click to collapse
One module that is using it wrong.
Others? None?
riahc3 said:
Question:
Is Xposed or any of its modules suppose to give zygote root access? Doesnt Xposed already take care of that?
Click to expand...
Click to collapse
No. You must have root access on your device before trying to install Xposed.
Please go read in the Zygote sub-forums to learn how to get root access, if it is possible.
Spott07 said:
No. You must have root access on your device before trying to install Xposed.
Please go read in the Zygote sub-forums to learn how to get root access, if it is possible.
Click to expand...
Click to collapse
...wow...really?
Spott07 said:
No. You must have root access on your device before trying to install Xposed.
Please go read in the Zygote sub-forums to learn how to get root access, if it is possible.
Click to expand...
Click to collapse
I accidentally unrooted my phone multiple times yet Xposed still works. So I'd say you are wrong, Xposed only requires unlocked bootloader/recovery.
levizx said:
I accidentally unrooted my phone multiple times yet Xposed still works. So I'd say you are wrong, Xposed only requires unlocked bootloader/recovery.
Click to expand...
Click to collapse
Technically, you are correct.
However, you can't get root access without unlocking the bootloader/recovery, so it's easiest just to start with root as your goal. By the time you unlock bootloader/recovery you're already 90% of the way to root.
Spott07 said:
Technically, you are correct.
However, you can't get root access without unlocking the bootloader/recovery, so it's easiest just to start with root as your goal. By the time you unlock bootloader/recovery you're already 90% of the way to root.
Click to expand...
Click to collapse
90% of the way to root means EXACTLY that, not rooted. So saying Xposed REQUIRES root is not just "technically" wrong, there's nothing right about that statement, and that's a fact.
levizx said:
90% of the way to root means EXACTLY that, not rooted. So saying Xposed REQUIRES root is not just "technically" wrong, there's nothing right about that statement, and that's a fact.
Click to expand...
Click to collapse
To install Xposed requires permission or workarounds to edit system files at the root level. End of story.
However you go about it, whether the user account has ongoing root access or not, whether the device allows root/bootloader access out-of-the-box or if you have to use exploits, whether it continues to run after the *user account* has unrooted, is immaterial.
SuperSU or equivalents do not *provide* root access, and removing them is not the same as unrooting the entire device. They instead take existing root access and bring it to where it is convenient for the user.
Unlocking the bootloader/system partition IS rooting your device, even if you never install a root manager program, despite how the terminology has been distorted in popular use here on XDA.
Xposed requires root access. Xposed modules do not provide root access if your device does not already have it.
Ok, fine. But where did the "zygote" related discussion ended up? I've just had a zygote root permission request which I denied, and now SuperSU is not responding and crashing. Some other non root app nor Xposed module is also closing itself...
Sent from my Moto G4 Plus using XDA Labs
The Analog Kid said:
Ok, fine. But where did the "zygote" related discussion ended up? I've just had a zygote root permission request which I denied, and now SuperSU is not responding and crashing. Some other non root app nor Xposed module is also closing itself...
Click to expand...
Click to collapse
Zygote process is in the system, and should not request root permission (already has it).
You encountered a bug which you should have neither allowed/disallowed and just rebooted your device.
Search the supersu threads, the bug get's reported every now and then.
Chainfire said:
There is a case where an internal crash of zygote(64) will attempt to create log files as root. This is a left-over from Android development and really shouldn't be in production builds, but it often is. It is impossible to know if that is the cause, though.
Click to expand...
Click to collapse
corkiejp said:
Zygote process is in the system, and should not request root permission (already has it).
You encountered a bug which you should have neither allowed/disallowed and just rebooted your device.
Search the supersu threads, the bug get's reported every now and then.
Click to expand...
Click to collapse
Well, I've searched for that indeed; but there's no concluding answer that I can spot whatsoever. Anyway, just to see if granting zygote root permission (Chainfire's "suggestion" picked from one zygote related discussion) resulted in any help, I just did... And it positively doesn't. SuperSu has exactly the same bad behavior. I even updated it to 2.82 SR5, to no avail. Nevertheless, I agree this is something that just entered device since SuperSU was working as usual for one month a few days back; I can say it started right after I tried the SuperSU logs section. As of know, I have a nice collection of different "Cracker" logs regarding SuperSU crashes (though, sometimes it just stops). One of the most dramatic SuperSU related events, involved multiple apps and even system stopping in sequence following SuperSU's own. That is something I couldn't even find reports of in any SuperSu nor zygote threads. I think I'll keep trying some stuff before definitely going full restore and start from zero.
Sent from my Moto G4 Plus using XDA Labs
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.