AS IS SOLUTION, you are liable for your own device. I'm not responsible for bricked devices.
This is assuming you've rooted .310 rom and upgraded OTA to .244!! This has not been tested on any other progression.
I've owned the phone for 1 week and I found the solution to bootloops on folder mounts.
1. Find this file in the link link below; remountrebootfix-windows.zip - [Click for QR Code] (948.7 KB, 21 views), download it, and extract.
http://forum.xda-developers.com/showthread.php?t=2421730
2. Run the appropriate bat file for your root.
3. Install Link2SD.
i tried everything but it says link2sd doesn not have root excess even though i have supersu installed and root excess and also my mobile is rooted according to this procedure http://forum.xda-developers.com/showthread.php?t=2392865
nikeburrrr said:
i tried everything but it says link2sd doesn not have root excess even though i have supersu installed and root excess and also my mobile is rooted according to this procedure http://forum.xda-developers.com/showthread.php?t=2392865
Click to expand...
Click to collapse
I'm sorry for your troubles, but as the original post states, [ROOT REQUIRED]. However, I'll share some of my notes with you.
I noticed busybox wasn't installed on my device. You may want to look into it.
When I installed it, it didn't have the required permissions, and I couldn't manual change the permissions in the terminal app (not linked). After running the the correct .bat file, I didn't not have anymore boot loops. In fact, I'm able to load FM(foldermount) & Link2sd without issue. My original post works for me, and I'd thought I'd share. That is all. GL
By this way, foldermount also works too. Thank you
FYI, I found that running both link2sd and FM at boot could cause a mount conflict. Example, my sdext2 wasn't showing up in es manager and it affected my apps.
Sent from my C5502
this is the cmd prompt i get... it doesnt show positive results no matter what and i even gave root permissions to the command. any solutions?
I'm going to ask a ton of Qs that may or may not help you. I know I would want someone to help me out. Please thank if successful and a little more detail too.
1. You rooted .310, and did not upgrade OTA to .244 to obtain root, even after downgrading?
2. You have SuperSU or SuperUser installed on your phone?
3. You intalled busybox?
4. You ran the .bat file with busybox installed?
5. What happened? (reboot or bootloop)
6. You installed Link2SD and followed the universal Link2SD steps? (please find a guide if not)
7. What happened? (reboot or bootloop)
I don't know what "everything" is, so I had to ask and I hope it helps you and or anyone else out.....
Sent from my C5502
mobifi said:
I'm going to ask a ton of Qs that may or may not help you. I know I would want someone to help me out. Please thank if successful and a little more detail too.
1. You rooted .310, and did not upgrade OTA to .244 to obtain root, even after downgrading?
2. You have SuperSU or SuperUser installed on your phone?
3. You intalled busybox?
4. You ran the .bat file with busybox installed?
5. What happened? (reboot or bootloop)
6. You installed Link2SD and followed the universal Link2SD steps? (please find a guide if not)
7. What happened? (reboot or bootloop)
I don't know what "everything" is, so I had to ask and I hope it helps you and or anyone else out.....
Sent from my C5502
Click to expand...
Click to collapse
ok now im goona explain wt things i did and try to ans all ur questions..
1)i rooted .310 and then flashed .244 except system option and isntalled pre rooted .244 system to get the root permissions
2)i have supersu installed
3)installed busybox and given proper root permissions
4)yes i ran the bat file after busybox installed
5)bootloop
6)yes i followed all the necessary steps for link2sd including partition and setting primary for both and also tried fat32 and ext2 formats but suffers bootloop anyway
i didnt know about the busybox until u asked me the Qs but no use its still bootlooping....im going to try a ota update if available in india (i dont think they have it yet) if not then this process probably would never work for me...if u can please try to do this link2sd procedure after u have root excess using this method http://forum.xda-developers.com/showthread.php?t=2392865
and please upload a pic of cmd prompt showing successful results...i need to check something
I wouldn't be able to upload the .bat cmd prompt until the weekend at the soonest. But, I did include working screen shots of my firmware and link2sd. I think there's something important in the system only rom file... And that you probably need the OTA for this method to be successful too. There's a permission issue that needs to be resolved and I'm sure it'll work for people that haven't received the OTA. We just don't know the procedure yet.
Sent from my C5502
And FYI; I'd enjoy assisting you further by subjecting my ONLY device to your procedure if I had a spare device to work with, but unfortunately, I don't. And I don't believe anyone would fault me on this...
Sent from my C5502
another crazy thing i tried is that i flashed a global LTE stock rom and rooted it...but no OTA update available...only thing i can do is wait for an official OTA update in india..
There's a screen shot of this file /system/ect/vold.fstab and there's a line missing. If you're able to figure out how to express the missing line, then you may have a shot. I ran into boot loops. The file control the mounting instructions.
Sent from my C5502
Related
Q&A for [LB] The definitive root Remount-Reboot fix!
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
FolderMount
I flashed it, but after that I lost my root permission. After towelroot I have root permission again, but foldermount causes reboot again. How should I fix this issue?
towelrooted Xperia M - stock 4.3 build 15.4.A.1.9 - LB
Hi,
I have the Xperia Z1 compact with android 4.4.4 this work with device?
fenix2021 said:
Hi,
I have the Xperia Z1 compact with android 4.4.4 this work with device?
Click to expand...
Click to collapse
Try it yourself.
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!
Remount reboot problem for Experia LT30p
I rooted my Experia LT30p phone and installed PhilZ Touch Recovery according to the instructions at http://forum.xda-developers.com/showthread.php?t=2798411. Afterwards
I followed the instructions at http://forum.xda-developers.com/xperia-z/orig-development/lb-definitive-root-remount-reboot-fix-t2317432 and installed the BusyBox app by Robert Nediyakalaparambil, opened this app and selected "install (requires root)" (I am assuming that that is ment with update your busybox). After installing Link2SD the phone keeps rebooting. Only if I remove the SD card, the phone boots properly.
Waiting for device, connect usb cable
Like @asbesto "I am stuck at Waiting for device, connect usb cable" even after follow those steps that he did it in this guide...
I'm using Xperia SP C5303, Android 4.3 12.1.A.1.205 rooted (SuperSU) and already installed BusyBox
Any ideas ?
I try to root my Xperia M C1905, entered in instal in remountreboot fix, and it didn't find my device there. I enabled USB debugging. Thanks in advance. Just says waiting for device, connect USB cable now...
hi friend
i upgraded my sony xperia z2 to 4.4.4 and rooted
i installed your fix as i did this in 4.2.2
but after a week my phone start to reboot automatically this means this fix dosen't work on this version
dude i just working on my phone for a week to make it working with folder mount ,for noob like me it's hard to installing rooms and root them and again and again (
i just want to thank you for what u did for us ,
but can you make fix working on this version ?
about link2sd bootloop
Does it fix the bootloop that occured to me while creating second partitions for link2sd?i tried every possible methods for that but everytime my phone went on bootloop which could be eliminated by removing the sd card.
Can anyone help me??
I have an xperia m... Rooted via towelroot...i want to play nfs most wanted...
I installed "Folder Mount"... Pasted the game data in sdcard/android/data... Copied the folder
name in internal/android/data... But when i try to mount them via folder mount...and click on the pin...my phone reboots...everytime it happens with my xperia m...can anyone help me
out??
I am dying to play nfs most wanted... Help anyone...??
In post #281, chemcup had a problem with errors due to read-only file system, e.g.:
cp: can't create '/system/bin/killric.sh': Read-only file system
I had the same problem with an Xperia LT30. This is a factory unlocked version direct from Sony (but my BL is still locked).
I ran across a ticket mentioning that doing an "su" first allows remounting. See the note by Blister Bee.
https://jira.cyanogenmod.org/browse/CYAN-5908
Anyway, went into adb, did the su remount, and then ran the script and it worked!
Root Vanished.
Everytime when I run the program and apply Remount Reboot Fix, it breaks my root. What to do, I have Sony Xperia M, running 4.3 android.
[[Solved]] [[Guide]]How to apply remountrebootfix on locked boot loader.
I have seen many peoples facing the problem of reboot even after the remountrebootfix so I m posting this idea.
I have applied this method on my Sony Xperia M, and got a full root access. You may also try it manually...
Warning- I will not be responsible for any damage caused to your phone, you are doing it at your own.
1. Download towelroot apk by Geohot...
2. Open it and click make it rain. Now you will get Half root access.
3. Now download remountrebootfix flashable zip and extract it somewhere you remember on your sd card.
4. First of all you need busybox for this, I think you would have already installed the latest version of it previously.
5. Now go to system/bin in your phone's root and if you find ctrlaltdel and killric.sh then delete them. And paste new ctrlaltdel and killric.sh from the extracted folder. Now reboot your phone.
6. After that download latest version of foldermount from play store, and try to mount any folder, if it fails then it will show a message to fix the rom, fix it and then again reboot. Now Foldermount will work perfectly.
make changes undone
Hi NUT,
i just wondered if you could implement a feature to make the fix undone. This could be useful if i want to use the OTA update again that seems to need RIC service to run for verifying system.
The reason i asked is because i tried to unroot via SuperSU option "completely unroot", i removed the manually done SD fix and tried to install the OTA. It fails half of the installation because i think the RIC service is not up and running and therefore it recognize a system change.
...would be really cool though. Thanks NUT for your hard work. I'll appreciate it!
best regards
Soul Inferno
I f'ed up guys, it seems that after rooting I dont have access to edit data on my phone, it can boot and all, but I cant for example take pictures(says it doesn have space wich is not true), intall apps, etc. I dont know in what extents it affected because I can uninstall apps for example.
When I try to delete a file with a file explorer it says the access was denied. Nor I can copy files from my pc to the phone.
I have a XT1063 with lollipop 5.0.2 that I installed manually before and worked great.
I installed Super SU through TWRP 2.8.5.0 (maybe wasnt compatible with lollipop?) that have Super SU 2.4 built in (according to what i’ve read, maybe this version of Super SU isnt compatible?).
Anyway, after that I proceeded to install busybox with default configuration and later smscript, dont know if all this is relevant. I only was aware of the problem when I tried to download a script for smcript but couldnt save it to my phone.
So next I tried to unroot from super su configuration with no luck, only got to unroot after uninstalling busybox. (also uninstalled smscript if that matters).
I hope I gave enough data if you need more just ask, thanks!
fede011 said:
I f'ed up guys, it seems that after rooting I dont have access to edit data on my phone, it can boot and all, but I cant for example take pictures(says it doesn have space wich is not true), intall apps, etc. I dont know in what extents it affected because I can uninstall apps for example.
When I try to delete a file with a file explorer it says the access was denied. Nor I can copy files from my pc to the phone.
I have a XT1063 with lollipop 5.0.2 that I installed manually before and worked great.
I installed Super SU through TWRP 2.8.5.0 (maybe wasnt compatible with lollipop?) that have Super SU 2.4 built in (according to what i’ve read, maybe this version of Super SU isnt compatible?).
Anyway, after that I proceeded to install busybox with default configuration and later smscript, dont know if all this is relevant. I only was aware of the problem when I tried to download a script for smcript but couldnt save it to my phone.
So next I tried to unroot from super su configuration with no luck, only got to unroot after uninstalling busybox. (also uninstalled smscript if that matters).
I hope I gave enough data if you need more just ask, thanks!
Click to expand...
Click to collapse
I got the same problem here! pls HELP!
I also had the same problem on my XT1068
Just reboot the device and format the internal storage using TWRP 2.8.6.0 (Latest). Problem will be solved
sharkymyn said:
I also had the same problem on my XT1068
Just reboot the device and format the internal storage using TWRP 2.8.6.0 (Latest). Problem will be solved
Click to expand...
Click to collapse
It means that I have to clean install everything again? I dindt want to go to this point, but thanks!
Worked Well on All Lollipop Versions of ALE-L21
After many unsuccessful attempts, finally i found a solution, and it works like a charm...
First of All Download KINGROOT.apk
install it and run Kingroot... It will take some time to root your ALE-L21.
if unsuccessful, try again, it will surely work after retries... in my case it rooted my phone in third attempt.
After rooted successfully with Kingroot. then another step is to replace kingroot with SUPER SU, because Super SU works with all rooted apps, KINGROOT lack this feature.
I have made a small script to remove Chinese kinguser, all related files and folders, and install SuperSU.
This script will do all the work for you without using PC, just by terminal, first of all, thanks to chainfire for his SuperSU files.
Before starting :
Download and install Terminal emulator app.
Download and unzip "Replace_Kingroot_With_SuperSU.zip" file.
Steps :
Send the extracted folder "mrw" to the internal storage of your device and make sure that this folder contains 4 files
Open Terminal emulator and type :
Code:
su
Allow root permission
Type :
Code:
sh /sdcard/mrw/root.sh
It might display some error, at the end it will launch supersu or open supersu manually.
Update su binary normal, then reboot.
Done !
Now you can enjoy the power of root and Super Su...
Terminal Emulator for android
https://play.google.com/store/apps/...ore/apps/details?id=jackpal.androidterm&hl=en
Replace_Kingroot_With_SuperSU.zip
http://www.mediafire.com/download/x1efi7ev6nf3mvd/Replace_Kinguser_with_SuperSU-v2.0.zip
KingRoot.apk
http://androidmtk.com/download-kingroot-application
Thanks,
It works with me.
ALE-L21C185B130
--------
Hopefully soon we get simple way to unlock boot loader.
Huawei cloud application accounts for the unlock code is not on this phone log more than 14 days!
Happy to Hear this from you.
But can't works on the beta build marshmallow's.
dkonect said:
But can't works on the beta build marshmallow's.
Click to expand...
Click to collapse
Not Tested on Marshmallow.. that's why mentioned that it works on Lollipop..
Some errors on script start
Kingroot icon is still there and can't remove
com.kingroot.kinguser still active, if freezed supersu doesn't work anymore
ItalianWolf said:
Some errors on script start
Kingroot icon is still there and can't remove
com.kingroot.kinguser still active, if freezed supersu doesn't work anymore
Click to expand...
Click to collapse
You got error because you did not send mrw folder in main directory of sd card, you should send that folder to internal and external memory also to avoid any errors... update me when done...
saifkhan9187 said:
You got error because you did not send mrw folder in main directory of sd card, you should send that folder to internal and external memory also to avoid any errors... update me when done...
Click to expand...
Click to collapse
I'm following your instruction exactly, why not?
how can i blame you if i don't follow exactly what you wrote?
mrw was in root of sdcard, supersu and su binaries are working (if i don't freeze com.kinroot.kinguser) but what i wrote it's valid.
I launched again the script and after a lot of errors this time supersu asked me to reboot, first time didn't; now seems all kingroot trace are gone!
EDIT:
After testing i see that a lot of times supersu needs to be started manually to have the auth promp for an app, my english isn't so good, i'll write an example:
start (first time) an app that requires root
wait for auth prompt by supersu
wait a lot, so open supersu, then it shows the request for authorize
a second app started just after show immediatly the auth promp
When com.kingroot.kinguser was active the promp from supersu was everytime immediate.
Latest: kngroot unlocks bootloader
Is some chance this work in future on marshmallow ? thanks
Dear saifkhan9187,
How to update superSU?
I got failure message when SuperSU try updating.
Making this I still can get the OTA updates?
Is that ota still available?
Recently, about a month, I got the b188 update... Android 5.0.1
aab44 said:
Dear saifkhan9187,
How to update superSU?
I got failure message when SuperSU try updating.
Click to expand...
Click to collapse
Got the same error first time, reboot, launch again the script (you will see lot of errors this time file are already deleted no matter) then start supersu if not starts; this time doesn't fail.
@ItalianWolf how did you check for unlocked boot loader? Fastboot? Thanks!
@rHycH yes, reboot in fastboot mode and you can see in red that bootloader is unlocked
ItalianWolf said:
Got the same error first time, reboot, launch again the script (you will see lot of errors this time file are already deleted no matter) then start supersu if not starts; this time doesn't fail.
Click to expand...
Click to collapse
Thanks, its updated now.
--------
Waiting for simple way to unlock boot loader of ALE-L21
@aab44 bootloader is unlocked now, you can see in fastboot!
Please, is there any way to undo this and use kingroot again ??
or at least have an option to use an different busybox ??
since this have made Link2sd and foldermount unuseable for me
Many Thanks in advance
nibb-1 said:
Please, is there any way to undo this and use kingroot again ??
or at least have an option to use an different busybox ??
since this have made Link2sd and foldermount unuseable for me
Many Thanks in advance
Click to expand...
Click to collapse
Junst do full unroot from supersu and use again kingroot (install and root)
Hi I just rooted my Z1 using KingoRoot APK app and I installed Lucky Patcher to install Floating Fake Location as "system app". The thing is, I cannot uninstall Floating Fake Location afterwards using tools like Root Uninstaller Pro,KingoSuperUser etc. At first I thought it was Floating Fake Location issue but soon I realize I can't even uninstall other Sony bloatware such as Socialife, Xperia Lounge etc.
Please enlighten me why I can't uninstall system app even tho I am rooted.
P/S: it may have something to do with my root (partial? as I didn't unlock my bootloader), as I can't even mount r/w using root explorer or any other app that can mount r/w on /system.
Steven90 said:
Hi I just rooted my Z1 using KingoRoot APK app and I installed Lucky Patcher to install Floating Fake Location as "system app". The thing is, I cannot uninstall Floating Fake Location afterwards using tools like Root Uninstaller Pro,KingoSuperUser etc. At first I thought it was Floating Fake Location issue but soon I realize I can't even uninstall other Sony bloatware such as Socialife, Xperia Lounge etc.
Please enlighten me why I can't uninstall system app even tho I am rooted.
P/S: it may have something to do with my root (partial? as I didn't unlock my bootloader), as I can't even mount r/w using root explorer or any other app that can mount r/w on /system.
Click to expand...
Click to collapse
You also need to instal Supersu, which is an interface for granting root. Then you will be able to delete system apps.
optimumpro said:
You also need to instal Supersu, which is an interface for granting root. Then you will be able to delete system apps.
Click to expand...
Click to collapse
I am using Kingo SuperUser to grant the apps root permission. Had some trouble replacing Kingo SuperUser with Chainfire SuperUser but I figured Kingo should've done the trick as well. When I mount Kingo did prompt me for permission and I allowed it, somehow I think the root is incomplete ?
Steven90 said:
Hi I just rooted my Z1 using KingoRoot APK app and I installed Lucky Patcher to install Floating Fake Location as "system app". The thing is, I cannot uninstall Floating Fake Location afterwards using tools like Root Uninstaller Pro,KingoSuperUser etc.
...
...
somehow I think the root is incomplete ?
Click to expand...
Click to collapse
Does your device have recovery installed? You can delete system apps through it: mount /system through XZ Dual Recovery's TWRP and delete the folder with the app's apk inside. You could also try flashing a SuperSU zip this way to fix root, but make sure you don't use the systemless version.
I suggest you next time don't use kingroot or any one-click root: though uncomplicated, they're notorious for being untrustful, leaking private IMEI information to unknown servers, and unreliable. Read THIS thread thoroughly, re-root using the method in the 2nd post, and upgrade to 5.1.1, or get a pre-rooted FTF through XperiFirm.
kentexcitebot said:
Does your device have recovery installed? You can delete system apps through it: mount /system through XZ Dual Recovery's TWRP and delete the folder with the app's apk inside. You could also try flashing a SuperSU zip this way to fix root, but make sure you don't use the systemless version.
I suggest you next time don't use kingroot or any one-click root: though uncomplicated, they're notorious for being untrustful, leaking private IMEI information to unknown servers, and unreliable. Read THIS thread thoroughly, re-root using the method in the 2nd post, and upgrade to 5.1.1, or get a pre-rooted FTF through XperiFirm.
Click to expand...
Click to collapse
No I haven't installed any custom recovery.
Cause I am already using 5.1.1 so I figured Kingo Root is the easiest way to go, didn't know it will cause so much trouble. So basically I need to unroot then root again using the "proper" method? I am already on 5.1.1 btw.
Steven90 said:
No I haven't installed any custom recovery.
Cause I am already using 5.1.1 so I figured Kingo Root is the easiest way to go, didn't know it will cause so much trouble. So basically I need to unroot then root again using the "proper" method? I am already on 5.1.1 btw.
Click to expand...
Click to collapse
The fact that you can't install Supersu and get root indicates that your phone is not fully rooted. I bet you wouldn't be able to install recovery either for the same reason...
Do the classic rooting, install TWRP and then flash any pre-rooted stock rom you want...
optimumpro said:
The fact that you can't install Supersu and get root indicates that your phone is not fully rooted. I bet you wouldn't be able to install recovery either for the same reason...
Do the classic rooting, install TWRP and then flash any pre-rooted stock rom you want...
Click to expand...
Click to collapse
I suspect I am not fully rooted as well. Can you point me a direction towards "classic" rooting my my Z1 5.1.1 ? Almost every post I went points me back to one-click-root solution.
I have the same problem, it's because we can't remount /system to rw ("operation not permitted"), so the update to SU isn't working as well, tried several different methods with terminal emulator but without any luck. Neither will total commander help in this situation. I'm begining to lose hope
Steven90 said:
I suspect I am not fully rooted as well. Can you point me a direction towards "classic" rooting my my Z1 5.1.1 ? Almost every post I went points me back to one-click-root solution.
Click to expand...
Click to collapse
Ulvgrim said:
I have the same problem, it's because we can't remount /system to rw ("operation not permitted"), so the update to SU isn't working as well, tried several different methods with terminal emulator but without any luck. Neither will total commander help in this situation. I'm begining to lose hope
Click to expand...
Click to collapse
Try this, it's almost a one-click tool
http://forum.xda-developers.com/showthread.php?t=2784900
Exploit maybe works with 5.1.1, but if not, downgrade your firmware to 5.0.2, use Easyroot to exploit, then upgrade back.
The "classic" root I was referring to requires downgrading from Sony's Lollipop/Kitkat FW to Jellybean due to Sony patching the exploits in the newer FW used for rooting. The steps are outdated now and is replaced by Easyroot. http://forum.xda-developers.com/showthread.php?t=2688933
Could someone please point me at instructions on how to root LN14.
I've searched the HD/HD+ forums for 'root LN14' and 'rooting LN14' and got no results (which by itself is suspicious).
have you enabled Developer Options?
I, for one, had no luck with either SuperSu or addon su. The first would put the HD+ into a permanent boot loop necessitating a re-install from scratch,and the latter would install but the unit still indicated it was not rooted. Doing the Dev Op made no difference. A real mystery!
harryzee said:
I, for one, had no luck with either SuperSu or addon su. The first would put the HD+ into a permanent boot loop necessitating a re-install from scratch,and the latter would install but the unit still indicated it was not rooted. Doing the Dev Op made no difference. A real mystery!
Click to expand...
Click to collapse
The file addonsu-14.1-arm.zip in the main folder is the one to use. As I seem to recall, you might have to enable, disable, then re-enable, in order for root access to take effect.
digixmax said:
The file addonsu-14.1-arm.zip in the main folder is the one to use. As I seem to recall, you might have to enable, disable, then re-enable, in order for root access to take effect.
Click to expand...
Click to collapse
That is the one I flashed using 3.0.1.0 TWRP. Not clear on your second sentence: "...enable, disable,, then re-enable...". Forgive me for being lost as to what you physically/specifically mean. Please explain.
Thanks.
harryzee said:
That is the one I flashed using 3.0.1.0 TWRP. Not clear on your second sentence: "...enable, disable,, then re-enable...". Forgive me for being lost as to what you physically/specifically mean. Please explain.
Thanks.
Click to expand...
Click to collapse
I meant "enable, disable,, then re-enable" the root access option in "Developer Options".
Aha! Will give it a go. Thanks.
5/2/2018:
Okay: I d/l three android root checkers and titanium backup. The first root checker (Clivin Inc. with small green android robot graphic) told me I was not rooted both before following your above instructions and after. The other two (d/l after following the above) both say I am rooted. However, I was not and am still not able to get "TB" to run. It says "failed" and that I am not rooted.
Since the HD+ is running really well now in its stripped down mode, I can "leave well enough alone" or try to get "TB" working so I can remove anything not needed for my chosen minimal functionality (ereader, viewing videos, photo review/minor editing) that would further reduce unnecessary battery drain.
Thanks again for the above clarification and any additional thoughts.
I am having this same problem
- Root options *do* appear in my Developer settings, but no amount of toggling on/off/on seems to enable root
- I have flashed the Lineage SU addon, log shows successful in TWRP but no change after boot
- SuperSU from Play Store says "SU Binary occupied"
- Adaway says "Rooted Android required- Either the su binary could not be found or you did not allow root permission for Adaway" ie I believe I am indeed *not* rooted.
- SuperSU flashable zip is a broken link on their website.... http://www.supersu.com/download
Out of ideas here, anyone got anything else I can try?
Edit: I was able to obtain Root properly by flashing Magisk & installing the Magisk Manager APK from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
You got it. Use Magisk. Works wonders and way better than SuperSU or any other root permission tool I've came across. It's even akin to, and even has within it, xposed and other magical rooted modules for you to try out for a day or two and then decide you don't need it.
pchc_lx said:
I am having this same problem
- Root options *do* appear in my Developer settings, but no amount of toggling on/off/on seems to enable root
- I have flashed the Lineage SU addon, log shows successful in TWRP but no change after boot
- SuperSU from Play Store says "SU Binary occupied"
- Adaway says "Rooted Android required- Either the su binary could not be found or you did not allow root permission for Adaway" ie I believe I am indeed *not* rooted.
- SuperSU flashable zip is a broken link on their website.... http://www.supersu.com/download
Out of ideas here, anyone got anything else I can try?
Edit: I was able to obtain Root properly by flashing Magisk & installing the Magisk Manager APK from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse