adb connection will be reset, what next

[jchavez]

I did the part one of fascinateroot and the dos window got stuck in the adb connection will be reset, adb server on desktop and re-login, what do I do next?

 

[Kevin Gossett]

I came across this the first time I tried on my mac. I just restarted the process, and it worked the second time around

 

[Dirrk]

I came across this the first time I tried on my mac. I just restarted the process, and it worked the second time around

Thats exactly what you need to do.

 

[jchavez]

update to my issue

actually, I could not do the one click root, it always got stuck in creating directories, so, I just follow the manual rooting, followed the commands as they were shown, and it was very easy actually and fast, I have root, downloaded terminal manager, typed su, and bingooooooo
then I installed the lagfix, so I am a happy camper now, I am just waiting for a recovery program and a rom with froyo 2.2 and this will rock, Yesterday I was about to change the phone for a droid x, but I will give it a chance, it is starting to look nice and interesting to me.

 

[aznstormin]

Got this first 2 times...well, the first time I was on a PC w no admin privileges (still ran it as admin tho). Anyway, did it on my PC at home, and it worked fine..it showed that message, but after about 2-3 minutes, it continued with the rooting process.

 

[quarky42]

I tried and got stuck there a couple times. Then I rebooted my phone and tried again. It worked perfectly at that point. I guess I should have rebooted the phone first before trying to root it.

 

[Froalskiner#WN]

I'm getting the same error. I'll try leaving it longer to see if it finishes. I was at the 10 minute mark...

 

[ellisz]

If it hangs, start over. The one time it says press any key and you go to soon, it will tell you to wait 2 minutes.

It should not stall more than a few minutes.

 

[pashacan]

I have the same problem. My device is LG Optimus One. It's v10e.

C:\Users\Seyhan>cd c:\android-sdk-windows\platform-tools

c:\android-sdk-windows\platform-tools>adb push rageagainstthecage-arm5.bin /data
/local/tmp/rageagainstthecage
43 KB/s (5392 bytes in 0.120s)

c:\android-sdk-windows\platform-tools>adb push su /data/local/tmp/
641 KB/s (26264 bytes in 0.040s)

c:\android-sdk-windows\platform-tools>adb push busybox /data/local/tmp/
1710 KB/s (1926944 bytes in 1.100s)

c:\android-sdk-windows\platform-tools>adb shell
$ chmod 4755 /data/local/tmp/rageagainstthecage
chmod 4755 /data/local/tmp/rageagainstthecage
$ chmod 4755 /data/local/tmp/busybox
chmod 4755 /data/local/tmp/busybox
$ cd /data/local/tmp
cd /data/local/tmp
$ ./rageagainstthecage
./rageagainstthecage[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3341, 3341}[*] Searching for adb ...
[+] Found adb as PID 1927[*] Spawning children. Dont type anything and wait for reset![*][*] If you like what we are doing you can send us PayPal money to[*] 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:\android-sdk-windows\platform-tools>adb shell
error: device not found

c:\android-sdk-windows\platform-tools>

Coming down here than getting stuck. Never continue. Please help me...