This is on the froyo dell streak 5 using Superoneclick 2.1.1
SuperOneClick v2.1.1.0
Checking drivers...
Killing ADB Server...
OK 0.04s
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 4.08s
Waiting for device...
OK 8.06s
2.2
Getting manufacturer...
Dell Inc.
OK 0.03s
Getting model...
Dell Streak
OK 0.03s
Getting version...
15697
OK 0.04s
Checking if rooted...
False
OK 0.06s
Installing BusyBox (temporary)... - Step #1
4850 KB/s (1062992 bytes in 0.214s)
OK 0.27s
Installing BusyBox (temporary)... - Step #2
OK 0.03s
Rooting device... - Step #1
4433 KB/s (585731 bytes in 0.129s)
OK 0.19s
Rooting device... - Step #2
OK 0.02s
Rooting device... - Step #3
OK 0.02s
Rooting device... - Step #4
OK 0.02s
Rooting device... - Step #5
OK 7.05s
Remounting /system with read-write access...
error: closed
FAILED
I am not a noob to rooting but noob to this dell. Is there something I am missing?
You should have searched away,this question has been asked a couple of time.USE GINGERBREAK OR SUPERUSER ETC.
Sent from my Dell Streak using XDA App
Just a heads up (I nearly missed it),
After rooting my Galaxy S2 with Doomlord's Rooting Toolkit I pulled out my N1 to see if it would work and it did! Within 30secs I was fully rooted.
My N1 was running 2.3.6 stock till now and I didn't want to wipe to be able to root and this is the way.
I know I had been waiting a long time for this so maybe it'll be useful to others.
Doomlord's Rooting Toolkit: http://forum.xda-developers.com/showthread.php?t=1319653
Zergrush Exploit: http://forum.xda-developers.com/showthread.php?t=1296916
Update: Note that several manufacturers have patched their firmware to make this exploit fail. I don't know if this still works for the N1 though I believe it should considering I haven't seen an update come out for it (could've missed it) So if it fails for you and you got a very recent firmware could be google fixed it.
Could you give a little more detailed instruction how to do it?
Instructions are in the first link.
The gist of it is
1. You need to have your phone's drivers installed for adb to work
2. set to usb debugging
3. connect usb cable
4. run the bat file
5. press space to start the process
6 30secs later (for me) it rebooted and I was rooted.
So to confirm, this I's a working Gingerbread 2.3.4 / 2.3.6 Root exploit without unlocking the bootloader?
Oh man, my Nexus is just begging to be reunited with CyanogenMod!
Sent from my Nexus One using XDA App
Airbag888 said:
Instructions are in the first link.
The gist of it is
1. You need to have your phone's drivers installed for adb to work
2. set to usb debugging
3. connect usb cable
4. run the bat file
5. press space to start the process
6 30secs later (for me) it rebooted and I was rooted.
Click to expand...
Click to collapse
Oh okay, I thought you have to do something special as you provided two links.
I just did those steps and it worked flawless.
Thanks!
@CPM
Yes it roots your phone without unlocking the Bootloader even on 2.3.6 (as is my case)
@DarsVaeda
Sorry for the confusion I was just trying to provide references and credits where due.
Works great! Thanks.
last exploit here: http://cloud.github.com/downloads/revolutionary/zergRush/zergRush.zip
Step by step:
empty /data/local/tmp/
C:\adb pust zergRush /data/loca/tmp
adb chmod 755 /data/local/tmp/zergRush
wait...
C:\adb remount
adb push su /system/bin
adb push su /system/xbin
adb push Superuser.apk /system/app
adb chmod 4755 /system/bin/su
adb chmod 4755 /system/xbin/su
reboot phone
You can su
Try: Install connectbot (or any Terminal) from Google Market connect local, type su, allow. Done.
Now remote bloatware: facebook, Amazone, twitter )
Cheers Airbag888 for bringing this exploit to our attention (and of course everyone else involved in finding the exploit and scripting it)
Works like a charm. I couldn't revert back to the older 2.3.3 Gingerbread after HTC fixed my power button. Suffered the "Main version is older" error downgrading and nothing else worked.
My Nexus is now safely reunited with CyanogenMod and I'm mighty happy
Sent from my Nexus One using XDA App
I'm new to this so I have a question!
If I root my phone using this method will i then be able to use rom manager to install cyanogen rom or do I have to do anything extra?
adamspir said:
I'm new to this so I have a dummy question!
If I root my phone using this method will i then be able to use rom manager to install cyanogen rom or do I have to do anything extra?
Click to expand...
Click to collapse
If you root via any method (this one included)
you can install a custom recovery of any kind (including clockwork which comes with Rom Manager)
you can install compatible Roms via Rom manager as well.
It should not void your warranty either since you're not unlocking your bootloader.
However make sure to do a backup before you install a new ROM and also to wipe your data/cache via recovery when you install another ROM
Thanks!
Hi !
Assuming that an unlocked bootloader wouldn't be a problem, I just tried your method, alas to no avail. Here is the output I got :
Code:
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Pressione qualquer tecla para continuar. . .
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- cleaning
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- pushing zergRush"
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting permissions
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- executing zergRush
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- 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
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- pushing busybox
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting permissions
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- remounting /system
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- copying busybox to /system/xbin/
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting ownership
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting permissions
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- installing busybox
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- pushing SU binary
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting ownership
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting permissions
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting symlinks
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- pushing Superuser app
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- cleaning
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- rebooting
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
ALL DONE!!!
Pressione qualquer tecla para continuar. . .
I just loved the "ALL DONE!!!" message in spite of every single step having failed
My config looks like this...
Nexus One
Bought directy from Google
running 2.3.6, build GRK39F
bootloader unlocked for the first time through the SDK afew moment before trying to root
MacBook pro running Windows XP
Also tried Bexton's scripts, unsuccessfully.
Out of the blue, I would blame faulty ADB drivers, but since they worked for unlocking my bootloader, I guess they're ok. I'm a bit at loss there, what do you think I did wrong?
Edit: I'm now the first result for "nexus one"+"cannot connect to daemon" on google.fr. Yay me!
I'm not an expert, merely a messenger. But it appears adb isn't starting for you somehow.
I'd look into that.
Try launching it manually and trying to get a list of connected devices. (should give one named HTC#########)
Also if you have unlocked your bootloader then there are other methods to try.
Thanks Airbag888!
For future fellow rooters in need, here is what I did :
Tried to run a sample adb command from the command line, got the dreaded "ADB server didn't ACK"
Opened the Task Manager, noticed two instances of adb running, killed them both
Ran adb devices once again, and TADAA! it worked!
Mad with hope, launched DooMLoRD's script, and so far, it's running. Right now, I've reached the "executing zergRush" stage.
It's been running for a few minutes with no error message so far... Murphy's Law dictates that the process surely is frozen
Edit:
It has indeed frozen (or silently crashed) at "executing zergRush". Killed the adb process again, started the script again. But we're making progresses, I'm now stuck at
Code:
...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
--- 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
Ad3lphi said:
Hi !
Assuming that an unlocked bootloader wouldn't be a problem, I just tried your method, alas to no avail.
Click to expand...
Click to collapse
If your bootloader is unlocked, why are you even bothering with this. Just start up your phone in fastboot mode, connect to your computer, and flash a custom recovery (i.e., fastboot flash recovery <NameOfYourRecoveryHere.img>, then boot into your custom, and flash ChainsDD's superuser zip. Done.
If your bootloader is unlocked, you never have to worry about root, because you can root at any time...
efrant said:
If your bootloader is unlocked, why are you even bothering with this.
Click to expand...
Click to collapse
Because I feel like keeping the stock ROM until the first ICS-based custom ROMS are out. I just want root access to get the hang of tinkering with my N1 and trashing some bloatware apps.
Ad3lphi said:
Because I feel like keeping the stock ROM until the first ICS-based custom ROMS are out. I just want root access to get the hang of tinkering with my N1 and trashing some bloatware apps.
Click to expand...
Click to collapse
What does that have to do with anything? Did you read the rest of my post? What I gave you was the way to root if your bootloader is unlocked. I never mentioned anything about switching ROMS...
efrant said:
Just start up your phone in fastboot mode, connect to your computer, and flash a custom recovery (i.e., fastboot flash recovery <NameOfYourRecoveryHere.img>, then boot into your custom recovery, and flash ChainsDD's superuser zip. Done.
Click to expand...
Click to collapse
Much simpler. No change to your stock ROM at all.
Finally a exploit that doesnt involve formatting my phone
Now, I am planning to run this exploit when I get home tonight
My phone at the moment is 2.3.4 and I would guess this exploit would work for it?
And I also guess you can't install clockworkmod without unlocking your bootloader?
Warmo161 said:
Finally a exploit that doesnt involve formatting my phone
Now, I am planning to run this exploit when I get home tonight
My phone at the moment is 2.3.4 and I would guess this exploit would work for it?
And I also guess you can't install clockworkmod without unlocking your bootloader?
Click to expand...
Click to collapse
I successfully rooted 2.3.4 using the exploit. Then installed RA Amon recovery rather than ClockworkMod (personal choice). Then onto CyanogenMod 7.1 and S2E for loading my apps onto SD Card. All worked perfectly fine too.
Sent from my Nexus One using XDA App
Warmo161 said:
Finally a exploit that doesnt involve formatting my phone
Now, I am planning to run this exploit when I get home tonight
My phone at the moment is 2.3.4 and I would guess this exploit would work for it?
And I also guess you can't install clockworkmod without unlocking your bootloader?
Click to expand...
Click to collapse
You don't need to unlock the bootloader to install recovery or any different rom or run nandroid backup etc
Hey,
I tried several times to root my thinkpad tablet with the Thinkpad Tablet Root Exploit but only got "Exploit failed".
Unfortunately the thinkpadforums.com is currently down so I couldn't search for solutions.
The Tablet is connected to the PC and I can see the device in adb. It's also connected to a WIFI network.
I also tried to make a factory reset -> "Exploit failed"
I don't know what to do and hope you can help me.
Thanks
Trekky
Sorry forgot to download the needed Packages in SDK..works now
Trekky said:
Sorry forgot to download the needed Packages in SDK..works now
Click to expand...
Click to collapse
Could you elaborate on this? I'm also having trouble getting the exploit to work on my tablet, even after multiple tries and a factory reset... What exactly are the packages that you installed that helped?
Cheers,
-Alrua
alrua said:
Could you elaborate on this? I'm also having trouble getting the exploit to work on my tablet, even after multiple tries and a factory reset... What exactly are the packages that you installed that helped?
Cheers,
-Alrua
Click to expand...
Click to collapse
Hey,
because the thinkpadtabletforum was down I couldn't see the instructions for the Android SDK.
I forgot
Code:
3.3 At the end of the install chose to run the Android SDK Manager.
3.4 You will need the following package for the TPT:
-Android SDK Tools
[B]-Android 3.1 (API 12)[/B]
-Extras > Google USB Driver package
Check the status column for each and if is not installed select the check box beside the packages and click the Install Packages button.
3.5 If you get a Dependencies List select the Accept All radio button and click the Install button.
I hope this helps you.
Trekky
Don't believe what your c prompt says. I've heard a lot of folk saying theirs looked like it failed, but they have root access now. Check to see of you have access to your root directory with Root Explorer, ESFile Explorer, or another app that requires root. You also may need to download SU and Terminal from Market.
Hey,
I have the same problem. I started off with a factory reset.
I can see my device in adb. It is connected to a WIFI network, it is connected by USB, the screen is on, USB debugging is also switched on. I got all the needed packages in Android SDK [except the Google TV Addon which can be found under Android 3.1 --> it says: "Not compatible with Windows"]
Here is my log (just in case)
Code:
[*] Lenovo Thinkpad Tablet root script (Windows version)
[*] Exploit copyright (C) 2012 Dan Rosenberg (@djrbliss)
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Lenovo drivers installed, that your phone is
[*] connected via USB, and that your phone is connected to a wifi
[*] network.
[*]
[*] Press any key to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[*] Let's get ready to rumble...
[*] This may take awhile...
[*] Ignore any prompts or pop-ups on your tablet.
585 KB/s (5993 bytes in 0.010s)
[*] Thinkpad Tablet Root Exploit
[*] Copyright (c) 2012 Dan Rosenberg (@djrbliss)
[-] Exploit failed.
[1] Segmentation fault /data/local/tmp/...
[*] If the words "exploit failed" appear above, exit now and try again.
[*] Note: a segmentation fault is supposed to happen and should be ignored.
[*] Otherwise, press any key to reboot and continue rooting.
Press any key to continue . . .
Even if I simply continue; the device will not be rooted afterwards. Here the log which appears after I continue after the "Exploit failed"-error:
Code:
[*] Lenovo Thinkpad Tablet root script (Windows version)
[*] Exploit copyright (C) 2012 Dan Rosenberg (@djrbliss)
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Lenovo drivers installed, that your phone is
[*] connected via USB, and that your phone is connected to a wifi
[*] network.
[*]
[*] Press any key to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[*] Let's get ready to rumble...
[*] This may take awhile...
[*] Ignore any prompts or pop-ups on your tablet.
585 KB/s (5993 bytes in 0.010s)
[*] Thinkpad Tablet Root Exploit
[*] Copyright (c) 2012 Dan Rosenberg (@djrbliss)
[-] Exploit failed.
[1] Segmentation fault /data/local/tmp/...
[*] If the words "exploit failed" appear above, exit now and try again.
[*] Note: a segmentation fault is supposed to happen and should be ignored.
[*] Otherwise, press any key to reboot and continue rooting.
Press any key to continue . . .
And yes, I am aware that for some people, although they experienced some errors as well, the root worked just well. I do not seem to be one of the lucky ones.
I don't know what I can do anymore. I followed all the steps, everything works except that stupid root.
Edit: I think this has to do with the firmware update which came in during the last days. I installed the update and tried the root just afterwards but got the same "Exploit failed" result. That was the reason why I did a factory reset in the first place.
Sorry dude, the latest update fixed the exploit. The only thing you can do now is wait till some one finds a new exploit. Either that or haope that your micro usb port breaks and then get the main board replaced as that will likely be on old version you can then do the root again, that's hoping the service engineer is feelkng helpful and run all the updates for you.
Cheers
Tom
Sent from my ThinkPad Tablet using Tapatalk
I am the same ,just waiting.....
I dont know whether its due to a locked bootloader or what but when I try to flash a new kernel (Doomlord's 2.0GHz) I get the following appear on flashtool
Code:
07/024/2012 21:24:00 - INFO - FASTBOOT version info: [ version: 0.3 ]
07/024/2012 21:24:23 - INFO - Selected kernel (boot.img or kernel.sin): C:\Program Files (x86)\Android\android-sdk\platform-tools\boot.img
07/024/2012 21:24:23 - INFO - Flashing selected kernel
[B]07/024/2012 21:24:23 - INFO - FASTBOOT Output:
sending 'boot' (7900 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.002s
07/024/2012 21:24:23 - INFO - Please check the log before rebooting into system[/B]
07/024/2012 21:24:58 - INFO - Device will now exit fastboot mode and start booting into system
07/024/2012 21:24:59 - INFO - Device disconnected
07/025/2012 21:25:15 - INFO - Device connected with USB debugging off
07/025/2012 21:25:15 - INFO - For 2011 devices line, be sure you are not in MTP mode
07/025/2012 21:25:22 - INFO - Finished Fastboot Toolbox
07/025/2012 21:25:32 - INFO - Device connected with USB debugging on
07/025/2012 21:25:35 - INFO - Connected device : R800
07/025/2012 21:25:35 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
07/025/2012 21:25:35 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
07/025/2012 21:25:38 - INFO - [B]Root Access Allowed[/B]
any ideas on how to solve this. I know this is probably a VERY NOOBY thing to ask but I can flash everything, push files VIA adb, flash ROMS and what ever but kernels are being a PITA for this R800i
Bootloader is locked, you need to unlock.
Sent from my Darkforest Powered Xperia™ PLAY
just unlocked bootloaded but now my homebutton has stopped working any ideas?
NOOB at rooting tablet. My build number is A310_02_0039_0086_US.
I've tried everything and kept getting Failed Exploit.
[*] Press any key to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[*] Let's get ready to rumble...
[*] This may take awhile...
[*] Ignore any prompts or pop-ups on your tablet.
375 KB/s (5993 bytes in 0.015s)
[*] Thinkpad Tablet Root Exploit
[*] Copyright (c) 2012 Dan Rosenberg (@djrbliss)
[-] Exploit failed.
[1] Segmentation fault /data/local/tmp/...
[*] If the words "exploit failed" appear above, exit now and try again.
[*] Note: a segmentation fault is supposed to happen and should be ignored.
[*] Otherwise, press any key to reboot and continue rooting.
Press any key to continue . . .
The djrbliss exploit has been patched from the 75 update. As you are on the 86 update it will not work. Go to www.thinkpadtabletforums.com for a more recent exploit that works on your update.
I updated my tablet to 0089( US) and used this method to root. Goodluck.
http://opdecirkel.wordpress.com/2012/03/18/yareftpt/
question
[ThinkPadTablet_A310_02_0024_0060_US.zip
Put it on SD card and plug the SD card in the tablet
I've installed it in recovery mode, wipe/cache, battery discharge and then reboot.
Tried running the batch again and Exploit Failed..
I'm wondering if i can use this method to updated my tablet to 0089( US) and try rooting again.
Any thoughts?]
Factory reset my tablet, everything seems to work right but CMD closes after Step.8
I also checked root checker but still no root..