• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Avail] su to sd card

S

silent_hunter

Newbie
I am very new to all of this:

I am trying to root a straighttalk ZTE Merit, so I can have extra memory. I have tried both http://androidforums.com/avail-all-things-root/566407-root-zte-z990g-merit-avail-variant.html and http://androidforums.com/avail-all-...oot-flash-recovery-install-new-rom-links.html

I get to the reboot and then try and push the su and file can not be found. I know I am doing somthing wrong, but do not have the experience to figure it out. I have read about moving the su right to the sd card from the computer, but can not find the how to on it. Can I just move it to the sd card before I start the root process? If I do move it right to the sd card do I move the zip file or the extracted files?

I have also post a help question in JCase thread http://androidforums.com/avail-all-things-root/566407-root-zte-z990g-merit-avail-variant-2.html

Thanks,
Rodney
 
If you would have read the whole thread instructions are posted several times. You can skip to page 5&6 if you want to cut down on your reading.
 
Down load the su file and install it to your sd card. Or place it in your comp, or with the sync cable. Both ways work just fine. Go to the play store and download es file explorer. Use this app to copy the su file in the sd card and then swipe around to the /system/xbin/ install the su file there. It shoud have a little pop up that the file was placed there. I dont know the correct wording but it will tell you yes or no its there and its ok. Then you should be able finsh up the rest the rooting from here.
 
I still can not get the root. I downloaded es file explorer and put the su folder on my sd card. I could not find the /system/xbin/.

I also reset the phone and tried to root it again. everything in the first part went well. I think, please check:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Daddy>cd C:\android-sdk
C:\android-sdk>adb shell
$ mkdir /data/local/logs
mkdir /data/local/logs
$ mkdir /data/local/logs/kernel
mkdir /data/local/logs/kernel
$ am start -a android.intent.action.MAIN -n com.zte.emode/.logset
am start -a android.intent.action.MAIN -n com.zte.emode/.logset
Starting: Intent { act=android.intent.action.MAIN cmp=com.zte.emode/.logset }
$ ls -l /data/local/logs/kernel/log_kernel.txt
ls -l /data/local/logs/kernel/log_kernel.txt
-rwxrwxrwx root root 131072 2012-09-07 01:50 log_kernel.txt
$ rm /data/local/logs/kernel/log_kernel.txt
rm /data/local/logs/kernel/log_kernel.txt
$ ln -s /data/local.prop /data/local/logs/kernel/log_kernel.txt
ln -s /data/local.prop /data/local/logs/kernel/log_kernel.txt
$ ls -l /data/local.prop
ls -l /data/local.prop
-rw-rw-rw- root root 1134 2012-09-07 01:51 local.prop
$ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
$ exit
exit
C:\android-sdk>adb reboot
C:\android-sdk>

I then opened the command promp in the su folder that I placed in the tools folder and it all seemed to work. when I checked for root with root checker itsaid I did not have root.
 
mikec628 said:
Down load the su file and install it to your sd card. Or place it in your comp, or with the sync cable. Both ways work just fine. Go to the play store and download es file explorer. Use this app to copy the su file in the sd card and then swipe around to the /system/xbin/ install the su file there. It shoud have a little pop up that the file was placed there. I dont know the correct wording but it will tell you yes or no its there and its ok. Then you should be able finsh up the rest the rooting from here.
Click to expand...

Can you get there without having root access?

If you just put it on your top layer of you SD card you should be able to finish from there. Open SDK tools. From the start button in search type cmd. Right click cmd & run as admin. Run these commands:

adb shell
*press "enter"

su
*press "enter"

flash_image recovery /sdcard/
Recovery.img
*press "enter"

reboot recovery
*press "enter"

Now clear the cashe files & reboot. Open the Superuser app. You should now have root.
 
I did everything over agian here is what I did.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Daddy>adb shell
$ mkdir /data/local/logs
mkdir /data/local/logs
$ mkdir /data/local/logs/kernel
mkdir /data/local/logs/kernel
$ am start -a android.intent.action.MAIN -n com.zte.emode/.logset
am start -a android.intent.action.MAIN -n com.zte.emode/.logset
Starting: Intent { act=android.intent.action.MAIN cmp=com.zte.emode/.logs
$ ls -l /data/local/logs/kernel/log_kernel.txt
ls -l /data/local/logs/kernel/log_kernel.txt
-rwxrwxrwx root root 107955 2012-09-07 13:12 log_kernel.txt
$ rm /data/local/logs/kernel/log_kernel.txt
rm /data/local/logs/kernel/log_kernel.txt
$ ln -s /data/local.prop /data/local/logs/kernel/log_kernel.txt
ln -s /data/local.prop /data/local/logs/kernel/log_kernel.txt
$ ls -l /data/local.prop
ls -l /data/local.prop
/data/local.prop: No such file or directory
$ ls -l /data/local.prop
ls -l /data/local.prop
-rw-rw-rw- root root 4794 2012-09-07 13:13 local.prop
$ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
$ exit
exit
C:\Users\Daddy>adb reboot
C:\Users\Daddy>

and then to move the su file

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Daddy>cd c:\android-sdk\tools\
c:\android-sdk\tools>adb shell
# su
su
su: permission denied
# exit
exit
c:\android-sdk\tools>cd c:\android-sdk\tools\su
c:\android-sdk\tools\su>adb remount
remount succeeded
c:\android-sdk\tools\su>adb push su /system/xbin/su
699 KB/s (22364 bytes in 0.031s)
c:\android-sdk\tools\su>adb shell chown 0.0 /system/xbin/su
c:\android-sdk\tools\su>adb shell chmod 06755 /system/xbin/su
c:\android-sdk\tools\su>adb shell rm /data/local.prop
c:\android-sdk\tools\su>adb shell rm -r /data/local/logs
c:\android-sdk\tools\su>adb reboot
c:\android-sdk\tools\su>

After this step I downloaded superuser, and in the superuser app it has a check box in SU BINARY NOT FOUND OUTDATED BINARY NOTIFICATION.

What do I do from here?

Thanks,
Rodney
 
Still not working, the first part goes fine. Then this is what I get when I try and load the su.

Please take a look and tell me if you see anything that I am doing wrong. the platform tools only has the su file in it, without a folder.


C:\android-sdk\platform-tools>adb remount
adb server is out of date. killing...
* daemon started successfully *
remount succeeded
C:\android-sdk\platform-tools>adb push su /system/xbin/su
199 KB/s (22364 bytes in 0.109s)
C:\android-sdk\platform-tools>adb shell chown 0.0 /system/xbin/su
C:\android-sdk\platform-tools>adb shell chmod 06755 /system/xbin/su
C:\android-sdk\platform-tools>adb shell rm /data/local.prop
C:\android-sdk\platform-tools>adb shell rm -r /data/local/logs
C:\android-sdk\platform-tools>adb reboot
C:\android-sdk\platform-tools>


Could I have screwed something up by pushing the folder earlier? is the factory reset the only way to clear everything? the phone is only a few days old and I only have my google backup stuff on it currently.

 
look at this too. Does this look like the file is where it should be?

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Daddy>adb shell
$ cd /system/xbin/
cd /system/xbin/
$ ls
ls
su
dexdump
$ su
su
su: permission denied
$
 
Ok, try this:
> adb shell
$ rm -r /system/xbin/su
(if this comes back as not a directory, then try rm /system/xbin/su)
$ exit
> adb push su (the file itself) /system/xbin/su
> adb shell
$ chown 0.0 /system/xbin/su
$ chmod (whatever value the guide gives you) /system/xbin/su
$ su (this should switch $ to #)
 
first attempt:

C:\android-sdk\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
# rm -r /system/xbin/su
rm -r /system/xbin/su
rm failed for /system/xbin/su, Read-only file system
# rm /system/xbin/su
rm /system/xbin/su
rm failed for /system/xbin/su, Read-only file system
#
 
Thank you so much Motorhead1991, I HAVE ROOT!


C:\android-sdk\platform-tools>adb remount
remount succeeded
C:\android-sdk\platform-tools>adb shell
# rm -r /system/xbin/su
rm -r /system/xbin/su
# exit
exit
C:\android-sdk\platform-tools>adb push su /system/xbin/su
279 KB/s (22364 bytes in 0.078s)
C:\android-sdk\platform-tools>adb shell chown 0.0 /system/xbin/su
C:\android-sdk\platform-tools>adb shell chmod 06755 /system/xbin/su
C:\android-sdk\platform-tools>adb shell rm /data/local.prop
C:\android-sdk\platform-tools>adb shell rm -r /data/local/logs
C:\android-sdk\platform-tools>adb reboot
C:\android-sdk\platform-tools>
 
how to move or install su binary from the sd card to the system area ... my phone doesnt have the su binary ... i dont know why my phone doesnt have it ... does my phone broken..
 
You must log in or register to reply here.
Back
Top Bottom