How to Root

[n0m0n]

Step 3. Am I downloading the zip file to my SDCard or PC?
And Run Start_Root is that on my card or from my PC.

Just want to make sure.
Thanks

Can anyone share as to the above questions?
I have installed where I did not need a PC when on my Droid, and am just looking for clarity in respect to this device process.
Thanks

 

[bmidd]

Can anyone share as to the above questions?
I have installed where I did not need a PC when on my Droid, and am just looking for clarity in respect to this device process.
Thanks

To your PC. Unzip the folder and that file is in it. It truly is a one click process.

 

[sengokubattosai]

Can somebody message me the zip file? I cannot seem to download it!

 

[MarcoPSU]

yes, I downloaded there was nothing to indicate that I didn't install the drivers correctly, although for some reason when I would try to install 64bit drivers, it would install as x86 (which if I'm not mistaken is 32bit correct?)...... other than that one oddity, my computer said that the drivers installed properly. I'm stumped.

 

[MarcoPSU]

Did you install the drivers correctly? How about these steps that Dirrk posted:

OK, I figured it out. Kaspersky kept flagging the files zipped in the one 1 click root folder and preventing them from opening. So I paused protection and re-started the steps and everything worked great. And I've finally rid my Fascinate of everything Bing! So now when I use the search key it defaults to google for both normal and voice searches. Next up is to get rid of some of the VZ Bloat (that you mentioned are safe to rename in another of your posts). Thanks!

 

[flapdoodle]

error

I get an error while trying to root Fascinate.

error: more than one device and emulator

I get this error few times. and nothing happens, even tho' is says phone is restarting...

I tried few times but same message every time. PC does not have any issue with recognizing device(phone).

Thanks

 

[num1waldo]

mine said it was done but will not stop beeping at me.. beep beep beep beep and goes and goes... any sugest?

 

[jinx#AC]

Sorry to bring up an older thread but Removal of Root tool does not work.

After entering SU and mounting I do the RM for Superuser.apk and it says (in terminal on phone) -- No Such File or Directory

Any help would be appreciated.

PS: Ive done these procedures from a Terminal on my Phone and my Mac and nothing works. Superuser.apk does not exist. SU and Busybox do.

Help please

 

[dunner3106]

im having some trouble with this one click method. i have successfully rooted my old moto droid multiple times so i get the general idea of how to root a device but everytime i start this process for my fascinate it doesnt seem to work.the program runs to completion but i dont end up with SU at the end.

i end up with the following:

******************************************************************************
* *
* Dirrk's EZ Root v0.2 (Sebastien Krahmers Exploit) *
* *
******************************************************************************
*
* Testing if your device is connected
*
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
I500427ad188 device

*
* If you are NOT connected please follow these directions
* Install the correct drivers
* Turn On Debugging
* Check usb port, cable and phone

* Then rerun this application

*
Press any key to continue . . .
*
* Pushing the files to your phone
* rage.bin, busybox, Superuser.apk, su, com.sh
355 KB/s (0 bytes in 1867568.005s)
86 KB/s (0 bytes in 26264.000s)
227 KB/s (0 bytes in 196521.000s)
cannot stat 'rage.bin': No such file or directory
4 KB/s (0 bytes in 281.000s)
Unable to chmod /data/local/tmp/rage.bin: No such file or directory
* Restarting your phone to ensure the exploit will work
* When your phone comes back on please unlock it if it is locked and then
* wait
* About to exploit your device
* This will take about 3 minutes
*
* If it doesn't respond after waiting 5 minutes then it probably failed,
* so you should close this and run again
*
* Start Time: 17:08:58.63

*
*
** Successfully exploited, installing permanent root files and deleting temp fil
es
*
mount: Operation not permitted
/data/local/tmp/com.sh: cannot create /system/xbin/su: permission denied
/data/local/tmp/com.sh: cannot create /system/xbin/busybox: permission denied
/data/local/tmp/com.sh: cannot create /system/app/Superuser.apk: permission deni
ed
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
rm failed for /data/local/tmp/rage.bin, No such file or directory
*
* Restarting your phone now.
*
* Complete
*
******************************************************************************
Press any key to continue . . .

any help/advice/tips would be greatly appreciated.

 

[thebunny716]

everytime i click setup and start the drivers install it fails?

 

[jnabbott#AC]

******************************************************************************
* *
* Dirrk's EZ Root v0.2 (Sebastien Krahmers Exploit) *
* *
******************************************************************************
*
* Testing if your device is connected
*
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
I5003002bbb5 device

*
* If you are NOT connected please follow these directions
* Install the correct drivers
* Turn On Debugging
* Check usb port, cable and phone

* Then rerun this application

*
Press any key to continue . . .
*
* Pushing the files to your phone
* rage.bin, busybox, Superuser.apk, su, com.sh
654 KB/s (1867568 bytes in 2.787s)
132 KB/s (26264 bytes in 0.194s)
533 KB/s (196521 bytes in 0.360s)
3 KB/s (5392 bytes in 1.390s)
5 KB/s (281 bytes in 0.052s)
* Restarting your phone to ensure the exploit will work
* When your phone comes back on please unlock it if it is locked and then
* wait
* About to exploit your device (device shuts down)
* This will take about 3 minutes
*
* If it doesn't respond after waiting 5 minutes then it probably failed,
* so you should close this and run again
*
* Start Time: 21:09:35.58

*
error: device not found
*
** Successfully exploited, installing permanent root files and deleting temp fil
es
*
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
*
* Restarting your phone now.
*
error: device not found
* Complete
*
******************************************************************************
Press any key to continue . . . Device has now finished rebooting

All drivers are correctly installed, never had this problem before so help would be appreciated.

 

[LxiMax]

Ok. Mine went through with everything perfectly. Now what? It doesn't give you a superuser notification?

 

[jnabbott#AC]

Ok. Mine went through with everything perfectly. Now what? It doesn't give you a superuser notification?

No notificaton = no root

 

[krazymouse0]

I have the same problem as jnabbot, it says this... Can Anyone help me out?

*
* Testing if your device is connected
*
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
I5007c261713 device

*
* If you are NOT connected please follow these directions
* Install the correct drivers
* Turn On Debugging
* Check usb port, cable and phone

* Then rerun this application

*
Press any key to continue . . .
*
* Pushing the files to your phone
* rage.bin, busybox, Superuser.apk, su, com.sh
654 KB/s (1867568 bytes in 2.787s)
132 KB/s (26264 bytes in 0.194s)
533 KB/s (196521 bytes in 0.360s)
3 KB/s (5392 bytes in 1.390s)
5 KB/s (281 bytes in 0.052s)
* Restarting your phone to ensure the exploit will work
* When your phone comes back on please unlock it if it is locked and then
* wait
* About to exploit your device (device shuts down)
* This will take about 3 minutes
*
* If it doesn't respond after waiting 5 minutes then it probably failed,
* so you should close this and run again
*
* Start Time: 1:26:51.20

*
error: device not found
*
** Successfully exploited, installing permanent root files and deleting temp fil
es
*
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
*
* Restarting your phone now.
*
* Complete

 

[readimag]

Hey phone phone will get all the way up too the three min push then it just stops and says cant find device during the final copy also locks my phone up, any help would be great. Yea jsut read the post above me I have the same thing going on.

 

[ShinKen]

thank you! I was able to root my new phone using the 1-click method.

 

[mradlauer]

Ok...This is frustrating!

I was succesfully rooted, installed the .340 update and I am no longer rooted...I am using the linux version of doroot on my mac and succesfully rooted my droid x before with no issues.

I get an error message stating that the root exploit failed...

I have the superuser.apk on my phone still and everything..I'm not sure whats really going on. Does the exploit change base on version even though its still Froyo?

Any opinions or help would be greatly appreciated!

 

[lmocombe]

Super easy

Ok so I am just like many others on this thread. This whole rooting thing is new like brand new. I tried another way which took me at least 8 hours not still not figure it out. OMG this took me like 1 minute. That is why others program and I just thank them.... So now that I am all rooted can you help me get bing off and google back on.. as if I wasn't already asking too much how can I get flash on my fascinate as well? Any help is greatly appreciated and thanks for your work

 

[ardor67]

At the start I keep getting "error device offline" though my debugging is checked, I"m using the samsung usb cable, I installed the 64 bit driver on my computer, didn't work, uninstalled it and then installed the 32 bit driver and I'm still getting the same "error device offline" on my fascinate it says that that the usb is connected and debugging is on. PLEASE HELP!!!!

 

[hercmech]

ok so i did what it says, and when the phone restarts it says error:device not found, then it says complete? did it work?

++It did not work, Im thinking that it messed up by blowing past the restart part. My computer looses it as a drive then the root software seems to not find it again quick enough, then just blows through the rest of the process with errors