Related
So I have mac osx and windows. I've tried rooting on both. I can follow a tutorial, that is how I've rooted my thunderbolt when it first came out. But my new thunderbolt won't root using the methods that are working for others. So I request someone to help me out as to writing a step by step setup for required prerequisites programs... Thank you. Something isnt working. I just want to enjoy perks of root again.
Sent from my ADR6400L using XDA App
Which instructions are you trying to follow, JCase's or Cap's? Also, where is the root procedure failing for you? I only ask because there is no one here who could write better step by step instructions than the ones already included in both rooting methods.
Have to agree. Any information at all regarding how its failing would be most helpful.
Okay. For windows I used the script that is a batch file because I've heard it is super easy to use... When I first was running the script it would not find the device. Now it will find it with debugging on. But when debugging is on my device won't be listed in my computer. With debugging off it will show up on my computer. Anyways with the script it says it pushes all the files then when my phone is to reboot it won't.
Sent from my ADR6400L using XDA App
Make sure that your ADB is set up properly before you start using the batch file.
A great set of instructions can be found here:
http://www.droidforums.net/forum/droid-hacks/10924-how-adb-windows-made-easy.html
The batch file is also old and some of the files included in it might be too dated to use. Try using JCase's method.
Last login: Fri Jul 29 16:53:34 on ttys000
scott-roccas-macbook:~ scott87$ cd ..
scott-roccas-macbook:Users scott87$ cd ..
scott-roccas-macbook:/ scott87$ cd and*
scott-roccas-macbook:androidsdk scott87$ cd tools
scott-roccas-macbook:tools scott87$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT14RS010885 device
scott-roccas-macbook:tools scott87$ ./adb push busybox /data/local/
1867 KB/s (1062992 bytes in 0.555s)
scott-roccas-macbook:tools scott87$ ./adb push psneuter /data/local/
1764 KB/s (585731 bytes in 0.324s)
scott-roccas-macbook:tools scott87$ ./adb push misc.img /data/local/
1943 KB/s (262144 bytes in 0.131s)
scott-roccas-macbook:tools scott87$ ./adb shell chmod 777 /data/local/busybox
scott-roccas-macbook:tools scott87$ ./adb shell chmod 777 /data/local/psneuter
scott-roccas-macbook:tools scott87$ ./adb shell /data/local/psneuter
mmap() failed. Operation not permitted
scott-roccas-macbook:tools scott87$
following this tutorial for my mac... http://forums.androidcentral.com/th...9-mac-procedure-how-root-htc-thunderbolt.html I have rooted my orignal TB over 6 times. Now I cannot use the same method on my new TB. Wtf. It wont let me go past the step of ./adb shell /data/local/psneuter
what is wrong?
Where did you get the exploits file that contained the psneuter file and such? Try downloading the files from http://www.multiupload.com/K4BZ22SIT5 and verify the md5 is 3b359efd76aac456ba7fb0d6972de3af and try again.
I'm kinda clueless without firmware versions and what exploits exactly are being used.
My exploits folder matches the MD5 checksum... I am on the newest possible firm. Someone please help me solve this issue...
http://forum.xda-developers.com/showthread.php?p=12785644#post12785644
http://forums.androidcentral.com/thunderbolt-rooting-roms-hacks/73211-rooting-issues.html#post782824
Both of those links showed ppl having similar problems. Try their fixes of restoring to factory defaults and trying again or re-formatting your card.
Thank you for your help. Doing a factory reset made the difference. I greatly appreciate it.
Dueces.
Sent from my ADR6400L using XDA App
Check out these videos, they helped me go through all the steps. The second time I rooted this thing was harder because I thought I had everything setup, and I did but I had to redo everything to get it to work. Start fresh by doing the drivers again, then put the contents of the exploits zip in sdk tool, (all the files but one were correct on mine, I think it was just an outdated version and that was one of my hold ups)
http://www.youtube.com/watch?v=oKPSe12YDxQ
http://www.youtube.com/watch?v=mc6EMdPpF6o
This is why you should manually root, and not do the auto crap... problems
This thread is a collaboration by myself, paxChristos, DooMLorD, & amishxda. Please give credit where credit is due. Thanks.
This method has been confirmed to work on all models of the Xperia PLAY - R800x / R800i / R800a / R800at. Also works perfectly with the Xperia Arc.
WARNING: This doesn't work, however, on the Verizon Wireless R800x v2.3.2. Please update to v2.3.3 before rooting. - confirmed by paxChristos
WARNING #2: Confirmed that this doesn't work with 4.0.2.A.0.62
MAJOR WARNING - ICS (4.x) doesn't work with it & any update to GB (2.3.x) after November 2011 won't either.
paxChristos said:
The exploit used in this toolkit was patched back in November of 2011. No more updates will come from the exploit devs.
Click to expand...
Click to collapse
Thanks to everyone who tested this out for me & confirmed that it worked!
NOTE: Before you attempt to root your phone, please ensure that you have the Android SDK installed. It has the adb binary within it.
Android SDK
http://developer.android.com/sdk/index.html
All needed files have been attached for this process to work correctly.
Note: I didn't create zergRush. I only found the method to implement permanent root after zergRush has done its job.
Automatic Root
1) SuperOneClick
SuperOneClick now has the zergRush method built-in.
Please see the source thread if you have any questions.
Downloads available @ http://shortfuse.org/
Source: http://forum.xda-developers.com/showthread.php?t=803682a
2a) DooMLoRD's Easy Rooting Toolkit [v4] (zergRush Exploit)
This is the one click method that everyone has been asking for & DooMLoRD has answered with this.
DooMLoRD said:
UPDATE: added v4, with newest zergRush binary (21 Nov 2011) and few corrections/additions to script
UPDATE: most companies are patching the exploit in the latest firmwares (Samsung, Motorola, Sony Ericsson, etc)
UPDATE: added v3, with newest zergRush binary (16 Nov 2011) and newer superuser files
UPDATE: added v2, with newest zergRush binary (10 Nov 2011) and newer superuser files
[ support the developers ]
There have now been nearly 440,000 downloads of this easy rooting toolkit for various devices (see list here), and many more if you include variations/different translations, etc that use it.
Don't be a leech, buy me a coffee/beer/etc (and use the "Thanks" button!). Imagine if every user of this tool had donated me even $1...
if you want to support Revolutionary Team (creators of the Exploit which makes this possible ) you can donate to Revolutionary Team's PayPal Donation Link
[ Info ]
(WINDOWS ONLY)
WILL WORK ON BOTH LOCKED & UNLOCKED BOOTLOADER DEVICES!
just download the attached file, extract it using winzip/winrar
go to the folder where its extracted and execute "RUNME.bat"
read and follow the instructions on the screen!
Code:
---------------------------------------------------------------
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)
[*] 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
[ Tested on ]
Tested & Reported to be working on the THESE devices
[ Credits ]
Credits go to all those involved in making this possible!
zergRush Binary from: Revolutionary - zergRush local root
Inspired from: http://forum.xda-developers.com/showthread.php?t=1312859
[ Donations ]
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc My PayPal Donation Link
if you want to support Revolutionary Team (creators of the Exploit which makes this possible ) you can donate to Revolutionary Team's PayPal Donation Link
[ Download Links ]
DooMLoRD_v4_ROOT-zergRush-busybox-su.zip <NEW>
DooMLoRD_v3_ROOT-zergRush-busybox-su.zip
DooMLoRD_v2_ROOT-zergRush-busybox-su.zip
DooMLoRD_v1_ROOT-zergRush-busybox-su.zip
[ UnRooting ]
want to unroot? read this
[ Scripts posted by others ]
Rooting script for Linux
Rooting script for MAC OSX
Toolkit for GT-I9000
For Atrix 2
For VIZIO vTab1008
regards,
DooMLoRD
Click to expand...
Click to collapse
Source: http://forum.xda-developers.com/showthread.php?t=1319653
My deepest thanks to DooMLoRD for automating & simplifying this process!
2b) amishxda's modified Linux script (based on paxChristos' script // Source: DooMLoRD's Easy Rooting Toolkit)
amishxda said:
Update: Updated as per DooMLoRD's v4.0 script with zergRush binary of 21 Nov 2011 and with makespace which deletes Google Maps if there is not enough space.(< 6MB)
Hello
I am completely new to Android but not at all new to Linux.
I used paxchristos script (ran commands manually though) to root my Sony Ericsson Live with Walkman. (WT19i / Android 2.3.4 / Build 4.0.2.A.0.58)
Source threads used:
http://forum.xda-developers.com/showthread.php?t=1319653
http://forum.xda-developers.com/showthread.php?p=18615502
In an attached file, I fixed/modified/added few things in paxchristos script. Here is the detail:
1) Fixed error in symlinking su. (source/destination were same)
2) Don't delete (and recreate) /data/local/tmp/ directory unnecessarily, just delete its contents
3) Uses dd instead of cp (because DooMLoRD's script does, dont know why!). Update: as per anantshri, dd is used because cp has been known to give errors.
4) If your system already has 'adb' then it uses system 'adb' instead of one in zip-archive.
5) Updated zip archive to contain the latest files from DooMLoRD's archive (paxchristos archive seemed old)
Please try/verify and let me know if I missed something.
Thanks.
Click to expand...
Click to collapse
zergRush_automated_Linux_root.zip
Source: http://forum.xda-developers.com/showthread.php?p=20869699
Original script by paxChristos: http://forum.xda-developers.com/showthread.php?p=18615502#post18615502
Manual Root
3) Noob Friendly Guide
paxChristos has provided me with a very comprehensive guide regarding this process for anyone that absolutely wants a step-by-step layout.
It has been attached to this thread within a 7-zip file. If you would like the faster route, please follow my own instructions.
Download PDF Guide
4) Advanced Android Users (& those that are aiming to be) Guide
Download all required files. Drivers have been provided courtesy of paxChristos for anyone that needs them.
Do the following within a cmd (as administrator) or terminal prompt (through sudo or root user)
Code:
adb shell mkdir /data/local/tmp
adb push zergRush /data/local/tmp
adb chmod 755 /data/local/tmp/zergRush
adb shell
cd /data/local/tmp/
./zergRush
adb remount
adb push su /system/bin
adb push su /system/xbin
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
exit
adb install Superuser.apk
Alternate: adb push Superuser.apk /system/app
installed BusyBox (if it doesn't show up on the system already) via any busybox installer market app
Ran SuperUser & verified settings
Code:
adb reboot
Android should be completely rooted!
Automatic Unroot
DooMLoRD's Unrooting Script
DooMLoRD said:
UNROOTING SCRIPT v1.0
so here is the unrooting script to be USED ONLY AND ONLY IF U HAVE USED MY FILES (Easy Rooting Toolkit) FOR ROOTING
[ WARNING ]
if u have used any other way/solution for rooting then PLEASE DO NOT RUN THIS... you MIGHT END UP with damaged system...
(thats cause some ppl create symlinks for busybox in /system/bin/ which wipes out stock symlinks to /system/bin/toolbox and breaks/damages system)
[ DISCLAIMER ]
I AM NOT TO BE HELD RESPONSIBLE IF U DAMAGE UR PHONE / SPILL UR COFFEE / MISS UR ALARMS / ANY OTHER CALAMITY/MISHAP
REMEMBER YOU ARE DOING THIS AT YOUR OWN RISK
now that the warning is clear (hopefully) lets get to unrooting
Tested on:
Sony Xperia ARC
so here is the file.. (WINDOWS ONLY)
just download the attached file, extract it using winzip/winrar
go to the folder where its extracted and execute "RUNME-UNROOT.bat"
read and follow the instructions on the screen!
Code:
---------------------------------------------------------------
Easy rooting toolkit (v1.0)
UNROOTING SCRIPT
created by DooMLoRD
based heavily on FlashTool scripts (by Bin4ry and Androxyde)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) unroot ur device using special script
(2) remove Busybox and assocaited symlinks
(3) remove SU files and assocaiated data
[*] 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
---------------------------------------------------------------
if all goes well u will get output LIKE THIS
regards,
DooMLoRD
DooMLoRD_v1_UNROOTING.zip
Click to expand...
Click to collapse
Sources/Acks/Links/Attachments
Sources:
http://forum.xda-developers.com/showthread.php?t=1312082
http://forum.xda-developers.com/showthread.php?t=1296916
http://androidsu.com/superuser/
Acknowledgments:
Ch4lky - Sony Ericsson Xperia fix for zergRush (Revolutionary Team)
ieftm - zergRush (Revolutionary Team)
Revolutionary Team - many thanks to everyone who worked on zergRush
paxChristos - provided debug info to Ch4lky & created the Noob PDF guide
ChainsDD - Superuser & su
DooMLoRD - for the awesome rooting & unrooting scripts
CLShortFuse - SuperOneClick
Cl8rs - identified possibility for Xperia PLAY to use zergRush
XenonMD - confirmed that this works on the R800i
barlw - confirmed that this works on the R800a
Luniticus - confirmed that this works on the R800at
AndroHero - recommended the alternate method for pushing the Superuser.apk to /system/app for working around stability issues
amishxda - for updating paxChristos' script to work on more phones from Linux
Everyone else - who have confirmed that it works on many other phones
Please let me know any new information to smooth out the process. I'll modify this post to ensure it's a smooth one.
zergRush (no longer attaching due to new updates from the devs) - supports a large amount of phones
https://github.com/downloads/revolutionary/zergRush/zergRush.zip
Superuser v3.0.7 apk
http://goo-inside.me/superuser/Superuser-3.0.7-efgh-signed.zip
su v3.0.3.2 binary
http://goo-inside.me/superuser/su-bin-3.0.3.2-efghi-signed.zip
Thanks!!!
Edit: Please PM me if you were a part of discovery, research or one of the tools listed.
Thanks I wasn't trying to be stuck up or anything, just wanted credit.
Awesome...I've been watching the Zerg thread with bated breath and I didn't have to wait long.
i just wish I had my damn usb cable with me right now.
Big thanks to all involved, I will be trying this asap.
Is there a way to un-root? Just curious...
Step-by-literal-step
If you feel like seeing the step by step PDF Guide, go to these : attached to post #1, or:
At dropbox.com: http://db.tt/RaAUnzjW
At Ubuntu one: http://ubuntuone.com/64OujxgkGMv1N2QSoPmXin
or at Filesonic: http://www.filesonic.com/file/2730341354
If you're doing the script rooting in linux, do these things first
1) Download and unzip file (it's below at dropbox.com or ubuntu one; or it's posted in #1 as an attachment)
2) open up terminal
3) type "su"
4) enter your password
4a) if you don't have su set up
4b) type "passwd"
4c) enter you username password (no, there will be no ***s to show that you entered anything, just hit enter when you've inputted your password)
4d) input a password for root (unix) (no, there will be no ***s to show that you entered anything, just hit enter when you've inputted your password)
4e) type "su" and enter your password
5) navigate to location you unzipped the file to (chrome default download is /home/[your username]/Downloads)
6) type "chmod 755 runme-linux"
7) type "cd files"
8) type "chmod 755 adb"
9) type "cd .."
10) type "./runme-linux"
11) type "exit" x2 to exit terminal
12) enjoy your rooted play!
Here's the script (and all applicable files) (totally ripped off DooMLoRD's code, thank him, please, for me), go to these links:
At dropbox.com: http://db.tt/a4H6QFfV
At Ubuntu one: http://ubuntuone.com/7mD63kpsKzGmaou5hcftBV
Here's the linux script code
Code:
#!/bin/bash
#This is DooMLoRD's script for windows. I've ported it to linux
#Somethings to remember
#1) Chmod this file!! ("chmod 777 runme-linux")
#2) Run this script as su in terminal (if you haven't set up your su password run the command "passwd" in terminal, it'll ask you for your username password, and then you'll type in a root password. NOTE: You will not see any changes (i.e. *** representing typed letters) but the password is still being inputted.
#I skipped all of DooMLoRD's info because I'm using VIM and don't feel like rewritting it
echo "--Starting---"
echo "---Killing the adb server to make sure that there are no problems---"
./files/adb kill-server
echo "---Waiting for Device---"
./files/adb wait-for-device
echo "---Cleaning out any previous zergRush attempts---"
./files/adb shell rm -r /data/local/tmp
echo "---Creating temp folder for zergRush---"
./files/adb shell mkdir /data/local/tmp
echo "---Pushing zergRush---"
./files/adb push ./files/zergRush /data/local/tmp/
echo "---Fixing permissions for zergRush---"
./files/adb shell chmod 755 /data/local/tmp/zergRush
echo "---Running zergRush---"
./files/adb shell /data/local/tmp/zergRush
#If it gets stuck here for a long time then try:
#1)disconnect usb cable and reconnect it
#2)toggle "Usb Debugging" (first disable it then reenable it")
echo "---Device found!---"
./files/adb wait-for-device
echo "---Pushing busybox---"
./files/adb push ./files/busybox /data/local/tmp
echo "---Fixing busybox permissions---"
./files/adb shell chmod 755 /data/local/tmp/busybox
echo "---remounting system---"
./files/adb shell /data/local/tmp/busybox mount -o remount,rw /system
echo "---copying busybox to /system/xbin---"
./files/adb push files/busybox /system/xbin
echo "---fixing ownership and permissions---"
./files/adb shell chown root.shell /system/xbin/busybox
./files/adb shell chmod 04755 /system/xbin/busybox
echo "---installing busybox---"
./files/adb shell /system/xbin/busybox --install -s /system/xbin
echo "---cleaning up---"
./files/adb shell rm -r /data/local/tmp/busybox
echo "---pushing SU binary---"
./files/adb push ./files/su /system/bin/su
echo "---correcting ownership and permissions for SU---"
./files/adb shell chown root.shell /system/bin/su
./files/adb shell chmod 06755 /system/bin/su
echo "---correcting symlinks---"
./files/adb shell rm /system/xbin/su
./files/adb shell ln -s /system/bin/su /system/xbin/su
echo "---Pushing Superuser app---"
./files/adb push ./files/Superuser.apk /system/app/
echo "--cleaning---"
./files/adb shell rm -r /data/local/tmp
echo "---rebooting---"
./files/adb reboot
echo "---All done, your Xperia Play has been rooted by DooMLoRD---"
echo "---This script has been ported by paxchristos!!---"
echo "---If have any questions, feel free to email me @ [email protected]"
[Removed walkthrough because it's in the PDF guide. And the PDF guide has pictures. Pretty, pretty pictures of unicorns. Or command line. You decide.]
Thank you to: cl8rs for stumbling up zergRush,
Ch4lky, ieftm, and the Revolutionary team for making (and updating zergRush)
CrimsonSentinal13 for getting us from adb root to phone rooted!
DooMLoRD for doing the script in windows, and giving me something to work off of!
Have fun people, and enjoy!!
Note: With the stock kernal, we cannot overclock, but you can underclock your cpu
Note2: Drivers were added to the first post (Crimsonsentinal13) for sake of keeping everything simpler added drivers for Xperia Play -- to get them to work (if you don't already have them installed, goto device manager, find the SEMC driver (it might show up as android device or unknown device) then update driver, and point it to this zip (unzipped, of course)
Note3: Android SDK Download link: http://developer.android.com/sdk/index.html
Note4: Unrooting?? Who would want to unroot?? One way I unrooted (using my wife's Casio Commando was to uninstall superuser.apk, and the busybox installer (i know, i didn't get rid of everything) but at that point, unless the Verizon/Phone Company employee is a genius, they won't know whether or not you're rooted
Note5: OTA Updates. We don't know what'll happen. If one comes, DENY until we can figure out what'll happen... Most likely, it'll just lose root (hopefully temporarily, we won't know until we get there) but if it bricks all the rooted Plays, I don't want an angry mob with pitchforks at my or Crimsonsentinals13's doorstep
Note6: Updated guide!! Hopefully I fixed all the errors that were in there before (thank you to all the users that pointed them out to me) and added a few things.
Note6B: Somebody had a problem with a busybox installer not downloading from the android market. attached a free one off android market that I used. I only have guesses why this happened (pm setInstallLocation 2...?) but here one is so you have that option as well...
Note6C:I also attached insecure adb. Insecure ADB is COMPLETELY OPTIONAL and should only be downloaded and installed AFTER YOU HAVE ROOT if you want to use root in adb after you reboot. Again COMPLETELY OPTIONAL and you won't necessarily need it.
Note7: As jeffkhlam found out, at no point do you need fastboot. This doesn't unlock the bootloader (no custom roms.)
Note8: If you're having issues doing this, I'll be hopping on and off the thread between 8:00am until about 11:00pm Central Standard Time. If it's not between those hours, please wait, we'll get around to helping you!
Will it work with a locked bootloader
doua27 said:
Will it work with a locked bootloader
Click to expand...
Click to collapse
Yep. My Xperia PLAY is brand new & I got it to work w/o unlocking the bootloader.
I think you forgot the Windows driver you mentioned....
sorry, i was doing it all in linux, and i forgot them they're updating in 5 seconds...
I keep getting "Cannot copy boomsh, : Permission denied" at step 16 Help?
CrimsonSentinel13 said:
All needed files have been attached.
Download all required files.
Do the following within a cmd or terminal prompt
Code:
adb shell mkdir /data/local/tmp
adb push zergRush /data/local/tmp
adb chmod 755 /data/local/tmp/zergRush
adb shell
cd /data/local/tmp/
./zergRush
adb remount
adb push su /system/bin
adb push su /system/xbin
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
exit
adb install Superuser.apk
installed BusyBox (if it doesn't show up on the system already) via any busybox installer market app
Ran SuperUser & verified settings
Code:
adb reboot
Android should be completely rooted!
Sources:
http://forum.xda-developers.com/showthread.php?t=1312082
http://forum.xda-developers.com/showthread.php?t=1296916
http://androidsu.com/superuser/
Acknowledgments: Ch4lky, ieftm, paxChristos, ChainsDD, Cl8rs
Please let me know any new information to smooth out the process. I'll modify this post to ensure it's a smooth one.
Click to expand...
Click to collapse
So if i do this and root the device but still locked bootloader does that mean that i cant install cyanogenmod?
But can used root applications?
garner said:
So if i do this and root the device but still locked bootloader does that mean that i cant install cyanogenmod?
But can used root applications?
Click to expand...
Click to collapse
Yes that's correct it's only for root apps etc. You need to unlock your bootloader for flashing custom roms and kernels. So no CyanogenMod without unlocking your BL.
Regards Dousan...
Is this is also the correct steps for r800i's ?
I'm on 2.3.3 with my r800i , i won't lose anything using this method, with a locked bootloader, just want/need root access lol
Cl8rs said:
I keep getting "Cannot copy boomsh, : Permission denied" at step 16 Help?
Click to expand...
Click to collapse
Same thing here....
CoconutWillie said:
Same thing here....
Click to expand...
Click to collapse
I think he forgot a 'cd' in step 16:
cd /data/local/tmp/zergRush 'enter'
Regards Dousan...
Alright, so after numerous tries i finally got my phone rooted. Big thanks for all the instructions.
Cl8rs said:
I keep getting "Cannot copy boomsh, : Permission denied" at step 16 Help?
Click to expand...
Click to collapse
Make sure that /data/local/tmp has permissions to give you full access.
tekken179 said:
Is this is also the correct steps for r800i's ?
I'm on 2.3.3 with my r800i , i won't lose anything using this method, with a locked bootloader, just want/need root access lol
Click to expand...
Click to collapse
I don't know how it works with the R800i. Please try it & let us know how it works.
Dousan said:
I think he forgot a 'cd' in step 16:
cd /data/local/tmp/zergRush 'enter'
Regards Dousan...
Click to expand...
Click to collapse
zergRush isn't a directory, it's a binary. Using the cd command won't work on it.
See the guide I posted, now has info to get past annoying stutters
Anybody stuck at step 16, input the following commands
1) cd /data/local/tmp
2) rm boomsh
3) rm sh
4) continue on with rooting!
Sent from my R800x using XDA App
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?....
Hello,
I have a new Fujitsu Stylistic M532 Android Tablet. It would be great if someone could help me to root this tablet.
Which Information are neccessary from the tablet?
Maybe there is a standart process to test?
Please let me know what i can do to try to root the tablet?
Best regards
Sent from my M532 using xda app-developers app
Hello again,
Here are some more information about the tablet
Android 4.0.3
Kernel 2.6.39.4
Nvidia Tegra 3 T30S
MicroSDHC Slot
Mini USB Port
Updating via an external memory card (micro SD card)
Download and copy the system update package onto an external memory card (micro SD card).
Slide the memory card (micro SD card) into your Tablet PC.
Switch your Tablet PC off by one long press of the ON/OFF switch and confirm the question on the shut down with OK.
Switch your Tablet PC on again.
When you see the Android logo on the screen, press the ON/OFF switch and the volume button (increase volume) and keep them pressed for 2 seconds and then release them.
⇒ After a few seconds you reach the Recovery menu.
Info: If the Fujitsu logo appears on the screen, then you have not reached the recovery menu. Repeat the above step until you reach the recovery menu.
Select "apply update from external storage".
Info: Navigate as follows through the menu:
Volume button (increase volume) to select an option above the current option
Volume button (decrease volume) to select an option below the current option
ON/OFF switch to confirm the selection
Follow the instructions on the screen to perform the system update.
⇒ After the system update has completed, you will be in the recovery menu again.
Select "Reboot system now" to finish the system update.
Sent from my M532 using xda app-developers app
I am also considering buying this tablet. Therefor a root manual would be highly appreciated.
Thanks.
OK. I think no one has done the root on this tabet.
Maybe somone could give me a hint what i can try to root this tablet?
I`m ready to try some some procedures
maybe a standart procedure is available for android 4?
Or is the rooting of each device different?
What happens if i try a wrong procedure? I think a recovery of the os should always be possible or not?
Maybe someone could answer some questions
Sent from my M532 using xda app-developers app
I have the same tablet. Have you already tried to root it?
Is there any guide available in the meantime?
Hi,
I also have the M532, it is really great.
Any advise how to root it would be appreciated.
Thanks for any hint.
Sent from my STYLISTIC M532
I have no fujitsu tablet, but the same model Pegatron Chagall. (exactly the same)
this set you can upgrade my Fujitsu tablet?
Rom which includes applications?
I don't think so.
Look at the detailed update procedure from Fujitsu and you will see that the update process is checking the model and version information and refuses to install if they do not match.
You're right, the update package does not work on my tablet (Síragon 4N) ... it's a shame.
However, if there is a method to be root, so if you serve ...
Even this recent tablet market, hopefully get into the right hands and can unlock.
Hey, has anyone managed to root the M532?
Is there anyone I could send my M532 to to have it rooted?
ironxp said:
I have no fujitsu tablet, but the same model Pegatron Chagall. (exactly the same)
Click to expand...
Click to collapse
+1
Could someone download the boot.img and recovery.img from this tablet? We need those files in order to modify the following values in the default.prop file
filero.secure=0
ro.debuggable=1
persist.service.adb.enable=1
Repack the images and flash it using fastboot to get a privileged shell.
After doing that you will be able to root this table using "unlockroot" software
mandraxxx said:
Could someone download the boot.img and recovery.img from this tablet? We need those files in order to modify the following values in the default.prop file
Click to expand...
Click to collapse
All you can find is a .pkg file which you need for an upgrade.
How to download boot and recovery
I would be glad to, but how do I find them and get them copied to get to you?
mandraxxx said:
Could someone download the boot.img and recovery.img from this tablet? We need those files in order to modify the following values in the default.prop file
filero.secure=0
ro.debuggable=1
persist.service.adb.enable=1
Repack the images and flash it using fastboot to get a privileged shell.
After doing that you will be able to root this table using "unlockroot" software
Click to expand...
Click to collapse
Here is the pkg file which you can download on this page
-Script by Bin4ry-
I have a Tablet Chagall / Pegatron / Siragon 4N (the same model as the Fujitsu)
I tell them that I tried several rooting script:
Cube Root for ICS 4.0.3 , Cube Root for ICS 4.0.3 v2 , DROID 3 easy root script v7, Root_with_Restore_by_Bin4ry_v8, Google Nexus 7 ToolKit, NRT_v1.5.3., superclick, El UnlockRoot..
and three do not remember ...
And no I worked ...
today ... was half annoyed, and I happened to search again Bin4ry script and found this:
"Root_with_Restore_by_Bin4ry_v10" and try with this script by several methods ... but nothing ...
(http://forum.xda-developers.com/showthread.php?t=1886460)
Then I found this old script bin4ry original,
But it did not work ...
script "Root para ICS 4.1.A.0.562"
What I did was change a few lines ... why were here on xda forum
Here the modified
*******************************************************************
@echo This is an adapted idea from the methods of
@echo Dan Rosenberg (vulnfactory.org)
@echo -Script by Bin4ry-
echo off
cd data
echo Please plug the device in ADB-Mode
adb wait-for-device
echo Rename /data/local/tmp to be able to create symlink
adb shell mv /data/local/tmp /data/local/tmp.old
echo Trying to create /data symlink
adb shell ln -s /data /data/local/tmp
adb reboot
echo Waiting for device to reboot
adb wait-for-device
adb shell rm /data/local.prop > nul
echo Trying to write value in tablet to prop-file
adb shell "echo \"filero.secure=0\" > /data/local.prop"
adb shell "echo \"ro.debuggable=1\" > /data/local.prop"
adb shell "echo \"persist.service.adb.enable=1\" > /data/local.prop"
echo Rebooting
adb reboot
echo Waiting for device to reboot again
adb wait-for-device
echo Try to remount /system
adb remount
echo Pushing su and Superuser.apk
adb push su /system/bin/su
adb shell chmod 06755 /system/bin/su
adb push Superuser.apk /system/app/Superuser.apk
adb shell chmod 644 /system/app/Superuser.apk
echo Cleanup of the Stuff created while running
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.old /data/local/tmp
adb reboot
cd ..
pause
echo Reboot and done Have fun!
*******************************************************************
Note that the only thing not to run this script to copy the application was Superuser.apk and of course change the privileges ...
Install the "superuser" from the market ... and remove the line copy the superuser, and run the whole script.
It was no root ...
I returned to run the scritp of bin4ry, V10 ... and did you root the tablet seems.
(standard option)
Check and reset the tablet, and was even root ..., delete all tablet for recovery to start once again ... and continued to root ...
But, try to certify and document the process for publishing ... and V10 bin4ry script, we apply "unroot"
Now I could not repeat the process, and I could not do root again ...
... but I notice that in the folder / system, I find the SU ...
If someone wants to try, because only must be sure that you can restart the tablet completely ... so that applications may have the lost ...
I managed to root, unroot after applying ...
I root Bin4ry the script, and then with the same script I unroot (Here)
And now I root with script WkPark (Here)
Try making the tablet fujitsu root with these script, they must work ...
My tablet is a Pegatron \ Chagall \ Síragon 4N, which is exactly equal to the Fujitsu ...
ironxp said:
I managed to root, unroot after applying ...
I root Bin4ry the script, and then with the same script I unroot (Here)
And now I root with script WkPark (Here)
Try making the tablet fujitsu root with these script, they must work ...
My tablet is a Pegatron \ Chagall \ Síragon 4N, which is exactly equal to the Fujitsu ...
Click to expand...
Click to collapse
What a pitty!
Did not work on my M532
I only get following message when i try to run the script rooting.bat
Pushing busybox...
error: device not found
error: device not found
error: device not found
rooting.sh: adb: Invalid argument
[*] Remove old fake files...
error: device not found
error: device not found
rooting.sh: adb: Invalid argument
[*] Restore fake backup...
adb: unable to connect for backup
adb: unable to connect for backup
rooting.sh: adb: Invalid argument
[*] Please look at your device and select RESTORE button!
[*] Waiting ...
error: device not found
error: device not found
rooting.sh: adb: Invalid argument
[*] Running ...error: device not found
error: device not found
rooting.sh: adb: Invalid argument
[*] check /data/local.prop
***** FAIL *****
Please retry again
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.
Best regards
quaker75 said:
What a pitty!
Did not work on my M532
I only get following message when i try to run the script rooting.bat
Pushing busybox...
error: device not found
Best regards
Click to expand...
Click to collapse
These errors are not connected in "ADB mode" to your pc
Brother, first try to install the driver of google android sdk, and not those of Fujitsu tablet (if you have one installed, it is best to uninstall and reboot the PC)
Then do a factory reset of the tablet, marking the option to delete all.
*- Active in Developer options, USB debugging, stay active and allow test location. Also active in security, unknown sources.
*- Connect the tablet (verifies that Windows recognizes it as "Android ADB Interface")
*- Run the script WkPark friend, follow the instructions and after two reboots, you will have root access to the tablet.
Performs a shutdown and start at the end and if you can run a new factory restore. Install "Root Check" of the market
*- If you do not succeed, try the same steps but running the script Bin4ry friend, and using the "Special" ... you follow the steps indicated.
Always remember to run a shutdown and startup at the end of each script ...
If you have problems with applications that are lost, do not pay much attention as you can re-run a factory reset or restore the tablet for recovery, for it ready.
I can certify that the script works Bin4ry and also the WkPark
(I have a tablet exactly like yours ... Pegatron / Chagall / Síragon 4N)