Database Users

[Q] Troubleshooting rooting KF on Mac

Hi guys,
since the link to SU in this thread
http://forum.xda-developers.com/showthread.php?t=1443071
is no more available, i used this thread to root my KF
http://forum.xda-developers.com/showthread.php?t=1349613
i tried nearly everything i could find to root my KF, but still no success.
Following please find a log
--- DEVICE FOUND
--- pushing busybox
4133 KB/s (1075144 bytes in 0.254s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'Superuser.apk' to '/system/app/./Superuser.apk': Read-only file system
--- cleaning
--- rebooting
--- WAITING FOR DEVICE
3793 KB/s (3104805 bytes in 0.799s)
Error: Could not access the Package Manager. Is the system running?
All Done, Kindle Fire ROOTED!!!
Check out RootKindleFire.com for more cool hacks!
Click to expand...
Click to collapse

Geizt said:
Hi guys,
since the link to SU in this thread
http://forum.xda-developers.com/showthread.php?t=1443071
is no more available, i used this thread to root my KF
http://forum.xda-developers.com/showthread.php?t=1349613
i tried nearly everything i could find to root my KF, but still no success.
Following please find a log
Click to expand...
Click to collapse
It would be tremendously easier to root your KF in a Windows 7 Bootcamp environment.

Rooting just not working

Hello,
I have tried searching these forums for an eligible solution however all my attempted search terms came back with threads that did not quite explain what i am experiencing. Or for that matter were understandable by me. So excuse me in advance if you believe this question has been answered somewhere else. Instead of expressing your rage please feel free to send me a message pointing me in the right direction.
I have tried multiple ways to obtain root access to my tablet. Sadly all of them failed.
What I understand from this is that somehow there is not enough memory on a partition in order to succeed.
Here's the conflict Does one need root access to say, enlarge or change a partition?
DooMLoRD's method seemed to get the furthest but ultimately failed.
--- checking free space on /system
19 KB/s (439 bytes in 0.021s)
df: /mnt/.lfs: Function not implemented
--- Free space on /system : 0 bytes
--- NOT enough free space on /system!!!
--- making free space by removing Google Maps
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: Read-only file system
--- correcting permissions
Unable to chmod /system/xbin/busybox: Read-only file system
--- installing busybox
[1] Segmentation fault /system/xbin/bus...
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Click to expand...
Click to collapse
GT-P1000
Firmware version 2.3.6
Baseband version P1000XXJPZ
Kernel version 2.6.35.7
GINGERBREAD.XWJQ8

you are just simply in a wrong forum....
better find your answer on Original Galaxy Tab 7.0
http://forum.xda-developers.com/forumdisplay.php?f=752

edan1979 said:
you are just simply in a wrong forum....
better find your answer on Original Galaxy Tab 7.0
http://forum.xda-developers.com/forumdisplay.php?f=752
Click to expand...
Click to collapse
Valid point, Moving thread.

[OSX] stuck on rooting defy+

hi there,
today i got my first android phone motorola defy plus and i´m really stuck on rooting android the whole day.
first, i got ADB, installed and checked if it will find my phone. :good:
then, i downloaded "easy root toolkit and started it via terminal. this is what i got:
CONFIRM ALL THE ABOVE THEN
Press any key to continue...
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush"
cannot stat 'files/zergRush': No such file or directory
--- correcting permissions
Unable to chmod /data/local/tmp/zergRush: No such file or directory
--- executing zergRush
./data/local/tmp/zergRush: not found
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
cannot stat 'files/busybox': No such file or directory
--- correcting permissions
Unable to chmod /data/local/tmp/busybox: No such file or directory
--- remounting /system
/data/local/tmp/busybox: not found
--- copying busybox to /system/xbin/
/data/local/tmp/busybox: cannot open for read: No such file or directory
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
rm failed for /data/local/tmp/busybox, No such file or directory
--- pushing SU binary
cannot stat 'files/su': No such file or directory
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
cannot stat 'files/Superuser.apk': No such file or directory
--- cleaning
rm failed for *, No such file or directory
--- rebooting
ALL DONE!!!
Click to expand...
Click to collapse
i really got no chance to root my phone via windows pc so i was going to ask for help here.
my defy+ is running following software:
2.3.4.
Build: 4.5.1.-134_DFP-74
Baseband EPU93_U_00.60.00
thank you very much in advance for your help.

try this tool maybe will help you http://forum.xda-developers.com/attachment.php?attachmentid=1235958&d=1343854436
on my defy red bl4 it work
with this tool (if it work on your defy+) can check bl version, can root and can install bootmenu

I just got my Defy+ rooted by following this http://forum.xda-developers.com/showthread.php?t=1820282
Actually i couldnt get it rooted by my self, but i flashed SBF that was rooted allready.

vaserbanix said:
try this tool maybe will help you http://forum.xda-developers.com/attachment.php?attachmentid=1235958&d=1343854436
on my defy red bl4 it work
with this tool (if it work on your defy+) can check bl version, can root and can install bootmenu
Click to expand...
Click to collapse
yeah. great.
but this is an executable and osx does not support exe-files.
so both methods are not suitable for OSX

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

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