Data recovery app doesn't recognize Root (Samsung Note 5) Please Help! - Magisk

Hello everyone,
I am facing an issue and will be eternally grateful if someone helped me with it. I recently lost some very important audio recordings from my phone. These are very important and I want to run a data recovery tool to help retrieve them but all such tools require root access. I then rooted my phone using magisk and checked the status via those root check apps and they show the status as rooted. However, the problem is that none of the data recovery tools recognize the root and hence cannot run a scan. Perhaps I am overlooking something here. Model of my phone is SM-N920I. I flashed the magisk via twrp and have also installed the Magisk manager. Everything is up to date. Again, when I check the root status of my phone via the app "Root checker basic" it says "Root access is properly installed". Also, when I am using the data recovery tool i.e. Fonelab my phone does not prompt me for root access. Nothing is shown on the screen.
I am sorry if this thread is in the wrong section. Mods can feel free to move it or notify me. Thanks

If other root apps are functioning properly it's an issue with the app you're trying to use. You should contact the developers of the apps in question...

Related

[Q] How can I check that my HTC One is rooted?

Context: I recently bought a new car (VW Golf 2009 mark 6) and I want to connect my HTC One via bluetooth, but the bluetooth module in the car says phone not compatible.
I found that the BT module in my car wouldn't work with stock phone, but that I could install RSAP for Android if I rooted my phone.
I unlocked my bootloader using the instructions on the root section for the HTC One on here
I then progressed to trying to root my phone after watching the subsequent vid
I have flashed the device with both TWRP and Clockwork Mod
I have Super User installed, does that not mean I'm rooted?
When I use root checker basic, it just says "Sorry! This device does not have proper root access." Any ideas why I'm blocked at this point?
It also seems to mean I can't install the rsap for android.
The same happens when I use Clockwork Mod, I have installed super user, but I still can't install rsap. The error message when I try to do so says:
Installation failed. sync mount -o rw,remount -t ext4/dev/block/mmcblk0p35/system failed/system/bin/su[1]: syntax error:'('unexpected
Any help greatly appreciated!
Thanks in advance
try a different app that needs root access eg titanium backup, goomanager or rom manager. if neither works you probably did something wrong by rooting. also check your super user or supersu app in drawer
there is an app, root checker (https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en) try that.
Prash8429 said:
there is an app, root checker, try that.
Click to expand...
Click to collapse
Hi Prash,
I have already tried that app, root checker basic, it just says "Sorry! This device does not have proper root access."
Any ideas why I'm blocked at this point?
Thanks

Can't even install XPosed (Flashfire Issue?)

So I got around to "rooting" my "LG G4" (H525) via that one click tool called Kingroot.
So far so fine.
Pretty much all applications that require root will will allow it...
Except for one:
FlashFire....
It keeps telling me that root access was not possible,
that I shall't install SuperSU.
[However SuperSU will error out right on the start telling me to `update the binary']
=> What binary ? Why update it (just got the newest SuperSU from the Playstore)?
Trying to flash said binary using any Flashify merly showed me the lovely "your device is bricked" bugdroid...
Any idead from someone with similar FlashFire / SuperSU problems ?
Thanks in advance:
-Rye-
Do you have a custom recovery/twrp?
Sent from my HTC One M9 using Tapatalk
Nope, all stock.
(Part of the reason why this confuses me so much... I changed nothing... except for Root)
KingRoot is intentionally designed to serve two purposes. The first is to give you root access through their app. The second, which they don't warn you about, is to prevent you from managing that root access any other way than through their app.
They have written their app specifically to force you to use their root manager and to prevent you from uninstalling it and installing any other SU app. They went so far as to specifically block installation of SuperSU because they're upset that it replaces their app (which is blatantly absurd and hypocritical). If that's acceptable to you, then certainly do it their way.
However, because they place such restriction on root access (which seems to be a self-contradictory philosophy) then it directly interferes with the installation of more powerful root apps like flashing utilities and Xposed itself.
At this point there are two options. Either you can find a utility that breaks their stranglehold on your device and follow the specific instructions to remove their app and install something that's not restrictive, or you can restore your device to pre-root condition and root it again yourself using the open, non-restrictive methods made available to the community. Each method may be about as complicated as the other.

Magisk PC Debug usb App problem

Hello to all,
by mistake I deleted the camera folder and I'm trying to recover lost photos. I have an LG G3 with fulmics rom + Magisk.
I found some free recovery suites (like free android data recovery), but they tell me they can not get root permissions. I activated USB debugging and then the root permission request should appear, but it does not show up and it does not go. With another program the request appears to me, I grant it to him but the program always tells me that he could not get root permisisons. How can I do?
I would like to avoid installing an app on the cell because it would overwrite some data and maybe I compromise the recovery of the photos ...
If you know any other free app that works you make me happy!

Rooting LN14????

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

Magisk Manager with built-in su

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.

Categories

Resources