Rooting the Galaxy Player (All Versions) (Windows, Mac, Linux)

apapousek

Senior Member
Jul 18, 2011
308
266
0
Hello All,

I just bought a Galaxy Player yesterday and wanted to root. Okay, I thought, to XDA I go. It seems the general consensus here is to use SuperOneClick.

While the SuperOneClick method may work for most people running Windows, it's fairly annoying for those in the Linux and Mac crowd. It sometimes may work after installing the correct mono application and libraries, but that's quite a bit to download.

So, I thought it'd be nice to have only one thing to download, extract, and run the root all of the Galaxy Players on all platforms.

Anyway, I based this root on DooMLoRD's easy rooting toolkit. It uses the zergRush exploit, and will install Busybox, su binaries, and the Superuser apk. It should run on Linux, Mac, and Windows fine.

Does NOT work with Android 2.2.x, upgrade to 2.3.x using KIES.

Needed:
Either:
A Linux or Mac computer with adb installed and in the path (executable from terminal by typing in 'adb')
For Macs, I recommend using Homebrew to install. Install Homebrew, then type
Code:
brew install android-sdk
or
A Windows computer

The rootme files (available in tar.gz or zip)
::Mod edit::
Try this link http://www.mediafire.com/?hixwwt1bes9hmiu

Extract:
On Linux/Mac: tar -zxvf rootme.tar.gz in a terminal, or using a graphical utility
On Windows: Just use 7z, or the built in extraction tool (or whatever floats your boat)

Run:

Linux/Mac:
Open terminal and go to the root directory:
cd root/
Make rootme.sh executable:
chmod +x rootme.sh
Execute:
./rootme.sh

Windows:
Open up cmd (Using CTRL+R or from Vista/7's start menu)
cd to the "root" directory
Run runme.bat (You may have to run cmd as Administrator, depending on your version of Windows)

Compatible Operating Systems:

Linux 32: unknown
Linux 64: compatible

Windows 32: compatible (thanks nukleuzN)
Windows 64: compatible (thanks kiwijunglist)

Mac OS X: unknown

Compatible Devices:

Galaxy Player 4.0 16 GB: unknown
Galaxy Player 4.0 US 8 GB: unknown
Galaxy Player 4.0 International 8 GB: unknown

Galaxy Player 5.0 16 GB: unknown
Galaxy Player 5.0 US 8 GB (YP-G70XAA): compatible
Galaxy Player 5.0 International 8 GB: unknown

Galaxy S WiFi 5.0 8 GB (YP-G70CW): compatible

Please test and post your results.
 
Last edited by a moderator:

Rasa11

Senior Member
Dec 24, 2011
1,079
578
0
Lunar Base VII, Sector IX
Very good! Just what I needed. :)
I'm strictly Linux, so all these posts and tools that "require windows" really bug me.
(and always kinda baffle me..) , Mass amounts of people hacking on windows machines? lol
Like, people can root/hack devices like this..
but haven't moved up from windows? :O

Going to give this a try on my SGP 4.0 (US) soon.
Will let you know. :)

P.s. If I ef something up..
or if something just happens to mess up or break..
Is there an easy way to reverse it? lol

Much appreciated dude. :)
 
  • Like
Reactions: weehooherod2

apapousek

Senior Member
Jul 18, 2011
308
266
0
Very good! Just what I needed. :)
I'm strictly Linux, so all these posts and tools that "require windows" really bug me.
(and always kinda baffle me..) , Mass amounts of people hacking on windows machines? lol
Like, people can root/hack devices like this..
but haven't moved up from windows? :O

Going to give this a try on my SGP 4.0 (US) soon.
Will let you know. :)

P.s. If I ef something up..
or if something just happens to mess up or break..
Is there an easy way to reverse it? lol

Much appreciated dude. :)
Glad to see another strictly Linux person here. I'm working on an unrooting script. As far as recovery goes, Meticulus has made a partial Odin recovery. Oh. 32 or 64 bit linux?
 

apapousek

Senior Member
Jul 18, 2011
308
266
0
Awesome! :)
Thanks man.

my main machine is 32 bit. (Thinkpad)
I do have a desktop that runs 64 bit but I hardly ever use it or turn it on.
Might actually go to my sister soon if she doesnt get her laptop back. lol
Wonderful! Added to list! Thanks!
 

tcat007

Senior Member
Jul 3, 2011
5,397
1,998
253
Austin, TX
Going to try on W7-64 this weekend. What's the "SystemUI.apk" for?

Connect USB cable - turn on USB debugging - and click runme.batt (within the "root" folder)..... Right?

I rooted my Optimus-V with Gingerbreak, no computer. Just want to be sure I do this right.
 

apapousek

Senior Member
Jul 18, 2011
308
266
0
Going to try on W7-64 this weekend. What's the "SystemUI.apk" for?

Connect USB cable - turn on USB debugging - and click runme.batt (within the "root" folder)..... Right?

I rooted my Optimus-V with Gingerbreak, no computer. Just want to be sure I do this right.
SystemUI.apk is from another post, someone messed their copy up, so I gave them mine. But yea, that's what you do. I rooted my Iconia in a similar manner to your Optimus-V. Make sure your phone has debugging mode enabled, though.
 

G.I.Geoff

Senior Member
Apr 5, 2011
129
11
0
Atlanta
Very good. Liking this. But to the stupid comment about not moving up from windows? Windows seven is great. it is my favorite operating system. With Linux falling slightly behind. It's the people who hack from OSX that confuse me. I used one. Was given one as a gift. And sold it after a month. Some operating systems really blow.

/sig
"What kinda phone do you have?" "Epic." "I see that! And I want one, so what's the name?" "epic." "no, I know your phone is epic, what kind of phone is it?!" "legendary?"
 

apapousek

Senior Member
Jul 18, 2011
308
266
0
Very good. Liking this. But to the stupid comment about not moving up from windows? Windows seven is great. it is my favorite operating system. With Linux falling slightly behind. It's the people who hack from OSX that confuse me. I used one. Was given one as a gift. And sold it after a month. Some operating systems really blow.

/sig
"What kinda phone do you have?" "Epic." "I see that! And I want one, so what's the name?" "epic." "no, I know your phone is epic, what kind of phone is it?!" "legendary?"
I personally prefer it in this order: Linux > Mac > Windows. Anyone who uses Windows for "hacking" is foolish. Linux has the best compilers, and the best command shell. Mac is able to use these technologies as well. If you just learned a bit more about computers, you'd know this. Anyway, this is a dev thread, not a flame war.
 

Rasa11

Senior Member
Dec 24, 2011
1,079
578
0
Lunar Base VII, Sector IX
I personally prefer it in this order: Linux > Mac > Windows. Anyone who uses Windows for "hacking" is foolish. Linux has the best compilers, and the best command shell. Mac is able to use these technologies as well. If you just learned a bit more about computers, you'd know this. Anyway, this is a dev thread, not a flame war.
+1

Exactly.
 

G.I.Geoff

Senior Member
Apr 5, 2011
129
11
0
Atlanta
I personally prefer it in this order: Linux > Mac > Windows. Anyone who uses Windows for "hacking" is foolish. Linux has the best compilers, and the best command shell. Mac is able to use these technologies as well. If you just learned a bit more about computers, you'd know this. Anyway, this is a dev thread, not a flame war.
To tell the truth I despise Mac. And all you gotta do is look and. There are great compilers for both Linux and windows. I still put windows as my favorite. Linux barely behind it. And don't tell me to learn more. I build computers. and I study them. So honestly from my informed opinion, windows is the best. lol, but this is very off topic. Lol I'm not trying to flame

/sig
"What kinda phone do you have?" "Epic." "I see that! And I want one, so what's the name?" "epic." "no, I know your phone is epic, what kind of phone is it?!" "legendary?"
 
Last edited:

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,095
25,085
0
Owego, NY
There are, to my knowledge, no toolchains for Windows capable of building Android, and I don't think any sane person ever tries to compile a Linux kernel using cygwin + codesourcery for Windows.

If you want to do Android development, Linux is the way to go. Linux is the first-tier supported platform for AOSP. MacOS is doable but often has all sorts of weird "gotchas". Windows is completely unsupported for any sort of Android platform work.
 

apapousek

Senior Member
Jul 18, 2011
308
266
0
To tell the truth I despise Mac. And all you gotta do is look and. There are great compilers for both Linux and windows. I still put windows as my favorite. Linux barely behind it. And don't tell me to learn more. I build computers. and I study them. So honestly from my informed opinion, windows is the best. lol, but this is very off topic. Lol I'm not trying to flame

/sig
"What kinda phone do you have?" "Epic." "I see that! And I want one, so what's the name?" "epic." "no, I know your phone is epic, what kind of phone is it?!" "legendary?"
Puttig together x86 hardware is a bit differet than using a compiler. I would know, I do both.

There are, to my knowledge, no toolchains for Windows capable of building Android, and I don't think any sane person ever tries to compile a Linux kernel using cygwin + codesourcery for Windows.

If you want to do Android development, Linux is the way to go. Linux is the first-tier supported platform for AOSP. MacOS is doable but often has all sorts of weird "gotchas". Windows is completely unsupported for any sort of Android platform work.
And you beat me to the punch by 10 minutes, great.
 

nukleuzN

Senior Member
Jun 1, 2009
134
6
0
Tromsø
Code:
 ---------------------------------------------------------------
	              Easy rooting toolkit (v1.0)
                    created by DooMLoRD
			  edited by Anthony Papousek
         using exploit zergRush (Revolutionary Team)
    Credits go to all those involved in making this possible!
 ---------------------------------------------------------------
  [*] This script will:
      (1) Root your device using the zergRush exploit
      (2) Install Busybox (1.18.4)
      (3) Install SU ./files (3.0.5)
  [*] Before you begin:   
      (1) Make sure you have adb in your path and the correct udev rules for your device
      (2) Enable USB DEBUGGING 
            from (Menu\Settings\Applications\Development)
      (3) Enable UNKNOWN SOURCES
            from (Menu\Settings\Applications)
      (4) [OPTIONAL] Increase screen timeout to 10 minutes
      (5) Connect USB cable to PHONE and then connect to PC
 ---------------------------------------------------------------
 Connect Device to begin 
 --- STARTING ----
 --- Cleaning
rm failed for *, No such file or directory
 --- Pushing zergRush
331 KB/s (23052 bytes in 0.067s)
 --- Correcting permissions of zergRush on device
 --- Executing zergRush and giving primary root access over adb
 		This may take a while

[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.

[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.

[+] Found a Froyo ! 0x00017108
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
 --- 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
2290 KB/s (1075144 bytes in 0.458s)
 --- 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 './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
 Your device should now be rooted. 
 
 It's time to update your su binary. 
 Open the Superuser app, go to Preferences (Menu\Preferences),
 and hit Su Binary v3.X (3.0, in this case). When prompted, 
 update to the newest version of the su binary. 
 Congratulations, you've successfully rooted! 
 If something went wrong, pm apapousek on the XDA Forums
 or email [email protected]
Darn...

I have tried
  • Disconnect usb cable and reconnect it
  • Toggle USB DEBUGGING (first disable it then enable it)

This is my udev:
Code:
$ sudo vi /etc/udev/rules.d/51-android.rules
PHP:
UBSYSTEM=="usb", ATTR{idVendor}=="04E8", MODE="0666", GROUP="plugdev"
Code:
$ sudo chmod a+r /etc/udev/rules.d/51-android.rules
$ sudo restart udev
adb:
Code:
[email protected]:~/Downloads/root$ adb devices
List of devices attached 
c089041f0e4e939e	device
Phone
Model: YP-G70
Firmware: 2.2.2 (Stock, ofcourse..)
Kernel v.: 2.6.32.9 [email protected] #1
Build no.: FROYO.XXKG1

Computer
OS: Ubuntu 11.10 64-Bit
Hardware: Lenovo Thinkpad X220i

Anyone knows the trick? ;-)
 

apapousek

Senior Member
Jul 18, 2011
308
266
0
Code:
 ---------------------------------------------------------------
	              Easy rooting toolkit (v1.0)
                    created by DooMLoRD
			  edited by Anthony Papousek
         using exploit zergRush (Revolutionary Team)
    Credits go to all those involved in making this possible!
 ---------------------------------------------------------------
  [*] This script will:
      (1) Root your device using the zergRush exploit
      (2) Install Busybox (1.18.4)
      (3) Install SU ./files (3.0.5)
  [*] Before you begin:   
      (1) Make sure you have adb in your path and the correct udev rules for your device
      (2) Enable USB DEBUGGING 
            from (Menu\Settings\Applications\Development)
      (3) Enable UNKNOWN SOURCES
            from (Menu\Settings\Applications)
      (4) [OPTIONAL] Increase screen timeout to 10 minutes
      (5) Connect USB cable to PHONE and then connect to PC
 ---------------------------------------------------------------
 Connect Device to begin 
 --- STARTING ----
 --- Cleaning
rm failed for *, No such file or directory
 --- Pushing zergRush
331 KB/s (23052 bytes in 0.067s)
 --- Correcting permissions of zergRush on device
 --- Executing zergRush and giving primary root access over adb
 		This may take a while

[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.

[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.

[+] Found a Froyo ! 0x00017108
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
 --- 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
2290 KB/s (1075144 bytes in 0.458s)
 --- 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 './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
 Your device should now be rooted. 
 
 It's time to update your su binary. 
 Open the Superuser app, go to Preferences (Menu\Preferences),
 and hit Su Binary v3.X (3.0, in this case). When prompted, 
 update to the newest version of the su binary. 
 Congratulations, you've successfully rooted! 
 If something went wrong, pm apapousek on the XDA Forums
 or email [email protected]
Darn...

I have tried
  • Disconnect usb cable and reconnect it
  • Toggle USB DEBUGGING (first disable it then enable it)

This is my udev:
Code:
$ sudo vi /etc/udev/rules.d/51-android.rules
PHP:
UBSYSTEM=="usb", ATTR{idVendor}=="04E8", MODE="0666", GROUP="plugdev"
Code:
$ sudo chmod a+r /etc/udev/rules.d/51-android.rules
$ sudo restart udev
adb:
Code:
[email protected]:~/Downloads/root$ adb devices
List of devices attached 
c089041f0e4e939e	device
Phone
Model: YP-G70
Firmware: 2.2.2 (Stock, ofcourse..)
Kernel v.: 2.6.32.9 [email protected] #1
Build no.: FROYO.XXKG1

Computer
OS: Ubuntu 11.10 64-Bit
Hardware: Lenovo Thinkpad X220i

Anyone knows the trick? ;-)
Open up rootme.sh with a text editor. Try using its steps one by one, typing the commands into your bash shell. After running the zergrush exploit, run "adb shell" and see if you get a # or a $.
 

nukleuzN

Senior Member
Jun 1, 2009
134
6
0
Tromsø
Hi,

Thanks for your reply. Here is the result ($ instead of #):

Code:
[email protected]:~/Downloads/root$ adb wait-for-device
[email protected]:~/Downloads/root$ adb shell "cd /data/local/tmp/; rm *"
rm failed for *, No such file or directory
[email protected]:~/Downloads/root$ adb push files/zergRush /data/local/tmp/
378 KB/s (23052 bytes in 0.059s)
[email protected]:~/Downloads/root$ adb shell "chmod 777 /data/local/tmp/zergRush"
[email protected]:~/Downloads/root$ adb shell "/data/local/tmp/zergRush"

[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.

[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.

[+] Found a Froyo ! 0x00017108
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
[email protected]:~/Downloads/root$ adb shell
$     
$ exit
[email protected]:~/Downloads/root$