Related
Everytime I run the .bat for the my prompt reads Your device is a Nook Tablet meaning we can continue!
[/quote]Now, just making sure you WANT to root it!
[-] Cannot copy boomsh.: Permission denied
Installing superuser and su...
2313 KB/s (843503 bytes in 0.356s)
1819 KB/s (22364 bytes in 0.012s)
failed to copy 'root-files\su' to '/system/bin/su': Read-only file system
Installing and setting up busybox...
failed to copy 'root-files\busybox' to '/system/xbin//busybox': Read-only file s
ystem
1963 KB/s (12066 bytes in 0.006s)
[quote/]
I tried to root when in version 1.4.0 then downgraded back to 1.4.0 when the OTA hit and tried once more only to get the same error. Tried to cmod the entire system folder from both an adb shell and android terminal. any ideas guy?
Do you have USB Debugging enabled (in both boxes)?
Yea, its shows my device in the beginning of the script. =\
I think you need to run the runmefirst. bat then apply the other .bat to root
Sent from my LG GT540 Swift using XDA App
Did the runmefirst.bat.
logoguy said:
Did the runmefirst.bat.
Click to expand...
Click to collapse
ok then if that didn't work then its 100% drivers issue check this its the best step by step tutorial i have found , check step 3 or better the whole tut
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.
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.
Moved to Dev and stickied
Rasa11 said:
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.
Click to expand...
Click to collapse
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?
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
Rasa11 said:
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
Click to expand...
Click to collapse
Wonderful! Added to list! Thanks!
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.
tcat007 said:
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.
Click to expand...
Click to collapse
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.
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?"
G.I.Geoff said:
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?"
Click to expand...
Click to collapse
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.
apapousek said:
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.
Click to expand...
Click to collapse
+1
Exactly.
apapousek said:
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.
Click to expand...
Click to collapse
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?"
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.
G.I.Geoff said:
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?"
Click to expand...
Click to collapse
Puttig together x86 hardware is a bit differet than using a compiler. I would know, I do both.
Entropy512 said:
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.
Click to expand...
Click to collapse
And you beat me to the punch by 10 minutes, great.
I build computers. and I study them. So honestly from my informed opinion, windows is the best.
Click to expand...
Click to collapse
lol, too funny.
FYI
Win7 64bit
Internation Galaxy S Wifi 5" running FROYO
Extracted to desktop/root
tried runme.bat as administrator
Didn't work gave "File/path not found errors"
Then
extracted to c:\root\
ran command prompt
cd c:\root\
runme.bat
-> Unable to mount system error
--
I successfully rooted by flashing a ROM that was pre-rooted
http://forum.xda-developers.com/showthread.php?t=1446774
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? ;-)
nukleuzN said:
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? ;-)
Click to expand...
Click to collapse
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 $.
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$
Can I suggest you flash a room that is pre rooted, this worked for me?....
Hi, I am trying to root my YP-GB1 using the DooMLord_v4 ROOt - zergRush method and am having no luck. I saw this done in a video on youtube, but it is not working for me. I have the adb drivers installed and usb debbuging turned on. Here are the result when I run the "runme.bat.
I keep getting a "read only file system."
Any help would be greatly appreciated. Thanks.
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur 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
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
450 KB/s (23060 bytes in 0.050s)
--- correcting permissions
--- executing 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 GingerBread ! 0x00000118
[+] 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
2631 KB/s (1075144 bytes in 0.399s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
18 KB/s (439 bytes in 0.023s)
df: /mnt/.lfs: Function not implemented
df: /mnt/secure/asec: Permission denied
--- Free space on /system : 20672 bytes
--- no cleanup required
--- 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
ALL DONE!!!
Press any key to continue . . .
Hi. I have the same problem as you, and haven't found a fix yet, but from my knowledge, the zergRush exploit has been patched.
not sure if this is your problem but 2 tips when rooting:
1. Temporarily disable any antivirus programs on your computer.
2. Run the rooting program As ADMINISTRATOR if your using windows, by right-clicking and choosing "run as administrator"
those are the usual suspects, I personally used the superoneclick method on mine, another choice, if you have the US version of the 4.0 is to simply flash this ROM http://forum.xda-developers.com/showthread.php?t=1512331&highlight=stock+rooted+4+0 IIRC its prerooted.
Thanks for the replies. Yes I have tried the superoneclick, right clicking the exe, giving it admin rights, and disabling antivirus before running. I will try them again this evening in case I overlooked something and repost the results. Thanks again, and if anyone has more ideas, please let me know-I really want to root this thing!
In high version, Zergrush doesn't work so it need to be rooted via Rom or Kernel.
Sent from my SHW-M110S using xda premium
So if I install a modded kernal like this one - Tegrak Kernel Build 29 for GT-I9000 - using odin. I should be able to root then using superoneclick method? And this should work with the latest firmware 2.3.6? I've done a little with the old Archos 43A using the Urukdroid rom and kernel, but haven't done that with any other device. I will read up on some of the info on this site about this Tegrak kernel and odin before diving in too deep. If anyone has done this with this YP-GB1 model please let me know. Thanks again for the advice.
dteth said:
So if I install a modded kernal like this one - Tegrak Kernel Build 29 for GT-I9000 - using odin. I should be able to root then using superoneclick method? And this should work with the latest firmware 2.3.6? I've done a little with the old Archos 43A using the Urukdroid rom and kernel, but haven't done that with any other device. I will read up on some of the info on this site about this Tegrak kernel and odin before diving in too deep. If anyone has done this with this YP-GB1 model please let me know. Thanks again for the advice.
Click to expand...
Click to collapse
Nononono. Tegrak kernel doesn't work like that. I am a GB1 user, and when using tegrak kernel, you can root with tegrak kernel app.
Sent from my SHW-M110S using xda premium
So I have done some research on the Tegrak kernel, so let me ask if I got this right.
1). I have this kernel on my yp-gb1--->2.6.35.7-GB1KRKPC-CL795804.
From what I have read, this kernel will work with my device-->[KERNEL] (XXJVT) Tegrak Kernel Build 29 for GT-I9000.
2). download odin and download this kernel to my device.
3). download the Tegrak Root app from the play store.
4). Root device from the Tegrak Root app.
??is this right?
Will this new kernel change anything already on my device and will all the player functions work eg. Camera, etc? And also thanks to everyone who has taken the time to help me with my questions and the the great developers on this site!!
After having some issues previously with ROMs randomly rebooting, I decided to unroot to UCKH7 and start over, using a different rooting method. Previously, since I was on UCK66, I used method 2c from this thread (http://forum.xda-developers.com/showthread.php?t=1311081). This time around I wanted to try method 2a, as it is the preferred method for UCKH7 build. I ensured that the flash counter was not tripped, downloaded and extracted DooMLoRD's Easy Rooting Toolkit v4.0, ensured I had necessary drivers, and enabled USB debugging, Unknown sources, and 10-minute screen timeout.
Upon running the "runme.bat" script, this is the message from the terminal window:
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
--- 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
2792 KB/s (1075144 bytes in 0.376s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
107 KB/s (439 bytes in 0.004s)
df: /mnt/.lfs: Function not implemented
df: /mnt/secure/asec: Permission denied
--- Free space on /system : 44224 bytes
--- no cleanup required
--- 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
ALL DONE!!!
All of this was in the span of 10 seconds. I searched the forums to see if anyone had any similar experience with I777 or in general, and the only thread I found was this one: http://forum.xda-developers.com/search.php?searchid=58896743
There doesn't seem to be a consensus as to what the issue may be, and I haven't seen any I777 users clamor about this. Is anyone familiar with the messages above? Thank you.
Phone details:
Model No: SGH-I777
Android version: 2.3.4
Baseband version: I777UCKH7
Kernel Version: 2.6.35.7
Build no: GINGERBREAD.UCKH7
wwjd3 said:
After having some issues previously with ROMs randomly rebooting, I decided to unroot to UCKH7 and start over, using a different rooting method. Previously, since I was on UCK66, I used method 2c from this thread (http://forum.xda-developers.com/showthread.php?t=1311081). This time around I wanted to try method 2a, as it is the preferred method for UCKH7 build. I ensured that the flash counter was not tripped, downloaded and extracted DooMLoRD's Easy Rooting Toolkit v4.0, ensured I had necessary drivers, and enabled USB debugging, Unknown sources, and 10-minute screen timeout.
All of this was in the span of 10 seconds. I searched the forums to see if anyone had any similar experience with I777 or in general, and the only thread I found was this one: http://forum.xda-developers.com/search.php?searchid=58896743
There doesn't seem to be a consensus as to what the issue may be, and I haven't seen any I777 users clamor about this. Is anyone familiar with the messages above? Thank you.
Phone details:
Model No: SGH-I777
Android version: 2.3.4
Baseband version: I777UCKH7
Kernel Version: 2.6.35.7
Build no: GINGERBREAD.UCKH7
Click to expand...
Click to collapse
Sorry no one helped you out, I can't say why it didn't work but I see "cannot stat 'files\zergRush': No such file or directory" That tells me you didn't extract the zip file and then run it from the extracted folder and NOT the .zip file.... 2c. wouldn't be the reason for the ROMS randomly rebooting it's the ROMS you flashed not the rooted KH7 package.... Always make sure before flashing any ROMS you wipe data/factory reset in recovery, then wipe cache & dalvik (I always wipe data/factory reset again after flashing the ROM) I can tell you I have been running AOKP for awhile with 0 issues maybe try that ROM.... GL
http://forum.xda-developers.com/showthread.php?t=1574718 Link to AOKP
The Rooting is taking forever also facing the adb server is out of date. killing...
Tried rooting my WT19i on .58 stock rom with GB. I used Flashtool to flash it with stock rom as it was on ICS before. Flashed successfully. But then after trying to root via this toolkit facing these errors. please help.
this is incomplete log.. process terminated later without rooting...
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur 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
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
adb server is out of date. killing...
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
cannot open 'files\zergRush': No such file or directory
--- correcting permissions
--- executing zergRush
--- 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
2447 KB/s (1075144 bytes in 0.429s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
docrj said:
Tried rooting my WT19i on .58 stock rom with GB. I used Flashtool to flash it with stock rom as it was on ICS before. Flashed successfully. But then after trying to root via this toolkit facing these errors. please help.
this is incomplete log.. process terminated later without rooting...
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur 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
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
adb server is out of date. killing...
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
cannot open 'files\zergRush': No such file or directory
--- correcting permissions
--- executing zergRush
--- 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
2447 KB/s (1075144 bytes in 0.429s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
Click to expand...
Click to collapse
You're kidding right? You don't even have a device with the same manufacturer and you come here asking for help?
Sent from my Zanpakuto using Getsuga Tensho!
ooops
Nick281051 said:
You're kidding right? You don't even have a device with the same manufacturer and you fine here asking fit help?
Sent from my Zanpakuto using Getsuga Tensho!
Click to expand...
Click to collapse
I had couple of tabs open and both had xda pages that were related to same doomlord issue. posted in the wrong one. Apologies.
docrj said:
I had couple of tabs open and both had xda pages that were related to same doomlord issue. posted in the wrong one. Apologies.
Click to expand...
Click to collapse
Ah okay well no harm no foul.
Sent from my Zanpakuto using Getsuga Tensho!
Nick281051 said:
Ah okay well no harm no foul.
Sent from my Zanpakuto using Getsuga Tensho!
Click to expand...
Click to collapse
I feel a bit harmed. . Like one third. I want compensation.
Phalanx7621 said:
I feel a bit harmed. . Like one third. I want compensation.
Click to expand...
Click to collapse
Nope nothing for you!
Sent from my Zanpakuto using Getsuga Tensho!
Nick281051 said:
Nope nothing for you!
Sent from my Zanpakuto using Getsuga Tensho!
Click to expand...
Click to collapse
I'm a saaaaad panda.
Today i saw Bin4ry's root method for ICS and JB devices, so i thought i give it a try.
Since i cant yet post on dev threads, i started this thread so people try it themselves, and maybe post findings here and on Bin4ry's original thread.
All i got was
Code:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= (14.09.2012) =
======================================================================
Device type:
1) Xperia T
2) LT26,LT22 etc.
3) Other
Make a choice: 3
Normal Mode enabled!
Please connect device with ADB-Debugging enabled now....
3532 KB/s (1085140 bytes in 0.300s)
2183 KB/s (22364 bytes in 0.010s)
3432 KB/s (843503 bytes in 0.240s)
^CTerminate batch job (Y/N)? n
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Successful, going to reboot your device!
Waiting for device to show up again....
mount: permission denied (are you root?)
remount failed: Operation not permitted
/system/xbin/su: cannot open for write: Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
/system/app/Superuser.apk: cannot open for write: Read-only file system
Unable to chmod /system/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
You can close all open command-prompts now!
After reboot all is done! Have fun with Root!
Bin4ry
Press any key to continue . . .
!^CTerminate batch job (Y/N)? n
At this point, first run i said yes, and batch just closed.
Second run, i said no, so the rest came up. Phone rebooted twice, never asked me to press anything, and no root.
AndStuff said:
Today i saw Bin4ry's root method for ICS and JB devices, so i thought i give it a try.
Since i cant yet post on dev threads, i started this thread so people try it themselves, and maybe post findings here and on Bin4ry's original thread.
All i got was
Code:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= (14.09.2012) =
======================================================================
Device type:
1) Xperia T
2) LT26,LT22 etc.
3) Other
Make a choice: 3
Normal Mode enabled!
Please connect device with ADB-Debugging enabled now....
3532 KB/s (1085140 bytes in 0.300s)
2183 KB/s (22364 bytes in 0.010s)
3432 KB/s (843503 bytes in 0.240s)
^CTerminate batch job (Y/N)? n
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Successful, going to reboot your device!
Waiting for device to show up again....
mount: permission denied (are you root?)
remount failed: Operation not permitted
/system/xbin/su: cannot open for write: Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
/system/app/Superuser.apk: cannot open for write: Read-only file system
Unable to chmod /system/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
You can close all open command-prompts now!
After reboot all is done! Have fun with Root!
Bin4ry
Press any key to continue . . .
!^CTerminate batch job (Y/N)? n
At this point, first run i said yes, and batch just closed.
Second run, i said no, so the rest came up. Phone rebooted twice, never asked me to press anything, and no root.
Click to expand...
Click to collapse
I think that method just works on some models.
Try this method: http://talk.sonymobile.com/thread/41119. Works for me
By the way: I have ICS 4.1.B.0.587 firmware
I know about this method, but i don't wanna flash roms etc.
(.587 on mini pro? if yes info!)
AndStuff said:
I know about this method, but i don't wanna flash roms etc.
(.587 on mini pro? if yes info!)
Click to expand...
Click to collapse
.587 isn't released yet for mini pro, you will have to wait. Not sure if/when we will get it!
You will have to downgrad the your firmware if you want to root ics or a gingerbread firmware like 4.0.2.A.0.62 or.69. Check out my signature, see your firmware version and decide if you want to root, if yes follow the steps
Bin4ry's himself said that it doesn't work for se xperias.
the suggested way to root from above works. I used the unlocked bootloader to directly flash cm.
Sent from my MK16i using xda premium