Grabbed
Superuser-3.1.3-arm-signed.zip from
Superuser
extracted the su and superuser.apk to root of where adb.exe is.
Some of this you can possibly cut out but I was basically just trying different things til I got it to work plus i wanted the su and superuser.apk on root of sdcard incase needed again.
I'm on win 8 pro so I had to set it to run as admin for adb to even work.
commands:
adb shell
su
mount -o rw,remount -t yaffs1 /dev/block/system /system
adb push su /sdcard/
adb push superuser.apk /sdcard/
adb shell
su
cp /sdcard/su /system/bin/
cp /sdcard/superuser.apk /system/app/
Don't have to reboot I don't think but always best to so you don't have to set read-only on system again. check to see if you have root with root check basic or whatever app you want.
Let me know if it works for you. I'd even consider starting a remote session and trying it if anyone would be up for it.
I'm pretty sure that's all I had to do.
I got root by using the files you listed but running a slightly different set of commands.
I initially thought that I did not have the su-backup file but while poking around I found it in the system folder (this is the most important piece!). I looked at Matt's script and stripped out the things that worked for me. I had thought earlier that even if you had a copy of the su-backup you still needed root to get it to work. I was wrong. Looking at the permission settings of su-backup in the system folder I noticed that the backup file has the same rights as the su file. So here are the commands that I used from Matt's script (some may not be needed but...) (fyi - I'm on Windows 7 Ultimate and ran Windows command prompt with administrator privileges: (for all instances of
/system/su-backup you'll need to substitute where your copy of su-backup is - IE. if it's in /system/usr/ you'll use
/system/usr/su-backup instead
adb kill-server > nul
adb start-server > nul
ping 1.1.1.1 -n 1 -w 500 > nul
adb wait-for-device devices > nul
adb shell "/system/su-backup -c 'mount -o rw,remount -t ext4 /dev/block/system /system'"
adb shell "/system/su-backup -c 'cp /system/su-backup /system/bin/su'"
adb shell "/system/su-backup -c 'chmod 6755 /system/bin/su'"
I then tested to see if I have su rights by going into adb shell and running "su":
adb shell
su
If you do not get any errors and just the shell prompt then that should mean that you have su rights. Then I did the following:
su -c 'cp /sdcard/su /system/xbin/su'
su -c 'cp /sdcard/Superuser.apk /system/app/Superuser.apk'
su -c 'chmod 6755 /system/xbin/su'
su -c 'chmod 644 /system/app/Superuser.apk' <----- I didn't do this but probably should
su -c 'rm /system/bin/su' <----- I didn't do this but probably should - some with more knowledge please let me know why this should be done - thx!
exit
exit
adb reboot
Or you can do it in the Windows Command line (dos prompt):
adb shell "su -c 'cp /sdcard/su /system/xbin/su'"
adb shell "su -c 'cp /sdcard/Superuser.apk /system/app/Superuser.apk'"
adb shell "su -c 'chmod 6755 /system/xbin/su'"
adb shell "su -c 'chmod 644 /system/app/Superuser.apk'"
adb shell "su -c 'rm /system/bin/su'"
adb reboot
After rebooting I ran my voodoo OTA and it asked for superuser rights and in voodoo it says that I have root and root privileges.
Hope this helps!!!
EDIT: Forgot to add that I copied the files su and Superuser.apk using ES Explorer to the root of my internal sdcard. Oh, and "Thanks" Matt!!!