i used SuperOneClick - and my phone was on debugging mode.
after clicking 'root' button on the top, all i got was
SuperOneClick v1.6.5.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 psneuter...
1333 KB/s (585731 bytes in 0.429s)
OK
chmod psneuter...
OK
Running psneuter...
I also tried rageagainstthecage , but also all i got was ;
something something something
. . . waiting for device.
and (not responding) .
any idea ? ;(
sophialyu said:
any idea ? ;(
Click to expand...
Click to collapse
yeah, dont use SuperOneClick on the atrix
use aRoot..... its only mentioned in 5 out of 6 threads around here
do you have all the drivers installed?
what version of the OS are you running on the phone?
my os version is 2.2.1, and yes, i installed all the drivers.
also i tried aRoot, and yay!!! it seems to work.
now i got a superuser app.
thanks for your help xD !!
Related
hey i have a problem here.....
i have root my x10 mini....(as the busybox told me "your phone is rooted")
but i still have problem to open Root Explorer and used Link2SD
so... i thought that my phone was rooted wrongly.....
i do like to unroot and root it back...
but when i used SuperOneClick to unroot
it say this :
>>>
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
199 KB/s (5392 bytes in 0.026s)
OK
chmod rageagainstthecage...
- exec '/system/bin/sh' failed: Exec format error (8) -
OK
Running rageagainstthecage...
- exec '/system/bin/sh' failed: Exec format error (8) -
FAILED
<<
i have enable usb debugging
my phone Build number is :
2.1.1.A.0.6
Baseband version:
M76XX-TSNCJOYM-53404015
Firmware version:
2.1-update1
Model number:
E10i
some one please HELP me !!!
sorry 4 my bad English
Reboot your device and try running root apps.
If still the same.
Im not sure what problems are you having. Since unrooting doesnt fix your probs. Try flashing it back with seus.
It will wipe entire data. So make sure backup what you need.
Sent from my U20i using XDA Premium App
I also got the same problem too.Restoring from Sony Ericsson should be the only method to unroot your your phone.
You maybe flash X10 mini (pro) by SEUS ( Sony Ericsson Update Service). SEUS is download from sonyericsson.com. Problem is completed.
First of all, I am a complete novice at this and in hindsight should probably not have attempted to do this. If you can be of assistance, please try to use layman terms whenever possible. I am really quite clueless as to some of the jargon used on here.
Anyways, I was successful in installing unlocking the bootloader and rooting the phone, and subsequently installed the Android Revolution HD ROM. Afterwards (probably in error), I was trying to perform s-off, but while running controlbear, the screen turned to the 3 green arrows forming a circle. Now it is completely stuck like that. I have tried removing the battery, SIM card, and every other fix I have found on here but nothing is working.
I tried pressing power + down arrow but that gets be to fastboot, but none of the options help. The only options I getr are Bootloader, Reboot, Reboot Boatloader, and Power Down. Under Hboot, I have Fastboot, Recovery, Factory Reser, Clear Storage, Simlock, and Image CRC. I have tried every option and all of them lead me back to the green arrows. In addition, my SD card is not recognized my computer making it impossible to install anything from it.
Right now the phone is unlocked, with HBOOT 1.93.0002
I have tried running controlbear several times, and have gotten many different responses. Below are a few
======== ControlBear 0.7 beta for JuopunutBear S-OFF ==========
Rebooting from bootloader
Waiting...
...Waiting
Detecting...Starting up......
Connecting to device...
Searching device.....
ADB server didn't ACK
* failed to start daemon *
error:
Connect device and install drivers
Press ENTER to exit.....
Click to expand...
Click to collapse
======== ControlBear version 0.2.1 for JuopunutBear S-OFF ==========
Old beer detected...... Please wait......
Starting up......
Backing up......
Transferring backups....
Backup ok!!
Using eMMC dev /dev/block/mmcblk0
Using MMC dev /dev/block/mmcblk1
Boot partition is /dev/block/mmcblk0p22
Recovery partition is /dev/block/mmcblk0p23
Is information correct? You have 5 seconds time to press CTRL+C
Finding some beer.....
Found first....
Found second....
Found third....
Found fourth....
Hmmmm... where is that last one....... Wait a sec....
Waiting device....
Found device... Please wait...
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
** daemon still not runningerror: cannot connect to daemon
Waiting device....
** daemon still not runningerror: cannot connect to daemon
** daemon still not runningerror: cannot connect to daemon
** daemon still not runningerror: cannot connect to daemon
Found device... Please wait...
adb server is out of date. killing...
* daemon started successfully *
error: device not found
** daemon still not runningerror: cannot connect to daemon
Waiting device....
** daemon still not runningerror: cannot connect to daemon
** daemon still not runningerror: cannot connect to daemon
ADB server didn't ACK
* failed to start daemon *
error: protocol fault (no status)
ADB server didn't ACK
* failed to start daemon *
error: protocol fault (no status)
** daemon still not runningerror: cannot connect to daemon
** daemon still not runningerror: cannot connect to daemon
ADB server didn't ACK
* failed to start daemon *
Click to expand...
Click to collapse
======== ControlBear version 0.2.1 for JuopunutBear S-OFF ==========
Old beer detected...... Please wait......
Starting up......
Waiting device
Backing up......
Transferring backups....
Backup ok!!
Making room for beer......
Loading sixpacks on sdcard......
Loaded......
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Waiting device....
Found device... Please wait...
Click to expand...
Click to collapse
After doing the wire trick, I hoped it had helped but it still only boots to the arrows.
Can anyone please give me advice? I don't care if you berate me for being such a noob as I probably deserve it, but I want this damn thing to work!
Thanks in advance
Keep trying the wire trick until it confirms a successful run. You can't stop if it says its still sober. Then when its done you can reflash the ruu in bootloader.
I would, but I can't even get it back to that now.
======== ControlBear 0.7 beta for JuopunutBear S-OFF ==========
Starting up......
Connecting to device...
Searching device.....
Found device.....
Backing up......
Transferring backups....
Backup ok!!
Getting into bar.....
Raising Glass
SUCCESS - Taking a sip.
SUCCESS - Beer is tasty.
SUCCESS - Beer is tasty.
SUCCESS - Beer is tasty.
SUCCESS - Beer is tasty.
SUCCESS - Buddies and Beer
Checking alcohol level......
Let's take one more......
S-OFF Failed
Errorcode: 66732337
ErrorMsg: Still sober
Quit....
Press ENTER to exit.....
Click to expand...
Click to collapse
======== ControlBear version 0.2.1 for JuopunutBear S-OFF ==========
Old beer detected...... Please wait......
Starting up......
Backing up......
Transferring backups....
Backup ok!!
Using eMMC dev /dev/block/mmcblk0
Using MMC dev /dev/block/mmcblk1
Boot partition is /dev/block/mmcblk0p22
Recovery partition is /dev/block/mmcblk0p23
Is information correct? You have 5 seconds time to press CTRL+C
Finding some beer.....
Found first....
Found second....
Found third....
Found fourth....
Hmmmm... where is that last one....... Wait a sec....
Waiting device....
Found device... Please wait...
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
** daemon still not runningerror: cannot connect to daemon
Waiting device....
** daemon still not runningerror: cannot connect to daemon
** daemon still not runningerror: cannot connect to daemon
** daemon still not runningerror: cannot connect to daemon
Found device... Please wait...
adb server is out of date. killing...
* daemon started successfully *
error: device not found
** daemon still not runningerror: cannot connect to daemon
Waiting device....
** daemon still not runningerror: cannot connect to daemon
** daemon still not runningerror: cannot connect to daemon
ADB server didn't ACK
* failed to start daemon *
error: protocol fault (no status)
ADB server didn't ACK
* failed to start daemon *
error: protocol fault (no status)
** daemon still not runningerror: cannot connect to daemon
** daemon still not runningerror: cannot connect to daemon
ADB server didn't ACK
* failed to start daemon *
Click to expand...
Click to collapse
Close controlbear
Uninstall HTC Sync
run controlobear
======== ControlBear 0.7 beta for JuopunutBear S-OFF ==========
Starting up......
Connecting to device...
Searching device.....
Found device.....
Backing up......
Transferring backups....
Backup ok!!
Getting into bar.....
Raising Glass
SUCCESS - Taking a sip.
SUCCESS - Beer is tasty.
SUCCESS - Beer is tasty.
SUCCESS - Beer is tasty.
SUCCESS - Beer is tasty.
SUCCESS - Buddies and Beer
Checking alcohol level......
Let's take one more......
S-OFF Failed
Errorcode: 66732337
ErrorMsg: Still sober
Quit....
Press ENTER to exit.....
Click to expand...
Click to collapse
As for the other one, reduce the pause between taps to 1.5 sec
If you want to stop, open cmd & cd to the controlbear folder & type "controlbear -r" without quotes
kgs1992 said:
Close controlbear
Uninstall HTC Sync
run controlobear
As for the other one, reduce the pause between taps to 1.5 sec
If you want to stop, open cmd & cd to the controlbear folder & type "controlbear -r" without quotes
Click to expand...
Click to collapse
Ok, so I took the phone back and got a new one. I am an idiot and am thinking of trying this again :fingers-crossed:
If I decide to proceed, in what order should I try these things?
unroot
Juopunutbear S-OFF
HTC Amaze 4G All-In-One Toolkit V3.2
I am gonna punch myself in the balls if I screw this one up
A HUGE thank you kgs1992 for helping me get this done! It is much appreciated!
Thread can now be closed
Run ruu
Sent from my MyTouch 4G Slide
Yes girls know about XDA
you can thank a girl on here
amandez said:
Run ruu
Sent from my MyTouch 4G Slide
Yes girls know about XDA
you can thank a girl on here
Click to expand...
Click to collapse
You don't need to run the ruu after s-off, just simply unlock the bootloader or rebooting in general after it takes you to the bootloader should work fine, I never had to run a ruu reload after the multiple s-off's I did, dunno why it's recommended.
Dark Nightmare said:
You don't need to run the ruu after s-off, just simply unlock the bootloader or rebooting in general after it takes you to the bootloader should work fine, I never had to run a ruu reload after the multiple s-off's I did, dunno why it's recommended.
Click to expand...
Click to collapse
O ohkay
Sent from my MyTouch 4G Slide
Yes girls know about XDA
you can thank a girl on here
Hey all. I'm trying to deodex my stock rom on my at&t motorola atrix 2, running ics leak #1. I run xUltimate (v: 2.4) and all goes well, until i get to option 3 (deodex apps). It fails on ContactsProvicer2_0, and attached is the screenshot of it. Any help would be appreciated.
Also, sorry if this was in the wrong section. Mods, move it if need be.
Hi,
I want to deodex my stock rom, ICS 4.0.4, Alcatel OT 992D, MT6577 1gHz dualcore, rooted, with busybox and TWRP recovery. I have a Windows 8 64bit instaled on my laptop. Using xUltimate 2.4.2, trying also with xUltimate 2.4, but without a succses in both case. When I connect phone and pc via usb, run as administrator main.exe from /C:/xUltimate, I got message below:
Code:
* Checking Script Version.... *
* Checking Phone ROM Build.... *
* Waiting for Phone... *
adb server is out of date. killing...
* daemon started successfully *
and that's it, nothing hapends just staying forewer. I think that I have ADB driver, cause ADB and android SDK working. If I typing:
Code:
adb shell
su
from platform-tools, I got a message "shell has been granted superuser permission" on my phone display. Also, I can run comands such a "reboot", "bootanimation", etc.
Please, tell me and help me, how to run xUltimate with succes, and where is my mistake. If you need some kind of log, just tell me whichone and how to generate and I'll upload.
Thanks advance.
I have the same problem
stiw47 said:
Hi,
I want to deodex my stock rom, ICS 4.0.4, Alcatel OT 992D, MT6577 1gHz dualcore, rooted, with busybox and TWRP recovery. I have a Windows 8 64bit instaled on my laptop. Using xUltimate 2.4.2, trying also with xUltimate 2.4, but without a succses in both case. When I connect phone and pc via usb, run as administrator main.exe from /C:/xUltimate, I got message below:
Code:
* Checking Script Version.... *
* Checking Phone ROM Build.... *
* Waiting for Phone... *
adb server is out of date. killing...
* daemon started successfully *
and that's it, nothing hapends just staying forewer. I think that I have ADB driver, cause ADB and android SDK working. If I typing:
Code:
adb shell
su
from platform-tools, I got a message "shell has been granted superuser permission" on my phone display. Also, I can run comands such a "reboot", "bootanimation", etc.
Please, tell me and help me, how to run xUltimate with succes, and where is my mistake. If you need some kind of log, just tell me whichone and how to generate and I'll upload.
Thanks advance.
Click to expand...
Click to collapse
I have the same problem too
Is any body to help me?
Same problem!
Hi, I'm trying to root my galaxy s4.. I'm on a mac and doing this through a windows VM. Odin works fine, but when I run the motochopper bat file all I get is..
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
And nothing more... has someone else had success doing this on a mac or did I forget to do a critical step?
Youre doing fine. Once that comes up, check your phone. You should have a popup asking you to confirm the RSA fingerprint. Confirm it and the process should get going.
Sent from my SCH-I545 using Tapatalk 2
I've tried a script and I've tried a program. Both give the same result. On Android 5.1 by the way.
It's not because it couldn't find the serial port, by the way. It only said that this time around because I switched it from MTP to PTP like someone said to do.
Full log:
Code:
Starting adb server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Waiting for device...
Device detected!
Pushing files...
3486 KB/s (1048328 bytes in 0.293s)
1792 KB/s (9226 bytes in 0.005s)
3958 KB/s (4017098 bytes in 0.991s)
Rebooting...
Looking for LG serial port...
Serial port not found! please insert the phone manually into Download mode.
Disconnect the USB cable and turn off the phone.
Then press and hold the Volume Up button, and while you're doing that connect the USB cable again.
Waiting for device...
Phone found at COM3!
Rooting phone...
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#FAIL
#
Done!
ibounce said:
I've tried a script and I've tried a program. Both give the same result. On Android 5.1 by the way.
It's not because it couldn't find the serial port, by the way. It only said that this time around because I switched it from MTP to PTP like someone said to do.
Full log:
Code:
Starting adb server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Waiting for device...
Device detected!
Pushing files...
3486 KB/s (1048328 bytes in 0.293s)
1792 KB/s (9226 bytes in 0.005s)
3958 KB/s (4017098 bytes in 0.991s)
Rebooting...
Looking for LG serial port...
Serial port not found! please insert the phone manually into Download mode.
Disconnect the USB cable and turn off the phone.
Then press and hold the Volume Up button, and while you're doing that connect the USB cable again.
Waiting for device...
Phone found at COM3!
Rooting phone...
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#FAIL
#
Done!
Click to expand...
Click to collapse
Which version of the G Vista do you have (carrier?) and which software version is it on (not just the android version).
es0tericcha0s said:
Which version of the G Vista do you have (carrier?) and which software version is it on (not just the android version).
Click to expand...
Click to collapse
Android Version is actually 5.1.1
Carrier: Verizon
Model Number is: VS880
Software Version: VS88023A
For some reason it says "Software status: Modified" so, I don't know what that's about.
ibounce said:
Android Version is actually 5.1.1
Carrier: Verizon
Model Number is: VS880
Software Version: VS88023A
For some reason it says "Software status: Modified" so, I don't know what that's about.
Click to expand...
Click to collapse
According to the forum members on this thread http://forum.xda-developers.com/android/help/lg-g-vista-root-request-t2849017 there has not been a method to root on the update you are on. You would need to revert to an older version. Some members were having trouble with that part as well, as you can read on the last 2 or 3 pages.
es0tericcha0s said:
According to the forum members on this thread http://forum.xda-developers.com/android/help/lg-g-vista-root-request-t2849017 there has not been a method to root on the update you are on. You would need to revert to an older version. Some members were having trouble with that part as well, as you can read on the last 2 or 3 pages.
Click to expand...
Click to collapse
Aw man. Alright, well thank you for your help!
ibounce said:
Aw man. Alright, well thank you for your help!
Click to expand...
Click to collapse
You're welcome. Yea, it's confusing because it really matters about the software version it's on, and most guides are just generic and tell you it roots 5.0.x or 5.1.x without detailing the more important part as manufacturers often put out small little updates that often block root access that was found in the previous build. Especially so for ATT and VZW.