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
With all major changes to SuperSU, there are updates to both the GUI and binary. The GUI is the part you see on screen, the binary is what allows other apps to actually acquire root access. The first time you open SuperSU after such an update, it will attempt to update the binary to the latest version.
There are a lot of components to the binary and it needs to be set up just right for everything to work. This is a complex operation, and sometimes it fails. SuperSU is used by dozens of millions of users across hundreds of different devices, running even more different firmware revisions - any change always has the potential to break something somewhere.
SuperSU offers multiple ways of installation: in-app 'normal', in-app TWRP/CWM, and ZIP via TWRP/CWM. These all have their own strengths and weaknesses, so if one doesn't work, try the others if available.
If you are reporting an update failure, you should include at least the following information. Some information requires some skill with adb to retrieve.
- Exact device model
This includes the brand, the model, and the carrier variant (if applicable: mostly USA, Korea, China)
- Exact firmware version
Which exact firmware are you using? If you are using a custom firmware, please include a link to the download for this firmware. If on top of that, you are also using a custom kernel, please include a link to the download for that as well.
- Exact Android version
Android x.y
- Exact SuperSU version
Which version were you running, and to which version are you updating? If using Pro, do you have OTA survival mode enabled?
- Interfering apps
There are some apps that can interfere with SuperSU installation, primarily:
- other Superusery apps
- Xposed
- BusyBox (symlinked or non-symlinked)
Include in your report if you have one or more of these installed.
- Update methods tried
In-app 'normal', in-app via recovery, and ZIP via recovery. If you used one of the recovery options, please include exactly which version of which recovery you are using, and if it's not an official build (so a TWRP not from the TeamWin website, a CWM not from CWM's site, etc) a link to where you got it from.
Note that if you let TWRP or CWM "fix" root for you, or let them disable the firmware from flashing a new recovery (sometimes you are asked this), you have broken root, and the only way to recover it is flashing the full ZIP through recovery.
- What kind of root are you left with?
After a failed binary update, multiple outcomes are possible:
- Root is lost. Apps cannot get root anymore, you cannot get root using "su" from an adb shell, etc
- Root seems to mostly still work. Most apps still work, and/or "su" still works from an adb shell
- Nothing seems to have changed at all, even the GUI still shows the old version number
Report what state your device is in now. Note that you can get the version of the main "su" binary by running "su -v" from a terminal emulator or adb shell.
- Logs from TWRP, when updating the binary using the TWRP/CWM button inside the SuperSU app
After pressing the TWRP/CWM button, the device should reboot into TWRP, do it's thing for a few seconds, then reboot into Android. If SuperSU still complains about the binary, please retrieve the TWRP log file. You can retrieve it via adb pull /cache/recovery/last_log, which should produce the last_log file in your current directory. You still need at least partial root from booted Android to retrieve this log. Sadly it is wiped and replaced with a new file when you boot into recovery a second time, so you cannot retrieve it that way. Note that this log will always contain a number of errors, as the installer tries several things in several ways, that work differently on different firmwares. Attach this log file.
- Logs from TWRP, when updating SuperSU completely via ZIP
If after you boot back into Android, SuperSU is not working right or still asks for updated binaries, reboot back into TWRP, install the ZIP again. After the ZIP is installed, you can retrieve the log file via adb pull /tmp/recovery.log, which should produce the recovery.log file in your current directory. Attach this log file.
- Logs from SuperSU (very important)
If SuperSU keeps asking you to update the binaries after trying any which way and failing, please post the detection log. After updating has failed, don't reboot, but produce detection information via adb logcat -d | find /i "installer" > logcat.txt (Windows, use 'grep -i' instead of 'find /i' on Linux or OSX), which should produce a logcat.txt file in your current directory with several lines mentioning SuperSU. Attach this log file.
- Various logs (very important)
Some additional handy information can be gotten by via some adb shell calls. If you that working, copy/pasting the following commands should produce a nice sulog.txt file in your current directory, which you should attach to your post:
(as always with copy/pasting, make sure you press enter a few times afterwards to make sure the last line was flushed)
Code:
adb shell getprop > sulog.txt
adb shell set >> sulog.txt
adb shell toolbox id >> sulog.txt
adb shell busybox >> sulog.txt
adb shell su -v >> sulog.txt
adb shell su -V >> sulog.txt
adb shell su -h >> sulog.txt
adb shell su --self-test >> sulog.txt
adb shell ls -l /system/xbin/*su* >> sulog.txt
adb shell ls -lZ /system/xbin/*su* >> sulog.txt
adb shell ls -lZ /system/bin/toolbox >> sulog.txt
adb shell ls -l /system/bin >> sulog.txt
adb shell ls -l /system/xbin >> sulog.txt
adb shell ls -laR /su >> sulog.txt
adb shell ps >> sulog.txt
In closing
All this information will help diagnose the problem, and potentially help fix the issue if there is something wrong with SuperSU itself (which is not unheard of). The more information you provide, the better you can be helped. Still, be aware that often it takes a while to get a problem sorted. Even when a lot of people are having the same problem (and many problems may look the same but deep down are separate issues), it is rare to find a user who actively wants to help fix the issue. Most users will only complain but then don't really assist in solving the issue. If you can be someone who can actively help, and by that I mean being responsive to questions, being available for a live debugging session, etc, you are a rare gem indeed, and your assistance will be greatly appreciated.
If you are writing multiple posts, it is always helpful if you keep linking back to your original post with the report. Saves me time.
Sorry for the inconvenience!
SGH-T999
4.3
2.06 can update to 2.14 but binary update never takes
BusyBox but dont know what kind
In-app 'normal', in-app via recovery, and ZIP via recovery after that binary update still fails normal and via TWRP v2.8.0.1
Still have root
Update has make my Galaxy S5 is unusable...
After update I am unable to open any Google based apps, Gmail, maps, YouTube, etc. I get an error that says "Unfortunately, [app] has stopped.". Im also getting the "Unfortunately, the process com.google.process.gapps has stopped" error. What do I need to do? I did a factory reset hoping thats would fix the problem but it hasn't. It seems as thought it's not reading my SD card as well. It's showing I don't have pic or that one is even installed. I can make calls but that's about it. No Internet, no connections, no apps. Can't even sign onto my gmail to be able to download any app from the play store. I am out of town & without a computer until later tonight. Would re rooting fix my problem? I do not have recovery flashed onto my phone. It wasn't available when I rooted & I never got around to doing it. Pleasant Help! I have a titanium back up of my 0hone but can't download the application to try that avenue.
shadow322 said:
SGH-T999
4.3
2.06 can update to 2.14 but binary update never takes
BusyBox but dont know what kind
In-app 'normal', in-app via recovery, and ZIP via recovery after that binary update still fails normal and via TWRP v2.8.0.1
Still have root
Click to expand...
Click to collapse
As stated on IRC, I'm going to need the logs described above.
Emmie0702 said:
After update I am unable to open any Google based apps, Gmail, maps, YouTube, etc. I get an error that says "Unfortunately, [app] has stopped.". Im also getting the "Unfortunately, the process com.google.process.gapps has stopped" error. What do I need to do? I did a factory reset hoping thats would fix the problem but it hasn't. It seems as thought it's not reading my SD card as well. It's showing I don't have pic or that one is even installed. I can make calls but that's about it. No Internet, no connections, no apps. Can't even sign onto my gmail to be able to download any app from the play store. I am out of town & without a computer until later tonight. Would re rooting fix my problem? I do not have recovery flashed onto my phone. It wasn't available when I rooted & I never got around to doing it. Pleasant Help! I have a titanium back up of my 0hone but can't download the application to try that avenue.
Click to expand...
Click to collapse
Sounds unlikely to be due to SuperSU. Either way, there's nothing you can really do about it now. Situations like these I advise a factory reset and a data restore.
Chainfire said:
Sounds unlikely to be due to SuperSU. Either way, there's nothing you can really do about it now. Situations like these I advise a factory reset and a data restore.
Click to expand...
Click to collapse
I've done a factory reset & stoll have the same problem. How would I restore data?
Emmie0702 said:
I've done a factory reset & stoll have the same problem. How would I restore data?
Click to expand...
Click to collapse
You would restore the data from a backup you've made before resetting ?
In SuperSU you can try 'full unroot' from Settings (twice if necessary) and unroot, see if that resolves the slowness/crashing.
The only backup I have is a titanium backup. I can't get anything to download from the play store. I never flashes recovery because it wasn't available when I rooted. I never went back to add it (which I could kick myself for right now). Would re rooting help? Supersu isn't on my phone anymore either. I'm not sure what happened to that.
Edit: could the platform.xml under /etc/permissions/platform.x ml have anything to do with it?
Knox
Emmie0702 said:
After update I am unable to open any Google based apps, Gmail, maps, YouTube, etc. I get an error that says "Unfortunately, [app] has stopped.". Im also getting the "Unfortunately, the process com.google.process.gapps has stopped" error. What do I need to do? I did a factory reset hoping thats would fix the problem but it hasn't. It seems as thought it's not reading my SD card as well. It's showing I don't have pic or that one is even installed. I can make calls but that's about it. No Internet, no connections, no apps. Can't even sign onto my gmail to be able to download any app from the play store. I am out of town & without a computer until later tonight. Would re rooting fix my problem? I do not have recovery flashed onto my phone. It wasn't available when I rooted & I never got around to doing it. Pleasant Help! I have a titanium back up of my 0hone but can't download the application to try that avenue.
Click to expand...
Click to collapse
@Emmie0702 I think it's a weird Knox Action -i mean, It MAY happen 'coz Knox
Chainfire said:
Note that if you let CWM "fix" root for you (sometimes you are asked this), you have broken root, and the only way to recover it is flashing the full ZIP through recovery.
Click to expand...
Click to collapse
CWM is asking for that. I have to answer Yes or No. So I should click No ?
sorry wrong thread
Samsung N7100 Hong Kong (rom is UK)
N7100XXUFND3
4.4.2
2.14 pro
Don't have OTA survival mode enabled.
Before updating the SU, I can use the SU as usual. But after updating the SU binary via normal, it says I didn't install the execute file ( something like that, since I'm using Chinese), which means i haven't root.
So, do i need to re-root, then update the SU binary?
p220fhf said:
Samsung N7100 Hong Kong (rom is UK)
N7100XXUFND3
4.4.2
2.14 pro
Don't have OTA survival mode enabled.
Before updating the SU, I can use the SU as usual. But after updating the SU binary via normal, it says I didn't install the execute file ( something like that, since I'm using Chinese), which means i haven't root.
So, do i need to re-root, then update the SU binary?
Click to expand...
Click to collapse
You can give it a shot, rerooting via the ZIP ( http://download.chainfire.eu/supersu ) with TWRP. See if that helps, and let us know. If it doesn't fix the issue, I will find this firmware and flash it on my own N7100 (if possible) and see if I can replicate the issue.
SuperSU Problem!
I've rooted my device (GT-1335 - Android 4.4) with Windershare Rooting Toolkit, After rooting I've installed Root checker basic from the market and run it. It says your device is rooted. But when i wanted to go to root using FX explorer, it says you need permission from Advance user. When i click SuperSU after that it says that "There is no Su binary installed, and SuperSu cannot install it. This is a problem!", After that i checked whether my device is rooted or not with Root checker basic, but now its says that my device isn't rooted!
Please Help, and replay soon!
Note: My device isn't original samsung model!
super su still loading
After update super su in playstore my s4 octacore in app tab on supersu still loading but nothing happened...
I had problems with using Stock 4.4.4 on my i9305.
Was freezing/not opening, then when it did it wouldn't update.
So I went to the SuperSu site and downloaded the latest to instal via CWM.
Now working fine. Hope this helps someone.
Chainfire said:
You can give it a shot, rerooting via the ZIP with TWRP. See if that helps, and let us know. If it doesn't fix the issue, I will find this firmware and flash it on my own N7100 (if possible) and see if I can replicate the issue.
Click to expand...
Click to collapse
I tried to reroot on my s4, but nothing changes, when updating the SU to 2.14.
So, I think, maybe, the main problem is SU 2.14 on 4.4.2 and 4.3.
My s4 was 4.3 rooted, before the SU update, everything was fine. But after updating, the SU app said I didn't root. Then I updated my FW to 4.4.2(I9505ZHUFNB3), and used CF-root to root. Still ok, but when the SU updated to 2.14, thing happened again. (Now my s4 is temp unroot for playing game , but can't root again as it says "You didn't root")
Sorry for my bad English.
SuperSU 2.14 not working on s4 4.3
gokunjp said:
After update super su in playstore my s4 octacore in app tab on supersu still loading but nothing happened...
Click to expand...
Click to collapse
same problem here on my S4-quad-16G with samsung 4.3-stock, which was rooted mothns ago via AutoROOT+twrp2.7.01
p220fhf said:
I tried to reroot on my s4, but nothing changes, when updating the SU to 2.14.
So, I think, maybe, the main problem is SU 2.14 on 4.4.2 and 4.3.
My s4 was 4.3 rooted, before the SU update, everything was fine. But after updating, the SU app said I didn't root. Then I updated my FW to 4.4.2(I9505ZHUFNB3), and used CF-root to root. Still ok, but when the SU updated to 2.14, thing happened again. (Now my s4 is temp unroot for playing game , but can't root again as it says "You didn't root")
Sorry for my bad English.
Click to expand...
Click to collapse
same here update 2.14 from PlayStore f.cked-up the SuperSU app (i have waiting-donut on APPS and LOGS-tabs...)
Device stays rooted, and root-requests from other apps seems to work too, because there is a typical SuperSU-reuqest popup there....
So please fix the APP for Samsung 4.3 4.4 firmwares...
Versions 2.01+2.06 worked flawlessly.
what i have already tryed:
1) On the [Settings]-TAB: => UNINSTALL APP: Effect 'uninstalling...'-popup stays 4ever w/o effect
2) On the [Settings]-TAB: => UNINSTALL APP for a NEW SuperUserApp: Effect 'uninstalling...'-popup stays 4ever w/o effect
3) Booted into TWRP => INSTALL the SuperSU-2.14.ZIP, rebooting phone -> in SuperSU (the same waiting donuts on APPS/LOGS...)
Phone: i9505-OpenEUROPE quad-core/16G Samsung-stock-FW 4.3
Device I9505
Android Version: Stock 4.3 MKF
BusyBox v1.22.1
Wanam Xposed installed
Stock Recovery
Kingo Root
Google Play Update
Issue: After update from 2.13 to the latest 2.14 when supersu try to reinstall it stuck more than 5 minutes, I reboot my phone, reopen supersu but now in my "APPS" and "LOGS" I have some kind of neverending loop load, I can't manage to see my rooted apps there, and in my SETTINGS if I try to make some changes it stuck and need phone reboot, otherwise all my rooted apps work fine!
Chainfire said:
You can give it a shot, rerooting via the ZIP with TWRP. See if that helps, and let us know. If it doesn't fix the issue, I will find this firmware and flash it on my own N7100 (if possible) and see if I can replicate the issue.
Click to expand...
Click to collapse
I think i figure out the problem, is the SU bin update. My note 2 is rooted and is using SU 2.14 pro, but i don't update the bin. It works fine, but when opening the su app, it asks you to update the bin.
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 all!
I might be asking a stupid question, so forgive me if I do.
The situation is the following... I have a TVBOX Q96 HOME 4K (cheap Chinese one based on RK3229) that is pre-rooted. All applications using root work fine. However, there is no "superuser" manager installed on it in order to disallow certain apps to gain root access. In the past I already had a similar situation with some other box and when I installed SuperSU apk the device hasn't boot anymore. I that case I got a stock firmware and could unbrick it, but now I can't find any ROM for this device in order to play with it.
So, the question is... is it possible to install Magisk Manager in order to manage access to the built-in su? Older version I tried correctly identify the device as rooted (with SuperSU 2.76), but do not offer me a Superuser menu where I could manage access to the su of the apps. Neither I get a prompt when an app is requesting access to su.
Any solution to my problem?
No, you will not be able to use the Magisk Manager to manage superuser access for SuperSU.
Any idea what might cause the device to not boot anymore after installing SuperSU.apk?
I compared the installed su binary with the one from chainfire's UPDATE-SuperSU-v2.76-20160630161323.zip (arm7), and they are identical. What does installing an apk alone to the system beside managing the access for the apps?
I have to admit I don't know exactly what happens "behind the scene".
I have absolutely no idea why installing the SuperSU apk would cause your device not to boot... Sorry.
Edit: Wait... You write "installing an apk alone to the system". You're not installing it as a regular app, but to the /system partition? If so, that's what might be causing issues.
Sorry to mislead you... I wrongly expressed myself.
I'm not installing it as a system app - I have installed it (on previous box) as an ordinary user app and as I said the system couldn't boot anymore afterwards (I had to reflash the ROM to unbrick it).
BTW... this is a known issue with these Chinese TVBOXes. There are couple of posts also here in XDA about it and nobody knows AFAIK what is the root cause.