Database Users

SuperOneClick not givign root?

Okay, so I put my Atrix in USB debugging mode, and set it for Windows Media Sync.
This is the SuperOneClick log:
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...
1339 KB/s (585731 bytes in 0.427s)
OK
chmod psneuter...
OK
Running psneuter...
ROOTED
Pushing busybox...
1249 KB/s (1062992 bytes in 0.831s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/mmcblk0p12
OK
Reading OS Version properties...
Version: 2.2.1
OK
Remounting system with read-write access...
OK
Pushing su-v2...
1165 KB/s (26264 bytes in 0.022s)
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...
1511 KB/s (196521 bytes in 0.127s)
OK
Remounting system with read-only access...
OK
Running a SU test...
Success!
Click to expand...
Click to collapse
When I run Root Checker, I have Busybox installed correctly, but no root. I also have the SuperUser app.

Well when I did it, I didn't have it set to that, rather to the "none" setting.
After rooting, reboot the phone and see if you have super user. After confirming that, go back to the program and aacheck the install nonmarket apps.
Rooted/ROM Captivate
Rooted Atrix

FLAC Vest said:
Well when I did it, I didn't have it set to that, rather to the "none" setting.
After rooting, reboot the phone and see if you have super user. After confirming that, go back to the program and aacheck the install nonmarket apps.
Rooted/ROM Captivate
Rooted Atrix
Click to expand...
Click to collapse
Haha, that was it. Setting it to 'none', and then doing it worked for me

My issue was that the root was successful but busy box wasn't installed.

couldn't you install TiBu and install busybox through it? I did that and Busy box was there.

First do a Shell Root then after temporary root has been attained, click Root.
Oh and you might want to disable Development mode.
After that, go ahead and Enable Non-Market Apps while you're in the client.
Should be golden.

i9020T (OEM unlocked) 2.3.4 rooted using SuperOneClick 1.9.1

I don't know am I lucky or something.
Story: I manually update from 2.3.3 (with supercurio kernel) to stock 2.3.4.
OH NO!!! Low contrast comes back.
I tried some method to root the phone in order to use ROM manager (clockworkmod) but I got no success, but I did an experiment to flash the kernel using adb (I flash netarchy kernel extracted from this package http://forum.xda-developers.com/showthread.php?t=936219 ) with the following command:
cd\
cd (your adb tools location)
fastboot flash boot netarchy.img (make sure you copied the kernel to that directory to avoid hassle)
After that, I tried to run superoneclick 1.9.1 http://forum.xda-developers.com/showthread.php?t=803682 again using GingerBreak and this time it's working!!! (I was prompted to install busybox during root process).
After I restarted the phone, it's really rooted (I can use ROM manager and Root Explorer) and I run ROM manager again to flash clockworkmod and reboot to recovery. I picked this package to flash http://forum.xda-developers.com/showthread.php?t=949292 (get stock 2.3.4 version).
When you are in recovery, choose install zip package and MAKE SURE YOU TOGGLE SIGNATURE CHECK to bypass, and flash the James Bond kernel as well as other drivers.
Now my NS got "old color/contrast" and rooted. YAY!!!
Here is the log:
Code:
SuperOneClick v1.9.1.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
Getting OS Version...
2.3.4
OK
2.3.4
Pushing GingerBreak...
1264 KB/s (16830 bytes in 0.013s)
OK
chmod GingerBreak...
OK
Running GingerBreak...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
OK
Starting ADB Server...
OK
Waiting for device...
OK
Running GingerBreak...
ROOTED
Pushing busybox...
3305 KB/s (1062992 bytes in 0.314s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/platform/s3c-sdhci.0/by-name/system
OK
Remounting system with read-write access...
OK
Pushing su-v2...
693 KB/s (26264 bytes in 0.037s)
OK
chmod su...
OK
Pushing Superuser.apk...
2369 KB/s (196521 bytes in 0.081s)
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Checking for busybox
Copying busybox (/system/xbin/)...
OK
chmod busybox (/system/xbin/)...
OK
Installing busybox (/system/xbin/)...
OK
Remounting system with read-only access...
OK
Running a SU test...
Success!
Don't forget to reboot!
note: my NS is OEM unlocked

Will this work on my Nexus S running 2.3.4? About Phone Info shows the following:
Baseband Version = i9020XXKD1
Kernel version 2.6.35.7-ge382d80
[email protected] #1
Build number = GRj22
The boot loader is already unlocked.
Thanks in advance!

Anubis2k12 said:
Will this work on my Nexus S running 2.3.4? About Phone Info shows the following:
Baseband Version = i9020XXKD1
Kernel version 2.6.35.7-ge382d80
[email protected] #1
Build number = GRj22
The boot loader is already unlocked.
Thanks in advance!
Click to expand...
Click to collapse
It should work with i9020 as well. The only difference is for T-Mobile US (as long as 3G is 900/AWS/2100).

It's funny, I didn't like the fixed colors Google did to the Nexus S in 2.3.3 and higher but oh well and I got used to it... Then I was trying out some kernels (netcharty, etc.. that has "fixed" colors)...and it was back to the old way before Google fixed it.... and man holy cow, it's horrible. I can clearly see now how people were saying the original Nexus S colors were REALLY BLUE. heh.

Android rooting - Linux port of DooMLoRD script - ICS as well as Gingerbread

Update: I have now also made a Linux port for DooMLoRD's rooting of ICS phones.(Sony Xperia only)
Please see attached file: Xperia-2011-ICS-ROOT-emu-Linux.zip
Note: You need flashtool for linux. Procedure remains the same as for windows.
Original script thread: http://forum.xda-developers.com/showthread.php?t=1601038
Rooting procedure: http://talk.sonymobile.com/thread/41119?start=0&tstart=0
Please update Superuser app as well as SU binary to the latest version after rooting is done successfully.
Update: Updated as per DooMLoRD's v4.0 script with zergRush binary of 21 Nov 2011 and with makespace which deletes Google Maps if there is not enough space.(< 6MB).
Hello
I am completely new to Android but not at all new to Linux.
I used paxchristos script (ran commands manually though) to root my Sony Ericsson Live with Walkman. (WT19i / Android 2.3.4 / Build 4.0.2.A.0.58)
Source threads used:
http://forum.xda-developers.com/showthread.php?t=1319653
http://forum.xda-developers.com/showthread.php?p=18615502
In an attached file, I fixed/modified/added few things in paxchristos script. Here is the detail:
1) Fixed error in symlinking su. (source/destination were same)
2) Don't delete (and recreate) /data/local/tmp/ directory unnecessarily, just delete its contents.
3) Create /data/local/tmp if it does not exist.
4) Uses dd instead of cp (because DooMLoRD's script does, dont know why!). Update: as per anantshri, dd is used because cp has been known to give errors.
5) If your system already has 'adb' then it uses system 'adb' instead of one in zip-archive.
6) Updated zip archive to contain the latest files from DooMLoRD's archive (paxchristos archive seemed old)
Please try/verify and let me know if I missed something.
Thanks.

Very nice to know that fellow *nixers are on xda.

Thanks, I am still getting used to this forum.
Have already found answers to many of my questions regarding Android.
One thing that shocked me is Android uses Java and not C. I would have preferred C anyday.

ohk so few things
1) yes java is used mainly in Android, However look at NDK if you are a C fan.
2) dd command is used in scripts to avoid cp related issues. coz last i remember we encountered multiple errors based on scenarios where cp used to fail but dd used to work. so dd is defacto there.
@doomLord, Correct me if i am wrong.

Ah that clears dd confusion. Till now I was wondering why he chose dd? I thought may be because dd was faster for internal memory to internal memory transfer.
Since DooMLoRD is good programmer I knew there has to be a reason. And that is why I changed paxchristos script to use dd.

Updated to match with DooMLoRD's v4 script. See update on first post for details.

Just used this script on my Galaxy S 2 Skyrocket. Worked great!

Have used the script with Sony Ericsson Xperia Mini E10a Latin America.
Script runned, ADB found the device, device has rebooted correctly but... no root after reboot. Checked with Root Checker from Market.
Anyway, great script! Should work for some models.

On my phone (Milestone 2 with Gingerbread 2.3.6) the root process worked, but part of the space check it returns 90% of free space, the software does not correctly identify and delete my google maps. The following screen to evaluate and correct the bug. And congratulations for the initiative, I'd have to do it by hand when I found your script ready.
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
This script has been ported by paxchristos and modified by amish
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)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] 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 ENTER WITHIN 120 seconds TO CONTINUE OR ctrl-c to cancel
--Starting---
---Killing the adb server to make sure that there are no problems---
---Waiting for Device---
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
---Cleaning out any previous zergRush attempts---
mkdir failed for /data/local/tmp, File exists
rm failed for /data/local/tmp/*, No such file or directory
---Pushing zergRush---
531 KB/s (23060 bytes in 0.042s)
---Fixing permissions for zergRush---
---Running zergRush---
If it gets stuck here for a long time then try:
1)disconnect usb cable and reconnect it
2)toggle 'Usb Debugging' (first disable it then reenable it)
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[+] Zerglings found a way to enter ! 0x18
[+] Overseer found a path ! 0x000151e0
[*] Sending 189 zerglings ...
[+] Zerglings caused crash (good news): 0x4011ccd4 0x0074
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd19413 0xafd3925f
[*] Sending 181 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
---Waiting for Device---
---Pushing busybox---
2011 KB/s (1075144 bytes in 0.522s)
---Fixing busybox permissions---
---remounting system---
---checking free space on /system---
10 KB/s (439 bytes in 0.040s)
--- Free space on /system : 90% bytes
test: 90%: bad number
--- NOT enough free space on /system!!!
--- making free space by removing Google Maps
---copying busybox to /system/xbin---
2099+1 records in
2099+1 records out
1075144 bytes transferred in 0.084 secs (12799333 bytes/sec)
---fixing ownership and permissions---
---installing busybox---
---cleaning up---
---pushing SU binary---
546 KB/s (22228 bytes in 0.039s)
---correcting ownership and permissions for SU---
---correcting symlinks---
---Pushing Superuser app---
2160 KB/s (785801 bytes in 0.355s)
--cleaning---
---rebooting---
---All done, your Xperia has been rooted by DooMLoRD---
---This script has been ported by paxchristos and modified by amish!!---
---If have any questions, feel free to email me @ [email protected]---

Umm.... Freespace checking script was not developed by me. I have copied it directly from DooMLoRD script AS IS (had not tested it either). I think we dont need it anyway. It will be very rare that person rooting wud have run out of space. Person can re-install Google Maps (so no big harm done by bug)
But when I get the time I will check the DooMLoRD's script if there exist a bug.
Please click on THANKS if u liked my script

Your script has saved me a lot of work, because I'm tired of borrowing the notebook of my wife for flashing my phone and was looking for solutions for linux, missing root can do, I do not want to use SuperOneclick (did not want to install it just for Mono ) and go on to adapt the script DoomLord for Linux, which you did very well done. Now I can do everything on my computer with linux, what about the bug, I realized that the program was part of the original script, but I made a warning to those who wish, like me, deactivate the check room not to lose Google Maps (or have to reinstall the Market).

adb drivers in linux ?
Hy ! Can I use this script to root my Galaxy Note ? And can you say me how to install adb drivers in linux, plz ?

Just try it.
ADB is already there with script.
If you have fedora then u can install adb by running:
yum install android-tools

OK
Thank you, i will try. I didn't realize that "ADP" is the same as "ADP drivers".

well in linux there is nothing like drivers u can say
very few hardware require driver.
and when android itself is born from linux, linux shud already have support for it

Everything went well, thank you very much! We should just specify the need to execute the file "runme-linux" as root (with "sudo") ;-).
I would not to abuse, but would it be possible to have the same thing for unroot, please ?

Easy unroot for linux
Hy,
I used Amish translation to do the same for the DooMLoRD's Unrooting Script. I succesfully tried it with my phone, but REMEMBER YOU ARE DOING THIS AT YOUR OWN RISK (I suppose you know this song ;-))
DooMLoRD's instructions :
so here is the unrooting script to be USED ONLY AND ONLY IF U HAVE USED MY FILES (Easy Rooting Toolkit) FOR ROOTING
[ WARNING ]
if u have used any other way/solution for rooting then PLEASE DO NOT RUN THIS... you MIGHT END UP with damaged system...
(thats cause some ppl create symlinks for busybox in /system/bin/ which wipes out stock symlinks to /system/bin/toolbox and breaks/damages system)
More informations here http://forum.xda-developers.com/showthread.php?p=18615502 and here http://forum.xda-developers.com/showthread.php?t=1329360

I havent unrooted but I think unrooting wud be nothing but removing busybox symlinks (and busybox itself) and removing su binary and superuser.apk.

btw there is no need to run "runme-linux" as super user.
it works as normal user (recommended)

amishxda said:
btw there is no need to run "runme-linux" as super user.
it works as normal user (recommended)
Click to expand...
Click to collapse
If I run the script without sudo, the script block just after "* daemon started successfully *"
You can see below the console log :
Code:
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
This script has been ported by paxchristos and modified by amish
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)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] 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 ENTER WITHIN 120 seconds TO CONTINUE OR ctrl-c to cancel
--Starting---
---Killing the adb server to make sure that there are no problems---
---Waiting for Device---
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
^C [COLOR="Red"](because no reaction after 5 minutes)[/COLOR]
error: protocol fault (no status)
---Cleaning out any previous zergRush attempts---
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: insufficient permissions for device
error: insufficient permissions for device
---Pushing zergRush---
error: insufficient permissions for device
---Fixing permissions for zergRush---
error: insufficient permissions for device
---Running zergRush---
If it gets stuck here for a long time then try:
1)disconnect usb cable and reconnect it
2)toggle 'Usb Debugging' (first disable it then reenable it)
error: insufficient permissions for device
---Waiting for Device---
^C
If I run the same script as root (with "sudo"), the script continues without problem.

[Q] ADB Remount: Remount failed: Operation not permitted

So I was trying earlier to use ADB while trying to add WIFI to one of the ROMs.. I guess I mistyped something and now it is giving me this error..
How can I fix this? It's not really irking me but sometimes I just want to push a file through ADB and I don't want to keep having this error..
Code:
C:\adt-bundle-windows\sdk\platform-tools>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount failed: Operation not permitted
C:\adt-bundle-windows\sdk\platform-tools>adb remount
remount failed: Operation not permitted
C:\adt-bundle-windows\sdk\platform-tools>adb devices
List of devices attached
003cf8f9ded1abcc device
C:\adt-bundle-windows\sdk\platform-tools>adb root
adbd cannot run as root in production builds
C:\adt-bundle-windows\sdk\platform-tools>adb remount
remount failed: Operation not permitted
C:\adt-bundle-windows\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\adt-bundle-windows\sdk\platform-tools>adb root
adbd cannot run as root in production builds
C:\adt-bundle-windows\sdk\platform-tools>adb remount
remount failed: Operation not permitted
C:\adt-bundle-windows\sdk\platform-tools>
For some reason if I delete the whole adt-bundle-windows and extract it again from the .zip file.. It mounts but keeps getting the error
Code:
C:\adt-bundle-windows\sdk\platform-tools>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount failed: Operation not permitted
I'll be going to sleep soon, so if you need me to do something, I might not get back to you till morning.
Thanks for helping me!

You need an insecure kernel to have root in adb. Or root your phone.

klin1344 said:
You need an insecure kernel to have root in adb. Or root your phone.
Click to expand...
Click to collapse
i'm using franco.kernel - test 5.. and i am rooted? i can use supersu, ti backup, root explorer
Sent from my Nexus 4 using Tapatalk 2

Bump, any help on this?

Bumping this. I am having the same issue. Rooted on the latest stock andriod. Custom kernel as well.

You need an insecure boot.img
Either download the one on this post or enable root over adb if you are running CyanogenMod or AOKP.

Use the set of commands in the sticky.
Doesn't need an insecure kernel.

I've had this happen before. I fixed it by first killing adb with "adb kill-server", then do "adb root" to make adb run as root. Then you can "adb remount" to write to the filesystem, then push away! Hope that helps.

ess.boyer said:
I've had this happen before. I fixed it by first killing adb with "adb kill-server", then do "adb root" to make adb run as root. Then you can "adb remount" to write to the filesystem, then push away! Hope that helps.
Click to expand...
Click to collapse
This worked for me. I was pulling my hair out trying to get the system rw. adb root, did the trick. Make sure you set the phone in to root for adb in Settings/Developer option/Root Access

You are the f'ing man.

What is "adb kill-server".
ess.boyer said:
I've had this happen before. I fixed it by first killing adb with "adb kill-server", then do "adb root" to make adb run as root. Then you can "adb remount" to write to the filesystem, then push away! Hope that helps.
Click to expand...
Click to collapse
@ess.boyer;35057736 , thanks in advance , boss I am new user of android. I use Lenovo A789(ICS 4.0.4, MKT6577 from China) .I have rooted by mobile with SP_Flash_Tool_v3.1222.00 . Now I have remount problem. I want to solve it. What is "adb kill-server" . How can I get"adb kill-server"
and how can I able "adb remount" to write to the filesystem . Please help.

GUYS GUYS
i had this problem with Cyanogen and my kernel is Googy max
ye ADB ROOT command will work. But you can use adbd insecure APP and you don't need adb root command any more

what do i do with the img file??

[Q] [L3] Root problem

I try to root my LG Optimus E400 with Spectrum root.
For the first time, it's work, but i install with KDZ a default rom.
Now, i want root again but i can't.
Please help me.
Code:
[*]
[*] LG Spectrum Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest LG drivers installed, and that your tablet
[*] is connected via USB.
[*]
[*] 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.
link failed Permission denied
[*] Rebooting device...
[*] Waiting for device to reboot...
cannot create /data/local.prop: permission denied
[*] Rebooting device again...
[*] Waiting for device 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
link failed Read-only file system
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 system
[*] Cleaning up...
rm failed for /data/local.prop, No such file or directory
rm failed for /data/gpscfg/*, No such file or directory
Unable to chmod /data/: Operation not permitted
[*] Rebooting...
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
I have check USB Debugging.
I have latest drivers.

UP!
Help me please!

sKyNNNeT said:
UP!
Help me please!
Click to expand...
Click to collapse
Dont use Spectrum, use super one click 1.7

FlowUK said:
Dont use Spectrum, use super one click 1.7
Click to expand...
Click to collapse
I tryed. Don't work. He stop at step 7.
Any ideea?

sKyNNNeT said:
I tryed. Don't work. He stop at step 7.
Any ideea?
Click to expand...
Click to collapse
You need to try using a usb port at the back of your pc. Disable your anti virus. Your using rage against the cage mode right

FlowUK said:
You need to try using a usb port at the back of your pc. Disable your anti virus. Your using rage against the cage mode right
Click to expand...
Click to collapse
I'm on a laptop,i completly dezactivate antivirus, i try all ports, i try with another usb cable, i read in a place that...
Any ideea?

sKyNNNeT said:
I'm on a laptop,i completly dezactivate antivirus, i try all ports, i try with another usb cable, i read in a place that...
Any ideea?
Click to expand...
Click to collapse
use the rageagainstthecage exploit fro superoneclick 1.7
it will work

i cant root lg l3
hi evry1,
when i try rooting my lgl3(e400), it says daemon started successfully and its stuck there. plz help me, am new here n a beginner

!faQ said:
hi evry1,
when i try rooting my lgl3(e400), it says daemon started successfully and its stuck there. plz help me, am new here n a beginner
Click to expand...
Click to collapse
This is a driver problem, make sure your phone is connected the right way (USB), then enable USB Debugging on your phone, and install the latest LGE Drivers.

try degreade with kdz to v10d and then root with superoneclick 1.7 using regeagainsttheceiage exploit
works for me

ferdo.smicilkas said:
try degreade with kdz to v10d and then root with superoneclick 1.7 using regeagainsttheceiage exploit
works for me
Click to expand...
Click to collapse
Works. Thanks!

ensure that u have latest lg united drivers
Sent from my LG-E400 using xda premium