Going through all the steps for the easy root and eveything is working fine until the last step. it stopped after..
This process may take some time
adb server is out of date. killing...
* daemon started successfully *
starting final root process
1591 KB/s (585731 bytes in 0.359s)
1545 KB/s (1062992 bytes in 0.671s)
820 KB/s (26264 bytes in 0.031s)
property service neutered
killing adbd. (should restart in a second or two)
*server not running*
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adb is out of date. killing ...
Been sitting there for about 20 mins without moving.. any suggestions?
Kill ADB in taskmanager and restart it
Thanks dude.. did that and got root but with s-on.. should I just redo it again?
Hey everyone!
Ive decided to go with SOC because Im not confident to do anything else deeper yet.
Ive been having some trouble with it working. Ive gone to the following places:
http://forum.xda-developers.com/showthread.php?t=993321&highlight=SuperOneClick
http://forum.xda-developers.com/showthread.php?t=982029&highlight=SuperOneClick
http://forum.xda-developers.com/showthread.php?t=972235&highlight=SuperOneClick
When I just plugged it in and tried it this is the result:
SuperOneClick v2.1.1.0
Checking drivers...
Killing ADB Server...
OK 0.11s
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 4.14s
Waiting for device...
OK 0.09s
2.2.1
Getting manufacturer...
Dell Inc.
OK 0.05s
Getting model...
Dell Streak
OK 0.03s
Getting version...
14896
OK 0.03s
Checking if rooted...
False
OK 0.09s
Installing BusyBox (temporary)... - Step #1
1619 KB/s (1062992 bytes in 0.641s)
OK 0.75s
Installing BusyBox (temporary)... - Step #2
OK 0.04s
Rooting device... - Step #1
1629 KB/s (585731 bytes in 0.351s)
OK 0.46s
Rooting device... - Step #2
OK 0.04s
Rooting device... - Step #3
OK 0.02s
Rooting device... - Step #4
property service neutered.
killing adbd. (should restart in a second or two)
OK 0.05s
Rooting device... - Step #5
error: protocol fault (no status)
FAILED
When I tried turning off the phone, plugging it in, starting SOC and then turning the phone on when It says waiting for device:
SuperOneClick v2.1.1.0
Checking drivers...
Killing ADB Server...
OK 0.14s
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 4.16s
Waiting for device...
OK 26.09s
2.2.1
Getting manufacturer...
Dell Inc.
OK 0.03s
Getting model...
Dell Streak
OK 0.03s
Getting version...
14896
OK 0.03s
Checking if rooted...
False
OK 0.07s
Installing BusyBox (temporary)... - Step #1
3223 KB/s (1062992 bytes in 0.322s)
OK 0.43s
Installing BusyBox (temporary)... - Step #2
OK 0.03s
Rooting device... - Step #1
3091 KB/s (585731 bytes in 0.185s)
OK 0.29s
Rooting device... - Step #2
OK 0.02s
Rooting device... - Step #3
OK 0.02s
Rooting device... - Step #4
property service neutered.
killing adbd. (should restart in a second or two)
OK 0.03s
Rooting device... - Step #5
OK 8.09s
Remounting /system with read-write access...
error: closed
FAILED
Im going to try an earlier version of SOC. I will check back here a little later with results. Thanks in advance!
I HAVE ANSWERED MY OWN QUESTION / PROBLEM!!!!!!!!!!!!!!!!!!!!!!
I ran SOC 1.7 and it was fine. I just had to.......
Turn phone off.
Start SOC 1.7.
clicked rageagainstthecage
clicked root
saw this:
SuperOneClick v1.7.0.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
1053 KB/s (5392 bytes in 0.005s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
ROOTED
Pushing busybox...
2227 KB/s (1062992 bytes in 0.466s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/mtdblock6
OK
Reading OS Version properties...
Version: 2.2.1
OK
Remounting system with read-write access...
OK
Pushing su-v2...
777 KB/s (26264 bytes in 0.033s)
OK
chmod su...
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Copying busybox (/system/xbin/)...
OK
chmod busybox (/system/xbin/)...
OK
Installing busybox (/system/xbin/)...
OK
Pushing Superuser.apk...
1230 KB/s (196521 bytes in 0.156s)
OK
Remounting system with read-only access...
OK
Running a SU test...
Success!
and BAM Im rooted!
Thank God for this forum !!!
As promised, I've published my root exploit. It's possible that this exploit will wipe your /data partition. This did not happen on the two devices that have been successfully rooted, but I don't want any nasty surprises. Please back up your applications and data if you're worried about this. There is no risk of permanent damage to the device, but by running this exploit, you assume all responsibilty.
You can root your device with the following steps:
1. Ensure your device is in USB debugging mode, is connected to your PC, and that ADB works. Instructions on this are available in this thread:
http://forum.xda-developers.com/showthread.php?t=1327139
2. Download the exploit here:
http://vulnfactory.org/public/Sony_Tablet_S_Root_Windows.zip
3. Unzip the full contents of the zip.
4. Run "run.bat"
---
Full details on how the exploit works are posted here:
http://vulnfactory.org/blog/2012/02/08/rooting-the-sony-tablet-s/
I can't guarantee that this exploit will work after receiving an OTA update, including ICS. As always, when rooted, be cautious of accepting OTA updates unless you have received confirmation that the root exploit has not been patched.
If you pledged towards the bounty, details on how to donate are at the bottom of the above blog post.
Enjoy,
Dan Rosenberg (@djrbliss)
P.S. For those interested in reposting this, I have no affiliation with any forum (including XDA).
nice work!
What is the indicator of success?
I get to * daemon started successfully *, but nothing more.
@ejchis: Superuser.apk should be installed on your device and apps that needs root rights should work now (Titanium backup, AdwareBlock ect)
obicom said:
@ejchis: Superuser.apk should be installed on your device and apps that needs root rights should work now (Titanium backup, AdwareBlock ect)
Click to expand...
Click to collapse
Thanks. I'm not getting to that point for some reason. I think my adb is not functioning properly. I need to play with this some more. I've always been a terminal emulator guy, so I'm not particularly confident with my adb skills.
I can confirm that this works perfectly. Let's hope this is but the first step in making this an awesome device. Many thanks!!!
use the command "adb devices" you should see what looks like a serial number show up. If nothing shows up then you have a problem with your ADB drivers. You may just need to restart the computer.
Thank !!!
Rooted
.............
Awesome! Works great! THX!!
Works great ... full respect from my side .... well done ... !!
YOU ARE MY HERO !!!!
My adb was being funky. I found a post somewhere else through Google where someone had to rename their adb.exe file to adb.exe.exe, reboot their computer, and rename the file back to adb.exe. I did this as a stab in the dark, and my command prompt suddenly began working for me. Tablet is currently rebooting for a third time. I'm keeping my fingers crossed.
EDIT: SUCCESS! Thank you, djrbliss.
Great, thank you for this !
I tried to use the exploit after a factory reset, and I can't get it to work.
Code:
F:\Desktop\Sony_Tablet_S_Root_Windows>run.bat
[*]
[*] Sony Tablet S root script (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Before continuing, ensure USB debugging is enabled, that ADB
[*] is working properly, and that your tablet is connected via USB.
[*]
[*] WARNING: This exploit may result in wiping your /data partition,
[*] causing you to lose any applications and data on your tablet.
[*] There should be no risk of permanent damage to your device, but
[*] by running this script you accept all responsibility.
[*]
[*] Press enter to root your tablet...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] Device found.
[*] Pushing log flooder to device...
583 KB/s (5382 bytes in 0.009s)
[*] Preparing to append to packages.list...
[*] Rebooting device...
[*] Waiting for tablet to reboot.
[*] Attempting to move system package library directory...
[+] System package com.google.android.location has uid 10029
[+] Flooding log...
[*] If you received any errors in the previous step, abort the exploit
[*] and try again. Otherwise, press any key to continue.
Press any key to continue . . .
[*] Rebooting device...
[*] Waiting for tablet to reboot.
[*] Attempting to insert fake local.prop entry...
[+] Flooding log...
[*] Rebooting device...
[*] Waiting for tablet to reboot.
[*] Attemping persistence...
remount failed: Operation not permitted
failed to copy 'su' to '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
[*] Cleaning up...
failed on '/data/data/com.google.android.location/lib.bak' - Permission denied
[*] Rebooting...
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
ADB works and debugging is enabled.
Got it working. Next step is CWM and then a nice fresh cup of awesomeness. Thanks Dan. Expect a donation your way.
Judah001 said:
Is anyone able to make a YouTube video for people like me who can’t seem to figure it out? That would be totally appreciated not only by me but I’m sure the rest of our tablet S community. Thanks for root!
Click to expand...
Click to collapse
OKay
rjsmith2007 said:
I tried to use the exploit after a factory reset, and I can't get it to work.
Code:
F:\Desktop\Sony_Tablet_S_Root_Windows>run.bat
[*]
[*] Sony Tablet S root script (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Before continuing, ensure USB debugging is enabled, that ADB
[*] is working properly, and that your tablet is connected via USB.
[*]
[*] WARNING: This exploit may result in wiping your /data partition,
[*] causing you to lose any applications and data on your tablet.
[*] There should be no risk of permanent damage to your device, but
[*] by running this script you accept all responsibility.
[*]
[*] Press enter to root your tablet...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] Device found.
[*] Pushing log flooder to device...
583 KB/s (5382 bytes in 0.009s)
[*] Preparing to append to packages.list...
[*] Rebooting device...
[*] Waiting for tablet to reboot.
[*] Attempting to move system package library directory...
[+] System package com.google.android.location has uid 10029
[+] Flooding log...
[*] If you received any errors in the previous step, abort the exploit
[*] and try again. Otherwise, press any key to continue.
Press any key to continue . . .
[*] Rebooting device...
[*] Waiting for tablet to reboot.
[*] Attempting to insert fake local.prop entry...
[+] Flooding log...
[*] Rebooting device...
[*] Waiting for tablet to reboot.
[*] Attemping persistence...
remount failed: Operation not permitted
failed to copy 'su' to '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
[*] Cleaning up...
failed on '/data/data/com.google.android.location/lib.bak' - Permission denied
[*] Rebooting...
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
ADB works and debugging is enabled.
Click to expand...
Click to collapse
Try running the .bat file again, it happened to me first time, but when I tried it second time it worked.
05081983 said:
Try running the .bat file again, it happened to me first time, but when I tried it second time it worked.
Click to expand...
Click to collapse
When I run the bat file the second time, I get an error related to the files that the exploit handles:
Code:
[+] System package com.google.android.location has uid 10029
[+] Flooding log...
failed on '/data/data/com.google.android.location/lib' - Permission denied
link failed File exists[*]
Code:
F:\Desktop\Sony_Tablet_S_Root_Windows>run.bat
[*]
[*] Sony Tablet S root script (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Before continuing, ensure USB debugging is enabled, that ADB
[*] is working properly, and that your tablet is connected via USB.
[*]
[*] WARNING: This exploit may result in wiping your /data partition,
[*] causing you to lose any applications and data on your tablet.
[*] There should be no risk of permanent damage to your device, but
[*] by running this script you accept all responsibility.
[*]
[*] Press enter to root your tablet...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] Device found.
[*] Pushing log flooder to device...
656 KB/s (5382 bytes in 0.008s)
[*] Preparing to append to packages.list...
[*] Rebooting device...
[*] Waiting for tablet to reboot.
[*] Attempting to move system package library directory...
[+] System package com.google.android.location has uid 10029
[+] Flooding log...
failed on '/data/data/com.google.android.location/lib' - Permission denied
link failed File exists
[*] If you received any errors in the previous step, abort the exploit
[*] and try again. Otherwise, press any key to continue.
Press any key to continue . . .
[*] Rebooting device...
[*] Waiting for tablet to reboot.
[*] Attempting to insert fake local.prop entry...
[+] Flooding log...
[*] Rebooting device...
[*] Waiting for tablet to reboot.
[*] Attemping persistence...
remount failed: Operation not permitted
failed to copy 'su' to '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
[*] Cleaning up...
failed on '/data/data/com.google.android.location/lib.bak' - Permission denied
[*] Rebooting...
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
F:\Desktop\Sony_Tablet_S_Root_Windows>
I guess it is not so "easy" to get CWM on the tablet. As I know, CWM is part of kernel and this is signed on the Sony Tablet S ....
@Dan:
Is it right and do you see a opportunity to get CWM on Tablet S?
rjsmith2007 said:
When I run the bat file the second time, I get an error related to the files that the exploit handles:
Code:
[+] System package com.google.android.location has uid 10029
[+] Flooding log...
failed on '/data/data/com.google.android.location/lib' - Permission denied
link failed File exists[*]
Click to expand...
Click to collapse
I just uploaded a new version of the exploit that should fix this problem. Just unzip it, execute "run.bat", and let me know how it goes.
If anyone has been having any problems with the exploit, please try the new version here:
http://vulnfactory.org/public/Sony_Tablet_S_Root_Windows.zip
djrbliss said:
I just uploaded a new version of the exploit that should fix this problem. Just unzip it, execute "run.bat", and let me know how it goes.
If anyone has been having any problems with the exploit, please try the new version here:
http://vulnfactory.org/public/Sony_Tablet_S_Root_Windows.zip
Click to expand...
Click to collapse
Thanks. I'll try it out now!
Edit: I'm still getting the same end result. Should I wait for the device to boot fully to the launcher, when it asks me to press a button before it continues?
I am attempting to run and root via cyanogenmod
(same way as http://forum.xda-developers.com/showthread.php?t=2230140&highlight=supersu honestly)
This is the roots completion:
Code:
[*]
[*] Razr Blade: Motorola Droid Razr 4.1 Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Thanks to p3droid for assistance in testing.
[*]
[*] Note: this will not work on Razr HD, Razr M, etc.
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Please carefully follow any instructions provided in the exploit.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] Device found.
[*] Phase one...
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Phase two...
[*] Complete the following steps on your device:
[*] 1. Open the Smart Actions application.
[*] 2. Select "Get Started".
[*] 3. Select "Battery Saver".
[*] 4. Select "Save".
[*] 5. Press the Home button.
[*]
[*] Press enter here once you have completed the above steps.
Press any key to continue . . .
1131 KB/s (3477 bytes in 0.003s)
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Phase three (this will take a minute)...
failed on '/data/logger' - Permission denied
mkdir failed for /data/logger, File exists
Unable to chmod /data/logger: Operation not permitted
link failed File exists
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Phase four...
3097 KB/s (91992 bytes in 0.029s)
3855 KB/s (1867568 bytes in 0.473s)
3737 KB/s (574184 bytes in 0.150s)
4155 KB/s (63838 bytes in 0.015s)
[*] Cleaning up...
/system/bin/sh: su: not found
[*] Rebooting...
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
problem is that this happens...
[see attachments]
so I have no clue... i've been running it in admin and no luck.
im an idiot... took it out of mass storage and it worked.
Hello guys!
Simply I screwed up. I Installed existenz rom and simply forgot to install dual recovery before rebooting.... Of course system doesn't show up, but i flashed stock rom from ftf file. My problem is simply - how to again install double recovery? I tried this: http://teamw.in/project/twrp2/232
Of Course i tried installing by NUT installer but without any success.
Any thoughts about this?
Thx
PS. My Log from nut installer
==============================================
= =
= PhilZ Touch, CWM and TWRP Dual Recovery =
= Maintained by [NUT] =
= =
= For Many Sony Xperia Devices! =
= =
==============================================
1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on unrooted ROM using the TowelRoot method
4. Install ADB drivers to windows
5. Exit
Please choose install action.
[1,2,3,4,5]?3
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
=============================================
Getting ro.build.product
=============================================
Device model is D6503
Firmware is 17.1.2.A.0.314
=============================================
Step2 : Sending the recovery files.
=============================================
mkdir failed for /data/local/tmp/recovery, File exists
7 KB/s (29 bytes in 0.004s)
1923 KB/s (15757 bytes in 0.008s)
97 KB/s (501 bytes in 0.005s)
1445 KB/s (11842 bytes in 0.008s)
2522 KB/s (56834 bytes in 0.022s)
752 KB/s (3082 bytes in 0.004s)
93 KB/s (385 bytes in 0.004s)
3869 KB/s (657704 bytes in 0.166s)
4332 KB/s (3158546 bytes in 0.712s)
5432 KB/s (2319570 bytes in 0.417s)
4382 KB/s (1875988 bytes in 0.418s)
2170 KB/s (8889 bytes in 0.004s)
=============================================
Step3 : Setup of dual recovery.
=============================================
=============================================
Attempting to get root access for installation using TowelRoot now.
NOTE: this only works on certain ROM/Kernel versions!
If it fails, please check the development thread (Post #2) on XDA for more detai
ls.
REMEMBER THIS:
XZDualRecovery does NOT install any superuser app!!
You can use one of the recoveries to root your device.
=============================================
=============================================
Sending files
=============================================
307 KB/s (1572 bytes in 0.005s)
1474 KB/s (13592 bytes in 0.009s)
cannot stat 'easyroottool\libexploit.so': No such file or directory
1854 KB/s (9496 bytes in 0.005s)
1483 KB/s (13672 bytes in 0.009s)
Copying kernel module...
2244 KB/s (34473 bytes in 0.015s)
186 KB/s (765 bytes in 0.004s)
1327 KB/s (13592 bytes in 0.010s)
Kernel version is 3.4.0-perf-g35f9635
Version does not match 3.4.0-perf-ge4322cd, needs patching...
1+0 records in
0+1 records out
19 bytes transferred in 0.001 secs (19000 bytes/sec)
Kernel module patched.
modulecrcpatch (by zxz0O0)
module_layout: patched to 0xCFADE050
__aeabi_unwind_cpp_pr1: match
kallsyms_lookup_name: not found
printk: not found
mem_text_write_kernel_word: not found
__aeabi_unwind_cpp_pr0: match
successfully patched
=============================================
Installing using zxz0O0's towelzxperia
(using geohot's towelroot library)
=============================================
towelzxperia (by zxz0O0)
thanks to geohot for libexploit
doing the magic
error: could not open libzxploit/system/bin/sh: /system/xbin/busybox: not found
=============================================
Installation finished. Enjoy the recoveries!
=============================================
Aby kontynuować, naciśnij dowolny klawisz . . .
PS2. I'm already at 17.1.2.A.0.314 rom (4.4.2) without root
Is your bootloader locked or unlocked?
The TWRP you were posting works only with FOTAKernel-Partition, which you can only use with modified LP kernel...
Problem solved, just rooted with exploit then i installed nut dual recovery.