Develop Bugs

[GUIDE][ROOT][19/Nov] r14: VISIONary + one click root

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note: This application is no longer being updated and is only recommended for use on Froyo builds.
What is VISIONary?
VISIONary (so named because it was originally an application designed for the T-Mobile G2 / HTC Vision) is an application you install on your device that allows you to Temproot or optionally Permroot your device, using the 'rageagainstthecage' exploit.
How do I use it?
It's pretty simple really. The options appear as follows:
Temproot on boot - use this to automatically Temproot on each boot (I suggest Temprooting manually first to confirm all is well before enabling this)
Run visionary.sh after root - this allows you to run a script (as root) after rooting. The script file is /data/local/visionary.sh
Set system r/w after root - this allows you to leave the /system partition read/write after root
Temproot now - root temporarily (the root wil be lost after reboot)
Attempt permroot now - attempt to apply a permanent root (please read the safety information below before doing this!)
Unroot now - this will unroot your device
Safety information!
You use VISIONary at your own risk! Although we test it as much as possible, we are unable to guarantee that weird things won't happen.
As a rule, the 'Temproot' option of VISIONary should be completely safe. It installs an application (Superuser) in the conventional way and then sets up a 'ramdisk' for the other parts, which is wiped on boot. As such, no changes are made to the system partition of your device, hence it is considered a 'safe options'.
Permroot on the other hand is inherently more risky. Permroot does make changes to the /system partition of your device. Technically speaking the only change that is made is the installation of a small file to /system/xbin, but any system partition change comes with risks. If you try to permroot, be aware that you might get into a situation where your device will not boot. For this reason, we recommend you have a 'safety net'.
In general, the best 'safety net' for going ahead and doing a Permroot is ensuring that you have a copy of the stock ROM to reinstall should things go wrong. This should be an original update EXE or zip from your device manufacturer / provider which matches the software version currently installed on your device. Bear in mind that flashing older versions is often not possible, so if your device has been updated over-the-air, an update may not yet be available in this form. Hence, you may not be able to find a 'safety net' and attempting to Permroot would be inherently risky. For HTC devices at least, one option would be to Temproot, edit the MISC partition to revert the 'mainver' to an older version, thereby allowing you to flash an update older than the currently installed version should things go wrong. That option is currently outside the scope of this post, although I will provide details on how to accomplish this in another post.
Got your safety net? Aware of the risks? The download is below.
Download
r14 - (see changelog below for details) - [url="http://android.modaco.com/content/software/320350/19-nov-r14-visionary-one-click-root/]DOWNLOAD[/url]
The download is in APK format (if it is downloaded with a 'zip' extension simply rename). Copy to your device and click to install (or run 'adb install -r com.modaco.visionaryplus.r14.apk' if you have the SDK installed).
NOTE: USB DEBUGGING MUST BE ENABLED FOR VISIONARY TO WORK!
And finally
Details on how to donate should you wish to do so are in download topic at MoDaCo.
Enjoy!
P

thanks for you guys work

works perfectly! thanks

Does nothing for me, just sits there saying rooting device, flashes every few seconds
Sent from my T-Mobile G2 using XDA App

Question Answered..
Thank you P, my reboot question has been answered... just click and proceed. (To Be Tested)
It feels so good to see you on the scene.. It's been a while.. Since the N1

v8pwrdz28 said:
Does nothing for me, just sits there saying rooting device, flashes every few seconds
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Same here

v8pwrdz28 said:
Does nothing for me, just sits there saying rooting device, flashes every few seconds
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Reboot and try again...
P

paulobrien said:
Reboot and try again...
P
Click to expand...
Click to collapse
How long should the program run?

I have no experience whatsoever in developing or rooting on Android, so excuse me if this is a stupid question. When you say that if we want something to happen every time we finish rooting at bootup, to put it in /data/local/visionary.sh, what exactly does that mean? How does one go about doing this?

when i run this it just keeps saying rooting device with spinning wheel at top then it reboots

Not Working
Just getting the spinning wheel and flashing with no progress. Even tried to reboot and start over with no results

Thank you for making my life easier.

Does this app require you to do the "one-time" first step of the temp root process before you can use it?

Like others have said, this doesnt work for me. Just flashes rooting please wait and nothing happens.

Hey thanks it worked .. At first it kept running and nothing happened, so i rebooted the phone and it worked in the first try.

LogicHell said:
Does this app require you to do the "one-time" first step of the temp root process before you can use it?
Click to expand...
Click to collapse
No...
P

What should happen...
Boot device
Click VISIONary icon
Phase 1 runs
Logo disappears briefly as app reloads
Phase 2 runs
App disappears and root is complete
If this doesn't happen, I suggest rebooting and trying again.
P

Does it use the old 'root' script (copy everything to /system/bin and /system/app) or the new method? The old one expires eventually when linux drops the cache, the new one stays forever (until reboot). (Also, putting superuser on /data/app means it remembers it's permissions and grants across reboot, instead of losing it every time.)
The updated script is here:
Disconn3ct said:
FYI I altered the script to survive cache flushes and such. If you use this instead of the old 'root' script (and put everything in /data/local/bin instead of tmp) it will make the bare mininum number of changes to /system and those changes will last until you reboot (instead of flushing out over time).
Click to expand...
Click to collapse

Auto Root
I downloaded Startup Manager from the Market and set VISIONary to auto load on each bootup and so as of right now it auto loads with each restart. Very handy until it auto loads on itself. Just a thought.

Disconn3ct said:
Does it use the old 'root' script (copy everything to /system/bin and /system/app) or the new method? The old one expires eventually when linux drops the cache, the new one stays forever (until reboot). (Also, putting superuser on /data/app means it remembers it's permissions and grants across reboot, instead of losing it every time.)
The updated script is here:
Click to expand...
Click to collapse
Good call on putting the Superuser APK on /system/app! re: the 'old' or 'new' way, i'm doing it the old fashioned way (didn't know there was another way, heh)!
If you can point me to it, i'll change it for r2.
P

TMobile GPad F 8.0 (V496) Info

For those that picked up a TMobile GPad F 8.0 recently, here's a good thread to ask questions until we either get a separate forum or get enough info to move over to the General.
Root
Kingroot works well following the instructions here: All you need for LG GPad 8.0 [LG v490] thread. Once rooted, replace it with SuperSu using this method.
It is best to use KingRoot 4.1 or earlier to root, replacing it as soon as possible. 4.5 is very difficult to uninstall, although you can purchase SuperSUMe on Google Play to attempt it.
OS
Stock OS is the only option at the moment. There is a system update available which fixes the stagefright bug. It can still be rooted.
Recovery
Thanks to @Rashed97 and @KAsp3rd a beta TWRP is available here. This is not a zip, so use Flashify, TWRP Manager or equivalent to flash zips. Hooking up a USB mouse also works well for in-recovery navigation.
Kernel
Similar to LG stock ROM on their phones, the kernel has some adjustable features accessible through Kernel Aduitor or Trickster.
Xposed
Xposed installs and runs well. G3TweakBox has the ability to adjust some extra settings.

ADB driver
I got one as part of the Father's Day promotion as I needed to upgrade my mobile internet hotspot. I would like to migrate from a Nexus 7 2013 and needed the ADB driver for restore using Helium. Has anyone come across a working ADB driver for this GPad?

I was able to root with Kingroot 4.1 and then replace Kinguser and su binaries to SuperSU using this method:
http://forum.xda-developers.com/showpost.php?p=60669196&postcount=1&nocache=1&z=4065499287098646
---------- Post added at 11:45 AM ---------- Previous post was at 11:39 AM ----------
These are the USB drivers I used . Got them from this thread: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951

nicknc said:
Anyone else had performance issues without rooting?
Click to expand...
Click to collapse
There are performance issues without root as well.

FYI I just unlocked this tablet. Doesn't give 4G LTE on AT&T though, only HSPDA+
To Unlock this model, access the Hidden Menu:
1) From Home screen,Touch the “ Contact”
2) Touch the “ Search Contact
3) You can see the “Keyboard” after Touch the “ Search Contact”
4) Touch the “＋ “ icon after Dialer 2945#*496#
5) Touch Network Lock, you only have 3 attempts to enter the correct Unlock Code which you can get from any online vendors.
6) Press Unlock

Rooted with Kingroot & replaced it with SuperSu using this script. No computer required just make sure you have Terminal Emulator installed!
Download the file attached and extract it
Put the mrw folder on the root of the sd card
Open Terminal Emulator and type:
Code:
su
grant terminal emulator root access
Next type:
Code:
sh /sdcard/mrw/root.sh
The script should then run and work it's magic. After it's completed SuperSU should open up and prompt you to update the binaries. Update the "Normal" way and reboot afterwards.
And that's it! :good:

Post 1000, hooray.
VRAM seems to be on by default and is eating up about 256K according to Kernel Aduitor. Disabling that helped performance some after I did a factory reset. The LTE radio is stronger than my G3, but that might just be a longer antenna.

the 'replace kingroot...' script didn't work for me. Anybody having issues with root not working after reboot? i have to re-root with kingroot every time. going to try the adb method now

sinshiva said:
the 'replace kingroot...' script didn't work for me. Anybody having issues with root not working after reboot? i have to re-root with kingroot every time. going to try the adb method now
Click to expand...
Click to collapse
Which KingRoot version did you use?

nicknc said:
Which KingRoot version did you use?
Click to expand...
Click to collapse
KingRoot-4.1.0.524.apk
[edit/]
I think they must have updated something on their end because now the same kingroot apk is working - root correctly persisting across reboots

You Are The Man {Works Like A Charm}
xoxo_xdagirl91 said:
Rooted with Kingroot & replaced it with SuperSu using this script. No computer required just make sure you have Terminal Emulator installed!
Download the file attached and extract it
Put the mrw folder on the root of the sd card
Open Terminal Emulator and type:
Code:
su
grant terminal emulator root access
Next type:
Code:
sh /sdcard/mrw/root.sh
The script should then run and work it's magic. After it's completed SuperSU should open up and prompt you to update the binaries. Update the "Normal" way and reboot afterwards.
And that's it! :good:
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I followed your instructions to the "T"! Your method for rooting with Kingsroot 4.1 English version, and replaced it with SuperSu
works like a charm! My suggestion to everybody, do everything in the internal storage area! Don't use your external SD Card using the above instructions! I'm making phone calls on this baby to via WiFi and LTE, sweet!

now just need to get roms
kinda makes me want to try and make my own.. I've never developed before. lol!

Which custom recovery we use?

Rican2008 said:
Which custom recovery we use?
Click to expand...
Click to collapse
Nothing out there yet that I've seen. It'll come-- the v500 has had TWRP for about 9 months now. This one has only been out a couple of weeks.

Rican2008 said:
Which custom recovery we use?
Click to expand...
Click to collapse
I got a CM recovery to build using the stock kernel source from LG, but I'm super hesitant to flash it, until I can verify the LG Updater software works for me. I don't have a Windows box ATM, so it'll take a bit more effort. I'll post here with results once I'm willing to flash.

Now that we have the root, has anyone tried to adjust the color of a panel? It is way too warm compared to my other devices (viewing my DSLR pics almost makes me think thr wirte balance was off).

northantara said:
I got a CM recovery to build using the stock kernel source from LG, but I'm super hesitant to flash it, until I can verify the LG Updater software works for me. I don't have a Windows box ATM, so it'll take a bit more effort. I'll post here with results once I'm willing to flash.
Click to expand...
Click to collapse
Well, I flashed it, and things went, err, poorly. I'm done trying. Turns out, it's not actually possible to recover from download mode with LGMobile Support Tool, at least until an update is made available online.

Thanks for trying. I assume the bootloader is locked on this too, meaning we will need to bump any flashable zips anyway.

The step to replace KingRoot with Supersu failed half way for me. Apparently there's a typo in the script >.< Now KingRoot thinks that the tablet is rooted even though it isn't... stuck with broken root...

That is not good news, if this baby has a locked boot loader I am taking it back. Left AT&T for locking the boot loaders of their devices.

Busybox fails to install

Accidentally installed the wrong busy box apk but cleared data and uninstalled then i tried installing the correct version of stericson busybox free and I'm greeted by this message
"There was a problem opening a shell with root access. this is either cause by supersu or by a device that is improperly rooted..."
It then goes on to say i should change permissions in supersu then reinstall. Of course I can't do this because our supersu does not have a settings menu.
I'm looking for help. Is there a way to resolve this over adb and change the su settings? Or can i reinstall supersu?--would that give me the popup i need to grant permissions (if that is in fact the issue...)
I'm not certain i can just run towel root again and reinstall supersu. I have the latest prerooted firmware installed.
BTW--I'm curious as to what happened. thinking the wrong busy box app is still causing issues because i did the same thing on my other fire tv and could easily install busy box again. Thanks.

You should be able to open the settingsmenu (or the apps list) of SuperSU in the FireTV system settings menu -> installed apps tab. Just start the SuperSU app for that.

Calibaan said:
You should be able to open the settingsmenu (or the apps list) of SuperSU in the FireTV system settings menu -> installed apps tab. Just start the SuperSU app for that.
Click to expand...
Click to collapse
Unless I'm misunderstanding, you can't do that with our supersu (think its just the way rbox designed it that supersu can't be opened). Go to applications and try it. I assume your setup is the same as mine--cwm & and prerooted firmware.
I'm thinking I'll just uninstall/reinstall supersu, but not even sure that will resolve the busybox issue.

No, I have not a rooted aTV (those for the german market were never deliverered with a rootable firmware, hope this changes with stagefright vulnaribilty). I assumed you´re running the regular SuperSU from Chainfire which does acts as a Superuser access management tool:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It should be possible to call this superuser app from the apps tab within the system menu like every other sideloaded app. Of course when you´re running another supersu app this probably won´t work.

Calibaan said:
No, I have not a rooted aTV (those for the german market were never deliverered with a rootable firmware, hope this changes with stagefright vulnaribilty). I assumed you´re running the regular SuperSU from Chainfire which does acts as a Superuser access management tool:
It should be possible to call this superuser app from the apps tab within the system menu like every other sideloaded app. Of course when you´re running another supersu app this probably won´t work.
Click to expand...
Click to collapse
Thanks. I have read in other thread people talking about using superuser app to access those settings we can't get with supersu on AFTV. That was a long time ago and don't think there was much feedback on how it worked.
I messed things up more than I thought. None of my root apps are working (ROM manager, titanium backup, samba file sharing, etc.
Wondering if just reinstalling the ROM.zip will fix everything? Only thing about that is it doesn't ask to regrant su for my installed apps normally. Not sure if it'll be different because root isn't functioning properly...

So maybe someone can confirm this? If I wipe factory reset in cwm will supersu reinstall and reset su settings? (Actually pretty sure it will) But really rather not do that because I'm forward thinking enough to install titanium backup but not smart enough to backup apps and data (always put it off then forgot) Now of course I can't use titanium.
So if that's my only option I'll do it but hoping there's a simpler way like flashing supersu zip in recovery. AND if that's an option should I first remove supersu apk in system/app?

I've had issues with the Busybox installer, too. It claims you can begin installing right away, but it's a good idea to wait until it finishes its scan to do the install.

Sizzlechest said:
I've had issues with the Busybox installer, too. It claims you can begin installing right away, but it's a good idea to wait until it finishes its scan to do the install.
Click to expand...
Click to collapse
Well I didn't actually want busybox installer. I wanted busybox free by stericson. I'm not even sure if the installer is by stericson. So did you try to run that installer program again and let it complete? Or were you actually talking about busybox free which is what I've always used on AFTV (its the recomended version we all are probably using). But not paying attention I installed the wrong apk. Now none of my root apps work which I don't understand. Busybox having trouble makes sense but pretty sure I've run other root apps without busybox in the past.
Its looking like I need to wipe it but not in a huge hurry. The AFTV functions OK without root so I'll hang around for a better solution.

KLit75 said:
Well I didn't actually want busybox installer. I wanted busybox free by stericson. I'm not even sure if the installer is by stericson. So did you try to run that installer program again and let it complete? Or were you actually talking about busybox free which is what I've always used on AFTV (its the recomended version we all are probably using). But not paying attention I installed the wrong apk. Now none of my root apps work which I don't understand. Busybox having trouble makes sense but pretty sure I've run other root apps without busybox in the past.
Its looking like I need to wipe it but not in a huge hurry. The AFTV functions OK without root so I'll hang around for a better solution.
Click to expand...
Click to collapse
This is what I was referring to: https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Can you connect to your Fire TV using adb and do a "su" command to see if you get root? Did you fully unlock your bootloader?

Sizzlechest said:
This is what I was referring to: https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Can you connect to your Fire TV using adb and do a "su" command to see if you get root? Did you fully unlock your bootloader?
Click to expand...
Click to collapse
That's the one that won't install. Yes. I can connect adb, reboot recovery and bootloader fully unlocked. I can't access everything in es file explorer because the root explorer option won't work without su permissions. But adb shell will get the # sign.

Install Xposed Framework to LG Spirit without recovery

This is method of installing Xposed Framework which is made by @rovo89 to use some tweaks without needing to modify system files (like SystemUI).
Original post was made in General Thread by @polfrank but I need to edit it with some new things which he is missing.
Code:
I'm in no way responsible for whatever happens to your device if things go wrong.
Your device is your responsibility, proceed with caution and only if you know what you're doing.
Apps and stuff which is needed to install Xposed Framework
* Root
* BusyBox - IMPORTANT, script don't work properly without BusyBox installed
* Terminal Emulator
* adb if you don't wanna to use Terminal Emulator - use this version of adb -> http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
* Installer script - Updated to work with latest version of Xposed Framework zip files. It shows some minor problems which doesn't make installer not working. Translated from Spanish to English by @midzan21 aka myself.
* Xposed Framework zip file - IMPORTANT, download SDK21-ARM variant, not ARM64 or SDK22-ARM variant, because stock ROMs are compiled with 32-bit version, not 64-bit. Also SDK21 is for Lollipop 5.0.x and SDK22 is for Lollipop 5.1.x
* Xposed Installer apk - download latest version and install it
* Brain.apk - just in case, but still important
Installation process for Terminal Emulator:
1.) Put Xposed Framework zip, Xposed Installer apk and Installer script (extracted) on Internal memory of device (Internal SD Card, not your real SD card if you have it)
2.) Install BusyBox
3.) Open Terminal Emulator and enter this commands
3.1.) Gain Root Permissions after entering su command
Code:
su
sh /storage/emulated/legacy/installer
4.) Enter once 1 to continue installation
5.) When script finishes phone would automatically reboot (hint: added reboot command in latest version of script just for safety purposes)
6.) Install Xposed Installer apk
7.) Open Xposed Installer and check in Framework section check does it writes: Xposed framework version XX is active (XX is latest version)
8.) Install module which you want and after enabling it reboot phone
9.) Enjoy
Installation process for adb:
1.) Extract adb setup of provided adb
2.) Install BusyBox
3.) Go to adb folder
4.) Press Shift and Right Mouse Click and in context menu select Open command windows here
5.) Now copy Xposed zip file and installer file in adb folder
6.) Use this commands to do check if you Enabled Debugging in Developers options
Code:
adb devices
And after that you should see LG and some numbers with enabled right after that (this LG cripple is your Android Phone name for adb and fastboot)
7.) Copy files to internal SD card with this commands
Code:
adb push xposed-v80-sdk21-arm /sdcard/
adb push installer /sdcard/
Please note: always copy with latest vXX number Xposed zip
8.) Now it is easy stuff done, now it is time to do work which is hard part - doing commands to install Xposed
Commands are:
Code:
adb shell
su
mount -o remount, rw /system/
sh /storage/emulated/legacy/installer
9.) Enter once 1 to continue installation
10.) When script finishes phone would automatically reboot (hint: added reboot command in latest version of script just for safety purposes)
11.) Install Xposed Installer apk
12.) Open Xposed Installer and check in Framework section check does it writes: Xposed framework version XX is active (XX is latest version)
13.) Install module which you want and after enabling it reboot phone
14.) Enjoy
Problems, bugs and issues:
Currently none, added to script to remove LG QuickCover which make Force Close
Old bugs, problems and issues:
Weather FC (Fixed with never versions of Xposed Framework)
Tethering and networks in Settings FC (Fixed with never versions of Xposed Framework)
After every boot you have Android is upgrading screen (fixed with never versions of Xposed Framework)
To do list:
* Nothing at this point
Credits:
@rovo89 for Xposed Framework and Installer
@polfrank for original post in General Thread
Unknown person for creating original installer script

Changelog
Update #1 - 16.10.2015 @ 19:43
* Thread created
* Added link to this thread in General Thread for LG Spirit to @polfrank update thread post #1

There's no way to fix LG QuickCircle cover? because I use it and don't want to lose it

andrekeys1 said:
There's no way to fix LG QuickCircle cover? because I use it and don't want to lose it
Click to expand...
Click to collapse
There is no way to use QuickCircle cover because it is problematic with Xposed Framework for now. I tried before updating script with QC and it just got Force Close from booting up device.
Also I'm not sure would it work, but here is link to all LG V10 apps and there is QuickCircle app. Before testing make a a backup of stock apps just to be sure that it works and there is no problems.
https://mega.nz/#F!bpQGBbLQ!Q3eTeYxe5fIBLegkQjiI6A

Changelog
Update #2 - 7. 11. 2015 (0:12 @ CET)
* Updated installer script so it automatically remove /cache and /data/dalvik-cache (created back in end of October, tested and it works)
* Updated tutorial (shortened for few lines, but still it is way easier right now)
To-do list:
* Automatic installer without first confirmation and with automated reboot ( ETA: few days after this posting, need neighbours phone without Xposed to check it and test )
* Porting script to Android app ( early ETA: mid to end of December this year )

Is it possible to uninstall xposed?

Hallo. Whats the problem I have? i added files to internal /emulated/ directory. ES file manager said its internal SD Card. Maybe trouble is somewhere else?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

xyster13 said:
Hallo. Whats the problem I have? i added files to internal /emulated/ directory. ES file manager said its internal SD Card. Maybe trouble is somewhere else?
View attachment 3539627
Click to expand...
Click to collapse
Missing BusyBox, need to install that first before doing anything.

midzan21 said:
Missing BusyBox, need to install that first before doing anything.
Click to expand...
Click to collapse
But its installed. I checked with BusyBox Checker ant it shows that its installed. Any thoughts?

xyster13 said:
But its installed. I checked with BusyBox Checker ant it shows that its installed. Any thoughts?
Click to expand...
Click to collapse
Are files in
/storage/emulated/0
because that folder is linked to
/sdcard
I have no clue why some File Managers says different for internal SD, that is info which I get while using original Root Explorer (purchased while back when it was on some discount with few other apps like Titanium Backup Pro and Nova Launcher Prime as I remember good enough)

midzan21 said:
Are files in
/storage/emulated/0
because that folder is linked to
/sdcard
I have no clue why some File Managers says different for internal SD, that is info which I get while using original Root Explorer (purchased while back when it was on some discount with few other apps like Titanium Backup Pro and Nova Launcher Prime as I remember good enough)
Click to expand...
Click to collapse
Ok I did it. ES File Explorer(free version doesnt show emuated/0 directory thats why files where in /sdcard. Also just to warn - Root Explorer doesnt work Copy/Move/Paste commands doesnt work on this device or at least on mine. Explorer from google play works fine and I moved those files with this program.
Thank You!

xyster13 said:
Ok I did it. ES File Explorer(free version doesnt show emuated/0 directory thats why files where in /sdcard. Also just to warn - Root Explorer doesnt work Copy/Move/Paste commands doesnt work on this device or at least on mine. Explorer from google play works fine and I moved those files with this program.
Thank You!
Click to expand...
Click to collapse
ES Fle Explorer was always free, you maybe mistaken ES for some other File Explorer which have free & paid options.
On mine device Root Explorer works fine. That Explorer app is just free version of this paid app Root Explorer (same dev is for both apps)

midzan21 said:
ES Fle Explorer was always free, you maybe mistaken ES for some other File Explorer which have free & paid options.
On mine device Root Explorer works fine. That Explorer app is just free version of this paid app Root Explorer (same dev is for both apps)
Click to expand...
Click to collapse
Oops yeah my mistake. I was confused a little by the program list and names on google play. You are right about ES File Explorer

@midzan21
I'm wondering why do you need to further improve your method? It works perfectly fine for me, without any issues. I'm just curious.

there is any way to get quickcirle install zip or smth?
I uninstalled xposed framework cuz i am not using it anymore and i want to get my qucikcirle back.

fliperpl said:
there is any way to get quickcirle install zip or smth?
I uninstalled xposed framework cuz i am not using it anymore and i want to get my qucikcirle back.
Click to expand...
Click to collapse
How did you uninstall it ?

BrosseLi said:
How did you uninstall it ?
Click to expand...
Click to collapse
i broke it by change default SDCARD write partition (with some xposed module :E) and its not working. I uninstalled it with xposed uninstaller flashed by flashfire

fliperpl said:
i broke it by change default SDCARD write partition (with some xposed module :E) and its not working. I uninstalled it with xposed uninstaller flashed by flashfire
Click to expand...
Click to collapse
Okey, and FlashFire proposed you to mount the partitions ( Read&Write ), did you tick it or no ? I
I didn't and the log says that he couldn't mount my SD

BrosseLi said:
Okey, and FlashFire proposed you to mount the partitions ( Read&Write ), did you tick it or no ? I
I didn't and the log says that he couldn't mount my SD
Click to expand...
Click to collapse
i did.

fliperpl said:
i did.
Click to expand...
Click to collapse
Thanks a last question: which uninstaller did you download ?
The arm ,arm64 or armx86 ?
EDIT: flashed the arm version, it worked well

Q beta 5 is GREAT,but can not mount /system for now

I've tried Magisk Canary and different TWRP versions , even wipe system (It can be mounted when it‘s empty - -)

seardna said:
I've tried Magisk Canary and different TWRP versions , even wipe system (It can be mounted when it‘s empty - -)
Click to expand...
Click to collapse
Happened to me before. I believe I cleared the system partition and it worked.

TechNash said:
Happened to me before. I believe I cleared the system partition and it worked.
Click to expand...
Click to collapse
Please tell me the version of magisk and twrp you use?
I tried to wipe the system ,data , all partitions has been wiped with TWRP 3.3.0 . Than flash-all with -w.
Maybe some steps wrong, I have no idea .

seardna said:
Please tell me the version of magisk and twrp you use?
I tried to wipe the system ,data , all partitions has been wiped with TWRP 3.3.0 . Than flash-all with -w.
Maybe some steps wrong, I have no idea .
Click to expand...
Click to collapse
Latest TWRP from website, magisk stable

TechNash said:
Latest TWRP from website, magisk stable
Click to expand...
Click to collapse
Thanks. But can you mount system in the TWRP? While install Magisk , there are some errors failed to mount /system (Invalid argument )

Would this be why titanium backup doesn't open either ??

this happened with beta 4 also. don't know if it's twrp or magisk issue

Q5,same issue here, tried everything, factory reset, format partition, no luck
apart from this, everything works
in root explorer, you can't mount R/W

A latest magisk alpha version maybe solved this problem .
Here is the custom channel :backup up FIRST!
https://raw.githubusercontent.com/yzkpqv68745/magisk/master/alpha.json

solución
hello good forgive my English is not very good but I will tell you the solution I had the same problem the solution is that you have to go mount and select read mode and check the boxes then install the twrp in zip and then magisk and will not give you the system saddle problem and vendor I have magisk running that way if you have any questions let me know and I help you a greeting.

ismael47 said:
hello good forgive my English is not very good but I will tell you the solution I had the same problem the solution is that you have to go mount and select read mode and check the boxes then install the twrp in zip and then magisk and will not give you the system saddle problem and vendor I have magisk running that way if you have any questions let me know and I help you a greeting.
Click to expand...
Click to collapse
this method will work, I tried this with beta 4. But even then you can`t mount system and delete system apps. You will just pass the error while flashing magisk. I hope the dev will find solution for this. Also system apps are not in system/app anyomore, maybe that have some impact with all this

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
darkoj2007 said:
this method will work, I tried this with beta 4. But even then you can`t mount system and delete system apps. You will just pass the error while flashing magisk. I hope the dev will find solution for this. Also system apps are not in system/app anyomore, maybe that have some impact with all this
Click to expand...
Click to collapse
so that the system remains installed you have to leave it in read mode and select the vendor and the system you leave it marked then without unchecking you install the twrp and the magisk and everything is correct the system will be mounted.

I'm on official release 10.0.0 (QP1A.190711.020, Sep 2019) flashed without "-w" over android 9. Pixel 2.
Flashed latest TWRP (3.3.0-0) and 19.3 Magisk, then latest canary. Nothing helps.
Did you manage to find solution? I would appreciate any help.

ismael47 said:
[/IMG]
so that the system remains installed you have to leave it in read mode and select the vendor and the system you leave it marked then without unchecking you install the twrp and the magisk and everything is correct the system will be mounted.
Click to expand...
Click to collapse
Dude that does seem to work at least for the magisk install. It doesnt help fix other issues like adaway and titanium backup from not being able to mount system though!
Appreciate your effort anyway

There's a setting in magisk that'll allow you to install adaway. Systemless hosts...tap it then reboot and adaway should install.
That worked for me.

I was able to get /system to mount by going to Advanced Wipe and selecting 'system' and choosing repair -> Change File System - EXT2 then go back and switch it back to EXT4.
I have not been able to get /vendor mounted and I believe it is because the syntax used has changed.
I read that AOS10 uses a form of EXT4 that preserves it as ready only, possibly by filling the used space of the drive preventing any writing.
This explains some of the new obstacles TWRP must compensate for in order to maintain compatibility w/ AOS10
https://source.android.com/devices/architecture/kernel/mounting-partitions-early
I have had luck installing Magisk by enabling USB Debug and typing in ADB shell:
cat /dev/block/sda19 > /sdcard/boot.img
Open Magisk and chose to install to file and select the boot.img.
Replace boot.img in the zip file that contains Android 10 factory firmware.
Current Marlin factory firmware [ https://dl.google.com/dl/android/aosp/marlin-qp1a.191005.007.a1-factory-c27241e0.zip ]
Inside marlin-qp1a.191005.007.a1-factory-c27241e0.zip is another archive: image-marlin-qp1a.191005.007.a1.zip ; inside this archive is boot.img.
Using 7zip you can open this archive and drag / drop boot.img replacing the stock image with the Magisk patched one.
Run Flash-all.bat, note it *WILL Wipe* your device but include a Magisk patched boot.img.
Once you finish initial setup of phone, download magisk manager and when you open it, it will automatically patch and reboot your phone enabling root. (make sure you have internet connection before opening magisk manager)
After you have root enabled phone you can customize /system to your liking and then cat /dev/block/sda33 > /sdcard/system.img to replace the firmware version.
(Still am not able to load /system as RW using FX, so have yet to be able to modify .props)
You can locate the various links and identify if you are using slot a/b by typing in TWRP terminal : ls -la /dev/block/by-name/
Side note:
The wizard himself has delicate and important matters of being a present father and managing the obstacles of keeping the brood happy-content and also providing nurturing support to the new addition and persistent validation for the wifey. [Congrats])
(apologies for improper formatting de-pretyfied by inotoxication)