[Q] Rogers 2.2 SuperOneClick problems - Streak 5 Q&A, Help & Troubleshooting

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 !!!

Related

HELP, I've lost root!

HELP ME, I've lost root!
I ran the X10root v 1.0.8 although i already had root and now i lost root. (X10i 2.1 nordic)
If i try to root it again with the SuperOneClick thing i get the following:
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...
526 KB/s (5392 bytes in 0.010s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
ROOTED
Getting mount path...
/dev/block/mtdblock2
OK
Remounting system with read-write access...
OK
Pushing su...
failed to copy 'su' to '/system/bin/su': Permission denied
OK
Pushing superuser.apk...
2628 KB/s (196521 bytes in 0.073s)
OK
chmod su...
OK
Remounting system with read-only access...
OK
Device was not rooted!
FAILED
Click to expand...
Click to collapse
Please, help me.
EDIT:
Maybe this is also relevant: (adb shell)
# su
su
reloc_library[1245]: 3654 cannot locate '_ZNK7android6Parcel15setDataPositionEj'...CANNOT LINK EXECUTABLE
#
Click to expand...
Click to collapse
2.1 or 1.6?
X10i 2.1 nordic
theeedy said:
X10i 2.1 nordic
Click to expand...
Click to collapse
Factory reset....
:/
Sent from my X10i using XDA App
Try again - http://forum.xda-developers.com/showthread.php?t=824788
I tried it already around 10 times.
EDIT: I had to reflash the firmware -.-

[Q] Easy Root Method...

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?

[Q] SuperOne Click Error!

SuperOneClick v2.1.0.0
Checking drivers...
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
2.2.1
Getting manufacturer...
HTC
OK
Getting model...
T-Mobile myTouch 3G
OK
Getting version...
300801
OK
Checking if rooted...
False
OK
Installing BusyBox (temporary)... - Step #1
868 KB/s (1062992 bytes in 1.195s)
OK
Installing BusyBox (temporary)... - Step #2
OK
Rooting device... - Step #1
660 KB/s (585731 bytes in 0.866s)
OK
Rooting device... - Step #2
OK
Rooting device... - Step #3
OK
Rooting device... - Step #4
property service neutered.
killing adbd. (should restart in a second or two)
OK
Rooting device... - Step #5
OK
Rooting device... - Step #6
False
OK
Getting mount path...
/dev/block/mtdblock3
OK
Remounting /system with read-write access...
OK
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Pushing su-v2...
failed to copy 'C:\Users\Jose\AppData\Local\Temp\Rar$EX84.184\Root\su-v2' to '/system/xbin/su': No space left on device
OK
Installing su... - Step #1
failed to copy 'C:\Users\Jose\AppData\Local\Temp\Rar$EX84.184\Root\su-v2' to '/system/xbin/su': No space left on device
OK
Installing su... - Step #2
Unable to chmod /system/xbin/su: No such file or directory
OK
Installing su... - Step #3
Unable to chmod /system/xbin/su: No such file or directory
OK
Installing SuperUser... - Step #1
failed to copy 'C:\Users\Jose\AppData\Local\Temp\Rar$EX84.184\Root\Superuser.apk' to '/system/app/Superuser.apk': No space left on device
OK
Checking for busybox
[1] Segmentation fault busybox true
OK
Remounting /system with read-only access...
OK
OK
Running a SU test...
Test failed!
FAILED
why i cant root my android? :/
josecleocir said:
SuperOneClick v2.1.0.0
Checking drivers...
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
2.2.1
Getting manufacturer...
HTC
OK
Getting model...
T-Mobile myTouch 3G
OK
Getting version...
300801
OK
Checking if rooted...
False
OK
Installing BusyBox (temporary)... - Step #1
868 KB/s (1062992 bytes in 1.195s)
OK
Installing BusyBox (temporary)... - Step #2
OK
Rooting device... - Step #1
660 KB/s (585731 bytes in 0.866s)
OK
Rooting device... - Step #2
OK
Rooting device... - Step #3
OK
Rooting device... - Step #4
property service neutered.
killing adbd. (should restart in a second or two)
OK
Rooting device... - Step #5
OK
Rooting device... - Step #6
False
OK
Getting mount path...
/dev/block/mtdblock3
OK
Remounting /system with read-write access...
OK
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Pushing su-v2...
failed to copy 'C:\Users\Jose\AppData\Local\Temp\Rar$EX84.184\Root\su-v2' to '/system/xbin/su': No space left on device
OK
Installing su... - Step #1
failed to copy 'C:\Users\Jose\AppData\Local\Temp\Rar$EX84.184\Root\su-v2' to '/system/xbin/su': No space left on device
OK
Installing su... - Step #2
Unable to chmod /system/xbin/su: No such file or directory
OK
Installing su... - Step #3
Unable to chmod /system/xbin/su: No such file or directory
OK
Installing SuperUser... - Step #1
failed to copy 'C:\Users\Jose\AppData\Local\Temp\Rar$EX84.184\Root\Superuser.apk' to '/system/app/Superuser.apk': No space left on device
OK
Checking for busybox
[1] Segmentation fault busybox true
OK
Remounting /system with read-only access...
OK
OK
Running a SU test...
Test failed!
FAILED
why i cant root my android? :/
Click to expand...
Click to collapse
As it says you have not enough space on your device
Sent from my X8 using xda premium
Please use the Q&A Forum for questions Thanks
Moving to Q&A

[Q] Problem ReRooting 2.3.5 with Zerg

Hey everybody, I was wondering if anyone could be of any assistance in helping me out with rerooting 2.3.5? I tried using Zerg, and followed all of the instructions in one of the references (SBF to 2.3.4, apply 2.3.5 update, etc.), and I'm still having no luck. Anyone know what's going on? I'd really love to flash Eclipse 2.0.1.
Do you have usb debugging enabled along with unknown sources? What problem are you having?
Sent from my Eclipsed and ICS themed X2.
Yeah...we need more details about how it's falling to help you
I am pretty sure tho it never"told me" I was rooted.
After it completed I waited a couple minutes , reboot my phone and was good to go
Might want to also point out that he should flash 2.0.2 not 2.0.1 since the OP still says 2.0.1....
I have USB debugging enabled, along with unknown sources. Also, I have the phone set to charge mode. Anything else you guys need to know? It's pretty much just throwing tons of errors during Zerg, then after a reboot, nothing has changed. It fails to install anything. I'm on 2.3.5, just like the reference post said, so I don't understand what's going on. P.S. Eclipse 2.0.1 is the one on the post still, though I have seen 2.0.2, I don't know where I could get it, since nitro's post doesn't have it.
You might want to try usb mass storage mode. That's how I always run mine with no problems.
Sent from my Eclipsed and ICS themed X2.
i believe you have to use it on pc mode if you're using windows..100% fail proof for me and I've done this countless number of times
paul_viado said:
i believe you have to use it on pc mode if you're using windows..100% fail proof for me and I've done this countless number of times
Click to expand...
Click to collapse
Yeah that's what I thought as well
paul_viado said:
i believe you have to use it on pc mode if you're using windows..100% fail proof for me and I've done this countless number of times
Click to expand...
Click to collapse
I've tried both of PC mode and USB Mass Storage, and neither one of them worked. I kept getting device not found errors. Any help there?
I have had the same problem as the op that's why I like root keeper but I have not gone to eclipse.
Did u download zergrush as a.zip correct?
Did u make sure to extract everything to the desktop?
And do u have the correct motorola drivers installed?(32bit 64 bit)
tried uninstalling and reinstalling drivers?
Reboot computer after extracting everything to desktop?
Hook phone to computer before opening zergrush?
Lots of different things to try.
If u try all that(and more) just try a different computer.
---------- Post added at 08:33 PM ---------- Previous post was at 08:29 PM ----------
After re reading thread and seeing its device not found errors it makes me suspect motorola drivers are causing the.problem somehow.
Or maybe try a different.USB port and.even a different USB cord
ashclepdia said:
Did u download zergrush as a.zip correct?
Did u make sure to extract everything to the desktop?
And do u have the correct motorola drivers installed?(32bit 64 bit)
tried uninstalling and reinstalling drivers?
Reboot computer after extracting everything to desktop?
Hook phone to computer before opening zergrush?
Lots of different things to try.
If u try all that(and more) just try a different computer.
---------- Post added at 08:33 PM ---------- Previous post was at 08:29 PM ----------
After re reading thread and seeing its device not found errors it makes me suspect motorola drivers are causing the.problem somehow.
Or maybe try a different.USB port and.even a different USB cord
Click to expand...
Click to collapse
I tried literally ALL of these things, to no avail. The drivers are fine, though, as the device not found errors only happened when it wasn't in Charge Mode. Can anyone here read the log if I copy and paste it here?
Worth a shot.
No proMises but it might help someone understand what happening.
---------------------------------------------------------------
Easy rooting toolkit (v3.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (16 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
--- cleaning
adb server is out of date. killing...
* daemon started successfully *
--- pushing zergRush"
adb server is out of date. killing...
* daemon started successfully *
206 KB/s (23056 bytes in 0.109s)
--- correcting permissions
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
--- executing zergRush
adb server is out of date. killing...
* daemon started successfully *
./data/local/tmp/zergRush: permission denied
--- 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
adb server is out of date. killing...
* daemon started successfully *
--- pushing busybox
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
--- correcting permissions
adb server is out of date. killing...
* daemon started successfully *
Unable to chmod /data/local/tmp/busybox: No such file or directory
--- remounting /system
adb server is out of date. killing...
* daemon started successfully *
/data/local/tmp/busybox: not found
--- copying busybox to /system/xbin/
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
--- correcting ownership
adb server is out of date. killing...
* daemon started successfully *
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
adb server is out of date. killing...
* daemon started successfully *
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
rm failed for /data/local/tmp/busybox, No such file or directory
--- pushing SU binary
adb server is out of date. killing...
* daemon started successfully *
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
--- correcting permissions
adb server is out of date. killing...
* daemon started successfully *
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
adb server is out of date. killing...
* daemon started successfully *
rm failed for /system/xbin/su, Read-only file system
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
--- pushing Superuser app
adb server is out of date. killing...
* daemon started successfully *
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
--- rebooting
adb server is out of date. killing...
* daemon started successfully *
ALL DONE!!!
Press any key to continue . . .
I don't remember it telling me adb server out of date .
Could be your problem.
But I'm the last person to ask about adb sorry lol.
---------- Post added at 08:52 AM ---------- Previous post was at 08:50 AM ----------
Wait.
What 2.3.5 build are you on?
I know someone said they had problems rooting one of them...make sure its the one from Overminds thread inn development
I'm on .412, the one from Overminds post. As far as the ADB goes, I'm lost as well.
Try going to the Windows Task Manager and ending all adb.exe services and processes. Then give it a shot. From what I can gather that error comes from an old adb session being open on your computer.
Sent from my Eclipsed and ICS themed X2.
T3HBR1AN said:
Try going to the Windows Task Manager and ending all adb.exe services and processes. Then give it a shot. From what I can gather that error comes from an old adb session being open on your computer.
Sent from my Eclipsed and ICS themed X2.
Click to expand...
Click to collapse
I looked, and there was none open. I'll try again now and see if there's any difference.
What it keeps saying is that this is a Read-Only file system, and that it can't push the SU and Busybox to the right place. The only thing I'm confused about is why.
Id say thats because you haven't gained root access so the root file system is still r/o. There was one other thing I found relating to the adb out of date error but it was over my head. Where did you get your copy of zerg from?
Sent from my Eclipsed and ICS themed X2.

Can't root my phone XT910

Hi all,
I got a !#$£ù%@ problem with my phone
I explain u what i've done :
- first, my phone comes with stock SFR rom
- i root, install CWM, install fastboot files to upgrade to 651.73.30
- do a nondroid backup
- install custom rom ARCTIC 2.0.0 + update + lime theme
From here ... my phone got some bugs : no settings page and many other things
So ... i do a factory reset and now ... cant do anything to re-root my phone.
I install some different fastboot files (1.6.5.1-73_SPU-9-TA-4 / 6.5.1-73_SPU-11-PASS-10 / 6.5.1-73_SPU-11-M1-2)
I got always "permition denied" with ADB
Drivers are ok, i use USB debugging and Charge only USB mode
When i use RSD, there is no wipe ... is it normal ?
Help me please ...
Code:
Appuyez sur une touche pour continuer...
--- STARTING ----
--- WAITING FOR DEVICE
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
--- cleaning
adb server is out of date. killing...
* daemon started successfully *
rm failed for *, No such file or directory
--- pushing zergRush"
adb server is out of date. killing...
* daemon started successfully *
1876 KB/s (23056 bytes in 0.012s)
--- correcting permissions
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
--- executing zergRush
adb server is out of date. killing...
* daemon started successfully *
./data/local/tmp/zergRush: permission denied
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it the
--- DEVICE FOUND
adb server is out of date. killing...
* daemon started successfully *
^CTerminer le programme de commandes (O/N)*? o
PS : sorry for my bad english
Well i don't understand why but after 2 days of crazy zerg attacks ... this morning, all is ok and the script run perfectly ...
I think there is a little gremlin is in my house ...

Categories

Resources