i'm trying to install Magisk root on my LG G6 H870 and i've unlocked my bootloader and got TWRP Running
Howver everytime i try to flash Magisk i get the same "Unable to mount \System (device or something BUSY)" error
Does anyone know what's going wrong and how i can fix it?
Please i've been trying to root for days and i'm just not getting it
Please format data. The problem should be gone.
McCoffee said:
i'm trying to install Magisk root on my LG G6 H870 and i've unlocked my bootloader and got TWRP Running
Howver everytime i try to flash Magisk i get the same "Unable to mount \System (device or something BUSY)" error
Does anyone know what's going wrong and how i can fix it?
Please i've been trying to root for days and i'm just not getting it
Click to expand...
Click to collapse
Just managed to fix the issue!
By setting the system to "Mount Read-Only" or whatever the setting found under mount in TWRP is and then ticking the mount box for system the install suddenly worked and it's now running Magisk
Great! Enjoy your phone.
Related
Hi, I have a Samsung Galaxy S4 from ATT and I rooted my phone about 4 months ago using a downgrade to MK2 method.
Everything was working fine until I had one app (Puzzles and Dragons, japanese version) that apparently doesn't like it when SuperSU is on. I turned SuperSU off, only to realize that I had to change the Superuser.apk file in /system/app as well (i don't know why but this app hates on superuser). Now since /system/app files are all read only, I need root access again to modify the file name. However, when I start up SuperSU again, it tells me there is no SU binary installed, and that I need to manually re-root.
I'm trying to find a way around this, and a couple of people said to boot into recovery and install the .zip file for SuperSU. I went ahead and downloaded SuperSU-v2.02.zip, and put it on my phone, and booted into Safestrap recovery. When I try to install it, it says "unable to mount '/system'" and "unable to mount '/systemorig'"...
Another round of google-ing. Apparently Clockwork Mod Recovery (CWM) is the solution. But now that I've disabled SuperSU, I no longer have root access, so CWM doesn't work!
****. Do I really have to manually re-root? Every time I root using the downgrade-root-upgrade-keeproot method I wipe everything on my phone, and I'd really like to not wipe my phone. Is there a way around this?
TL;DR: I'm looking for a fix to any of the following:
1. no SU binary installed
2. unable to mount '/system' and '/systemorig'
3. rooting NC1 that doesn't wipe all of my data
Thanks in advance.
EDIT: Towelroot saves the day. Still working on getting P&D Japanese to work.
Hi everyone,
I have some weird root on my Meizu Pro 5 with 5.1.6.0 G. Root permissions are ON in the Settings/Fingerprint and Security/Root Permission/ . I have a list of apps with Allow permission, including SuperSU, BusyBox, Root Explorer and Terminal Emulator. When I launch any of these apps for the first time I get a prompt for permission and I choose Allow.
However, Root checker does not recognize the root and Kingroot failed to root the device. When I boot device into fastboot to unlock the bootloader to install TWRP, I see “Fastboot [locked, rooted]” message. Whenever I try to use “su” command in the Terminal it returns access denied or something similar. SuperSU app fails to update the binary, although, ES Explorer has root access to explore files.
I tried to Reset to factory settings - same issue
Tried to Factory reset + Format internal storage and test root on clean device without even restoring from a backup - same issue
Tried to flash update.zip from File Explorer and from Recovery itself - firmware corrupt and does nothing.
Not sure when and what went wrong. I updated to 5.1.6.0G via terminal commands, hence I had su access with no problems.
Do you have any ideas? Now I just want to revert to the original state of the device and repeat the rooting from scratch, but unable to do so since any firmware I tried was "corrupt" and terminal does not let to use commands.
P.S. After "Factory reset + Format internal storage" in the very first boot of the device I noticed that Root access was already ON, even though I skipped the Flyme account login step. The phone is working fine - no bootloops, not bricked. Even Xposed is installed and working fine. The only issue is with the root, which appears to be incomplete.
Something similar happened to me.
Just update Flyme and check clear data. Then root it again.
Found the problem: if you are unrooted on the bootloader (check with [power] + [vol-])
And rooted within flymeos, you experience this problem.
I've got the same issue but I'm unable to instal another version of flymeOS (got corrupted firmware).
Does someone know how to fix ?
Atarhorn said:
I've got the same issue but I'm unable to instal another version of flymeOS (got corrupted firmware).
Does someone know how to fix ?
Click to expand...
Click to collapse
I might be able to help you, do you have a locked bootloader ?
Hi! I've updated my device to Oreo and I'm wondering if there is a way to root it. Kinda of a newbie here, rooted my LG G2 and LG L3 E400 using guides.. can someone help me please?
Download Magisk, patch the bootloader, copy it off to your PC, flash it back on in fastboot, job jobbed.
dj9364 said:
Hi! I've updated my device to Oreo and I'm wondering if there is a way to root it. Kinda of a newbie here, rooted my LG G2 and LG L3 E400 using guides.. can someone help me please?
Click to expand...
Click to collapse
You can root it the same way as on Nougat, make sure bootloader is unlocked, flash TWRP 3.1.10 and latest SuperSU and you are done...just this.
Works flawless, i already did it on mine.
Guys is possible to root the phone without sd card?
Dottorfox said:
Guys is possible to root the phone without sd card?
Click to expand...
Click to collapse
There is a problem in twrp with oreo, after the first time you boot in oreo, twrp can't mount /data partition, so to root you must format data (NOT WIPE), flash magisk or SU and then reboot. After the boot you can't no more mount data in recovery. Probably the fix will come.
Dadda98 said:
There is a problem in twrp with oreo, after the first time you boot in oreo, twrp can't mount /data partition, so to root you must format data (NOT WIPE), flash magisk or SU and then reboot. After the boot you can't no more mount data in recovery. Probably the fix will come.
Click to expand...
Click to collapse
There is no doubt that fix will come because S9 has the exact same problem and it got fixed already. We have to wait for US997 variant to get an update so devs can start working on this issue.
1. I booted TWRP to make Nandroid. I saw this error: E:recv error on uevent
2.I opened Magisk Manager/Uninstall/Restore Image
3.Tried to updated Android: failed
4.I rebooted phone and SafetyNet check failed
5.Booted TWRP and flashed magisk.zip
6.SafetyNet check failed, root check failed
So I tried this
1.I booted TWRP
2.flashed magisk-uninstaller.zip
3.rebooted phone
4.updating Android failed, SafetyNet check failed
So I flashed magisk.zip and I have root at least but I am without the November update. Any idea what's wrong?
In TWRP mount /system read-only. You also must revert any changes you've done to system. Flash newest Magisk uninstaller in TWRP > Mount system read-only in TWRP > Boot and try to apply OTA update.
I must say reverting system back to read-only didn't help me. I haven't been able to figure out why my OTAs fail even when Magisk is uninstalled and system r/o. Doesn't really bother me because I flash stock images provided in this forum, so far so good.
PS You might want to skip the November update, I've read only negative things about it (battery drain; SIM PIN bug that will prevent you from booting the phone if you're not using English language).
The problem is that I didn't make any system changes. I could update Android a month ago without any problem. From then on I installed just two apps: Microsoft To-Do & Moy game. I didn't do anything else. Just using already installed apps... Of course, I always used an option "Keep read only" while using TWRP. But something must be broken, even I uninstall Magisk completely via TWRP, Root checker app shows me "root access is not properly installed in this device. Anyway, I think the fastest way to solve my problem, without losing my data, is to flash a fastboot image.
galaxy s8, uk version, keep getting that error, trying to root it, installed twrp ok.
any ideas guys ? its driving me nuts