Related
Hi!
My phone is LG Optimus One. The version is v10e.
I am new at this. This is my first android phone. I want to move the applications to SD Card. Because phone memory is not enough. So, i am trying to root my phone. Aldready 4 days. I aldready tried to root with different ways approximately 100 times. Every time the problem is same.
I am trying to root with Android SDK, OptimusRoot, then opening CMD window. I heard, everyone rooting with this way and the way with z4root. I can't root with z4root because its not working on the version v10e.
There was some guides "about rooting with opening CMD" on some website forums. I can't post the the links because, posting outside links not permitted for new users. I did everything on their guides. Every prerequisites fulfilled. Than opened a CMD window. Then, this...
C:\Users\Seyhan>cd c:\android-sdk-windows\platform-tools
c:\android-sdk-windows\platform-tools>adb push rageagainstthecage-arm5.bin /data
/local/tmp/rageagainstthecage
43 KB/s (5392 bytes in 0.120s)
c:\android-sdk-windows\platform-tools>adb push su /data/local/tmp/
641 KB/s (26264 bytes in 0.040s)
c:\android-sdk-windows\platform-tools>adb push busybox /data/local/tmp/
1710 KB/s (1926944 bytes in 1.100s)
c:\android-sdk-windows\platform-tools>adb shell
$ chmod 4755 /data/local/tmp/rageagainstthecage
chmod 4755 /data/local/tmp/rageagainstthecage
$ chmod 4755 /data/local/tmp/busybox
chmod 4755 /data/local/tmp/busybox
$ cd /data/local/tmp
cd /data/local/tmp
$ ./rageagainstthecage
./rageagainstthecage
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3341, 3341}
[*] Searching for adb ...
[+] Found adb as PID 1927
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$
c:\android-sdk-windows\platform-tools>adb shell
error: device not found
c:\android-sdk-windows\platform-tools>
Click to expand...
Click to collapse
it's coming to here;
[*] adb connection will be reset. restart adb server on desktop and re-login.
then nothing happens. Its killing adb but never restart. I waited 20 minutes but nothing changed. Just 2 times its reconnected but once reconnected its still "$". I couldn't get the "#". Every time same problem. If anyone knows something about this, please help me. This is already a death battle for me. If anybody can help me with root my phone, i can't explain how i will be thankful.
Thanks for your interests.
Z4 root?
for someone new to this, you seem to doing it the hardest way?
/edit just seen it wont let you use it?
Tried superoneclick method?
If that "v10e" that you have is an Android v2.2.1 or v2.2.2 (check in Settings - About Phone - Android version), then your effort is in vain. You must downgrade to v2.2 in order to be able to root. This thread gives you a lot to read about how to flash an original ROM (which you will make sure is 2.2, that means "v10a") using KDZ.
Is this the german V10E? As far as i know, thats is the android 2.2.2 version which isn't rootable using z4 or rageagainstthecage.
I have the same version, and I did it like this:
1. flashed back to V10A
2. rooted using Z4
3. installed custom recovery
4. downloaded the V10E
5. built a custom rom from this (with root, deleted some stuff and some tweaks)
6. installed that rom using custom recovery
That way, I got a rooted V10E without that LG crap.
I found all neccessary links in this forum, basically I just followed this instructions:
[HOWTO] Cook your custom rom for LG P500: http://forum.xda-developers.com/showthread.php?t=901417
Takes some time, but is worth the effort!
Try to downgrade to 2.2 via KDZ tool .... (10B I think)
I recommend you to stick with 2.2 as it not only provides easy root access
but, it has some tweaks such as volume button swap in landscape mode, etc.
which 2.2.1 or above breaks...
Most roms are built on 2.2 -> see megatron rom
I've seen the Zerg root for the 4G, but after reading some comments about it there's been speculation that the 1.45.1500.2 is Zerg root proof. It there a way to root the Amaze with 1.45.1500.2 software?
On another note... I'm not able to tether with my phone? i'm able to make a hot spot and all yet, I cannot connect any devices to it. The devices seem to not be able to acquire the IP address.
All tips and suggestions are helpful, so please comment as I'm sure you'll be able to help me with my issues one way or another.
Have you unlocked your bootloader?
Sent from my HTC Amaze 4G using xda premium
*edit
What's the complete process in rooting the device with the 1.45.1500.2 software? I'm going to bootload it as soon as it's fully charged.
To unlock your bootloader:
Go to http://htcdev.com/register/ and register an account with them.
Then select "Begin Unlock bootloader"
Follow the steps. It is easy. Just back up your info because when you unlock it, it will require a hard reset.
To do install ClockWorkMod Recovery (CWM), go to this link.
http://forum.xda-developers.com/showthread.php?t=1316855
Follow the instructions that says "Installation from fastboot (hboot only ||Hard Method||):" (It's actually very easy and it worked on the new ROM update)
Download the ClockworkMOD 5.0.2.7 Amaze 4g and not the ClockworkMOD 5.0.2.0 Amaze 4g.
To root, you can install a prerooted Custom ROM or you can download SuperUser (SU) from here
http://www.multiupload.com/TI14RLNE8A
Just boot into CWM and flash the su-2.3.6.3-ef-signed.zip if you want to root it with your stock ROM.
To get WiFi Tethering working, you need root (duh).
Download WiFi Tether for Root Users 3.1-beta9
http://code.google.com/p/android-wifi-tether/downloads/detail?name=wifi_tether_v3_1-beta9.apk
After you install it, press the menu button. Select "Settings". Change the Device Profile to HTC Amaze / HTC Ruby. You are good to go!
Much appreciated, will try this tonight and will get back to you
Alright, so I've tried the Bootloader process and I've received an error:
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: .
Error Reason: .
That's after I went through the steps and had to paste the coding from the cmd onto the site. What's the problem?
HTC Bootloader unlock
I just read another post that said the HTC bootloader unlock page is broken today. I was trying to unlock my new t-mobile US amaze today and have the same errors as you.
RyanB125 said:
Alright, so I've tried the Bootloader process and I've received an error:
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: .
Error Reason: .
That's after I went through the steps and had to paste the coding from the cmd onto the site. What's the problem?
Click to expand...
Click to collapse
Tardango said:
I just read another post that said the HTC bootloader unlock page is broken today. I was trying to unlock my new t-mobile US amaze today and have the same errors as you.
Click to expand...
Click to collapse
Alright, I guess i'll have to try again tomorrow.
The site is down I believe. I tried it for my friend. If it works, let me know!
Zerg not working on my unlocked Amaze
I have unlocked my bootloader and am running 1.43.531.3. I get pretty much the same set of errors every time I run the bat file. I have tried factory resetting it 3 times and trying again, but it always does the same thing. Occasionally it'll also say rm failed: no such file or directory on the adb shell rm /data/local/tmp/*sh command. USB debugging is on.
C:\Zerg>adb wait-for-device
C:\Zerg>adb push zergRush /data/local/
1294 KB/s (21215 bytes in 0.016s)
C:\Zerg>adb shell chmod 777 /data/local/zergRush
C:\Zerg>adb shell rm /data/local/tmp/*sh
C:\Zerg>adb shell /data/local/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 ! 0x00017118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
C:\Zerg>adb wait-for-device
C:\Zerg>adb shell sleep 1
C:\Zerg>adb remount
remount failed: Operation not permitted
C:\Zerg>adb shell mount -o rw,remount rootfs /
mount: Operation not permitted
C:\Zerg>adb shell mount -o remount,suid /dev/block/mmcblk0p29 /system
mount: Operation not permitted
C:\Zerg>adb shell chmod 4755 /system/bin/sh
Unable to chmod /system/bin/sh: Read-only file system
C:\Zerg>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Zerg>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Zerg>adb push ./busybox /system/bin
failed to copy './busybox' to '/system/bin/busybox': Read-only file system
C:\Zerg>adb shell chmod 4755 /system/bin
Unable to chmod /system/bin: Read-only file system
C:\Zerg>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Zerg>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Zerg>adb push ./Superuser.apk /system/app
failed to copy './Superuser.apk' to '/system/app/Superuser.apk': Read-only file
system
C:\Zerg>adb install ./androidterm.apk
1969 KB/s (92780 bytes in 0.046s)
pkg: /data/local/tmp/androidterm.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\Zerg>adb wait-for-device
C:\Zerg>adb shell sync
C:\Zerg>pause
Press any key to continue . . .
Have you installed CWM?
Still getting the same errors as before. :/
edit* is there any report as to when the HTCdev page will be fixed?
I tried is an hour ago. The HTCDev site is working. I got my friend's unlock key.
its not the HTCdev site, its the way you copied the key over to the box. absolutely no spaces are allowed.
but im gettin the same error for zerg. this is crap, i basically blanked my phone just to unlock it and restore everything.
is this a software version problem?
hasoon2000 said:
I tried is an hour ago. The HTCDev site is working. I got my friend's unlock key.
Click to expand...
Click to collapse
I'm still receiving the same error!
PM me the token ID in a text file attachment. I will see what the issue is.
pepsishine said:
its not the HTCdev site, its the way you copied the key over to the box. absolutely no spaces are allowed.
but im gettin the same error for zerg. this is crap, i basically blanked my phone just to unlock it and restore everything.
is this a software version problem?
Click to expand...
Click to collapse
Assuming you are trying to root, you might try this approach. Worked for me. After the wifi update I had to reset to factory and remove CWM to get the update to install. After the update I did this again and all went well except I got an error during the root process using the file I downloaded from that thread. Thought maybe I was out of luck, but after rebooting the phone it was rooted. Been working fine for the past several days.
hasoon2000 said:
PM me the token ID in a text file attachment. I will see what the issue is.
Click to expand...
Click to collapse
Alright, give me a sec, i'll pm you.
Are you on Telus or Wind mobile? I heard that they didn't give HTC permission to allow the customers to unlock their bootloaders
Sent from my HTC_Amaze_4G using xda premium
I'm with Wind.
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?....
Sorry for being such a noob. I've followed every instruction to the "T".
I've unlocked the bootloader from HTC with no problems. Then I ran OneClickRoot_1.1... it stated I had achieved Perm root. But no su binary is found. I tried to manually install Superuser from the market as well as busybox. I can't figure it out. I've researched these forums for hours. I also made sure phone was in "Charge only", usb debugging was enabled, and HTC Sync was closed.
Does this have anything to do with me accepting the OTA on Thursday, before I tried to root. Please help. I'll include the script from the OneClick.
Press any key to continue . . .
--- WAITING FOR DEVICE ---
--- Device Connected ---
Checking for previous attempts...
Pushing Zergrush...
2251 KB/s (23060 bytes in 0.010s)
Setting Permissions...
Gaining Perm Root (Aka running 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
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE ---
--- Device Connected ---
Pushing Busybox
2592 KB/s (1075144 bytes in 0.405s)
Setting Permissions...
Remounting System...
mount: permission denied (are you root?)
Coping Busybox to /system/xbin/...
/system/xbin/busybox: cannot open for write: Read-only file system
Installing Busybox...
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
Installing Superuser...
failed to copy 'tools\su' to '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
failed to copy 'tools\Superuser.apk' to '/system/app/./Superuser.apk': Read-onl
file system
Removing tools That Was Pushed To Data...
Congrats You Are Now Perm Rooted...
Press any key to continue . . .
I assume this is this the one click root NilsP posted? That one worked great for me. Make sure USB debugging is enabled and you have checked the box under applications to enable use of non-market apps.
If you continue to have issues, flash the AmonRa recovery via fastboot and under Developer Options you can choose to install superuser while in recovery.
You will have to flash Amon Ra recovery through fastboot. There is info about that in development thread. Read through first few pages of Amon Ra thread. Once you have recovery, boot it up from hboot, and then install su and superuser from development section in Amon Ra recovery. The only confusing part for me was preparing to flash Amon Ra thru Windows command prompt due to my inexperience. PM me for further assistance. Good luck. One click does not work for the OTA.
Thanks guys...wish me luck
Kbartley77 said:
Thanks guys...wish me luck
Click to expand...
Click to collapse
You should be able to put Amon Ra inside the same folder you just used for unlocking. Then use command:
Fastboot flash recovery (nameofrecoveryfilehere)
You will need to add .IMG to the file name for it to work.
Sent from my ADR6425LVW using Tapatalk
Kbartley77 said:
Sorry for being such a noob. I've followed every instruction to the "T".
I've unlocked the bootloader from HTC with no problems. Then I ran OneClickRoot_1.1... it stated I had achieved Perm root. But no su binary is found. I tried to manually install Superuser from the market as well as busybox. I can't figure it out. I've researched these forums for hours. I also made sure phone was in "Charge only", usb debugging was enabled, and HTC Sync was closed.
Does this have anything to do with me accepting the OTA on Thursday, before I tried to root. Please help. I'll include the script from the OneClick.
Press any key to continue . . .
--- WAITING FOR DEVICE ---
--- Device Connected ---
Checking for previous attempts...
Pushing Zergrush...
2251 KB/s (23060 bytes in 0.010s)
Setting Permissions...
Gaining Perm Root (Aka running 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
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE ---
--- Device Connected ---
Pushing Busybox
2592 KB/s (1075144 bytes in 0.405s)
Setting Permissions...
Remounting System...
mount: permission denied (are you root?)
Coping Busybox to /system/xbin/...
/system/xbin/busybox: cannot open for write: Read-only file system
Installing Busybox...
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
Installing Superuser...
failed to copy 'tools\su' to '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
failed to copy 'tools\Superuser.apk' to '/system/app/./Superuser.apk': Read-onl
file system
Removing tools That Was Pushed To Data...
Congrats You Are Now Perm Rooted...
Press any key to continue . . .
Click to expand...
Click to collapse
if you can't root using oneclickroot,
flash AmonRA recovery using cleanflash
then install su and superuser under Developer menu under AmonRA recovery.
Amonra Recovery: http://forum.xda-developers.com/showthread.php?t=1339679
Cleanflash: http://forum.xda-developers.com/showthread.php?t=1416791
Same Issue
feralicious said:
You should be able to put Amon Ra inside the same folder you just used for unlocking. Then use command:
Fastboot flash recovery (nameofrecoveryfilehere)
You will need to add .IMG to the file name for it to work.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Hello, I am having the same issue. I use Clean Flash 1.0, and the image file from Amonra PH98IMG.zip. Everything says that it worked. I load SU through Recovery. No icon appears under Apps for superuser so I go to the market and load SuperUser. The first time I run Root Explorer the SuperUser image appears allowing me to grant approval. When I go into Terminal Emulator and type SU I am granted access. So I restart my phone and go back to Terminal Emulator, when I type SU I get Access Denied. The one thing that is stated here and in another thread is the part about "Fastboot flash recovery (recovery.img)". What is this and were is it done? Do you type it just as shown minus the quotes? Is that what I am missing and causing a permanent root to act like a temporary root.
Thank you for your help.
dnvm said:
Hello, I am having the same issue. I use Clean Flash 1.0, and the image file from Amonra PH98IMG.zip. Everything says that it worked. I load SU through Recovery. No icon appears under Apps for superuser so I go to the market and load SuperUser. The first time I run Root Explorer the SuperUser image appears allowing me to grant approval. When I go into Terminal Emulator and type SU I am granted access. So I restart my phone and go back to Terminal Emulator, when I type SU I get Access Denied. The one thing that is stated here and in another thread is the part about "Fastboot flash recovery (recovery.img)". What is this and were is it done? Do you type it just as shown minus the quotes? Is that what I am missing and causing a permanent root to act like a temporary root.
Thank you for your help.
Click to expand...
Click to collapse
go here
http://forum.xda-developers.com/showthread.php?t=1466474
Im in the same boat.. I took the ota update and now i cant root. I tried going into cmd to flash the recovery img, and it says "cannot load recovery img" I also tried using clean flash 1.0 and i get the same thing "cannot load" and than the phone just boots in fastboot.. What could be the problem?
feralicious said:
You should be able to put Amon Ra inside the same folder you just used for unlocking. Then use command:
Fastboot flash recovery (nameofrecoveryfilehere)
You will need to add .IMG to the file name for it to work.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Still not showing root. Any more ideas??
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\KC>cd c:\Android
c:\Android>Fastboot flash recovery recovery.img
sending 'recovery' (7062 KB)...
OKAY [ 1.430s]
writing 'recovery'...
OKAY [ 5.036s]
finished. total time: 6.467s
c:\Android
Kbartley77 said:
Still not showing root. Any more ideas??
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\KC>cd c:\Android
c:\Android>Fastboot flash recovery recovery.img
sending 'recovery' (7062 KB)...
OKAY [ 1.430s]
writing 'recovery'...
OKAY [ 5.036s]
finished. total time: 6.467s
c:\Android
Click to expand...
Click to collapse
c:/Android>fastboot flash recovery (name of recovery).img
Not recovery.img
Sent from my ADR6425LVW using xda premium
Alright I rebooted into Bootloader and selected recovery.
It put me into RA-Vigor-v3.0.6
Which option do I select?
-Reboot system now
-USB-MS Toggle
-Backup/Restore
-Wipe
-Partition
-Mounts
-Other
-Format Data
-Dev. Menu
-Power off
Please forgive me for my newbness.
Kbartley77 said:
Alright I rebooted into Bootloader and selected recovery.
It put me into RA-Vigor-v3.0.6
Which option do I select?
-Reboot system now
-USB-MS Toggle
-Backup/Restore
-Wipe
-Partition
-Mounts
-Other
-Format Data
-Dev. Menu
-Power off
Please forgive me for my newbness.
Click to expand...
Click to collapse
Developer menu if your trying to achieve root. Then there is an option to install su and superuser. Select that then after that is done immediately reboot. You may or may not still have to download the superuser off the market and update it. I didn't but alot of people reported having to do so.
I'm ROOTED!!!! Thank you everyone for your time and patience!!!
qudwis, thank you for responding. That Post is what I followed, but I do not see any way once in Fastboot were I can type "fastboot flash recovery recovery_signed.img". I restart my phone and I get to the screen were HBOOT and Fastboot are located. But there is no command line to type into. That is were I need the step by step to help me.
Thank you for your help.
dnvm said:
qudwis, thank you for responding. That Post is what I followed, but I do not see any way once in Fastboot were I can type "fastboot flash recovery recovery_signed.img". I restart my phone and I get to the screen were HBOOT and Fastboot are located. But there is no command line to type into. That is were I need the step by step to help me.
Thank you for your help.
Click to expand...
Click to collapse
You have to do this in Cmd, while the phone is in fastboot
Sent from my DROID RAZR using XDA App
dnvm said:
qudwis, thank you for responding. That Post is what I followed, but I do not see any way once in Fastboot were I can type "fastboot flash recovery recovery_signed.img". I restart my phone and I get to the screen were HBOOT and Fastboot are located. But there is no command line to type into. That is were I need the step by step to help me.
Thank you for your help.
Click to expand...
Click to collapse
You run those commands on your PC in a command/DOS prompt.
Hi all,
I have some problems with trying to root my Xperia Ray with the DooMLoRD's Easy Rooting Toolkit [v4.0](zergRush Exploit).
I have done all the pre-work, allowing USB debugging and unknown apps, connecting the device to the computer (Windows 7) per USB, drivers were installed automatically and I installed the Sync Companion, too. Starting the script --> Does not work.
Using adb then manually and working myself through the script, there is one line where the script stops working (all other command lines prior were working fine):
adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
Error message: mount: permission denied (are you root?)
as all the other command lines depend on this command, there are more error messages later, but I guess this is the most crucial one. It seems for this command you need root access, but I dont have it (since I am trying to get it with the script... ;-) )
Any ideas how to get the command and the script working?
Device: Xperia Ray, Android Version 2.3.4, Build Number 4.0.2.A.0.69, Kernel Version 2.6.32.9-perf [email protected] #1
Cheers and thanks for helping!
Chris
You cant root the .69 firmware. Unless you flash a different kernel.
And please post your questions here http://forum.xda-developers.com/showthread.php?t=1450295
Sent from my ST18i using xda premium
boni2504 said:
Hi all,
I have some problems with trying to root my Xperia Ray with the DooMLoRD's Easy Rooting Toolkit [v4.0](zergRush Exploit).
I have done all the pre-work, allowing USB debugging and unknown apps, connecting the device to the computer (Windows 7) per USB, drivers were installed automatically and I installed the Sync Companion, too. Starting the script --> Does not work.
Using adb then manually and working myself through the script, there is one line where the script stops working (all other command lines prior were working fine):
adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
Error message: mount: permission denied (are you root?)
as all the other command lines depend on this command, there are more error messages later, but I guess this is the most crucial one. It seems for this command you need root access, but I dont have it (since I am trying to get it with the script... ;-) )
Any ideas how to get the command and the script working?
Device: Xperia Ray, Android Version 2.3.4, Build Number 4.0.2.A.0.69, Kernel Version 2.6.32.9-perf [email protected] #1
Cheers and thanks for helping!
Chris
Click to expand...
Click to collapse
i am also have problem like him too...but i using Xperia Ray ICS 4.0.4 Build Number 4.1.B.0.431
GB 2.3.4 .69 and ICS 4.0.4 you can't
Root. Search for solution. Gb .42 and 4.0.3 can
Sent from my ST18i using XDA
snailboykh said:
i am also have problem like him too...but i using Xperia Ray ICS 4.0.4 Build Number 4.1.B.0.431
Click to expand...
Click to collapse
for 4.0.4, u have to downgrade the kernel to 4.0.3 and use the ics emulator hack exploit to root it. Then flash back to 4.0.4 kernel
Downgrade to fw.42 or 58 with flashtool.
I also have the same problems as you.
Which is better fw?
.42 or 58?
I cant share a link here cos i am a newbie. Just read my post yesterday...
Sent from my ST18i using XDA
guys i am trying to root my xperia ray with zerg rush
but its not working please help
[+] Found a GingerBread ! 0x00015118[*] Scooting ...[*] Sending 149 zerglings ...[*] 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
3016 KB/s (1075144 bytes in 0.348s)
--- 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
ALL DONE!!!
Press any key to continue . . .
which version do you vant to root?
Please post your question in Q&A thread, its a development section.
If I were you, I would research regarding which FW's do the ZergRush exploit apply...
and please post in the proper thread...
There are rooting methods for each FW, please use search
and to the viewers, PLEASE DON'T TRY TO ANSWER THE QUESTION, it is better to redirect the user to the proper thread... so please let us break the cycle