Database Develop

A: 10.3.1.A.0.244 Working Link2SD [ROOT REQUIRED]

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

[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.

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

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...

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.