Quote:
Originally Posted by Tordre
I got it working under linux after, my udev settings were wrong. You can just use the bat file provided and make proper conversions or try below copy and paste this code block into a file in the same folder as runme.bat, save it as runme.sh, chmod +x runme.sh, and then ./runme.sh to run it. This assumes you have the adk installed in linux, and your path includes where adb is.
Code:
echo "---------------------------------------------------------------"
echo " Easy rooting toolkit (v4.0)"
echo " created by DooMLoRD"
echo " using exploit zergRush (Revolutionary Team)"
echo " Credits go to all those involved in making this possible!"
echo "---------------------------------------------------------------"
echo "[*] This script will:"
echo " (1) root ur device using latest zergRush exploit (21 Nov)"
echo " (2) install Busybox (1.18.4)"
echo " (3) install SU files (binary: 3.0.3 and apk: 3.0.6)"
echo " (4) some checks for free space, tmp directory "
echo " (will remove Google Maps if required)"
echo "[*] Before u begin: "
echo " (1) make sure u have installed adb drivers for ur device"
echo " (2) enable \"USB DEBUGGING\" "
echo " from (Menu\Settings\Applications\Development)"
echo " (3) enable \"UNKNOWN SOURCES\""
echo " from (Menu\Settings\Applications)"
echo " (4) [OPTIONAL] increase screen timeout to 10 minutes"
echo " (5) connect USB cable to PHONE and then connect to PC"
echo " (6) skip \"PC Companion Software\" prompt on device"
echo "---------------------------------------------------------------"
echo " CONFIRM ALL THE ABOVE THEN "
echo "--- STARTING ----"
echo "--- WAITING FOR DEVICE"
adb wait-for-device
echo "--- creating temporary directory"
adb shell "cd /data/local && mkdir tmp"
echo "--- cleaning"
adb shell "cd /data/local/tmp/"
echo "--- pushing zergRush"
adb push files/zergRush /data/local/tmp/.
echo "--- correcting permissions"
adb shell "chmod 777 /data/local/tmp/zergRush"
echo "--- executing zergRush"
adb shell "./data/local/tmp/zergRush"
echo "--- WAITING FOR DEVICE TO RECONNECT"
echo "if it gets stuck over here for a long time then try:"
echo " disconnect usb cable and reconnect it"
echo " toggle "USB DEBUGGING" (first disable it then enable it)"
adb wait-for-device
echo "--- DEVICE FOUND"
echo "--- pushing busybox"
adb push files/busybox /data/local/tmp/.
echo "--- correcting permissions"
adb shell "chmod 755 /data/local/tmp/busybox"
echo "--- remounting /system"
adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
echo "--- checking free space on /system"
adb push files/makespace /data/local/tmp/.
adb shell "chmod 777 /data/local/tmp/makespace"
adb shell "./data/local/tmp/makespace"
echo "--- copying busybox to /system/xbin/"
adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
echo "--- correcting ownership"
adb shell "chown root.shell /system/xbin/busybox"
echo "--- correcting permissions"
adb shell "chmod 04755 /system/xbin/busybox"
echo "--- installing busybox"
adb shell "/system/xbin/busybox --install -s /system/xbin"
adb shell "rm -r /data/local/tmp/busybox"
echo "--- pushing SU binary"
adb push files/su /system/bin/su
echo "--- correcting ownership"
adb shell "chown root.shell /system/bin/su"
echo "--- correcting permissions"
adb shell "chmod 06755 /system/bin/su"
echo "--- correcting symlinks"
adb shell "rm /system/xbin/su"
adb shell "ln -s /system/bin/su /system/xbin/su"
echo "--- pushing Superuser app"
adb push files/Superuser.apk /system/app/.
echo "--- cleaning"
adb shell "cd /data/local/tmp/"
echo "--- rebooting"
adb reboot
echo "ALL DONE!!!"
Also if you are going for a virtual method, if you are using windows 7 pro or ultimate you could use XP mode that is free you don't need to worry about getting an XP license (provided for free from microsoft), and has USB emulation mode.
EDIT Just tried to get it working on windows 7 again and it worked. I went into the device manager and uninstalled the mass storage device with the kobo vendor ID 0x2237, then when I plugged it back in it caused windows to re-install all the drivers for the device including the ADB drivers. You need to have the device plugged in to uninstall its drivers. muskiestallker try this.
Speculation I have a feeling this is occurring because of certain android phone manufacturers improperly installing drivers. |
Many thanks for the script and info,.It took awhile to figure out where it belonged in my system and get it working. I already had adb installed for my Acer A500. I also want to thank danifunker and the rest of the group that worked on this. After Kobo bricked my wife's stock Kobo Vox I figured it needs to be hacked and backed up. All done. Had to relearn Linux to do it and I am going to keep at Linux and Android.