Related
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
hi,i get this message when i try to run adb remount(remount failed: Operation not permitted) or adb root(adbd cannot run as root in production builds).phone is rooted on.55 and i can see it when running adb devices.The reason i find it is because i cant install cwm as when i m running install get this
CWM Recovery for 2012 Xperia Installer
script created by kenjidct
The system cannot find the path specified.
* daemon not running. starting it now on port 5037 *
* daemon started sucessfully *
=============================================
Step1 : Waiting for Device.
=============================================
OK
=============================================
Step2 : Sending some files.
=============================================
cannot stat 'chargemon': No such file or directory
cannot stat 'charger': No such file or directory
cannot stat 'recovery.tar': No such file or directory
cannot stat 'sh': No such file or directory
cannot stat 'step3.sh': No such file or directory
=============================================
Step3 : Setting up files system partition.
=============================================
Unable to chmod /data/local/tmp/cwm/sh: No such file or directory
Unable to chmod /data/local/tmp/cwm/step3.sh: No such file or directory
sh: /data/local/tmp/cwm/step3.sh: not found
Finished!
Press any key to continue . . .
i m in this situation for about a month and i cant find a solution,and i think that i have properly connect phone to pc set up adb and root phone
Do you enable USB debugging mode?
And also unknown sources.
Sent from my Sony Xperia™ sola using XDA Premium App
Ben Ling said:
Do you enable USB debugging mode?
And also unknown sources.
Sent from my Sony Xperia™ sola using XDA Premium App
Click to expand...
Click to collapse
yes i did that
solved i think
http://forum.xda-developers.com/showpost.php?p=42023282&postcount=117 solved i use this and ihave cwm installed but i dont know if i can use it to update to jb since it says that is for ics only
Is your Locked Bootloader unlocked ?
no, i have locked bootloader
Hi evreyone !
I spent hours trying and reading posts everywhere I could without any success.
I'm trying to follow this rooting guide: http://forum.xda-developers.com/showthread.php?t=2634196 (Root and Dual Recovery for Locked Bootloader) and I'm stuck in a bootloop at step 10.
I'm using the last Z1C-lockeddualrecovery2.7.117-BETA.installer.zip and I noticed an error during recovery installation (after DEVICE WILL NOW REBOOT!):
Code:
##########################################################
#
# Installing XZDR version 2.7.117 BETA
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to allow installation.
Copy recovery files to system.
Copy mr wrapper script to system.
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Copy busybox to system.
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event3!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW REBOOT!
=============================================
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system running?
at com.android.commands.am.Am.run(Am.java:101)
at com.android.commands.am.Am.main(Am.java:82)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:235)
at dalvik.system.NativeStart.main(Native Method)
=============================================
REMEMBER THIS:
XZDualRecovery does NOT install any superuser app!!
You can use one of the recoveries to root your device.
=============================================
Waiting for your device to reconnect.
After entering CWM for the first time, reboot to system to complete this installer if you want it to clean up after itself.
=============================================
Installation finished. Enjoy the recoveries!
=============================================
(Note that I'm using Linux... I tried to run the bash script both as a user or as root)
If I continue the rooting process by flashing D5503_14.2.A.1.114_Generic UK.ftf (step 9), I'm stuck at step 10 as I can't boot any recovery. The phone is stuck in a bootloop, and after the green light pressing vol up (ou down) won't do anything...
I tried the whole process (from the begining: docomo) several time and end up everytime with the same result: an error at the end of the recovery installation and a bootloop at step 10 that prevent me from entering any recovery...
I'm out of ideas ! What can I do to manage the installation of the recovery ?
OldBeurt said:
What can I do to manage the installation of the recovery ?
Click to expand...
Click to collapse
Try a newer guide - http://forum.xda-developers.com/showthread.php?t=2688933
Thanks for your answer !
XperienceD said:
Try a newer guide - http://forum.xda-developers.com/showthread.php?t=2688933
Click to expand...
Click to collapse
Since I don't have access to any recovery, I don't understand how I can follow this guide (step 5: Go to recovery menu[...]).
What did you meant ?
OldBeurt said:
I don't understand how I can follow this guide (step 5: Go to recovery menu[...])
Click to expand...
Click to collapse
Read the requirements and it links to how to root, and if you can't or won't unlock your bootloader then you're going to have to jump through hoops.
XperienceD said:
Read the requirements and it links to how to root, and if you can't or won't unlock your bootloader then you're going to have to jump through hoops.
Click to expand...
Click to collapse
Of course I red the requirements. The root method described is the same (http://forum.xda-developers.com/showthread.php?t=2642081) than the one I followed (http://forum.xda-developers.com/showthread.php?t=2634196). And so the result is going to be the same: being stuck in a bootloop after flashing the recovery form the computer (flashing witch returns an error that I quoted above).
I need help to "recover" the recovery, I mean to be able to properly flash the dual recovery on my phone (whether I wish to unlock the bootloader or not is not the point for now, since I need to root with the locked bootloader in the first place).
It's obvious that there is an error while installing dualrecovery. However I don't know what could cause that error. I advise you to try install it on a fresh ubuntu / Windows client.
Edit: You are executing the install.sh script right? Because at first you select option 3, which is missing in your output. It looks like you are simply executing installrecovery.sh which is of course wrong.
Thanks for your input !
zxz0O0 said:
It's obvious that there is an error while installing dualrecovery. However I don't know what could cause that error. I advise you to try install it on a fresh ubuntu / Windows client.
Click to expand...
Click to collapse
I don't know where the error came from, but I tried several times (about 10) and it end up the same way ! I will try on another machine (Linux too).
zxz0O0 said:
Edit: You are executing the install.sh script right? Because at first you select option 3, which is missing in your output. It looks like you are simply executing installrecovery.sh which is of course wrong.
Click to expand...
Click to collapse
Yes I'm using install.sh, I just pasted the relevat part of the output, but here I paste all of it:
Code:
Will attempt to get root to install!
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Step1 : Waiting for Device.
=============================================
Succes
=============================================
Step2 : Sending the recovery files.
=============================================
mkdir failed for /data/local/tmp/recovery, File exists
0 KB/s (29 bytes in 0.056s)
362 KB/s (17768 bytes in 0.047s)
325 KB/s (15578 bytes in 0.046s)
11 KB/s (501 bytes in 0.043s)
272 KB/s (11791 bytes in 0.042s)
3186 KB/s (44383 bytes in 0.013s)
70 KB/s (3082 bytes in 0.042s)
9 KB/s (385 bytes in 0.041s)
3645 KB/s (657704 bytes in 0.176s)
3521 KB/s (2597754 bytes in 0.720s)
3936 KB/s (1842873 bytes in 0.457s)
5217 KB/s (2447499 bytes in 0.458s)
193 KB/s (8124 bytes in 0.041s)
=============================================
Step3 : Setup of dual recovery.
=============================================
=============================================
Attempting to get root access for installation using rootkitXperia now.
NOTE: this only works on certain ROM/Kernel versions!
If it fails, please check the development thread on XDA for more details.
=============================================
ro.build.product=C6903
ro.build.id=14.1.G.1.534
search kallsyms...
1 2 3 4
(kallsyms_addresses=c0899410)
(kallsyms_num_syms=00014df1)
kernel dump...
1 2 3 4 5 6 7 8 9
prepare_kernel_cred=c00b89f4
commit_creds=c00b8518
ptmx_fops=c0ea365c
Succeeded in getroot!
##########################################################
#
# Installing XZDR version 2.7.117 BETA
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to allow installation.
Copy recovery files to system.
Copy mr wrapper script to system.
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Copy busybox to system.
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event3!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW REBOOT!
=============================================
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system running?
at com.android.commands.am.Am.run(Am.java:101)
at com.android.commands.am.Am.main(Am.java:82)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:235)
at dalvik.system.NativeStart.main(Native Method)
=============================================
REMEMBER THIS:
XZDualRecovery does NOT install any superuser app!!
You can use one of the recoveries to root your device.
=============================================
Waiting for your device to reconnect.
After entering CWM for the first time, reboot to system to complete this installer if you want it to clean up after itself.
=============================================
Installation finished. Enjoy the recoveries!
=============================================
alohaa guys,first post and thread
sinds i cant post in the developers thread
ill post here
as the title says im stuck on the sony logo,after trying to root my z1c
flashtool still see my phone,but it says :device connected with USB debugging off
i tried a couple of times to get in the recovery menu,boot phone,and press either volume up or down S:
nothing ever happens it just shows the sony logo and dissapears,then it comes back again :S
i got the proper files on the mirco sd card,as written in the tutorial
http://forum.xda-developers.com/showthread.php?t=2642081
any help is appriciated,and i will look further also in the trheads if i can find a solution for this,but havent found anything yet,if there is any
I made the mistake to first connect the phone to the PC and then running flash tool. Try to start the flashtool first. When it asks You to connect the phone do so ( I think in fastboot mode).
Then the ftf files should be flashed properly and the phone boot up normally
Gesendet von meinem D5503 mit Tapatalk
konsi said:
I made the mistake to first connect the phone to the PC and then running flash tool. Try to start the flashtool first. When it asks You to connect the phone do so ( I think in fastboot mode).
Then the ftf files should be flashed properly and the phone boot up normally
Gesendet von meinem D5503 mit Tapatalk
Click to expand...
Click to collapse
yes flash tool was already running before,so it detects the phone,i tried flashing again and this time it worked,eg just the flashing
at .16 of the tutorial i posted a link of i flashed D5503_14.3.A.0.681_Generic_UK-nosystem.ftf ,but then afterward,still same logo from sony comes and goes,but it doesnt get in recovery mode S:
before i flash anything more,ill wait for anwers,i geuss overflashing doesnt exist but i very uncertian of what im doing now
btw thanks for the quick reply
edit this is what unroot gave me http ://i61.tinypic.com/jhufyg.png
Well, I'm a noob as well
I did the root process with instructions from another thread which was called noob proof it doesn't unlock the bootloader though. I don't have the link right now. But it is one on the top of the forum.
Btw the rooting process of this phone is IMHO very complicated.
Edit: sorry, I didn't see it was this thread you are talking about. I used the same ?
Gesendet von meinem D5503 mit Tapatalk
Please start again from step 1 of the guide. Post the output of dualrecovery installer once you run it.
Bootloop can be caused by multiple mistakes the user did.
konsi said:
Well, I'm a noob as well
I did the root process with instructions from another thread which was called noob proof it doesn't unlock the bootloader though. I don't have the link right now. But it is one on the top of the forum.
Btw the rooting process of this phone is IMHO very complicated.
Edit: sorry, I didn't see it was this thread you are talking about. I used the same ?
Gesendet von meinem D5503 mit Tapatalk
Click to expand...
Click to collapse
lol,i read a few pages further, this post it says start over again from step 1,if sony logo keeps coming up,and no green light flashes
http://forum.xda-developers.com/showpost.php?p=50227041&postcount=19
i will try again S:
edit: thanks @ zxz0O0 ill try D:
I would've done the same. Report if you succeed
Gesendet von meinem D5503 mit Tapatalk
guys thanks for the help,i managed to root my xperia z1c
and i think i know what went wrong,the first time i used Z1C-lockeddualrecovery2.7.123-BETA.installer
with option 3 [Installation on unrooted ROM]
at exact same time windows explorer crashed dont know why,but that resulted in a protocol failure??,and afterwards could not connect to device
error :device not found , it said a few times
this is why i could not get in the recoverymode
after starting at step 1 again
and i could start/boot with the flashed docomo firmware,i was very reliefed (btw whats up with that docomo sheep walking on the screen lol)
and useing Z1C-lockeddualrecovery2.7.123-BETA.installer, install.bat for the 2nd time i saw the difference
this time it gave me this
Code:
==============================================
= =
= 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 ]
[ 4. Exit ]
Please choose install action. [1,2,3,4]?3
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found
=============================================
Step2 : Sending the recovery files.
=============================================
0 KB/s (29 bytes in 0.457s)
19 KB/s (17768 bytes in 0.907s)
415 KB/s (15759 bytes in 0.037s)
163 KB/s (501 bytes in 0.003s)
720 KB/s (11798 bytes in 0.016s)
2405 KB/s (56662 bytes in 0.023s)
1003 KB/s (3082 bytes in 0.003s)
6 KB/s (385 bytes in 0.056s)
1316 KB/s (657704 bytes in 0.488s)
3564 KB/s (2602457 bytes in 0.713s)
3150 KB/s (2464762 bytes in 0.764s)
2776 KB/s (1845018 bytes in 0.649s)
234 KB/s (8658 bytes in 0.036s)
=============================================
Step3 : Setup of dual recovery.
=============================================
=============================================
Attempting to get root access for installation using rootkitXperia now.
NOTE: this only works on certain ROM/Kernel versions
If it fails, please check the development thread (Post #2) on XDA for more deta
ls.
REMEMBER THIS:
XZDualRecovery does NOT install any superuser app
You can use one of the recoveries to root your device.
=============================================
ro.build.product=C6903
ro.build.id=14.1.G.1.534
search kallsyms...
1 2 3 4
(kallsyms_addresses=c0899410)
(kallsyms_num_syms=00014df1)
kernel dump...
1 2 3 4 5 6 7 8 9
prepare_kernel_cred=c00b89f4
commit_creds=c00b8518
ptmx_fops=c0ea365c
Succeeded in getroot!
/data/local/tmp/recovery/install.sh: line 23: /system/xbin/busybox: not found
/data/local/tmp/recovery/install.sh: line 23: /system/bin/busybox: not found
##########################################################
#
# Installing XZDR version 2.7.123 BETA
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to a
low installation.
Copy recovery files to system.
Rename stock mr
Copy mr wrapper script to system.
Rename stock chargemon
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Creating /system/.XZDualRecovery to store a backup copy of busybox.
Copy busybox to system.
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event3!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW TRY A DATA SAFE REBOOT!
=============================================
=============================================
Your installation has already cleaned up after itself if you see the install.ba
/install.sh exit.
=============================================
=============================================
Installation finished. Enjoy the recoveries
=============================================
the rest was a piece of cake
thanks for all the very quick responses
this thread can be deleted by the mods if they wish to
or leave it for people with the same bad luck as me
Hey guys i cant get 4.4.4 rooted. I read it worked fine to root but i keep getting a 'apk not found' when i run easy root! Any help? I just got my windows 8 computer and got drivers installed fine and flashtool worked fine. Any help is appreciated!! Also battery dont seem as good as 757
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
zike47222 said:
Hey guys i cant get 4.4.4 rooted. I read it worked fine to root but i keep getting a 'apk not found' when i run easy root! Any help? I just got my windows 8 computer and got drivers installed fine and flashtool worked fine. Any help is appreciated!! Also battery dont seem as good as 757
Click to expand...
Click to collapse
go to https://towelroot.com/ using phone. click on lamda mark.it will down load apk ,install it .then run.instale su manager like supersu from play stroe.u r done
Lasantha said:
go to https://towelroot.com/ using phone. click on lamda mark.it will down load apk ,install it .then run.instale su manager like supersu from play stroe.u r done
Click to expand...
Click to collapse
I downloaded it.. tried tr tr-1 an tr-2 but no luck? it says rooted but it isnt. i have supersu and it says no binary installed. ??
Download towelroot and put in the files folder for easy root and then run install
try with this
mr mystery said:
Download towelroot and put in the files folder for easy root and then run install
Click to expand...
Click to collapse
Try with this file and easyroot v8.
The output looks like it says v10 but the content of folder /files is definitely not from v10. So I guess you mixed something.
The problem is that it can not cd to the folder /files, so are you sure you unpacked everything?
Are you wearing a towel on that pic? That's not a requirement for towelroot to work.
scnr
I have a different issue, hanged at cleaning up
Not sure if I should disconnect my phone or keep waiting... waited 10min and counting
==============================================
= =
= Easy Root Tool v10 =
= Supports various Xperia devices =
= created by zxz0O0 =
= =
= http://forum.xda-developers.com/ =
= showthread.php?p=53448680 =
= =
= Many thanks to: =
= - [NUT] =
= - geohot =
= - MohammadAG =
= - cubeundcube =
= - DooMLoRD =
= - nhnt11 =
= - xsacha =
= =
==============================================
=============================================
tr.apk not found. Trying to download from
https://towelroot.com/tr.apk
=============================================
######################################################################## 100.0%
=============================================
Extracting libexploit.so using 7z
=============================================
OK
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
Make sure you have only one Android device connected
BlueStacks emulator can also cause problems
=============================================
Device found
=============================================
Getting device variables
=============================================
Device model is D5503
Firmware is 14.4.A.0.108
=============================================
Sending files
=============================================
/dev/kmem exists. Using files of cubeundcube...
22 KB/s (953 bytes in 0.042s)
4828 KB/s (657704 bytes in 0.133s)
13 KB/s (729 bytes in 0.054s)
1854 KB/s (9496 bytes in 0.005s)
2670 KB/s (13672 bytes in 0.005s)
=============================================
Loading towelzxperia
=============================================
3318 KB/s (13592 bytes in 0.004s)
6422 KB/s (197320 bytes in 0.030s)
=============================================
Waiting for towelzxperia to exploit...
towelzxperia by zxz0O0 (EasyRootTool Version)
libexploit by geohot
creating libzxploit.so
libzxploit.so created
doing the magic
creating vm (loljavasucks)
libdvm opened (loljavasucks)
cleaning up
Click to expand...
Click to collapse
Iruwen said:
Are you wearing a towel on that pic? That's not a requirement for towelroot to work.
scnr
Click to expand...
Click to collapse
Haha epic :laugh:
mhaha said:
I have a different issue, hanged at cleaning up
Not sure if I should disconnect my phone or keep waiting... waited 10min and counting
Click to expand...
Click to collapse
Try closing it and then run install.bat again :good:
Thanks, that worked. Finally I can leave the house lol
zxz0O0 said:
The output looks like it says v10 but the content of folder /files is definitely not from v10. So I guess you mixed something.
The problem is that it can not cd to the folder /files, so are you sure you unpacked everything?
Click to expand...
Click to collapse
ok? i dont kno how i would have mixed it up but i have tryed alot of diff stuff. Used a diff computer and same problem it can never see the apk. will try again tonight.
Iruwen said:
Are you wearing a towel on that pic? That's not a requirement for towelroot to work.
scnr
Click to expand...
Click to collapse
Trying everything bro![emoji12][emoji12] but who looks that close at a pik?
zxz0O0 said:
The output looks like it says v10 but the content of folder /files is definitely not from v10. So I guess you mixed something.
The problem is that it can not cd to the folder /files, so are you sure you unpacked everything?
Click to expand...
Click to collapse
Do i need internet connection to root? I didn't think i did.
zxz0O0 said:
The output looks like it says v10 but the content of folder /files is definitely not from v10. So I guess you mixed something.
The problem is that it can not cd to the folder /files, so are you sure you unpacked everything?
Click to expand...
Click to collapse
Ok ive tryed v8-9-10 with all th TR apks.. what am i doing wrong? It says cant find tr-apk . I have used this before and it worked fine!
...
zike47222 said:
Ok ive tryed v8-9-10 with all th TR apks.. what am i doing wrong? It says cant find tr-apk . I have used this before and it worked fine!
Click to expand...
Click to collapse
i have the same problem as you
thanos kary said:
i have the same problem as you[/QUOTES]
Still dont know what the problem is/was but i got root by installing the dualrecovery and rooting with the supersu option it gives.. the 175 worked first then i flashed ftf again and had to use 168. but it workd. i think thats the build numbers anyhow..
Click to expand...
Click to collapse
zike47222 said:
thanos kary said:
i have the same problem as you[/QUOTES]
Still dont know what the problem is/was but i got root by installing the dualrecovery and rooting with the supersu option it gives.. the 175 worked first then i flashed ftf again and had to use 168. but it workd. i think thats the build numbers anyhow..
Click to expand...
Click to collapse
Of..I root. My phone.... I install. A kernel... I use. Fastboot. To flash. It and then. I install. Super Su. From. So card
Click to expand...
Click to collapse
I think some of us are not being successful because of some small barriers/details. The easyroot seems to work very nicely. I re-did the FTF and root process to see if I would have the same problems:
1) First I started with a fresh stock FTF flash: I chose UK Generic 108, though I'm sure any of the 108 FTF's will be fine. (D5503_14.4.A.0.108_Generic_UK_1279-4053.ftf).
2) Then of course made sure I had the Z1Compact ADB drivers installed. I believe if you install Sony PC Companion, it comes with these drivers (correct me if I'm wrong?). But you don't want PC Companion to interfere with the rooting process so if you have PC Companion installed, make sure it is closed / exited / gone from the system tray!
3) Then downloaded the Easy root v10 from this thread:
http://forum.xda-developers.com/showthread.php?t=2784900
This easyroot method is great - it roots, AND allows read/write access to the system area (if you need it).
4) Then extracted easy root v10 to a simple directory (like c:\temp\z1ceasyroot\)
5) At this point, make sure the phone isn't connected to the computer yet. Check to make sure you did the right settings on the phone.
Pausing here because some of you mentioned that easyroot started by saying it couldn't find the towelroot APK. I got this same error message - this was when I realized I had forgotten to do the USB Debugging & Unknown Sources settings!
Enable USB Debugging
To do this, go into Settings, Phone Info, and tap on the Build Number 7 times. Then go back into Settings, into Developer options, and turn on USB Debugging.
Enable Unknown Sources
Then in Settings, go to Security, and turn on "Unknown Sources"
6) Now you're pretty much ready. Open command prompt and navigate to the easyroot v10 folder.
7) Connect the phone to the PC - NOTE - on a fresh ROM install, the first time you connect the phone to the PC it will offer to install PC Companion. Skip that and tell it to go away.
8) Make sure the phone's screen is on, and not busy with any messages. It may be helpful to set a decent timeout (like 2 minutes) before the screen shuts off.
9) Now run the easyroot install.bat - the reason I mentioned above to have the screen on, is because if you are on a fresh rom install, this will be your first time connecting to the phone via ADB. A notification will pop up on the phone's screen to ask you if you want to allow the ADB connection. Say yes (and check the box so it doesn't bother you with that again).
The easyroot will run and do what it has to do.
NOTE: On my first run, it got stuck at "creating vm (loljavasucks)". I hit CTRL-C to break the process, closed the command prompt window, opened a new one, navigated back to the directory, and tried again.
NOTE: On my 2nd run, it got stuck just after the above, at "cleaning up". I did the same thing (stopped the process and closed the window.)
On the 3rd run, it ran completely.
LOG:
Code:
C:\temp\xperia-z1c-easyroot>install
==============================================
= =
= Easy Root Tool v10 =
= Supports various Xperia devices =
= created by zxz0O0 =
= =
= [url]http://forum.xda-developers.com/[/url] =
= showthread.php?p=53448680 =
= =
= Many thanks to: =
= - [NUT] =
= - geohot =
= - MohammadAG =
= - cubeundcube =
= - DooMLoRD =
= - nhnt11 =
= - xsacha =
= =
==============================================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
Make sure you have only one Android device connected
BlueStacks emulator can also cause problems
=============================================
Device found
=============================================
Getting device variables
=============================================
Device model is D5503
Firmware is 14.4.A.0.108
=============================================
Sending files
=============================================
/dev/kmem exists. Using files of cubeundcube...
931 KB/s (953 bytes in 0.000s)
6156 KB/s (657704 bytes in 0.104s)
355 KB/s (729 bytes in 0.002s)
2319 KB/s (9496 bytes in 0.003s)
2669 KB/s (13672 bytes in 0.005s)
=============================================
Loading towelzxperia
=============================================
3317 KB/s (13592 bytes in 0.004s)
6884 KB/s (197320 bytes in 0.027s)
=============================================
Waiting for towelzxperia to exploit...
towelzxperia by zxz0O0 (EasyRootTool Version)
libexploit by geohot
libzxploit.so created
doing the magic
creating vm (loljavasucks)
cleaning up
done
Checking if device is rooted...
Device rooted.
=============================================
Checking for Sony RIC
=============================================
Sony RIC Service found.
Installing RIC kill script "installmount.sh"...
Stock mount does not exist. Creating dir and link
Installing of mount.sh finished
Done. You can now unplug your device.
Enjoy root
=============================================
What to do next?
- Donate to the people involved
- Install SuperSU by Chainfire
- Install dualrecovery by [NUT]
- Backup TA partition
Press any key to continue . . .
C:\temp\xperia-z1c-easyroot>
10) Once that was done, I powered off the phone, back on, and went into the Play Store to get SUPERSU by Chainfire. Once that is done, you're finished. Like it suggests at the end of the rooting process, you may want to donate to the people that worked hard for this root method, install the NUT dual recovery, and backup your TA partition (Backing up your TA is important if you plan on unlocking your Bootloader!)
Using Xperia Z3 D6633 .
I hadn''t upgraded to Lolipop ( still am on 4.4 ) so I took a short cut to root- I could "root" using Kingo Super User Root.
But it wasn't root all the way. System partition cannot be mounted rw . Why do I want rw mount ?
I migrated from another phone where all my apps are in /ext4 partition of my sd .
L2SD on Z3 will not work -"Mount operation not permitted" .
I followed ALL above steps ( X 5 times ) .. and it hangs on the "javasucks" step
Code:
C:\Users\Administrator\Downloads\Compressed\EasyRootTool v12.4>install.bat
==============================================
= =
= Easy Root Tool v12 =
= Supports various Xperia devices =
= created by zxz0O0 =
= =
= http://forum.xda-developers.com/ =
= showthread.php?p=53448680 =
= =
= Many thanks to: =
= - [NUT] =
= - geohot =
= - MohammadAG =
= - cubeundcube =
= - nhnt11 =
= - xsacha =
= =
==============================================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
Make sure that you authorize the connection
if you get any message on the phone
=============================================
Device found
=============================================
Getting device variables
=============================================
Device model is D6633
Firmware is 23.0.1.F.0.96
=============================================
Sending files
=============================================
311 KB/s (1593 bytes in 0.005s)
2007 KB/s (657704 bytes in 0.320s)
256 KB/s (1575 bytes in 0.006s)
1159 KB/s (9496 bytes in 0.008s)
1335 KB/s (13672 bytes in 0.010s)
Copying kernel module...
1870 KB/s (34473 bytes in 0.018s)
160 KB/s (823 bytes in 0.005s)
948 KB/s (13592 bytes in 0.014s)
Kernel version is 3.4.0-perf-g7c8b3cb
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 0xFF791C4F
__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
=============================================
Loading towelzxperia
=============================================
1895 KB/s (13592 bytes in 0.007s)
2713 KB/s (197320 bytes in 0.071s)
=============================================
Waiting for towelzxperia to exploit...
towelzxperia by zxz0O0 (EasyRootTool Version)
libexploit by geohot
libzxploit.so created
doing the magic
creating vm (loljavasucks)
^CTerminate batch job (Y/N)? N
done
Checking if device is rooted...
Device rooted.
=============================================
Checking for Sony RIC
=============================================
Sony RIC Service found.
Installing RIC kill script installmount.sh...
Stock mount does not exist. Creating dir and link
Installing of mount.sh finished
Done. You can now unplug your device.
Enjoy root
=============================================
What to do next?
- Donate to the people involved
- Install SuperSU by Chainfire
- Install dualrecovery by [NUT]
- Backup TA partition
Press any key to continue . . .
C:\Users\Administrator\Downloads\Compressed\EasyRootTool v12.4>install.bat
==============================================
= =
= Easy Root Tool v12 =
= Supports various Xperia devices =
= created by zxz0O0 =
= =
= http://forum.xda-developers.com/ =
= showthread.php?p=53448680 =
= =
= Many thanks to: =
= - [NUT] =
= - geohot =
= - MohammadAG =
= - cubeundcube =
= - nhnt11 =
= - xsacha =
= =
==============================================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
Make sure that you authorize the connection
if you get any message on the phone
=============================================
Device found
=============================================
Getting device variables
=============================================
Device model is D6633
Firmware is 23.0.1.F.0.96
=============================================
Sending files
=============================================
388 KB/s (1593 bytes in 0.004s)
3380 KB/s (657704 bytes in 0.190s)
512 KB/s (1575 bytes in 0.003s)
772 KB/s (9496 bytes in 0.012s)
1668 KB/s (13672 bytes in 0.008s)
Copying kernel module...
1771 KB/s (34473 bytes in 0.019s)
200 KB/s (823 bytes in 0.004s)
1896 KB/s (13592 bytes in 0.007s)
Kernel version is 3.4.0-perf-g7c8b3cb
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 0xFF791C4F
__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
=============================================
Loading towelzxperia
=============================================
1020 KB/s (13592 bytes in 0.013s)
2875 KB/s (197320 bytes in 0.067s)
=============================================
Waiting for towelzxperia to exploit...
towelzxperia by zxz0O0 (EasyRootTool Version)
libexploit by geohot
libzxploit.so created
doing the magic
creating vm (loljavasucks)
What do I do now ? Pl help
( some notes : not sure if this is relevant
One thing - I tried Un-Installing KingoSuper User .. hoping it will put things at zero - just in case it had any bearing on this root installation. It kinda never really uninstalled because it installed itself as system app. Using L2SD I uninstalled it - but it never uninstalled quite. Google play showed it as installed. A reboot- and it was back again to fully installed form . So before running above steps - I froze it and I am still stuck )
sieger007 said:
Using Xperia Z3 D6633 .
I hadn''t upgraded to Lolipop ( still am on 4.4 ) so I took a short cut to root- I could "root" using Kingo Super User Root.
But it wasn't root all the way. System partition cannot be mounted rw . Why do I want rw mount ?
I migrated from another phone where all my apps are in /ext4 partition of my sd .
L2SD on Z3 will not work -"Mount operation not permitted" .
I followed ALL above steps ( X 5 times ) .. and it hangs on the "javasucks" step
Code:
==============================================
= =
= 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]?1
* 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 D6633
Firmware is 23.0.1.F.0.96
=============================================
Step2 : Sending the recovery files.
=============================================
mkdir failed for /data/local/tmp/recovery, File exists
9 KB/s (30 bytes in 0.003s)
1709 KB/s (15757 bytes in 0.009s)
81 KB/s (501 bytes in 0.006s)
770 KB/s (11842 bytes in 0.015s)
3390 KB/s (65965 bytes in 0.019s)
601 KB/s (3082 bytes in 0.005s)
187 KB/s (385 bytes in 0.002s)
3777 KB/s (657704 bytes in 0.170s)
2773 KB/s (3016755 bytes in 1.062s)
2494 KB/s (2319570 bytes in 0.908s)
2259 KB/s (1876508 bytes in 0.811s)
1253 KB/s (8987 bytes in 0.007s)
=============================================
Step3 : Setup of dual recovery.
=============================================
Look at your device and grant supersu access!
Press any key to continue AFTER granting root access.
-rwxr-xr-x 1 shell shell 657704 Feb 15 2015 /data/local/tmp/recovery/busybox
Press any key to continue . . .
2211 KB/s (13592 bytes in 0.006s)
3366 KB/s (34473 bytes in 0.010s)
332 KB/s (1705 bytes in 0.005s)
No system mount security
modulecrcpatch (by zxz0O0)
module_layout: patched to 0xFF791C4F
__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
insmod: init_module '/data/local/tmp/wp_mod.ko' failed (File exists)
##########################################################
#
# Installing XZDR version 2.8.2 RELEASE
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to allow installation.
insmod: init_module '/data/local/tmp/wp_mod.ko' failed (File exists)
insmod: init_module '/system/lib/modules/wp_mod.ko' failed (File exists)
Copy recovery files to system.
Rename stock mr
Copy mr wrapper script to system.
Rename stock chargemon
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Copy disableric to system.
Creating /system/.XZDualRecovery to store a backup copy of busybox.
Copy busybox to system.
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event3!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW TRY A DATA SAFE REBOOT!
=============================================
=============================================
Your installation has already cleaned up after
itself if you see the install.bat/install.sh exit.
=============================================
=============================================
Installation finished. Enjoy the recoveries!
=============================================
Press any key to continue . . .
It got the recovery in !
and then L2SD could get /ext4 to mount and I could see the old linked folders but I dont know if this is too good to be true. I sill am looking around to see . My previous phone - L2SD had to remount and reboot for the Ext4 to show up.
Click to expand...
Click to collapse