Database Users

Android 1.x / 2.x HTC Wildfire Local Root Exploit

Hi, I just found this post on packetstormsecurity with the code of an ingenious local root exploit for HTC Wildfire, which uses a flaw in the hotplug subsystem...
packetstormsecurity.org/files/view/98106/androidwildfire-exec.txt
I'm wondering if this could be the first step for a new 1-click root app for Wildfire...
Bye

bruno820 said:
Hi, I just found this post on packetstormsecurity with the code of an ingenious local root exploit for HTC Wildfire, which uses a flaw in the hotplug subsystem...
packetstormsecurity.org/files/view/98106/androidwildfire-exec.txt
I'm wondering if this could be the first step for a new 1-click root app for Wildfire...
Bye
Click to expand...
Click to collapse
sounds promising
Martin Eve's official blog about the exploit:
martineve.com/2010/08/15/htc-wildfire-stage-1-soft-root/
Erwin

i dont have linux now, can someone compile it and put binary here as addon ?

yes, i have linux... is it just a normal gcc compile? shouldn't it have a flag for arm cpu?
tell me how to do it and i will post the binary

maybe take flags and settings from here:
http://forum.xda-developers.com/showpost.php?p=7611978&postcount=75

ErwinP said:
martineve.com/2010/08/15/htc-wildfire-stage-1-soft-root/
Erwin
Click to expand...
Click to collapse
..........

but look at this date:
http://www.exploit-db.com/author/?a=3158

I made it!
Here is the binary
PS: Ubuntu Maverick has everything needed to build for arm architecture, just apt-get it...
$ sudo apt-get install gcc-arm-linux-gnueabi g++-arm-linux-gnueabi

did you tried to run it ?

No, I didn't... I'm trying to understand what to do next
Edit: it seems that I need the USB cable to use adb tool... I will try later when I will be at home.

I tried with terminal:
cat /sdcard/exploid > /sqlite_stmt_journals/exploid
chmod 0755 /sqlite_stmt_journals/exploid
/sqlite_stmt_journals/exploid
BUT this directory does not exist,error.
there is no sqlite_stmt_journals directory in wf

Maybe you have to connect the device to adb to make that directory appear.

the same while adb

No way
I connected my Wildfire to adb...
$ ./adb push exploid /sqlite_stmt_journals/exploid
failed to copy 'exploid' to '/sqlite_stmt_journals/exploid': No such file or directory
I guess that HTC has fixed this bug... please, someone contradict me!

hmmm..
the blog is dated by: August 15, 2010 ...

Ok, I managed to run the executable (I recompiled it, it's attached)... this is the output from adb:
$ ./exploid
[*] Android local root exploid (C) The Android Exploid Crew
[*] Modified by Martin Paul Eve for Wildfire Stage 1 soft-root
[+] Using basedir=/data/local/tmp, path=/data/local/tmp/exploid
[+] opening NETLINK_KOBJECT_UEVENT socket
[+] sending add message ...
[*] Try to invoke hotplug now, clicking at the wireless
[*] settings, plugin USB key etc.
[*] You succeeded if you find /system/bin/rootshell.
[*] GUI might hang/restart meanwhile so be patient.
[1] + Stopped (signal) ./exploid
[1] Segmentation fault ./exploid
$
I copied the executable to /data/local/tmp/ because i can't find /sqlite_stmt_journals/ on my device...
And finally.... invoking hotplug (wifi on/off) does nothing!! But at least it runs...

Code:
cut
* Copy from sdcard to /sqlite_stmt_journals/exploid, chmod 0755 and run.
* Or use /data/local/tmp if available (thx to ioerror!) It is important to
* to use /sqlite_stmt_journals directory if available.
cut
find this in exploid file....give it a try
use /data/local/tmp if available....
i've tried with no success no root access, no superuser, no titanium backup...
saluti, mario

Yes, I did it indeed.
I'm starting to think that this hack is for the stock Eclair, not for Froyo...

Lol martin did this method for the soft root ages ago.
Sent from my HTC Wildfire using XDA App

Ok ok, I know... but the code has been modified and put online again on 2/2/2011 (you can read this too).
My hope was that it had been adapted to 2.2, but it seems I was wrong... we would have never know without trying

[Q] Cant root using anything and got 1.34.405.5

I dont know whats wrong but suddenly i cant root my device after i downgraded to 1.34 .. I need to turn S-ON because my device needs to go for repairs.. I follow this guide:
http://forum.xda-developers.com/showthread.php?t=928671
but for some reason when i try to launch psneuter i get some wierd permission denied error..
Code:
adb push psneuter /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
1841 KB/s (265118 bytes in 0.140s)
adb shell chmod 777 /data/local/tmp/psneuter
adb push adb shell /data/local/tmp/psneuter
PK♥8+: permission denied
∩♣ÿ☼: permission denied
☼: permission denied
/data/local/tmp/psneuter: 6: Syntax error: "|" unexpected
so im stuck ! Any suggestions ?

Da9L said:
I dont know whats wrong but suddenly i cant root my device after i downgraded to 1.34 .. I need to turn S-ON because my device needs to go for repairs.. I follow this guide:
http://forum.xda-developers.com/showthread.php?t=928671
but for some reason when i try to launch psneuter i get some wierd permission denied error..
Code:
adb push psneuter /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
1841 KB/s (265118 bytes in 0.140s)
adb shell chmod 777 /data/local/tmp/psneuter
adb push adb shell /data/local/tmp/psneuter
PK♥8+: permission denied
∩♣ÿ☼: permission denied
☼: permission denied
/data/local/tmp/psneuter: 6: Syntax error: "|" unexpected
so im stuck ! Any suggestions ?
Click to expand...
Click to collapse
I guess as you've already achieved root / S-OFF etc, you find the command to S-ON there will probably be a command switch to S-OFF. Failing that, when I S-OFF'd, it produced a backup.

craiglay said:
I guess as you've already achieved root / S-OFF etc, you find the command to S-ON there will probably be a command switch to S-OFF. Failing that, when I S-OFF'd, it produced a backup.
Click to expand...
Click to collapse
Yes i do currently have S-OFF but need S-ON again because the phone is beeing returned for repairs..

Might be able to use rage, for temp root.
Sent from my HTC Vision using XDA Premium App

Re reading your post, i'm not sure psneuter is root for 1.34 i used it to get temp root on 1.72 downgraded and used rage for root on 1.34. Look in android development for the guide to downgrade and root (no links on app) start at after the 1.34 flash bit. gfree is the app that s-off so its likely gfree can also s-on. Running gfree with no switches should give a manual page, or just search gfree switches. (I'm not responsible for bricks etc!!)
Edit, rage gives temp root on 1.34
Sent from my HTC Vision using XDA App

Okay so i've managed to get root on the device ! Finally..
However i still have trouble running gfree.. i've tried a few methods but it gives me the same output
Code:
# /data/local/gfree -r /sdcard/part7backup-1298979588.bin
/data/local/gfree -r /sdcard/part7backup-1298979588.bin
/data/local/gfree: 1: Syntax error: ")" unexpected
# /data/local/gfree -s on -c HTC__Y13
/data/local/gfree -s on -c HTC__Y13
/data/local/gfree: 1: Syntax error: ")" unexpected
I "think" i managed to get root.. when i write 'adb shell' i dont go directly to a root shell, but only '$'. Writing 'su' phone ask me if i want to let permission to give a root shell which i accept whereafter i get the '#'
EDIT: Just tried it again using a newer version of gfree.. (The one i used above was 0.4) Same problems with gfree 0.7. But i have an idea that it can be because of this:
When i download the file 'gfree_07.zip' am i supposed to just rename this file to only 'gfree' without any extension and then with push it to phone with 'adb push gfree /data/local/' ? OR am i supposed to open the zip file and extract the gfree file within it and then push that file to the phone ?

Yes, you must unzip gfree_0x.zip file and move the extracted gfree binary file to your phone as instructions (and this thread) states. Good luck!!!
How I wish we wouldn't need to do this kind of trickery just to use our own phones as we wish...

Let us know if it eork. Ive been having the same trouble
Sent from my GT-P1000T using XDA Premium App

[Q] I bricked my kindle fire with bad build.prop

I have try to edit my lines in build.prop to get better android market success, however I bricked my device after reboot.
The kindle stay in blank screen after show the kindle fire logo, it still can access through adb , and superoneclick detected it's root , but the system folder is read-only therefore I can't restore the build.prop.
I tried to use su / mount command but it can't do anything except permission denied
Is that possible to use fastboot to restore the system folder?
I tried to rename the kindle official bin to update.zip but fastboot cannot regonize it.
Anyone have a kindle fire system image dump which can be use with fastboot?
Thanks!!! and sorry for my bad english

http://forum.xda-developers.com/showthread.php?t=1356257
Sent from my Kindle Fire using xda premium

tried many time’ but it's not working, zergrush can't root the device anymore... thx

This very same thing just happened to me today, here is my fix. I know you said that zergRush isn't rooting your device but I suspect that you are missing a step somewhere.
-Make sure that zergRush is in the same folder as adb (probably /android-sdk/platform-tools)
-follow steps 1 and 2 here
-now you need to mount /system as R/W
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
chmod 777 /system
then type
Code:
exit
to get out of shell
then you should be able to push build.prop to /system (make sure you have build.prop in the same folder as adb)
Code:
adb push build.prop /system
then reboot
Code:
adb reboot
Worked perfect for me!
Let me know if you have any other questions

Here is what I get when I run ./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 ! 0x00015118
[*] Scooting ...
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[-] No path found, let's hope ...
[*] Sending 149 zerglings ...
[-] No path found, let's hope ...
[*] Sending 149 zerglings ...
[-] Zerglings did not leave interesting stuff
What is that means?
Thanks

Someone please help, I bricked my Kindle Fire with a bad build.prop as well, but when I try to run ./zergRush, it gives me the error that it is not a 2.0/2.3 Android and quits . Any ideas?

all this bricking is making me want to a wait a couple weeks till i root my fire, things don't seem real stable right now.

krighton said:
all this bricking is making me want to a wait a couple weeks till i root my fire, things don't seem real stable right now.
Click to expand...
Click to collapse
Things are only as stable as those using them! These bricks are all USER error and are not true bricks.

SikYou said:
Things are only as stable as those using them! These bricks are all USER error and are not true bricks.
Click to expand...
Click to collapse
oh i'm sure that's the case, i rooted my nook but only after it was stable across the board, knowing my own limitations. I'll keep tabs on the progress.

I bricked my kindle too a few days ago with a bad build.prop. Well, in my case, I somehow managed to move my build.prop to the wrong folder and thus was left with an unbootable kindle. I had root, but I was unable to give ADB permission to use root, so in practice I really didn't have root.
What I ended up doing to fix my kindle was booting into fastboot and then flashing a valid system.img to the system partition of the kindle. Ask around and see if anyone is willing to offer up a system.img and then search for instructions on how to flash a system.img to your fire (I think the command is:
flash -i 0x1949 system path/to/system.img

I was able to fully recover by following the instructions on this post
http://forum.xda-developers.com/showpost.php?p=19974461&postcount=23
If anyone has any questions I can answer I will do my best to do so. I kinda had to piece together information from a bunch of different posts because there is all-inclusive guide on fixing a build.prop error.

Going Out My Mind

I have a HTC Desire Z
Im From the Uk
and the phones already been unlocked
I have restored it many times and the unlock has stayed with the phone.
before this i had a iphone 4
i am trying to root my phone to use gamechi and custom roms
i have tried so many ways, gold cards, adb its all so fkin confusing
i have tried visionary z4root etc.. nothing works.
sw
2.3.3
htc sense v 2.1
htc desire z a7272
software number 2.42.161.2
i have followed steps to use the commands for terminal, followed youtube videos, done gold cards etc... its so confusing even following step by step i end up getting an error or someting doesnt work correctly. i might be wrong but im guessing my software version. 2.3.3 so i have tried to follow steps to downgrade it, still no fkin joy
please .. help?
any help will be appreciated happy christmas

C:\android-sdk-windows\platform-tools>adb shell cat /sys/class/mmc_host/mmc2/mmc
2:*/cid
035344535530384780086c959000a7f2
C:\android-sdk-windows\platform-tools>adb push psneuter /data/local/tmp
push: psneuter/psneuter.c -> /data/local/tmp/psneuter.c
push: psneuter/psneuter -> /data/local/tmp/psneuter
2 files pushed. 0 files skipped.
994 KB/s (561954 bytes in 0.552s)
C:\android-sdk-windows\platform-tools>adb push misc_version /data/local/tmp
989 KB/s (589849 bytes in 0.582s)
C:\android-sdk-windows\platform-tools>adb shell chmod 777 /data/local/tmp/psneut
er
C:\android-sdk-windows\platform-tools>adb shell chmod 777 /data/local/tmp/misc_v
ersion
C:\android-sdk-windows\platform-tools>adb shell /data/local/tmp/psneuter
Failed to set prot mask (Inappropriate ioctl for device)
again stuck

we on the same boat, been trying for 2 days now i follow almost all the guide on here and nothing works<htc vision g2 t-mobile 2.3.4..any help will be appreciated

fank god i did it
first
http://forum.xda-developers.com/showthread.php?t=1178912
follow that guide every step
ignore fast boot downgrade do a manual downgrade
that will downgrade u to 2.2 what is needed
then when done
use this guide
http://www.addictivetips.com/mobile/how-to-gain-permanent-root-on-t-mobile-g2-desire-z-without-adb/
make sure u download all the relevant files
only ones that u need for ur device
after that boom
instal rom manager
and gamechi from the market
and aptoid and aptoid repos etc...
it worked for me
and i been trying for months
the wrong fkin methos
but this works 100%
i got cyanogenmod running.
it got stuck on boot and kept looping and i was like o ****
then i did a restore and bam its perfect all round
good luck mate
it is easy just too much detail is put sometimes
so it gets confusing
but this methos works 1000000% and im so friggin happy im a chew santas knee caps off

Awesome. Was about to say the 'downgrade' here is key to your phone version since it was factory launched with Gingerbread. Glad it's all good.
Sent from my HTC Vision using XDA App

Android rooting - Linux port of DooMLoRD script - ICS as well as Gingerbread

Update: I have now also made a Linux port for DooMLoRD's rooting of ICS phones.(Sony Xperia only)
Please see attached file: Xperia-2011-ICS-ROOT-emu-Linux.zip
Note: You need flashtool for linux. Procedure remains the same as for windows.
Original script thread: http://forum.xda-developers.com/showthread.php?t=1601038
Rooting procedure: http://talk.sonymobile.com/thread/41119?start=0&tstart=0
Please update Superuser app as well as SU binary to the latest version after rooting is done successfully.
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) Create /data/local/tmp if it does not exist.
4) 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.
5) If your system already has 'adb' then it uses system 'adb' instead of one in zip-archive.
6) 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.

Very nice to know that fellow *nixers are on xda.

Thanks, I am still getting used to this forum.
Have already found answers to many of my questions regarding Android.
One thing that shocked me is Android uses Java and not C. I would have preferred C anyday.

ohk so few things
1) yes java is used mainly in Android, However look at NDK if you are a C fan.
2) dd command is used in scripts to avoid cp related issues. coz last i remember we encountered multiple errors based on scenarios where cp used to fail but dd used to work. so dd is defacto there.
@doomLord, Correct me if i am wrong.

Ah that clears dd confusion. Till now I was wondering why he chose dd? I thought may be because dd was faster for internal memory to internal memory transfer.
Since DooMLoRD is good programmer I knew there has to be a reason. And that is why I changed paxchristos script to use dd.

Updated to match with DooMLoRD's v4 script. See update on first post for details.

Just used this script on my Galaxy S 2 Skyrocket. Worked great!

Have used the script with Sony Ericsson Xperia Mini E10a Latin America.
Script runned, ADB found the device, device has rebooted correctly but... no root after reboot. Checked with Root Checker from Market.
Anyway, great script! Should work for some models.

On my phone (Milestone 2 with Gingerbread 2.3.6) the root process worked, but part of the space check it returns 90% of free space, the software does not correctly identify and delete my google maps. The following screen to evaluate and correct the bug. And congratulations for the initiative, I'd have to do it by hand when I found your script ready.
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
This script has been ported by paxchristos and modified by amish
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (16 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable 'USB DEBUGGING'
from (Menu\Settings\Applications\Development)
(3) enable 'UNKNOWN SOURCES'
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip 'PC Companion Software' prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
PRESS ENTER WITHIN 120 seconds TO CONTINUE OR ctrl-c to cancel
--Starting---
---Killing the adb server to make sure that there are no problems---
---Waiting for Device---
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
---Cleaning out any previous zergRush attempts---
mkdir failed for /data/local/tmp, File exists
rm failed for /data/local/tmp/*, No such file or directory
---Pushing zergRush---
531 KB/s (23060 bytes in 0.042s)
---Fixing permissions for zergRush---
---Running 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)
[**] 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 ...
[+] Zerglings found a way to enter ! 0x18
[+] Overseer found a path ! 0x000151e0
[*] Sending 189 zerglings ...
[+] Zerglings caused crash (good news): 0x4011ccd4 0x0074
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd19413 0xafd3925f
[*] Sending 181 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
---Waiting for Device---
---Pushing busybox---
2011 KB/s (1075144 bytes in 0.522s)
---Fixing busybox permissions---
---remounting system---
---checking free space on /system---
10 KB/s (439 bytes in 0.040s)
--- Free space on /system : 90% bytes
test: 90%: bad number
--- NOT enough free space on /system!!!
--- making free space by removing Google Maps
---copying busybox to /system/xbin---
2099+1 records in
2099+1 records out
1075144 bytes transferred in 0.084 secs (12799333 bytes/sec)
---fixing ownership and permissions---
---installing busybox---
---cleaning up---
---pushing SU binary---
546 KB/s (22228 bytes in 0.039s)
---correcting ownership and permissions for SU---
---correcting symlinks---
---Pushing Superuser app---
2160 KB/s (785801 bytes in 0.355s)
--cleaning---
---rebooting---
---All done, your Xperia has been rooted by DooMLoRD---
---This script has been ported by paxchristos and modified by amish!!---
---If have any questions, feel free to email me @ [email protected]---

Umm.... Freespace checking script was not developed by me. I have copied it directly from DooMLoRD script AS IS (had not tested it either). I think we dont need it anyway. It will be very rare that person rooting wud have run out of space. Person can re-install Google Maps (so no big harm done by bug)
But when I get the time I will check the DooMLoRD's script if there exist a bug.
Please click on THANKS if u liked my script

Your script has saved me a lot of work, because I'm tired of borrowing the notebook of my wife for flashing my phone and was looking for solutions for linux, missing root can do, I do not want to use SuperOneclick (did not want to install it just for Mono ) and go on to adapt the script DoomLord for Linux, which you did very well done. Now I can do everything on my computer with linux, what about the bug, I realized that the program was part of the original script, but I made a warning to those who wish, like me, deactivate the check room not to lose Google Maps (or have to reinstall the Market).

adb drivers in linux ?
Hy ! Can I use this script to root my Galaxy Note ? And can you say me how to install adb drivers in linux, plz ?

Just try it.
ADB is already there with script.
If you have fedora then u can install adb by running:
yum install android-tools

OK
Thank you, i will try. I didn't realize that "ADP" is the same as "ADP drivers".

well in linux there is nothing like drivers u can say
very few hardware require driver.
and when android itself is born from linux, linux shud already have support for it

Everything went well, thank you very much! We should just specify the need to execute the file "runme-linux" as root (with "sudo") ;-).
I would not to abuse, but would it be possible to have the same thing for unroot, please ?

Easy unroot for linux
Hy,
I used Amish translation to do the same for the DooMLoRD's Unrooting Script. I succesfully tried it with my phone, but REMEMBER YOU ARE DOING THIS AT YOUR OWN RISK (I suppose you know this song ;-))
DooMLoRD's instructions :
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)
More informations here http://forum.xda-developers.com/showthread.php?p=18615502 and here http://forum.xda-developers.com/showthread.php?t=1329360

I havent unrooted but I think unrooting wud be nothing but removing busybox symlinks (and busybox itself) and removing su binary and superuser.apk.

btw there is no need to run "runme-linux" as super user.
it works as normal user (recommended)

amishxda said:
btw there is no need to run "runme-linux" as super user.
it works as normal user (recommended)
Click to expand...
Click to collapse
If I run the script without sudo, the script block just after "* daemon started successfully *"
You can see below the console log :
Code:
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
This script has been ported by paxchristos and modified by amish
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (16 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable 'USB DEBUGGING'
from (Menu\Settings\Applications\Development)
(3) enable 'UNKNOWN SOURCES'
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip 'PC Companion Software' prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
PRESS ENTER WITHIN 120 seconds TO CONTINUE OR ctrl-c to cancel
--Starting---
---Killing the adb server to make sure that there are no problems---
---Waiting for Device---
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
^C [COLOR="Red"](because no reaction after 5 minutes)[/COLOR]
error: protocol fault (no status)
---Cleaning out any previous zergRush attempts---
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: insufficient permissions for device
error: insufficient permissions for device
---Pushing zergRush---
error: insufficient permissions for device
---Fixing permissions for zergRush---
error: insufficient permissions for device
---Running 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)
error: insufficient permissions for device
---Waiting for Device---
^C
If I run the same script as root (with "sudo"), the script continues without problem.