Database Users

[Q] Rooting Problem, Won't mount. Line needs correction.

Hi, I am currently trying to room my Blade but I get this problem in cmd
$ exit
exit
C:\android-sdk-windows\platform-tools>adb kill-server
* server not running *
C:\android-sdk-windows\platform-tools>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\android-sdk-windows\platform-tools>adb shell
# mount -o rw,remount /system
mount -o rw,remount /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# exit
exit
C:\android-sdk-windows\platform-tools>adb push su /system/xbin/
failed to copy 'su' to '/system/xbin/': Is a directory
Click to expand...
Click to collapse
As you can see, I am unable to copy over su to system/xbin.
Does it have to do with the mount command line?

you dont need to use the mount command at all, you can just type 'adb remount' instead of 'adb shell', or if you want to use the mount command then the correct line is this:
mount -o remount,rw /dev/block/mtdblock5 /system
you were missing the device part of the mount command line, it's /dev/block/mtdblock5 for /system on the blade.
you've just given me an idea to post a rooting guide, there is an easier & better way, using adb, fastboot, clockworkmod & superuser.

I fixed it by just getting z4root and rom manager for clockworkmod.

pankaka said:
I fixed it by just getting z4root and rom manager for clockworkmod.
Click to expand...
Click to collapse
Cool. I've written a rough rooting guide using adb & fastboot here: http://forum.xda-developers.com/showthread.php?t=1319257
z4root uses a root exploit that only works on older versions of android. Some versions of the blade sold in some countries use newer versions of Android (2.2.2 or 2.3.5) that have that vulnerability fixed. I wrote a guide that will work on any blade, because it doesn't use any root exploits - it's bad that z4root worked, you need to update your rom!
The blade has an unlocked bootloader, so you can install clockworkmod using 3 commands
Code:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-5.0.2.0-blade.img
fastboot reboot
Then use clockworkmod to install the superuser zip file, or custom rom.

[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.

[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

[Q] G2 root failed

this is the msg after I tried to root my G2
Mounting system RW and pushing SU, then remounting system RO again
mount: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
Unable to chown /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
mount: Operation not permitted
Installing superuser
4862 KB/s (1468798 bytes in 0.295s)
pkg: /data/local/tmp/superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
***************************************************
Done.
***************************************************
Please check the above for any errors and let me know if you run into any issues
.
Enjoy your phone!
Press any key to continue . . .
and another 1
C:\Users\tyger\Desktop\lgroot>adb devices
List of devices attached
016ca36f4e46a587 device
C:\Users\tyger\Desktop\lgroot>adb devices
List of devices attached
C:\Users\tyger\Desktop\lgroot>adb devices
List of devices attached
016ca36f4e46a587 device
C:\Users\tyger\Desktop\lgroot>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $ id
id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1009
(mount),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt)
,3003(inet),3006(net_bw_stats)
[email protected]:/ $ id
I did everything I can, installed driver, restarted the phone and PC, just dont know whats going on. plz help.
thanks

Try downloading and running SuperSU. It will prompt you to update binaries, if it goes well, the phone is already rooted.

Have you used a root checker app? If you let us know what variant of the phone you have

tbishop91 said:
Have you used a root checker app? If you let us know what variant of the phone you have
Click to expand...
Click to collapse
I have the same issue. Says it isn't rooted with CPU-Z. LG D802 G2 32GB

whats ur version？ d802？

tengfeilee said:
whats ur version？ d802？
Click to expand...
Click to collapse
yeah.

[Q:SOLVED] su : not found; rooted without root access

Hello.
Some of you might already have heard this question, but didn't seem to find an specific answer for my phone > Canadian S4 SGH I377M running Android 4.3
After the first time, I've tried installing a custom recovery (after rooting with motochopper). I've got an error because I wasn't granted root access. Tried to see with an app : no root access neither. Verified with a terminal : no root access. Tried re-rooting, it shows the following message :
Code:
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *[*] Device found.[*] Pushing exploit...
4439 KB/s (1283460 bytes in 0.282s)[*] Pushing root tools...
4758 KB/s (366952 bytes in 0.075s)
3837 KB/s (1867568 bytes in 0.475s)
2829 KB/s (1578585 bytes in 0.544s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS][*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.[*] Cleaning up...[*] Exploit complete. Press enter to reboot and exit.
What is there left to do?

gr4v1ty said:
Hello.
Some of you might already have heard this question, but didn't seem to find an specific answer for my phone > Canadian S4 SGH I377M running Android 4.3
After the first time, I've tried installing a custom recovery. I've got an error because I wasn't granted root access. Tried to see with an app : no root access neither. Verified with a terminal : no root access. Tried re-rooting, it shows the following message :
Code:
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *[*] Device found.[*] Pushing exploit...
4439 KB/s (1283460 bytes in 0.282s)[*] Pushing root tools...
4758 KB/s (366952 bytes in 0.075s)
3837 KB/s (1867568 bytes in 0.475s)
2829 KB/s (1578585 bytes in 0.544s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS][*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.[*] Cleaning up...[*] Exploit complete. Press enter to reboot and exit.
What is there left to do?
Click to expand...
Click to collapse
What methods have you tried? Did you try the Chainfire Auto Root?

DeadlySin9 said:
What methods have you tried? Did you try the Chainfire Auto Root?
Click to expand...
Click to collapse
It was motochopper. Sorry forgot to mention. Also here the output of the root checker pro app
Code:
Root Access is not properly configured or was not granted.
Super User Application Status:
Superuser application - is NOT installed.
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your SGH-I337M device by Root Checker Pro version 1.3.5 from joeykrim in the Android Market - http://goo.gl/NcnHn
EDIT : Solved by using CF-Auto-root : http://forum.xda-developers.com/showthread.php?t=2293800
Sent from my SGH-I337M using Tapatalk