now i know this is pretty basic i couldnt find anywhere that tells you how to root on linux or any other unix os but here it is. Thanks goes to bubby!!! PLEASE check out his original post and HELP HIS EFFORTS
FOR bubbys ONE CLICK ROOT BUSYBOX INSTALLER SAMSUNG CONTINUUM V0.1!!
Finally, i after days of searching and trying to execute the commands for this root Manually i pulled my sd, and Formatted my phone and then Found the command to run the one click root on my continuum.
MAKE SURE YOU BACK UP YOUR FILES!! ITS A MUST,, ALSO DEFINATELY ODIN BEFORE THE ROOT.
Next, Open terminal Locate your Unzip folder i recommend you place the folder near your sdk folder Ex. CD ~/android-sdk-linux_x86/oneclickroot
since we've located the destination Check to make sure your in the right place ls. Look at the list make sure you see the run.sh Ok Now Type in the terminal
sh run.sh you should then see
One Click Root v 0.1 for the Samsung Continuum
Scripted by bubby323
read: 11: Illegal option -n
[: 18: Linux: unexpected operator
-e
Starting adb server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
-e
Copy and run the exploit (may take up to two minutes)
74 KB/s (5392 bytes in 0.070s)
0 KB/s (43 bytes in 0.075s)
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3712, 3712}
[*] Searching for adb ...
[+] Found adb as PID 2961
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
it comes to adb connection will reset, restart adb server on desktop and re-login.
unplug your phone and wait 10sec and plug it back in
then you should see
Wait for phone to reconnect...
run.sh: 77: [[: not found
Mount system as r/w, cleanup old files, do some basic configuration
rm failed for /system/bin/playlogo, No such file or directory
failed on '/system/bin/playlogo-orig' - No such file or directory
Unable to chmod /system/bin/playlogo: No such file or directory
63 KB/s (4793 bytes in 0.073s)
Copying files onto phone...
361 KB/s (26264 bytes in 0.070s)
1120 KB/s (196521 bytes in 0.171s)
1219 KB/s (978414 bytes in 0.783s)
1207 KB/s (486948 bytes in 0.393s)
9 KB/s (483 bytes in 0.051s)
Setting permissions...
Installing busybox...
Waiting for phone to reboot...
run.sh: 117: [[: not found
Cleaning up files...
read: 129: Illegal option -n
now your rooted to check go to the market and try installing Titanium back-up
if all goes well you have root access
Related
Hei All, Nubie got problem here, and getting crazy LOL..
I have Droid X ME811, and it has been 2 weeks I've trying to rooting my droid in manual way, im following this awesome steps
and what happen is I always get stuck when I try to restart adb because after restart adb device cant be detected anymore.
C:\android-sdk-windows\tools>adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ cd data/local/tmp
cd data/local/tmp
$ chmod 0755 rageagainstthecage-arm5.bin
chmod 0755 rageagainstthecage-arm5.bin
$ ./rageagainstthecage-arm5.bin
./rageagainstthecage-arm5.bin
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3814, 3814}
[*] Searching for adb ...
[+] Found adb as PID 1170
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$
C:\android-sdk-windows\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
(in this step, list always empty)
so I cant go to the next steps, I also try to go back to step $ cd data/local/tmp.
but seems like no different.
need advise
same exact problem here
Followed exact same steps, tried manually with adb, also tried other roms, pc mode, all other modes..nothing seems to work help please! I'm using ubuntu, adb works fine otherwise. Thanks
Hello everyone...
I've just read almost everything available for rooting the SE Live with Walkman (W9Ti) and simply could not root it. Zergrush details and phone specs are pasted for your reference. "Please Help".
---------------------------------------------------------------
Easy rooting toolkit (v4.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 (21 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 any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
adb server is out of date. killing...
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
1801 KB/s (23060 bytes in 0.012s)
--- correcting permissions
--- executing zergRush
[**] 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 ...
[-] Hellions with BLUE flames !
--- 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
--- pushing busybox
3716 KB/s (1075144 bytes in 0.282s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
68 KB/s (439 bytes in 0.006s)
--- Free space on /system : 179904 bytes
--- no cleanup required
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
c4capricorn said:
Hello everyone...
I've just read almost everything available for rooting the SE Live with Walkman (W9Ti) and simply could not root it. Zergrush details and phone specs are pasted for your reference. "Please Help".
---------------------------------------------------------------
Easy rooting toolkit (v4.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 (21 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 any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
adb server is out of date. killing...
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
1801 KB/s (23060 bytes in 0.012s)
--- correcting permissions
--- executing zergRush
[**] 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 ...
[-] Hellions with BLUE flames !
--- 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
--- pushing busybox
3716 KB/s (1075144 bytes in 0.282s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
68 KB/s (439 bytes in 0.006s)
--- Free space on /system : 179904 bytes
--- no cleanup required
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
Click to expand...
Click to collapse
Hi c4capricorn,
I have the same problem.
Do you find the solution?
Hey guys,
Just get the phone, so nothing is changed except turning on "debugging mode"
It's a HUAWEI Y201 PRO running Android 4.0.3
I like to use some apps as root and therefore I tried Root_with_Restore_by_Bin4ry_v18
Cause I'm running Ubuntu I configured /etc/udev/rules.d/99-android.rules and added the phone there.
adb is installed and seems to work well
Code:
[email protected]:~$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
78F5FD159EAB device
and running the script:
Code:
[email protected]:~/Downloads/Root_with_Restore_by_Bin4ry_v18$ sudo ./RunMe.sh
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (18.12.2012) v17 =
= ported to Linux by Kamistral (15.09.2012), =
= updated by codeworkx (01.10.2012) =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice:
1
Normal mode enabled!
Checking if i should run in Normal Mode or special Sony Mode
Please connect device with ADB-Debugging enabled now ...
remote object '/system/bin/ric' does not exist
remote object '/system/app/Backup-Restore.apk' does not exist
Normal Mode enabled!
Please connect device with ADB-Debugging enabled now ...
Pushing busybox ...
4697 KB/s (1085140 bytes in 0.225s)
Pushing su binary ...
3789 KB/s (91980 bytes in 0.023s)
Pushing Superuser app
4021 KB/s (996704 bytes in 0.242s)
Pushing ric
1 KB/s (57 bytes in 0.040s)
Making busybox runable ...
Now unlock your device and confirm the restore operation.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
Successful, going to reboot your device in 10 seconds!
Waiting for device to show up again ...
Copying files to it's place ...
mount: permission denied (are you root?)
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press key to exit ...
So there is trouble with mounting it. If I did everything in the right way the script seems not working for HUAWEI Y201 PRO
Maybe someone of you could add the phone.
BTW in the head is still v17 instead of v18
Have fun
I'm trying to root my Kindle Fire - my end goal is to get Jellybean running on it. I'm running Xubuntu on my desktop. Here's the process for rooting:
---------------------------------------------------------------
Easy rooting toolkit (v2.0)
created by DooMLoRD
Modified for Kindle Fire for Linux/Mac by Max Lee at RootKindleFire.com
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 (10 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
[*] Before u begin:
(1) enable USB DEBUGGING
from (Menu\Settings\Applications\Development)
(2) enable UNKNOWN SOURCES
from (Menu\Settings\Applications)
(3) [OPTIONAL] increase screen timeout to 10 minutes
(4) connect USB cable to PHONE and then connect 2 computer
---------------------------------------------------------------
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
563 KB/s (23056 bytes in 0.039s)
--- correcting permissions
--- executing zergRush
[**] 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 ! 0x00015118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- 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
--- pushing busybox
4395 KB/s (1075144 bytes in 0.238s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'Superuser.apk' to '/system/app/./Superuser.apk': Read-only file system
--- cleaning
--- rebooting
--- WAITING FOR DEVICE
5139 KB/s (3104805 bytes in 0.589s)
Error: Could not access the Package Manager. Is the system running?
All Done, Kindle Fire ROOTED!!!
Check out RootKindleFire.com for more cool hacks!
Click to expand...
Click to collapse
I'm running the command with sudo. The device is recognized as follows:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
5AA6002600000001 device
Click to expand...
Click to collapse
I've tried googling to solve, and either I'm coming up with the wrong terms, or... dunno. Found a ton of pages, but most of it is from a Windows perspective. Found a link to Kindle Fire Utility port for Linux, but link was dead.
I've tried running the above both with the Fire in USB mode and not (i.e. "disconnect").
Any ideas and insight would be quite welcome. I certainly don't mind relevant links to other places, either - I may well have missed relevant resources in my searching.
edit: Also, my adb_usb.ini file did initially contain 0x1949; per some threads I found I added 0x0006, which got my farther along, at least.
subedit: sorry for the delay in this edit, 5min wait time to edit my post. d'oh.
After the device fails like that, have you tried running the root process again immediately?
Sent from my Nexus 7 using Tapatalk
SwoRNLeaDejZ said:
After the device fails like that, have you tried running the root process again immediately?
Click to expand...
Click to collapse
Alas, yes. Have run the attempt around 15-20 times now, several times back to back.
Hmm.. Seems like an error in the script somewhere, are you using a bash file? Do you have access to a windows PC? This is exactly why I dualboot
Sent from my Nexus 7 using Tapatalk
SwoRNLeaDejZ said:
Hmm.. Seems like an error in the script somewhere, are you using a bash file? Do you have access to a windows PC? This is exactly why I dualboot
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I'm using whatever Xubuntu set up, plus a few aliases that definitely wouldn't interfere...
I've actually just set up a Windows VM in Virtualbox, so my next step will be to try from there. Maybe that'll give me some different errors, if nothing else. hehe
I know that people have been successful using the KFU inside of a VM so you may be good to go
Sent from my Nexus 7 using Tapatalk
Hello. Sorry for my (german) English.
After hours and hours testing I must ask the forum.
I have rootet some phones yet, but with the Sony Xperia Z 6603 I don't know what to do anymore.
I followed this help:
techbeasts.com/install-cwmtwrp-recovery-root-xperia-z-107a0228-firmware/
Sorry, I'm not allowed to format a extern link.
(Some things seems to has changed since the help was written. The links to EasyRootTool goes to One Click Root Tool, and in others helps the needed SDK is now Android Studio whith maybe other Filestructures, so I read)
I have (under windows 10)
1. Downgrade to .283 Firmware and rooted
The problem is at point
f: Download latest installer for Xperia Z (Z-lockeddualrecovery2.8.xx-RELEASE.installer.zip)
I have downloaded a Package XZDualRecovery-2.8-RELEASE. Hope that that is the right one.
A help tells me, that I should start a install.bat from that folder. This file is in the folder /src/ of the recovery-package.
I start the install.bat from there. At this point I don't know which option I should choose, because in the help bevor there was no word about SuperSU or other.
Code:
1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on an unrooted (Lollipop 5.0) ROM using rootkitXperia
4. Install ADB drivers to windows
I press "1" for luck and get the answers at the bottom of this post.
Ergo: I have no recovery installed. "NDR Utils" says:
Code:
Unable to read XZDR.prop
[NUT]'s XZDualRecovery is required'
The problem seems, that I don't know where to put the files from the recovery.
I tested something with
- starting the Android Studio before starting install.bat
(because I think that the adb-driver where activated with the studio)
- copying the Recovery-Folders to the Folder
...\AppData\Local\Android\Sdk\platform-tools
- copying the files that the install.bat needs (dr.prop and others) from the Folder
...\platform-tools\includes\builder\ to the platform-tools-Folder
but always the install.bat says that it can't find needed Files.
So how can I solve the problem? Whats my mistake?
Which files do I have to copy to which folder?
Firewall and Virusscan are offline and I have Admin-Rights.
RootChecker on the phone says that I have rooted. SuperSU has access.
SDK-platform-tools is in the windows System-Path.
Thanks from webazubi
Code:
* server not running *
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
=============================================
Getting ro.build.product
=============================================
Device model is C6603
Firmware is 10.5.1.A.0.283
=============================================
Step2 : Sending the recovery files.
=============================================
* 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 C6603
Firmware is 10.5.1.A.0.283
=============================================
Step2 : Sending the recovery files.
=============================================
cannot stat 'dr.prop': No such file or directory
cannot stat 'chargemon.sh': No such file or directory
cannot stat 'mr.sh': No such file or directory
cannot stat 'dualrecovery.sh': No such file or directory
1894 KB/s (65965 bytes in 0.034s)
cannot stat 'rickiller.sh': No such file or directory
2479 KB/s (29204 bytes in 0.011s)
91 KB/s (699 bytes in 0.007s)
2171 KB/s (34473 bytes in 0.015s)
260 KB/s (1202 bytes in 0.004s)
2058 KB/s (96956 bytes in 0.045s)
2133 KB/s (657704 bytes in 0.301s)
cannot stat 'recovery.twrp.cpio.lzma': No such file or directory
cannot stat 'recovery.philz.cpio.lzma': No such file or directory
cannot stat 'installrecovery.sh': No such file or directory
=============================================
Step3 : Setup of dual recovery.
=============================================
Unable to open /data/local/tmp/recovery/install.sh: No such file or directory
Look at your device and grant supersu access!
Press any key to continue AFTER granting root access.
-rwxr-xr-x 1 shell shell 657704 Nov 9 2014 /data/local/tmp/recovery/busybox
Drücken Sie eine beliebige Taste . . .
tmp-mksh: /data/local/tmp/recovery/install.sh: not found
=============================================
Installation finished. Enjoy the recoveries!
=============================================