Database Users

Unsuccessfull root on lg g2 f320k20f

Hi,
2nd time trying to root but still some message about can't reate, start and failed to copy. Full results below also. I've use the files and methods heree:
http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
http://forum.xda-developers.com/newreply.php?do=newreply&noquote=1&p=45693809&nocache=1
Mounting system, pushing su binary and installing SuperSu...
2244 KB/s (1085140 bytes in 0.472s)
cp: can't create '/system/xbin/busybox': Read-only file system
failed to copy 'su' to '/system/xbin/daemonsu': Read-only file system
cp: can't stat '/system/xbin/daemonsu': No such file or directory
failed to copy 'install-recovery.sh' to '/system/etc/install-recovery.sh': Read-
only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
Unable to open /system/xbin/su: No such file or directory
Rebooting Phone.
***************************************************
***************************************************
You should hopefully now be fully rooted!!
Wait for your device to reboot and continue
with ioroot script to backup EFS...
***************************************************
***************************************************
/sdcard/modemst1.img: cannot open for write: Read-only file system
/sdcard/modemst2.img: cannot open for write: Read-only file system
remote object '/sdcard/modemst1.img' does not exist
remote object '/sdcard/modemst2.img' does not exist
++++++++++++++++++++++++++++++++++++++++FULL RESULT START+++++++++++++++++++++++++++
======adbd is already running as root
uid=0(root) gid=0(root) context=u:r:shell:s0
If you do NOT see uid=0(root) gid=0(root) above then
it is likely your device firmware is not supported or
USB mode was not toggled properly. You can try to
run the script again.
Press CTRL+c to stop this script...
If you DO see uid=0(root) gid=0(root) mentioned above...
CONGRATS.. Rooted ADB is now confirmed.
You will have a rooted ADB shell but no apps on the
phone will
'be' is not recognized as an internal or external command,
operable program or batch file.
PRESS ENTER to continue with full root.
PLEASE NOTE!
Continuing with full root can trip LG's rootchecker.
This means your phone will show ROOTED in Download mode.
You can remove root flag by flashing stock firmware...
.bin .tot or .kdz
If you do not want to possibly invalidate your warranty
press CTRL+c to stop this script...
*******************************************************
Press any key to continue . . .
Mounting system, pushing su binary and installing SuperSu...
2244 KB/s (1085140 bytes in 0.472s)
cp: can't create '/system/xbin/busybox': Read-only file system
failed to copy 'su' to '/system/xbin/daemonsu': Read-only file system
cp: can't stat '/system/xbin/daemonsu': No such file or directory
failed to copy 'install-recovery.sh' to '/system/etc/install-recovery.sh': Read-
only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
Unable to open /system/xbin/su: No such file or directory
Rebooting Phone.
***************************************************
***************************************************
You should hopefully now be fully rooted!!
Wait for your device to reboot and continue
with ioroot script to backup EFS...
***************************************************
***************************************************
/sdcard/modemst1.img: cannot open for write: Read-only file system
/sdcard/modemst2.img: cannot open for write: Read-only file system
remote object '/sdcard/modemst1.img' does not exist
remote object '/sdcard/modemst2.img' does not exist
***************************************************
***************************************************
EFS partitions now in ioroot folder on computer...
They are named modemst1.img and modemst2.img
They will come in handy in case of an emergency.
Store them somewhere you won't lose them.
IOroot is now complete.
***************************************************
***************************************************
Press any key to continue . . .
++++++++++++++++++++++FULL RESULT END++++++++++++++++++++

Same problem here, no solution yet.

LG G2 root
Hello guys,
is there any solution for this? I have same issue
Thank you

Root LG G2 Korean Version

Hi I followed the method here: http://forum.xda-developers.com/showpost.php?p=48709232 and http://forum.xda-developers.com/showthread.php?p=45692679#post45692679
Unfortunately, the automatic rooting is not working, its say something see AUTOROOT MESSAGE BELOW . So I took the manual method but on Step 12:
12: adb shell "sync;mount -o remount,ro /system"
It says mount: Device or resource busy
So what should I do? Thanks
====AUTOROOT MESSAGE =======================================================================
Mounting system, pushing su binary and installing SuperSu...
2244 KB/s (1085140 bytes in 0.472s)
cp: can't create '/system/xbin/busybox': Read-only file system
failed to copy 'su' to '/system/xbin/daemonsu': Read-only file system
cp: can't stat '/system/xbin/daemonsu': No such file or directory
failed to copy 'install-recovery.sh' to '/system/etc/install-recovery.sh': Read-
only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
Unable to open /system/xbin/su: No such file or directory
Rebooting Phone.
***************************************************
***************************************************
You should hopefully now be fully rooted!!
Wait for your device to reboot and continue
with ioroot script to backup EFS...
***************************************************
***************************************************
/sdcard/modemst1.img: cannot open for write: Read-only file system
/sdcard/modemst2.img: cannot open for write: Read-only file system
remote object '/sdcard/modemst1.img' does not exist
remote object '/sdcard/modemst2.img' does not exist

Nubia Z17 Mini - System Read Only after a NANDroid Backup. It's driving me crazy

Hello every,
I would like to start by saything that I don't usually post on forums since I'll always search for hours on the internet.
I do find a solution after different atempts. But this time, absolutly nothing worked.
Nubia Z17 Mini NX569J (AArch64)
Marshmallow - Stock ROM (bought on Gearbest)
Rooted with lastest TWRP (3.2.1)
What happened : I tried to install the Xposed framework.
1/ Made a backup using TWRP containing every option I could check
2/ Installed the v86 framework from Xposed instead of the v89. It worked anyway.
3/ Back to my phone, I installed the Xposed App. Framework was detected successfully.
4/ I downloaded different framework from the App (Block Youtube Ads, Soundcloud Ads, Soundcloud downloader, Battery saving stuff...) and rebooted my phone.
5/ Long reboot time and stuck on a black screen.
6/ After many attemps, I went to TWRP and used my back-up. Everything was back to normal.
But ow, When I'm trying to install the v86 or v89 zip file from Xposed, I get this error :
Code:
Zip signature verification failed!
Error installing zip file '/sdcard/Download/xposed-v89-sd23-arm64.zip'
Without zip verification :
Code:
Installing zip file '/sdcard/Download/xposed-v89-sd23-arm64.zip'
Checking for MD5 file...
Skipping MD5 check : no MD5 file found
*******
Xposed framework installer zip
********
- Mounting /system and /vendor read-write
- Checking environment
Xposed version : 89
- Placing files
chown : /system/bin/dex2oat.orig.gz : Read-only file system
[FONT="Arial Black"][SIZE="4"]Updater process ended with ERROR: 1
Error installing zip '/sdcard/Download/xposed-v89-sd23-arm64.zip'[/SIZE][/FONT]
-> Full log from TWRP : goo.gl/3NP2Zw <-
What I tried so far :
-> TWRP is NOT on Read Only. The box in unchecked and I could use it to install SuperSU zip file.
-> Reinstalling TWRP
-> Reinstallling SuperSU
-> From ADB :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ su root
[email protected]:/ # mount -o rw,remount /system
mount: Read-only file system
-o rw,remount -t yaffs2 /dev/block/mtdblock3 /system <
mount: Read-only file system
255|[email protected]:/ # -writable-system
sush: -writable-system: not found
127|[email protected]:/ # mount -o rw,remount /dev/stl12 /system
mount: Read-only file system
255|[email protected]:/ # mount -o remount,rw /system /system
mount: Read-only file system
255|[email protected]:/ # mount -o remount,rw /system
mount: Read-only file system
255|[email protected]:/ #
With Xposed Installer :
Code:
chown: /system/bin/dex2oat.orig.gz: Read-only file system
Error 1 occured
Uninstall with Xposed Installer :
Code:
rm: can't remove '/system/xposed.prop : Read-Only file system
can't remove 'system/framework/XposedBridge.jar' : Read-only file system
rm: can't remove 'system/bin/app_process32' : Read-only file system
mv: can't rename '/system/bin/
app_process32_original': Read-only file system
Error 1 occured
Root Explorer : nothing happen when I click on "Mount as R/W".
Android Terminal app :
Code:
[B][email protected]:/# mount -o rw, remount /dev/block/system
mount: Read-only file system[/B]
I tried with Busybox too but it's the same problem : system is Read Only
Soooo here it is. I don't have any idea now. I backup up a few times but nothing change.
I was thinking about chaging for anothing ROM but I'm afraid about loosing battery life. And I don't want all of my applications again.
What do you think ?

I think you must reinstall your software from scratch. And you said you rooted your phone but not a word about if was with magisk or su.
I recommend you using magisk and systemless xposed.
Good luck

Issue Installing Busybox via Magisk

On Android version 8.1 v9.6.8.0
Magisk 19.1
Not entirely sure what's happening, but I can't install the Busybox or ADB/Fastboot modules in Magisk.
I've tried:
- installing through Magisk downloads section
- installing through Magisk manually
- reinstalling Magisk
- installing from TWRP
- reflashing the stock system image
Other modules are installing fine, but these both go through the motions and look like they've successfully installed, only not to be in the list of installed modules.
Saved log from my last attempt through Magisk:
- Copying zip to temp directory
- Installing Busybox_for_Android_NDK-1.30.1.zip
- Current boot slot: _b
- Device is system-as-root
Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip
inflating: install.sh
inflating: module.prop
Busybox Installer Script
mount: can't read '/etc/fstab': No such file or directory
mount: can't read '/etc/fstab': No such file or directory
mount: can't read '/etc/fstab': No such file or directory
by osm0sis @ xda-developers
Mounting...
Extracting files...
Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip
creating: META-INF/
creating: META-INF/com/
umount: can't unmount /dev/tmp/su: No such file or directory
creating: META-INF/com/google/
creating: META-INF/com/google/android/
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
inflating: README.md
inflating: busybox-arm
inflating: busybox-arm64
inflating: busybox-mips
inflating: busybox-mips64
inflating: busybox-x86
inflating: busybox-x86_64
inflating: install.sh
inflating: module.prop
Installing...
Using architecture: arm64
Using path: /dev/tmp/su/xbin
Cleaning...
Creating symlinks...
Unmounting...
umount: can't unmount /system: Device or resource busy
umount: can't unmount /data: Device or resource busy
umount: can't unmount /cache: Invalid argument
Done!
At my wits end and I'm not sure what to try next, short of wiping my phone and flashing the ROM again.

did you reformat to f2fs?

Never_Sm1le said:
did you reformat to f2fs?
Click to expand...
Click to collapse
No, it's still ext4.
The strange thing is that other modules installed fine like xposed.

azthemansays said:
No, it's still ext4.
The strange thing is that other modules installed fine like xposed.
Click to expand...
Click to collapse
Maybe something makes fstab unreadable. Aside from formatting to f2fs I can't think of another.

[SOLVED] Installing no-verity-opt-encrypt-6.1.zip failed > Logo Bootloop after installing TWRP on SM-G950F

Hi,
after I successfully customized my Samsung S II years ago (thanks to the XDA-community), I wanted to start with my S8, since to official support ended.
I could install TWRP. I think I followed the steps correctly as guided in:
https://forum.xda-developers.com/t/...1-x-twrp-for-galaxy-s8-and-s8-exynos.3847712/
twrp-3.5.2_9-0-dreamlte.img.tar is installed and it's possible to boot into it.
As described within the steps, I tried to install "no-verity-opt-encrypt-6.1.zip", which is failing.
At first I couldn't mount the data partition, so I formatted data partition as described.
The mouting of /preload failed, so I wiped it as described.
After that I got the following error:
######################################## dm-verity and forced encryption #
# disabler by jcadduono #
# version 6.1 #
#######################################
Unpacking the installer...Archive: /usb-otg/no-verity-opt-encrypt-6.1.zip
inflating: config.sh
creating: META-INF/
creating: META-INF/com/
creating: META-INF/com/google/
creating: META-INF/com/google/android/
inflating: META-INF/com/google/android/update-binary
creating: patch.d/
inflating: patch.d/02-no-dm-verity
inflating: patch.d/01-no-force-encrypt
creating: chromeos/
inflating: chromeos/kernel_data_key.vbprivk
inflating: chromeos/kernel.keyblock
inflating: patch.d-env
inflating: boot-patcher.sh
inflating: LICENSE
creating: tools/
creating: tools/x86_64/
inflating: tools/x86_64/futility
inflating: tools/x86_64/bootimg
inflating: tools/x86_64/bzip2
inflating: tools/x86_64/lz4
creating: tools/arm64/
inflating: tools/arm64/futility
inflating: tools/arm64/bootimg
inflating: tools/arm64/bzip2
inflating: tools/arm64/lz4
creating: tools/x86/
inflating: tools/x86/futility
inflating: tools/x86/bootimg
inflating: tools/x86/bzip2
inflating: tools/x86/lz4
creating: tools/arm/
inflating: tools/arm/futility
inflating: tools/arm/bootimg
inflating: tools/arm/bzip2
inflating: tools/arm/lz4
/tmp/updater[63]: .: config.sh: No such file or directory
Updater process ended with ERROR: 1
I:Install took 1 second(s).
Click to expand...
Click to collapse
Full recovery.log in the attachment.
Currently I'm stuck within a Samsung Logo Bootloop. What do I do wrong? Can I fix this?
I didn't found a similar problem within:
https://forum.xda-developers.com/t/...ll-twrp-on-exynos-samsung-after-2018.3747535/
Maybe someone can hint me in the right direction, please?
Thanks for any help.
Best regards
---
EDIT:
I successfully installed `RMM_Bypass_v3_corsicanu.zip` without an error, but `no-verity-opt-encrypt-6.1.zip` still doesn't work and the bootloop stays.
I tried to install the previous version `no-verity-opt-encrypt-6.0.zip` too. With no difference.
Download mode says:
CURRENT BINARY: Custom (0xc)
FRP LOCK: OFF
OEM LOCK: OFF
Secure Download: Enabled
CARRIER_ID: DBT

Just a suggestion
The no-verity zip - if failing try using earlier versions of twrp ( can be flashed using twrp or odin )
or use this no-verity zip. You will have to add ' quota ' to the downloaded zip file name.
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com

Thank you @spawnlives for your help.
Downgrading TWRP wasn't working. So I tried to install `Disable_Dm-Verity_quota_ForceEncrypt_11.02.2020.zip` from https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/ as suggested.
The S8 is booting again and Android has started successfully.