[How To] First time ╰╮╰╮ROOTING╰╮╰╮ walk-through 4/28/11

root error help me please

z4 root force closes and the one click root gave me this error below HELP!!!!



************************************************** ****************************
* *
* 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
I500aa1f5c9c 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
239 KB/s (0 bytes in 1867568.007s)
73 KB/s (0 bytes in 26264.000s)
277 KB/s (0 bytes in 196521.000s)
17 KB/s (0 bytes in 5392.000s)
3 KB/s (0 bytes in 281.000s)
* 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: 12:03:35.94

*
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 . . .
 
z4 root force closes and the one click root gave me this error below HELP!!!!



************************************************** ****************************
* *
* 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
I500aa1f5c9c 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
239 KB/s (0 bytes in 1867568.007s)
73 KB/s (0 bytes in 26264.000s)
277 KB/s (0 bytes in 196521.000s)
17 KB/s (0 bytes in 5392.000s)
3 KB/s (0 bytes in 281.000s)
* 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: 12:03:35.94

*
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 . . .

You are using an old version.follow the links in the original post of this thread

Sent from my ADR6400L using Tapatalk
 
Cannot find Titanium back up pro in apps

I successfully flashed eb01. Went to the google market, d/l'ed titanium backup pro, it successfully installed, but it isn't in my apps... I tried going back to the Google Market, searched for TBUP, and it showed that I have it installed, but would not allow me to select 'run.'

I rebooted my phone, and still, TBUP does not show up in my apps. HELP! Wrong thread? Sorry...


Okay, I d/led the key, not the app. fix.t. sorry for the wasted post.
 
Last edited:
I successfully flashed eb01. Went to the google market, d/l'ed titanium backup pro, it successfully installed, but it isn't in my apps... I tried going back to the Google Market, searched for TBUP, and it showed that I have it installed, but would not allow me to select 'run.'

I rebooted my phone, and still, TBUP does not show up in my apps. HELP! Wrong thread? Sorry...


Okay, I d/led the key, not the app. fix.t. sorry for the wasted post.

:D no such thing as a wasted post. I did the same thing, twice! If you ever have to wipe data, you.ll have to do it again.
 
Can't root after OTA 2.2

I was rooted and completely forgot to unroot before the 2.2 update. The phone works fine, no errors, but I can't get the one-click to work now.
I opened the batch file and went line by line myself to find the errors, I stopped after the first one:
Code:
C:\FascinateRoot_v02>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
I500d34fe5fe    device


C:\FascinateRoot_v02>adb push busybox /data/local/tmp/busybox
1433 KB/s (1867568 bytes in 1.272s)

C:\FascinateRoot_v02>adb push su /data/local/tmp/su
466 KB/s (26264 bytes in 0.055s)

C:\FascinateRoot_v02>adb push Superuser.apk /data/local/tmp/Superuser.apk
1279 KB/s (196521 bytes in 0.150s)

C:\FascinateRoot_v02>adb push rage.bin /data/local/tmp/rage.bin
21 KB/s (5392 bytes in 0.245s)

C:\FascinateRoot_v02>adb push com.sh /data/local/tmp/com.sh
7 KB/s (281 bytes in 0.036s)

C:\FascinateRoot_v02>adb shell chmod 0755 /data/local/tmp/rage.bin

C:\FascinateRoot_v02>adb reboot

C:\FascinateRoot_v02>adb devices
List of devices attached
I500d34fe5fe    device


C:\FascinateRoot_v02>adb shell /data/local/tmp/rage.bin
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C

[*] checking NPROC limit ...
[+] RLIMIT_NPROC={2655, 2655}
[*] Searching for adb ...
[+] Found adb as PID 2367
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] 7-4-3-C@web.de so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.

C:\FascinateRoot_v02>adb devices
List of devices attached
I500d34fe5fe    device

C:\FascinateRoot_v02>adb shell sh /data/local/tmp/com.sh
mount: Operation not permitted
/data/local/tmp/com.sh: cannot create /system/xbin/su: read-only file system
/data/local/tmp/com.sh: cannot create /system/xbin/busybox: read-only file system
/data/local/tmp/com.sh: cannot create /system/app/Superuser.apk: read-only file system
Unable to chmod /system/xbin/su: Read-only file system
Unable to chmod /system/xbin/busybox: Read-only file system

C:\FascinateRoot_v02>

calling rage.bin took all of 15 seconds. I remember it taking close to 5 minutes when I rooted 2.1

Little help here?
Thanks

EDIT: Woohoo, SuperOneClick 1.8 did the trick!
 
Last edited:
  • Like
Reactions: cho232
The One-Click Root worked for me a few months back, now the rage.bin file keeps disappearing when I try to to root. Its pretty weird. I'll extract FascinateRoot_v02 and the file will be there, then I'll click start root and my phone is detected but I get "cannot open rage.bin: No such file or directory. Then when I check the FascinateRoot_v02 folder the file has vanished.

Can someone tell me whats happening here?
 
The One-Click Root worked for me a few months back, now the rage.bin file keeps disappearing when I try to to root. Its pretty weird. I'll extract FascinateRoot_v02 and the file will be there, then I'll click start root and my phone is detected but I get "cannot open rage.bin: No such file or directory. Then when I check the FascinateRoot_v02 folder the file has vanished.

Can someone tell me whats happening here?

Turn off your virus scan then do it again.

(don't forget to turn the scanner back on when you're done ;))
 
Still did not work.
************************************************** ****************************
* *
* 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
I50010bfb063 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
1124 KB/s (1867568 bytes in 1.622s)
346 KB/s (26264 bytes in 0.074s)
1523 KB/s (196521 bytes in 0.126s)
cannot open 'rage.bin': No such file or directory
6 KB/s (281 bytes in 0.045s)
* 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 for your computer to properly connect to your phone it it does not
* unplug make sure media sync is disabled
Press any key to continue . . .
*
* Testing if your device is connected
*
List of devices attached
I50010bfb063 offline

*
* 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 . . .
* 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: 23:42:10.07
*
*
** 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: read-only file system
/data/local/tmp/com.sh: cannot create /system/xbin/busybox: read-only file syste
m
/data/local/tmp/com.sh: cannot create /system/app/Superuser.apk: read-only file
system
Unable to chmod /system/xbin/su: Read-only file system
Unable to chmod /system/xbin/busybox: Read-only file system
*
* Restarting your phone now.
*
Press any key to continue . . .
* Complete
*
************************************************** ****************************
Press any key to continue . . .
 
I've rooted my phone several times, most recently about a week ago, but now when I go through the same steps as before, I get the message "device not found" ..anyone know what the issue could be?
I was on sc2.9.2, flashed to stock to get the OTA, that went successfully, didn't like it, so went back to stock and now I get that message when I try to root
 
I've rooted my phone several times, most recently about a week ago, but now when I go through the same steps as before, I get the message "device not found" ..anyone know what the issue could be?
I was on sc2.9.2, flashed to stock to get the OTA, that went successfully, didn't like it, so went back to stock and now I get that message when I try to root

If your having problems rooting this way, give this method a shot. In my opinion it is very easy. Post 5.

http://forum.androidcentral.com/verizon-fascinate-rooting-roms-hacks/66762-samsung-fascinate-rooting-eb01-return-stock-remove-system-apps-other-how.html
 
Upgrading from stock originally I tried restoring system info and it didn't work either, had to re-clear caches.
 
Anybody ever run into problems with the rage.bin getting blocked by Windows 7? I had my AV turned off and when I tried to extract, nothing after the rage.bin would go. Tried with Winzip and it said it was blocked due to the security zone. I tried on my XP system and it seemed to work until I ran START_ROOT. It said it couldn't open rage.bin because there was no such file. So, I went back to the folders and in both the zipped and extracted folders, rage.bin had been deleted. What was I doing wrong?
 
Rerooting a samsung fascinate with froyo 2.2 update

So yes I am and idiot. I have my phone root using the 1 click method.
I saw froyo 2.2 was out and i decided to download it now I don't have root access:mad: but I have super user app permanently in my apps. Is there a way I can re root my phone without wiping it? I have been searching for hours now, but can't seem to find a solid method I also tried the adb method too. Please help!!!:-[
 
So yes I am and idiot. I have my phone root using the 1 click method.
I saw froyo 2.2 was out and i decided to download it now I don't have root access:mad: but I have super user app permanently in my apps. Is there a way I can re root my phone without wiping it? I have been searching for hours now, but can't seem to find a solid method I also tried the adb method too. Please help!!!:-[

Manual with ADB
http://forum.androidcentral.com/ver...-remove-system-apps-other-how.html#post699944

clockwork flash zip root. (recommended)
http://forum.androidcentral.com/ver...-remove-system-apps-other-how.html#post700079

stock rooted odin, this will wipe your data
http://forum.androidcentral.com/ver...s-hacks/78875-odin-stock-ed01-rom-kernel.html

debloated stock odin,
http://forum.androidcentral.com/ver...l-froyo-ed01-packaged-custom-roms-w-root.html
 
Crap!!!!!

I decided to go ahead and run the update to Froyo and when my phone rebooted, I get this force close loop. The message I get is this:

"The process com.google.process.gapps has stopped unexpectedly. Please try again"

What the heck happened and how do I fix this???? I need this phone up and running ASAP! Ahhhhhh!!!!!!!!!!!
 
re:Crap

I decided to go ahead and run the update to Froyo and when my phone rebooted, I get this force close loop. The message I get is this:

"The process com.google.process.gapps has stopped unexpectedly. Please try again"

What the heck happened and how do I fix this???? I need this phone up and running ASAP! Ahhhhhh!!!!!!!!!!!

I had the same problem. Had to go with the Hard reset. The phone was unusable

YouTube - Samsung Fascinate Hard Reset
 
I decided to go ahead and run the update to Froyo and when my phone rebooted, I get this force close loop. The message I get is this:

"The process com.google.process.gapps has stopped unexpectedly. Please try again"

What the heck happened and how do I fix this???? I need this phone up and running ASAP! Ahhhhhh!!!!!!!!!!!

describe what you did more specifically please.
 
Unrooted my phone, ran the OTA update. Update completed....phone rebooted and I continued to get that error. Wasn't running any custom ROMs or anything of that nature. It was just a simple one click root.