As the title says, I'm trying to see if magisk will work, and wanted input before I flash it.
jrk190 said:
As the title says, I'm trying to see if magisk will work, and wanted input before I flash it.
Click to expand...
Click to collapse
It works, I currently use it for root, ViPER, and Xposed.
I actually went ahead and installed it before you replied, and I've been looking for something like it for ages. It's really well done.
Thanks for the heads up. I just converted from SuperSU to Magisk with phh SuperUser with no problems. Works great.
yes, it's work, [kingroot]
Hi, can you post the link of the guide that you used to install and get the Magisk working??? I need a newbie friendly guide to get that poke go working -.-
turron83 said:
Hi, can you post the link of the guide that you used to install and get the Magisk working??? I need a newbie friendly guide to get that poke go working -.-
Click to expand...
Click to collapse
This is the guide I used: http://www.androidpolice.com/2016/09/11/guide-play-pokemon-go-0-37-rooted-android-magisk/
Thanks!! i only did the first step and after the rebooting, i can get into pokemon go and play!!
Cya guys!!
turron83 said:
Thanks!! i only did the first step and after the rebooting, i can get into pokemon go and play!!
Cya guys!!
Click to expand...
Click to collapse
The first part, you mean just unroot part?
Sent from my R1 HD using Tapatalk
Yes, installed so I could keep adblock and still play Pokemon Go with my kids. Used SuperSU full unroot and then followed the guides here on XDA for how to install it - works great
Installed following the android police tutorial. Root and xposed working. However, when I switch "Root Toggle" in Magisk Manager to the off position, it switches itself back to the on position. Anyone else getting this?
Edit:
This works, per u/Howie_The_Lord on reddit:
Quote:
It seems that this happens, when you ROM is preeroted, you need to delete the system/xbin/su with TWRP and let Magisk mount its own there.
Source: https://www.reddit.com/r/pokemongode...0_with_magisk/
Though, now I get a screen on PoGo saying that my device is not compatible. At least I’m past the authentication.
Trying using Automagisk. It's truly a set it and forget it. http://www.androidpolice.com/2016/0...oid-pay-without-constantly-toggling-root-off/
ytsejam1138 said:
Trying using Automagisk. It's truly a set it and forget it. http://www.androidpolice.com/2016/0...oid-pay-without-constantly-toggling-root-off/
Click to expand...
Click to collapse
I may look into this.
edit, just tried works great on pokemon-go.
Sent from my R1 HD using Tapatalk
This works, per u/Howie_The_Lord on reddit:
It seems that this happens, when you ROM is preeroted, you need to delete the system/xbin/su with TWRP and let Magisk mount its own there.
Click to expand...
Click to collapse
Source: https://www.reddit.com/r/pokemongodev/comments/5265m1/037_on_rooted_android_50_with_magisk/
Though, now I get a screen on PoGo saying that my device is not compatible. At least I’m past the authentication.
stevenlb said:
This works, per u/Howie_The_Lord on reddit:
Source: https://www.reddit.com/r/pokemongodev/comments/5265m1/037_on_rooted_android_50_with_magisk/
Though, now I get a screen on PoGo saying that my device is not compatible. At least I’m past the authentication.
Click to expand...
Click to collapse
I never got this or any problems.
installed
Magisk-v6.zip
rebooted
installed
phh-superuser-17-magisk.zip
rebooted
went to playstore
installed
phh's SuperUser
installed
Magisk_Manager_v1.2.apk
installed
AutoMagisk v1.0.apk
works great.
Related
I installed Xposed Installer and followed the instructions now my phone keeps restarting itself.
Any Idea how to fix? I rooted following these instructions http://forum.xda-developers.com/showthread.php?t=2066390
and followed these to install http://forum.xda-developers.com/showthread.php?t=2727372&page=2
What do you mean by restarting itself? Deinstall xposed again and check if you actually have root access (there is an app called root checker)
CCody said:
What do you mean by restarting itself? Deinstall xposed again and check if you actually have root access (there is an app called root checker)
Click to expand...
Click to collapse
Just did that. I do not have root access according to root checker. before i installed xposed it said i was rooted. I was able to restore it in recovery from a backup i did. any Idea how I can get this going. I really just want to root to use the Dot View Case Hack.
I always recommand a toolkit of ome isnt that familiar with rooting and this stuff. Go take a look at wugfresh toolkit. It helps a lot!
But your bootloader is open, right?
CCody said:
I always recommand a toolkit of ome isnt that familiar with rooting and this stuff. Go take a look at wugfresh toolkit. It helps a lot!
But your bootloader is open, right?
Click to expand...
Click to collapse
Yes and I just installed SUZip after i did the restore and double checked in Root Checker and now it says I have Root Access.
Now I just need the xposed Installer and ill be one step closer to the Dot View Hack lol
Du you also have the supersu (chainfire) app?
CCody said:
Du you also have the supersu (chainfire) app?
Click to expand...
Click to collapse
Yes the one with the Yellow Shield and the Red Hashtag.
elsavior04 said:
Yes the one with the Yellow Shield and the Red Hashtag.
Click to expand...
Click to collapse
Alright! What are we talking about then? You are good to go, man!
CCody said:
Alright! What are we talking about then? You are good to go, man!
Click to expand...
Click to collapse
Lol now if I can only get the xposed installer to install without issues ill be golden.
Thanks a million for the help. First time on this site and nothing but awsomeness :good::good::good:
Open supersu. Is xposed listed under apps? If no, then just reinstall the xposed app. To install your module, go to http://repo.xposed.info/module-overview, search for dot view hack, download and install it. In xposed you supposed to activate your module and do a reboot. Finish!
CCody said:
Open supersu. Is xposed listed under apps? If no, then just reinstall the xposed app. To install your module, go to http://repo.xposed.info/module-overview, search for dot view hack, download and install it. In xposed you supposed to activate your module and do a reboot. Finish!
Click to expand...
Click to collapse
Ok. So I DL the xposed app and installed it. I select framework then Install/Update and reboot, when i power it back on and open it says the following message
"app_process version 58 has been installed previously but version "---" was found now. If you didn't expect an old file to be restored, you might want to try installing via recovery auto or manual"
Should it say this?
Try to follow that suggestion. You seem to have a device that resets /system on a reboot.
rovo89 said:
Try to follow that suggestion. You seem to have a device that resets /system on a reboot.
Click to expand...
Click to collapse
I actually got it to work i hit soft reboot and not a full reboot and i got it working.
IDK if i do a full reboot if it will mess it up but for now it works :good:
elsavior04 said:
I actually got it to work i hit soft reboot and not a full reboot and i got it working.
IDK if i do a full reboot if it will mess it up but for now it works :good:
Click to expand...
Click to collapse
Just install it via the recovery.
GermainZ said:
Just install it via the recovery.
Click to expand...
Click to collapse
Done!
same prb
i have the same prb on my htc 816 dual sim, plz help me..............................
Have the phone rooted for adblock and root explorer but now that people cheat, they've blocked Pokemon Go if you're rooted. There is a video that shows how to bypass the block but I've not seen any posts in here saying if it was safe:
https://youtu.be/TBaZpiIDFQ8
Is it safe to do what he says to do in the video?
BenHolliday said:
Have the phone rooted for adblock and root explorer but now that people cheat, they've blocked Pokemon Go if you're rooted. There is a video that shows how to bypass the block but I've not seen any posts in here saying if it was safe:
https://youtu.be/TBaZpiIDFQ8
Is it safe to do what he says to do in the video?
Click to expand...
Click to collapse
Magisk does not work with this phone. Root cloak does.
Someone over in Resurrection Remix thread got Pokemon Go to work with Root Cloak:
Nitefire77 said:
Pokemon go works on my phone with rootcloak. Wasn't too difficult to get it working
Click to expand...
Click to collapse
You can ask him for details. So, you can still run a custom ROM if you wish...
ChazzMatt said:
Root Cloak.
Click to expand...
Click to collapse
I appreciate the reply ChazzMatt.
Tell me if I'm wrong here but I have to have Xposed installed which I never really messed with.
Xposed from here is what I found during search - http://forum.xda-developers.com/showthread.php?t=3034811
Rootcloak from here - http://repo.xposed.info/module/com.devadvance.rootcloak2
Will I have to reset to do Xposed or will it just be a simple flash through TWRP and then follow the instructions for Rootcload of is there more to getting Xposed installed than the simple "Must be flashed with a custom recovery (e.g. TWRP) to install the framework." that's in the post?
BenHolliday said:
I appreciate the reply ChazzMatt.
Tell me if I'm wrong here but I have to have Xposed installed which I never really messed with.
Xposed from here is what I found during search - http://forum.xda-developers.com/showthread.php?t=3034811
Rootcloak from here - http://repo.xposed.info/module/com.devadvance.rootcloak2
Will I have to reset to do Xposed or will it just be a simple flash through TWRP and then follow the instructions for Rootcload of is there more to getting Xposed installed than the simple "Must be flashed with a custom recovery (e.g. TWRP) to install the framework." that's in the post?
Click to expand...
Click to collapse
There's two parts to get Xposed Framework working, some sort of "alpha" file and then an "installer" file. You just need to ensure you are using the right installer for your phone's CPU chip. Then you can install th Xposed modules of your choice, like that Root Cloak. I've not messed with Xposed since over a year ago, when I went to CM as there was nothing CM was missing that I needed (in my opinion). How @Nitefire77 got Root Cloak to let him play the new locked down Pokemon Go, you will have to ask him.
There was a running Magisk discussion over in Resurrection Remix until the dev told people to take it elsewhere, that it doesn't work on our phone and to stop pestering him with requests for it. Then @Nitefire77 said he was using Root Cloak for Pokemon Go.
---------- Post added at 07:41 PM ---------- Previous post was at 07:36 PM ----------
Here, this might help
[OFFICIAL] Xposed for Lollipop/Marshmallow [Android 5.0/5.1/6.0, v86, 2016/07/08]
http://forum.xda-developers.com/showthread.php?t=3034811
I got them all installed. Pokemon Go refuses to connect to server so it's looking like a bust.
BenHolliday said:
I got them all installed. Pokemon Go refuses to connect to server so it's looking like a bust.
Click to expand...
Click to collapse
All I can say is to contact the guy who says he got it working with Root Cloak...
Nitefire77 said:
Pokemon go works on my phone with rootcloak. Wasn't too difficult to get it working
Click to expand...
Click to collapse
It was my understanding that root cloak is not good enough to bypass safetynet api (pokemon go and android pay security check) perhaps he is doing a hybrid where he actually is unrooting
Sent from my DROID Turbo using XDA-Developers mobile app
Hi,
I'm running stock ROM with TWRP recovery.
I've managed to successfully root my Note with Magisk.
Somehow I noticed that my device loses root after a reboot and sometimes even randomly. When I go into the custom recovery and flash Magisk 14 or 14.3 everything works fine for while, till it loses root again.
Could someone shed some light on my issue, please?
Thanks in advance.
I've also themed Magisk Manager with Substratum could that be the issue?
I'm also running stock rom, losing magisk root from time to time.
When root is lost, I'm getting a notification that "new magisk V14 is available.
Reinstalling with TWRP only to lose it again a day or two later.
You all need to change your settings in magisk manager. I had the same problem. Change your update channel to Beta. This will keep magisk 14.3 installed once you flash it in recovery after setting this. :highfive:
Are you using the hide root feature?
If so then that is probably your issue.
opasha said:
You all need to change your settings in magisk manager. I had the same problem. Change your update channel to Beta. This will keep magisk 14.3 installed once you flash it in recovery after setting this. :highfive:
Click to expand...
Click to collapse
This worked for me, thank you!!
ALEXRUSS55 said:
This worked for me, thank you!!
Click to expand...
Click to collapse
Welcome :highfive:
jpasint said:
Are you using the hide root feature?
If so then that is probably your issue.
Click to expand...
Click to collapse
What issue does this cause?
I have the same issue with last magisk beta, 16.4.. have anyone found a fix?
stiffis said:
I have the same issue with last magisk beta, 16.4.. have anyone found a fix?
Click to expand...
Click to collapse
Flash magisk v16.4, then open magisk manager disable magisk hide, for keep your root
kenpaci said:
Flash magisk v16.4, then open magisk manager disable magisk hide, for keep your root
Click to expand...
Click to collapse
Looks like that worked, thanks!
stiffis said:
Looks like that worked, thanks!
Click to expand...
Click to collapse
But it losses Android pay. Anyone with other solution to keep root and hide it?
Best regards
Webgurru
webgurru said:
But it losses Android pay. Anyone with other solution to keep root and hide it?
Best regards
Webgurru
Click to expand...
Click to collapse
Try disabling MagiskHide and re-enable it again (try also with a reboot between disabling and enabling)
stiffis said:
Try disabling MagiskHide and re-enable it again (try also with a reboot between disabling and enabling)
Click to expand...
Click to collapse
If I disable it, won't secure apps that run in the background pick up root? I'm guessing I should freeze them first or something?
hshah said:
If I disable it, won't secure apps that run in the background pick up root? I'm guessing I should freeze them first or something?
Click to expand...
Click to collapse
Try closing those apps first, I think it goes ok as long you don't start the apps yourself because most off the apps checks root at startup, but I can't guarantee you anything
Something weird has happened... I've not actually changed anything but now I tend to lose root immediately after rebooting.
I'm a technical person so whilst I say nothing has changed, I know that it probably has and I just can't remember.
I need Hide, so disabling that is not an option... I have no idea where to even start debugging this
Sent from my Samsung Galaxy Note 8 using XDA Labs
hshah said:
Something weird has happened... I've not actually changed anything but now I tend to lose root immediately after rebooting.
I'm a technical person so whilst I say nothing has changed, I know that it probably has and I just can't remember.
I need Hide, so disabling that is not an option... I have no idea where to even start debugging this
Sent from my Samsung Galaxy Note 8 using XDA Labs
Click to expand...
Click to collapse
Hi,
Same thing happening to me. Lost root soon after restart. I need it hide. Any genius mind can suggest some solution?
Best regards,
Webgurru
webgurru said:
Hi,
Same thing happening to me. Lost root soon after restart. I need it hide. Any genius mind can suggest some solution?
Best regards,
Webgurru
Click to expand...
Click to collapse
I've been posting my analysis here:
https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
We have some smart guys (ie @topjohnwu @Didgeridoohan @kantjer etc) and I don't know enough to sort this so the least I can do is provide as much information as possible
hshah said:
I've been posting my analysis here:
https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
We have some smart guys (ie @topjohnwu @Didgeridoohan @kantjer etc) and I don't know enough to sort this so the least I can do is provide as much information as possible
Click to expand...
Click to collapse
Any luck or help from this thread to resolve?
webgurru said:
Any luck or help from this thread to resolve?
Click to expand...
Click to collapse
Only been spamming the thread with my woes since yesterday so still early days. I'm certainly not expecting an immediate fix because this has been going on for quite some time and if it was easy, we wouldn't be having this conversation.
hshah said:
Only been spamming the thread with my woes since yesterday so still early days. I'm certainly not expecting an immediate fix because this has been going on for quite some time and if it was easy, we wouldn't be having this conversation.
Click to expand...
Click to collapse
Thanks. In my point of view this look to be a bug in Magisk. Did you tried some older version?
Hello everyone. I have created this thread (hopefully in the right place) to start a discussion on methods/developing methods to get fortnite to work on a rooted device, with magisk installed. Im currently running Dr. Ketan's rom (android pie) on a samsung galaxy note 9 and for obvious reasons (the fortnite galaxy skin) would like to play a few games and have it work without any hiccups. Im not looking to hack the game or any nonsense like that, so if anyone has a currently functioning method that doesnt require me to reflash stock firmware (as i dont have a pc and had to use a friends to unlock bootloader and such) and play on the unrooted device then re-root and install custom rom
evan5935 said:
Hello everyone. I have created this thread (hopefully in the right place) to start a discussion on methods/developing methods to get fortnite to work on a rooted device, with magisk installed. Im currently running Dr. Ketan's rom (android pie) on a samsung galaxy note 9 and for obvious reasons (the fortnite galaxy skin) would like to play a few games and have it work without any hiccups. Im not looking to hack the game or any nonsense like that, so if anyone has a currently functioning method that doesnt require me to reflash stock firmware (as i dont have a pc and had to use a friends to unlock bootloader and such) and play on the unrooted device then re-root and install custom rom
Click to expand...
Click to collapse
Uhh. Its already working. Atleast for me. You just need to hide magisk manager , hide Fortnite app and installer on magisk hide tab, disable usb debugging, and make sure there isn't magisk named folder or files inside your internal storage. That should do it. I'm on the note 8 and it works just fine
white7561 said:
Uhh. Its already working. Atleast for me. You just need to hide magisk manager , hide Fortnite app and installer on magisk hide tab, disable usb debugging, and make sure there isn't magisk named folder or files inside your internal storage. That should do it. I'm on the note 8 and it works just fine
Click to expand...
Click to collapse
Dang, really? Thanks man!
evan5935 said:
Dang, really? Thanks man!
Click to expand...
Click to collapse
Yep!! Its working on mine ....
white7561 said:
Yep!! Its working on mine ....
Click to expand...
Click to collapse
Its not workin for me bro, i hide magisk manage, have no folders or files named makgisk, or even have magisk in the name, hide the root apps with magisk as well as the fortnite installer and app before i launch each of them. It just deosnt work for me :'(
Are you running in magisk core mode, with adb/root disabled as well?
And what about USB/ADB Debugging? Have you turned that off as well?
white7561 said:
Yep!! Its working on mine ....
Click to expand...
Click to collapse
Didgeridoohan said:
And what about USB/ADB Debugging? Have you turned that off as well?
Click to expand...
Click to collapse
Yes but developer options is still on, does that make a difference? Also, I have not tried with magisk core mode off and root disabled, so if you are doing that then that may also be my issue
Edit: i turned on magisk core mode and disabled root and still does not work. Would having lucky patcher installed be an issue?
evan5935 said:
Yes but developer options is still on, does that make a difference? Also, I have not tried with magisk core mode off and root disabled, so if you are doing that then that may also be my issue
Edit: i turned on magisk core mode and disabled root and still does not work. Would having lucky patcher installed be an issue?
Click to expand...
Click to collapse
Prob yeah ...
white7561 said:
Prob yeah ...
Click to expand...
Click to collapse
Definitely was the issue. Deleted lucly patcher and also the Xposed installer (even though exposed isnt on Pie yet) and that combined with everything else did the trick
evan5935 said:
Definitely was the issue. Deleted lucly patcher and also the Xposed installer (even though exposed isnt on Pie yet) and that combined with everything else did the trick
Click to expand...
Click to collapse
Yep. Also . No xposed . Since it fails the safety net [emoji4]. Well. Happy gaming!! [emoji4][emoji4][emoji4]
Working still Season 9 Magisk 19.1? Not I
Anybody still using this method? I get all the way to the drop then get kicked out "can't sync user profile"
Magisk is hidden in a random folder, installer and game both hidden. Tried with Developer settings off and also with them on. Rooted.
Even Google Pay works so I'm head scratching here if there is a system processes that is now needing hidden or what to play the newest Beta. All help appreciated.
I have the same problem. Google pay is working but fortnite not
I'm on a rooted OnePlus 7 Pro and mine just stopped working yesterday. Was fine for about an hour after the Star Wars event then logged on around 10pm and I get kicked out as soon as I exited the bus. Keeps happening over and over again. No other software changes so I'm guessing there needs to be some update to Magisk to get it working again.
Chuck_C said:
I'm on a rooted OnePlus 7 Pro and mine just stopped working yesterday. Was fine for about an hour after the Star Wars event then logged on around 10pm and I get kicked out as soon as I exited the bus. Keeps happening over and over again. No other software changes so I'm guessing there needs to be some update to Magisk to get it working again.
Click to expand...
Click to collapse
Curious what was your setup? To have it work?
Pvt WhoOkid said:
Curious what was your setup? To have it work?
Click to expand...
Click to collapse
Stock OnePlus 7 pro with magisk and TWRP. Epic launcher and Fortnite both hidden in magisk hide. USB debugging turned off. No modules installed. Just using it for root. Worked fine until last night. Gpay and all other safety net apps work fine. It's just Fortnite. Logged in on a friend's Xbox and a really laggy ipad and could play on both so it's not my account - it's definitely the rooted phone and magisk no longer hides itself from Fortnite.
I'm really irritated with the whole thing because I was so close to finishing the season pass and now I can't play at all.
Here's another fix. These last few updates they have added more things to the blacklist. So remember that they basically scans the internal sdcard etc for MagiskManager folder right? Well now they scan TWRP folder too!! So try renaming it to something else without TWRP in it. And see if it works!. Just tried mine and still working just fine!
white7561 said:
Here's another fix. These last few updates they have added more things to the blacklist. So remember that they basically scans the internal sdcard etc for MagiskManager folder right? Well now they scan TWRP folder too!! So try renaming it to something else without TWRP in it. And see if it works!. Just tried mine and still working just fine!
Click to expand...
Click to collapse
Thanks for posting that. I renamed the folder and now it works again.
Now I need to figure out if I can leave it that way or if I need to keep switching the folder name back and forth to be able to use TWRP correctly.
Chuck_C said:
I'm on a rooted OnePlus 7 Pro and mine just stopped working yesterday. Was fine for about an hour after the Star Wars event then logged on around 10pm and I get kicked out as soon as I exited the bus. Keeps happening over and over again. No other software changes so I'm guessing there needs to be some update to Magisk to get it working again.
Click to expand...
Click to collapse
I have pretty much the same setup as you. Do you happen to get lag here and there? During game play? I was able to get mine working again by renaming the folder for trwp as suggested.
Chuck_C said:
Thanks for posting that. I renamed the folder and now it works again.
Now I need to figure out if I can leave it that way or if I need to keep switching the folder name back and forth to be able to use TWRP correctly.
Click to expand...
Click to collapse
With Tasker or Automate, you can set a trigger to automatically rename folder on start of Fortnite and rename back, after the game is closed.
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.