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

Uninstall as system app

The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?

DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
Sorry as I don't have a solution for your problem....
But still as far as I know Super user 2.46 is not fully compatible with android 5 & above.
On other hand I would suggest you to give a try to super user 2.49 beta which is the latest but still under development.
Hope you find this useful.
ayushbpl10

DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
If you want to make SuperSU a user app:
If SuperSU was "updated" by the Play Store (ie there's an eu.chainfire.supersu-*.apk in /data/app), then delete /system/app/SuperSU.apk and reboot. If it's flashed *and* the afore mentioned apk is *not* in /data/app, then move /system/app/SuperSU.apk to /data/app and reboot.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9

Sent from my Aqua i5 mini using xda-developers.com, powered by appyet.com

DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
If all you wanted to do was make it a user app, reroot, open supersu, go to cleanup and choose for reinstallation. After choosing that, if it says to reboot then press it again, do so, else reboot and install supersu from play. Done, supersu as a user app

mmonaghan34 said:
If all you wanted to do was make it a user app, reroot, open supersu, go to cleanup and choose for reinstallation. After choosing that, if it says to reboot then press it again, do so, else reboot and install supersu from play. Done, supersu as a user app
Click to expand...
Click to collapse
That doesn't work (v2.46 on LG G3 running v5.0.1). It loops trying to uninstall. After a couple minutes, I forced a reboot. SuperSU was still there, and as a system app.
Edit: The same thing happens when I tell SuperSU to completely unroot the LG G3. Since I needed to unroot in order to apply an LG/Verizon OTA update, I used LG's Flash Tool to replace the system partition (THAT removed SuperSU!), and then the OTA update was successful.
Since LG now supplies an on-phone backup/restore tool for the G3 as part of the Settings menu, I no longer need to run Titanium Backup, which means I no longer need root. Given the nuisance issues with rooting/unrooting/system updating/etc, I've decided to remain unrooted on the LG G3 for the time being. Quite a change for me, since this is the first Android device in well over a dozen for which I've made this decision.

kingroot to supersu switching problem

So recently i rooted my Xperia z1 using kingroot and it went smoothly i got root access,then i tried to switch it to supersu and it didnt work,i have used terminal emulator to run the shell file,the method in which you place mrw folder in phone memory,but it just uninstalls the kingroot and installs the supersu,it didnt upate the root app,so supersu doesn't update its binary,i have tried multiple times and i cant do it manually because i camt mount /system to r/w what can i do? Any help please i am so frustrated with this kingroot app.

Hamzashujah said:
So recently i rooted my Xperia z1 using kingroot and it went smoothly i got root access,then i tried to switch it to supersu and it didnt work,i have used terminal emulator to run the shell file,the method in which you place mrw folder in phone memory,but it just uninstalls the kingroot and installs the supersu,it didnt upate the root app,so supersu doesn't update its binary,i have tried multiple times and i cant do it manually because i camt mount /system to r/w what can i do? Any help please i am so frustrated with this kingroot app.
Click to expand...
Click to collapse
First and foremost: Do NOT use Kingroot. There are many threads that explain why Kingroot is shady:
http://androidforums.com/threads/kingroot-safe-to-use.923983/
https://www.reddit.com/r/Android/comments/3vmspw/thoughts_regarding_kingroot/
http://forum.xda-developers.com/showthread.php?t=2604749
Yes, I know there's guides that recommends users to use KingRoot. But unless you want to send private IMEI to China or leak information to the world, just don't use it.
Second, use THIS guide to obtain root.
Alternatively, you can go to the custom ROM route: this will save you a lot of time and headache. Jaguar ROM if you want some AOSP flavor, or DStrikerz if you like Sony's UI. Both includes root, but DStrikerz will allow flashing with locked bootloader. Read THIS for custom recovery.

Need Help with Z3 Compact

***UPDATE***
I removed Kingroot through their app and unrooted my phone. I tried another one click root, Kingoroot (I know, quite similar names.) The SU which this one installs, isn't restricting me and I successfully set read/write to /system.
I still would prefer to be using superSU but I get a binary occupied message, and the kingouser app doesn't have an option to switch SU app.
For anyone else struggling with kingroot not letting apps work properly, try kingo, who knows.
-----------------------------------------------------------------------------
I have the Z3 Compact, and I HAVE NO ACCESS to a PC, and thus have rooted my phone with King root (which was a terrible idea but any root is better than no root)
I have this issue, where King root in some way shape or form is not allowing anything that requires write permission to /storage access to it.
This is not allowing me to install/use things like busybox, lucky patcher, freedom, and is also, stopping me from using terminal emulator to do things such as mount -o rw,remount,/system or anything else. I tried to use a system I found on XDA to replace Kingroots superuser to SuperSU to get around this, however, the replace_kinguser method, fails with no write permission, and also, fails to remove kinguser from /system/apps/kinguser because that doesn't exist as a directory and I think Kingroot may have made changes to their superuser handler.
I really, really need help getting Kingroot out, and superSU in. Without the use of a PC. Considering I do, have root, there must be something I can do.
I also can't set system to write with ES file explorer or pretty much any other method on the first ten pages of Google.
Any time I try to set /system to r/w I get permission denied.
I'm running, android 5.0.2
Also, BOOTLOADER UNLOCK ALLOWED? NO
So I don't think I can flash a custom recovery of any kind.

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.