Z1s Root+Reovery+Deodex Android 4.3 Updated 6/18/14
This was put together by @ayuready1989 and @Tactic13
This Not A Rom "Do NOT WIPE ANYTHING JUST FLASH AS IS"
This is a Patch to keep root on reboot as well as deodex your current rom.[
NO LONGER USED
Please use Root 4.4.4 on z1s
Once you have recovery you can flash this instead of using the script it does not require you to make the script.
First of all we would like to thank @jcase for getting the initial root, @[NUT] for the recovery @xsacha for the ta backup and @RyokoN for some of the tools, if we forgot someone just send us a message.
Okay now for the fun part.
Make sure that you have usb debugging enabled.
Root with jcase method.
Install SuperSU from market reboot.
Run adb shell su -c "/system/xbin/kill_ric.sh"
Then adb shell su -c "mount -o remount,rw /system"
Install Recovery But use the one for the z1 Locked boatloader.
Finaly Flash Deodex + Root Devhost Minor
Optional
Backup Ta image. Ta Backup
We will keep working on this as well as start working on a rom just wanted to get this out to you guys.
You assume all the stand disclaimers when you flash this that not is to say that we wont help you.
Mine Just in case i need it.
Tactic13 said:
Mine Just in case i need it.
Click to expand...
Click to collapse
+1
This is what i get when trying to install recovery. Supersu working fine. I just used it for TB. Should I try SuperUser instead?
==============================================
= =
= 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]?1
* 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.
=============================================
9 KB/s (29 bytes in 0.003s)
3847 KB/s (15759 bytes in 0.004s)
244 KB/s (501 bytes in 0.002s)
2880 KB/s (11798 bytes in 0.004s)
5030 KB/s (56662 bytes in 0.011s)
1504 KB/s (3082 bytes in 0.002s)
187 KB/s (385 bytes in 0.002s)
5489 KB/s (657704 bytes in 0.117s)
5318 KB/s (2875482 bytes in 0.528s)
5240 KB/s (2581087 bytes in 0.481s)
5347 KB/s (1845510 bytes in 0.337s)
384 KB/s (8658 bytes in 0.022s)
=============================================
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 Apr 30 05:38 /data/local/tmp/recovery/busybox
Press any key to continue . . .
##########################################################
#
# Installing XZDR version 2.7.123 BETA
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to allow installation.
mount: permission denied (are you root?)
blockdev: applet not found
mount: permission denied (are you root?)
Copy recovery files to system.
cp: can't create '/system/bin/recovery.twrp.cpio.lzma': Read-only file system
cp: can't create '/system/bin/recovery.cwm.cpio.lzma': Read-only file system
cp: can't create '/system/bin/recovery.philz.cpio.lzma': Read-only file system
chmod: /system/bin/recovery.twrp.cpio.lzma: No such file or directory
chmod: /system/bin/recovery.cwm.cpio.lzma: No such file or directory
chmod: /system/bin/recovery.philz.cpio.lzma: No such file or directory
Rename stock mr
mv: can't rename '/system/bin/mr': Read-only file system
Copy mr wrapper script to system.
cp: can't create '/system/bin/mr': File exists
chmod: /system/bin/mr: Read-only file system
Rename stock chargemon
mv: can't rename '/system/bin/chargemon': Read-only file system
Copy chargemon script to system.
cp: can't create '/system/bin/chargemon': File exists
chmod: /system/bin/chargemon: Read-only file system
Copy dualrecovery.sh to system.
cp: can't create '/system/bin/dualrecovery.sh': Read-only file system
chmod: /system/bin/dualrecovery.sh: No such file or directory
Copy rickiller.sh to system.
cp: can't create '/system/bin/rickiller.sh': Read-only file system
chmod: /system/bin/rickiller.sh: No such file or directory
Installing NDRUtils to system.
cp: can't create '/system/app/NDRUtils.apk': Read-only file system
chmod: /system/app/NDRUtils.apk: No such file or directory
Copy disableric to system.
cp: can't create '/system/xbin/disableric': Read-only file system
chmod: /system/xbin/disableric: No such file or directory
Creating /system/.XZDualRecovery to store a backup copy of busybox.
mkdir failed for /system/.XZDualRecovery, Read-only file system
Copy busybox to system.
cp: can't create '/system/xbin/busybox': File exists
cp: can't create '/system/.XZDualRecovery/': Is a directory
chmod: /system/xbin/busybox: Read-only file 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 . . .
Re run the root as well as the second set of commands and on your phone it should ask you to grant root access to adb. But i installed SuperSu and used option 1.
same here, supersu and option 1,but make sure /sbin/xbin/kill_ric.sh is ran before u install recovery a couple times(2-3) just to make sure.
this is the specific one i used, for winblows V4
http://forum.xda-developers.com/showthread.php?t=2426739
So last night jcase remotely tested the exploit and rooted my Z1s. I installed the recovery this morning as instructed here and then flashed the deodex and root zip. Now my phone cannot achieve root via the adb commands or by itself. Furthermore the su binary that supersu had installed is gone and supersu cannot install it again. Any ideas what happened?
EDIT: Hmm, i installed the updated root method from the OP and that appears to have fixed it. Now to see if root sticks.
themacman1000 said:
So last night jcase remotely tested the exploit and rooted my Z1s. I installed the recovery this morning as instructed here and then flashed the deodex and root zip. Now my phone cannot achieve root via the adb commands or by itself. Furthermore the su binary that supersu had installed is gone and supersu cannot install it again. Any ideas what happened?
EDIT: Hmm, i installed the updated root method from the OP and that appears to have fixed it. Now to see if root sticks.
Click to expand...
Click to collapse
cool. if asked to fix root after cwm flash it seems safe to always chose to fix it
ayuready1989 said:
strange, the zip doesnt touch /system/xbin/su .. try the su fix that cwm asks for when trying to reboot after flashing a zip . ive selected yes and no, still the same result. still had root.. but flash via cwm and apply the fix root fix it asks, dont disable flash recovery though
Click to expand...
Click to collapse
Oh. When I first installed the deodex via philztouch it asked if i wanted to disable flashing of stock recovery. I said yes... That must have been my problem. However, everything works now, even rebooting holds root and system r/w. Also, can you link me to how you installed xposed? Edit: Nevermind, found out how myself
themacman1000 said:
Oh. When I first installed the deodex via philztouch it asked if i wanted to disable flashing of stock recovery. I said yes... That must have been my problem. However, everything works now, even rebooting holds root and system r/w. Also, can you link me to how you installed xposed?
Click to expand...
Click to collapse
alrighty, nice to know it works, thanks for actually giving feedback @themacman1000 now time for the modules and tweaks
themacman1000 said:
Oh. When I first installed the deodex via philztouch it asked if i wanted to disable flashing of stock recovery. I said yes... That must have been my problem. However, everything works now, even rebooting holds root and system r/w. Also, can you link me to how you installed xposed? Edit: Nevermind, found out how myself
Click to expand...
Click to collapse
I installed this apk.
http://dl-count.xposed.info/modules/de.robv.android.xposed.installer_v32_de4f0d.apk
Sent from my iPad using Tapatalk
I'm curious if Z1 roms would work for the Z1s... Considering they're basically the same phone... I did a full backup on mine, now considering trying that out...
I have don't its a pain in the but to get back you will lose everything.
We don't have a 4.4.2 kernel if we did we might be able to.
It's good to see T-Mobile roms,when you're overseas you can use WiFi Calling to call back to the US free.:thumbup::thumbup:
Sent from my HTC One_M8 using Tapatalk 2
Well you have the start right here it deodex the rom and root sticks
Tactic13 said:
I have don't its a pain in the but to get back you will lose everything.
We don't have a 4.4.2 kernel if we did we might be able to.
Click to expand...
Click to collapse
I was actually thinking 4.3 roms... I figured 4.4 wouldn't work, but 4.3 maybe?
adb shell chmod 755 /data/local/tmp/pwn
/system/bin/sh: chmod755: not found
Please help
jahjah440 said:
adb shell chmod 755 /data/local/tmp/pwn
/system/bin/sh: chmod755: not found
Please help
Click to expand...
Click to collapse
There's supposed to be a space between chmod and 755.
Elysian893 said:
There's supposed to be a space between chmod and 755.
Click to expand...
Click to collapse
Thank you I actually got it working before I had forgotten to give elevated permission to write to /data
I have achieved root!
what are the steps to installing the rom for this phone? do we have to delete anything in recovery?
---------- Post added at 06:03 PM ---------- Previous post was at 05:51 PM ----------
how do i backup the TA, complete sony noob here
---------- Post added at 06:05 PM ---------- Previous post was at 06:03 PM ----------
LaosPerson said:
what are the steps to installing the rom for this phone? do we have to delete anything in recovery?
---------- Post added at 06:03 PM ---------- Previous post was at 05:51 PM ----------
how do i backup the TA, complete sony noob here
Click to expand...
Click to collapse
nevermind, i just had to read the z2 link thing
Related
Just wanted to report that DooMLoRD's easy rooting toolkit works with DEFY+ with Android 2.3.6. Droid 3 root and SuperoneClick failed to root it
Link and steps in this post : http://forum.xda-developers.com/showthread.php?t=1321582
This doesn't work for me. I get lots of errors which suggest that the exploit doesn't work:
Code:
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
* daemon started successfully *
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush"
480 KB/s (23052 bytes in 0.046s)
--- 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
1562 KB/s (1075144 bytes in 0.671s)
--- 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 '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 . . .
As you say, the Droid 3 and Superoneclick methods don't work, and neither does z4root. I did have a look at the root procedure mentioned in post #1 of this thread but it's beyond my capabilities.
I just got hold of my nearly-new Defy+ this morning and I was looking forward to bringing it up to the same spec as my Defy. Without root, though, there's a lot I can't do (I've actually forgotten a lot of the things I need root for, but at a minimum SetVsel, 2ndinit and I think Clockworkmod recovery all need it ).
The phone says it's system version 45.0.1880.MB526.Retail.en.GB, build number is 4.5.1-134_DFP-188.
Anyone got any suggestions?
ejstubbs said:
This doesn't work for me. I get lots of errors which suggest that the exploit doesn't work:
Code:
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
* daemon started successfully *
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush"
480 KB/s (23052 bytes in 0.046s)
--- 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
1562 KB/s (1075144 bytes in 0.671s)
--- 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 '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 . . .
As you say, the Droid 3 and Superoneclick methods don't work, and neither does z4root. I did have a look at the root procedure mentioned in post #1 of this thread but it's beyond my capabilities.
I just got hold of my nearly-new Defy+ this morning and I was looking forward to bringing it up to the same spec as my Defy. Without root, though, there's a lot I can't do (I've actually forgotten a lot of the things I need root for, but at a minimum SetVsel, 2ndinit and I think Clockworkmod recovery all need it ).
The phone says it's system version 45.0.1880.MB526.Retail.en.GB, build number is 4.5.1-134_DFP-188.
Anyone got any suggestions?
Click to expand...
Click to collapse
That means its rooted, i got the exact same text when i rooted mine a moment ago
No, it's definitely not rooted: Titanium Backup refuses to run, for example.
Sorry. I didn't read the errors lol. Maybe backup ur Apps and then factory reset.
Sent from my MB526 using XDA App
In fact,no one can root the new Chinese rom
Jades007 said:
Maybe backup ur Apps and then factory reset.
Click to expand...
Click to collapse
Tried factory reset several times, no joy. It's a new phone and I haven't put anything on it yet, still trying to root it. The version of the firmware on this phone seems to be immune to the zergrush exploit.
I've also tried flashing a few of the other 2.3.6 sbfs with no joy - in fact all I have now is a black screen. It's flashable using rsdlite, so not completely bricked, but the end result is always the same - no response to the power button (so no possibility now of doing a factor reset, either).
I'm planning to send it to the Motorola service agent and see what it somes back with.
I've got exactly the same log and problem on my Xperia Arc S. Really impossible to root it?
Code:
---------------------------------------------------------------
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
Aby kontynuować, naciśnij dowolny klawisz . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
1876 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
2214 KB/s (1075144 bytes in 0.474s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
71 KB/s (439 bytes in 0.006s)
df: /mnt/secure/asec: Permission denied
--- Free space on /system : 186608 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!!!
Aby kontynuować, naciśnij dowolny klawisz . . .
Phone Software Version:
1253-8238_4.0.2.A.0.62
Bootloader unlock allowed: Yes
actually i rooted my defy (green lens) with 2.3.6 build like many deceived ones ....
just search for superone click v2.3.2.0.and download it..then dismount ur SD from the device and Enable debugging mode..connect ur device to pc and choose connection to do no thing then open super one click program and press on root bottom..it last for 2 min maximum...
Defy+ 2.3.6 Rooted!
On the 4th attempt rooting my Defy+ 2.3.6 worked! Initially I tried using DoomLoRD's rooting toolkit which said it was successful but didn't install the Superuser app, nor would su work. So then I tried SuperOneClick (v 2.3.2.0). Initially got messages saying the Adb server was out of date and the root failed. Deleted the usb driver package via the sdk and then reinstalled. Tried again - no good. Copied adb.exe, adbwinapi.dll and adbwinusbapi.dll from the sdk directory into Superoneclick adb directory. Tried again - failed. Then removed Droidexplorer (which I'd previously installed). Then reran SuperOneClick and it worked! Gave the same messages as DoomLoRD's kit from the 1st attempt but the Superuser app is there now and works. So thanks (& donation) to Shortfuse and DoomLoRD.
timjaknz said:
On the 4th attempt rooting my Defy+ 2.3.6 worked!
Click to expand...
Click to collapse
That sounds vaguely promising. Can you post the system version, kernel version and build number of your Defy+? I'd like to have some idea of whether it might work for mine, when it comes back from service.
ejstubbs said:
That sounds vaguely promising. Can you post the system version, kernel version and build number of your Defy+? I'd like to have some idea of whether it might work for mine, when it comes back from service.
Click to expand...
Click to collapse
Sure, it's a TelstraClear one (sourced from Oz but using in New Zealand). System version: 45.0.1321.MB526.SLTelstra.en.AU, Kernel version: [email protected] #1, Build: 4.5.1-134_DFP-1321.
I just worked for me too!
Thanks a lot!
{n00bOrgasm}
Mouaahhaa, finally rooted the àç§è(' phone...
In fact you did the job, I just kept sat on ma a...
So I guess you might like to have some details, the phone is a Moto Defy+, none of the well known clicknwatch tools worked for me but yours, I tried doing things myself but had no time enough so tried yours, to see...
Running the script from Ubuntu 11.10
The phone is an MB526
Android 2.3.4
System v. 45.074.MB526.Retail.en.FR
Kernel v. 2.6.32.9-gbad50c3
Build # 4.5.1-134_DFP74
Root verified, updated to last su version, the phone is perfectly fast and operational.
The script didn't returned any error, things were done in a couple seconds, Maps had to be removed, the only interesting thing (or maybe not), it said "All done, you Xperia has been rooted (...)".
Verified, it's definitely a Defy+.
Thank you very much...
Questions about this firmware has been discussed long time :
http://forum.xda-developers.com/showthread.php?t=1472086&page=9
But unfortunately so far no good results
Rooted!
With last version of DooMLord V4 my defy+ mb526 2.3.6 is now rooted thank you man!
I take it Motorola still hasnt released bootloader unlocks for thier devices?
So finally which method works for defy+ 2.3.6?????? plz reply frnds
CM7 2.3.7 QME
Can anyone confirm successfully rooting with DooMLord V4?
flflfl said:
Can anyone confirm successfully rooting with DooMLord V4?
Click to expand...
Click to collapse
It's zergRush. not worked. I'm using 4.5.1-134_DFP-231.
Hi everyone! I got the Nitro yesterday and I have tried EVERY possible method under the sun to get root onto my 2.3.5 V10J stock firmware. I am generally good at stuff, but the unbricking tutorial really confuses me. Is there any other way to just get CWM onto the phone and then install a pre-rooted ROM? Or an easier way to root? I tried superoneclick a 100 times, and it just behaves read only. does not allow the software to access root. This is the error I get with all rooting scripts!
---------------------------------------------------------------
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
failed to copy 'files\zergRush' to '/data/local/tmp/./zergRush': Permission deni
ed
--- correcting permissions
Unable to chmod /data/local/tmp/zergRush: No such file or directory
--- executing zergRush
./data/local/tmp/zergRush: not found
--- 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
failed to copy 'files\busybox' to '/data/local/tmp/./busybox': Permission denied
--- correcting permissions
Unable to chmod /data/local/tmp/busybox: No such file or directory
--- remounting /system
/data/local/tmp/busybox: not found
--- checking free space on /system
failed to copy 'files\makespace' to '/data/local/tmp/./makespace': Permission de
nied
Unable to chmod /data/local/tmp/makespace: No such file or directory
./data/local/tmp/makespace: not found
--- copying busybox to /system/xbin/
/data/local/tmp/busybox: cannot open for read: No such file or directory
--- correcting ownership
Unable to chmod /system/xbin/busybox: Read-only file system
--- correcting permissions
Unable to chmod /system/xbin/busybox: Read-only file system
--- installing busybox
--install: applet not found
rm failed for /data/local/tmp/busybox, No such file or directory
--- 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
rm failed for *, No such file or directory
--- rebooting
Apparently there is atm no way to get cwm or cwm recovery on your phone w/out going through oh no!'s rom which as a prerequisite you must follow the unbricking method.
If you want go to my profile and check out my recent posts in the nitro general subforum and youll see my little journey....which others were annoyed with ...lmao.
I am currently rooted, running stock ics and love it. I have no issues phone runs near perfect.
I did not "unbrick" my phone and just flashed an older rom (v18) and rooted.
Sparky's root method is the only method that will root this phone via ics.
I made a thread explaining in detail some steps that were not mentioned.
Dont bother with doomlord, oneclick.
Since the tapatalk search function sucks balls use the xda search function from the actual browser.
Hope that helps. Maybe someone else will chime in.
Dont fear the unbrick.
Take your time
Read slow and also read through other peoples posts and what they did wrong, how they remedied it blah blah...
Dont take any short cuts unless for sure, you know exactly what you are doing.
Make sure you have everything ready and have read through prior to doing it.
Nothing to fear flashing is pretty straight forward.
Just take your time.
:beer:
Sent from my LG-P930 using Tapatalk 2
I went from Stock ATT 2.5.6 V10J to ATT STOCK V10F .Using [GUIDE] Unbrick, Root, And Install CWM by mattman86 . Its long but doable its not even that long really .O tip uninstall all the drivers you might have installed and use the one that come with the unbricking pack ,its the key to the whole thing. Im in CM10 Nightly now .Good luck and dont get frustrated its rootable its just not a one click root.
Just keep trying to run the root. I used super one click and it took me at least 20-30 attempts to successfully root. If it asks you if your version is 2 or higher or fails to push any files to the phone, the root will not take. Just reboot the phone and keep trying.
Try using viperMOD PrimeTime v4.6, that's a lot easier and faster, despite what everyone else says, you can root 10j.
Good Luck
Plz help me i am a new user of arc and i have tried all the method for rooting but it was failed.i tried both the root toolkit ,superoneclick and Root_Exploit_OneClick but all falied.I have updated my arc and running ics 4.0.4 build number 4.1.B.0.31 plz help me i have to root it to uninstall useless aps and to install other roms.Plz plz help me Below is the error coming during the process of rooting my arc using Root tookit.:crying:
---------------------------------------------------------------
Xperia 2011 ICS Easy Rooting toolkit (v1.0)
created by DooMLoRD
"andorid emulator" trick
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using "andorid emulator" trick
(2) install Busybox (1.18.4)
(3) install SU files (ICS specific)
(4) do 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\Developer Options\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Security)
(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
--- symlinking tmp directory
failed on '/data/local/tmp' - Permission denied
link failed File exists
--- Rebooting
--- WAITING FOR DEVICE TO RECONNECT
--- PLEASE WAIT, THIS MAY TAKE A WHILE
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
--- enabling emulator hack
/system/bin/sh: cannot create /data/local.prop: Permission denied
--- Rebooting
--- WAITING FOR DEVICE TO RECONNECT
--- PLEASE WAIT, THIS MAY TAKE A WHILE
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
3359 KB/s (1075144 bytes in 0.312s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
27 KB/s (439 bytes in 0.015s)
--- Free space on /system : 67548
42852 bytes
test: 42852: unknown operand
--- NOT enough free space on /system!!!
--- making free space by removing Google Maps
--- 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/bin/sh: /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
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
--- rebooting
ALL DONE!!!
Press any key to continue . . .
4.0.4 version cannot be rooted directly with a program, no such hack.
You have two options.
1) Unlock bootloader (and lose DRM if done official way) and install/hotboot custom kernel to get root.
2) Install any previous ROM, which can be rooted (GB 4.0.2.A.0.42 or ICS4.0.3 4.1.A.0.562 for example), root it and then find the proper guide to root Xperia 4.0.4 and follow it.
alrdy unlocked bootloader
Someguyfromhell said:
4.0.4 version cannot be rooted directly with a program, no such hack.
You have two options.
1) Unlock bootloader (and lose DRM if done official way) and install/hotboot custom kernel to get root.
2) Install any previous ROM, which can be rooted (GB 4.0.2.A.0.42 or ICS4.0.3 4.1.A.0.562 for example), root it and then find the proper guide to root Xperia 4.0.4 and follow it.
Click to expand...
Click to collapse
i have already unlocked my bootloader but what is DRM and hotboot custom kernel
XperienceD said:
If you've unlocked your boot loader this should be easy. - http://forum.xda-developers.com/showthread.php?p=18445331#post18445331
Flash THIS with the flashtool, reboot, download the kernel and wifi modules from HERE, flash the kernel with fastboot, reboot to home screen. Reboot into CWM and flash the modules, reboot to home screen. Finally, reboot back into CWM and flash this CWMRoot.zip, done.
Click to expand...
Click to collapse
..
amanatkhan said:
i have already unlocked my bootloader but what is DRM and hotboot custom kernel
Click to expand...
Click to collapse
Actually the best option is to flash 4.1.A.0.562 using flashtool, root it and upsate to .431 with OTA.
Since u have already unlocked boot loader u wont be getting ota updates from sony. So there is no use of flashing 4.1.A.0.562 coz neways u cant update to .431 over OTA.
So its better to flash some custom roms like Ultimate hd 2 (ICS) or X gamer 1.8 (GB)
These 2 roms are the fastest ICS and GB roms available.
DRM is "Digital Rights Management"
its a way to lock down digital media to a specific user and in some cases restrict the ways in which that media can be used and/or copied
wifi problem
Calikrazd said:
DRM is "Digital Rights Management"
its a way to lock down digital media to a specific user and in some cases restrict the ways in which that media can be used and/or copied
Click to expand...
Click to collapse
i have installed Xperia Ultimate HD but wifi is not working.How to solve this
amanatkhan said:
i have installed Xperia Ultimate HD but wifi is not working.How to solve this
Click to expand...
Click to collapse
How To Install ROM: ===============
1. For Unlocked Bootloaders: Flash one of the Recomnend Kernels; "Adv. Stock Kernel" or "KTG Anzu"
So use one or the other kernel and you'll fix your wifi.good luck
Sent from Xperia Arc
I am trying to install CWM on my bootloader locked Xperia S.
It's all went smoothly; downgraded to gingerbread, run the rooting process, currently on a confirmed rooted ICS. Ran RecoverX and for all intentions it installs correctly with no errors. I restart my phone and tap the Sony logo numerous times... and I've tried a countless amount of times now but it just continues on loading stock ICS. It's really starting to get on my nerves now. Does anyone have any idea why it's happening? or is there any adb commands to check if CWM is installed?
RecoverX says accept any SuperUser prompts on the screen, but none appear.
RecoverX log:
Starting adb...
Wait for the device...
Check if the device is correctly rooted...
Check if busybox is installed...
Push files...
Unzip files...
Chmod files to 755...
Run installation script...
Clear temp folder...
Installation complete
Click to expand...
Click to collapse
I've also tried the older adb method via the install.bat but that says this:
Step1 : Waiting for Device.
=============================================
OK
=============================================
Step2 : Sending some files.
=============================================
mkdir failed for /data/local/tmp/cwm, Not a directory
failed to copy 'chargemon' to '/data/local/tmp/cwm': Not a directory
failed to copy 'charger' to '/data/local/tmp/cwm': Not a directory
failed to copy 'recovery.tar' to '/data/local/tmp/cwm': Not a directory
failed to copy 'sh' to '/data/local/tmp/cwm': Not a directory
failed to copy 'step3.sh' to '/data/local/tmp/cwm': Not a directory
=============================================
Step3 : Setting up files system partition.
=============================================
Unable to chmod /data/local/tmp/cwm/sh: Not a directory
Unable to chmod /data/local/tmp/cwm/step3.sh: Not a directory
sh: /data/local/tmp/cwm/step3.sh: not found
rm failed for /data/local/tmp/cwm, Not a directory
Finished!
Click to expand...
Click to collapse
Even though I clearly have access to my phone via adb. Because it's been rooted... Grr!
Nobody have any idea? Spent around 12 hours trying to sort it out yesterday so I'm completely out of things to try
For search purposes I ended up fixing it by updating the flashtool drivers for the phone (ticked every Xperia S checkbox). Well, it was either that or perhaps updating BusyBox, which is highly unlikely as I tried pretty much every version of it yesterday.
I am not responsible for whatever may happen to you or your device when using this, Run this at your own risk!!
Requires unlocked bootloader!
Based on SuperSU - v4.46 (the binary updates from within the app later on)
I put together root installer script that comes with SU-binary/App with a insecure boot.img, everything is done over adb shell since we don't have a recovery right now but i will be working on it and already booted CWM
For current firmware:
LMY47D - root-boot
For past firmware:
LRX21V - root-boot
For past firmware:
LRX21M - root-boot
crappy video but simple demonstration :good:How to install:
Download the zip depending on your Nexus Player's firmware than extract & run root-boot.bat (Other operating system support coming soon for the installer script) Made on windows 7
Follow and read the on screen instruction carefully
Click to expand...
Click to collapse
SU app and binarys gets installed to /system/* directory's, The insecure boot.img gets installed to be able to access root adb shell and install those binarys
The root-boot boot.img is temporarily booted once during this process on the first boot of installation, it does not flash the boot.img
The previous boot.img before the installation is restored after SU is installed
Click to expand...
Click to collapse
Thanks @Chainfire for Superuser
My Donation Box
Troubleshooting:
Check to make sure your device gets picked up in adb before running the script - - - ADB Drivers
This tool uses an unlocked bootloader and i have not unlocked mine yet, does unlocking the bootloader wipe the device? - - - Yes unlocking the bootloader will wipe the device
After fastboot flashed the boot.img than rebooted to the home screen i continued the the script like the installation steps said but it returned "device not found" - - - As long as it shows transferring files a few seconds after than its fine, adb restarts at that moment which will than return "device not found" than it reconnects and transfers. if fastboot flashed than rebooted fine than adb shouldn't have an issue
Help! Something went wrong and im bootlooping but i dont want to loose all my saved data - - - Everything is fine, Download the factory zip from here for your android version than extract the zip and retrieve the system.img and copy it into a folder that contains adb/fastboot and boot your device into fastboot mode and do "fastboot flash system system.img" doing it this way wont wipe your "/data" partition leaving everything intact but will restore the system back to its defaults
(If you were to run the factory zip as an update than it would format everything)
I installed SU with this method but cant use adb commands on my device - - - Go into "Settings>About" and click on "Build" 7 times very fast and it will enable "Developer options" in the settings menu, Go back to the settings menu and open developer options (You may need to reboot if it doesnt show up immediately) and enable the "USB debugging" option
Ill be updating this as new version of lollipop get released
support for both firmwares are up, any issues let me know i tested them both though and everything looked okay
Reuploading, had a minor issue
Edit: LRX21M link back up, let me know if there's any issues
Whoa...
Let the games begin....
ftarules said:
Whoa...
Let the games begin....
Click to expand...
Click to collapse
yeup, after recovery i have a few system modification ideas for the settings apk i was considering
i do have other devices to worry about though so it may take some time
bunchies said:
I put together root installer script that comes with SU-binary/App with a insecure boot.img, everything is done over adb shell since we don't have a recovery right now but i will be working on it and already booted CWM
For current firmware:
LRX21V - root-boot
Click to expand...
Click to collapse
Working well, Thank you, after semi-manually adapting for working from Linux Mint.
I don't have permission to do "adb logcat" or "adb shell logcat" anymore though, unless I restart adbd as root.
mikereidis said:
Working well, Thank you, after semi-manually adapting for working from Linux Mint.
I don't have permission to do "adb logcat" or "adb shell logcat" anymore though, unless I restart adbd as root.
Click to expand...
Click to collapse
Use adb shell
than type su to use root adb shell
Since running the script everything seems all good except for using voice search. Anybody else having issues where voice search just closes?
Update: Erased and manually flashed the V firmware as I was on M and now it appears to be working correctly, not sure if this is going to be a problem with people stuck on M for now but you may want to think of upgrading your fimware.
Getting ADB device not found.. Anywhere I can download drivers from? I have the latest android-sdk
xReaper7x said:
Getting ADB device not found.. Anywhere I can download drivers from? I have the latest android-sdk
Click to expand...
Click to collapse
http://developer.android.com/sdk/win-usb.html
at what point, adb will restart about half way through and it shows it cant connect to device but it really is
but if your in fastboot and it cant connect to the device than thats an issue
i should note this in the OP
Subscribed for later. Awaiting someone else to port a recovery for this, I am lazy.
Snuzzo said:
Subscribed for later. Awaiting someone else to port a recovery for this, I am lazy.
Click to expand...
Click to collapse
lol Snuzzo :good: recovery coming soon
Links are down. Does anyone have a mirror of 21V?
prsterero said:
Links are down. Does anyone have a mirror of 21V?
Click to expand...
Click to collapse
Links are up, hosted on android file host
Can mirror in a bit if needed
bunchies said:
Links are up, hosted on android file host
Can mirror in a bit if needed
Click to expand...
Click to collapse
Looks like it's working now. Before I was getting that the file couldn't be found. Thanks I appreciate you releasing this I just got it unlocked so time to root and have some fun expanding the storage to 128gb
Alright so I just got around to running the script, and none of the commands work after booting back up. There's a failure for every rmdir and mkdir command that's used, so the device doesn't get rooted. I tried doing a adb remount, but the device isn't allowing that.
________________________________________________________
root-boot: By Bunchies @xda
________________________________________________________
________________________________________________________
Power off/unplug the device, hold the power button while
plugging in the device until you see the google logo and
than let go to enter fastboot mode
________________________________________________________
________________________________________________________
Plugin the device to a PC using a usb cable
________________________________________________________
Press any key to continue . . .
waiting for ADB
target reported max download size of 536870912 bytes
sending 'boot' (5424 KB)...
OKAY [ 1.357s]
writing 'boot'...
OKAY [ 1.515s]
finished. total time: 2.876s
rebooting...
finished. total time: 0.602s
When boot completes
and you see the launcher
Press any key to continue . . .
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
rm: /system/bin/install-recovery.sh: Read-only file system
mkdir failed for /system/app/SuperSU, Read-only file system
mkdir failed for /system/bin/.ext, Read-only file system
failed to copy 'SuperSU/SuperSU.apk' to '/system/app/SuperSU/': Is a directory
failed to copy 'x86/su' to '/system/xbin/su': Read-only file system
failed to copy 'x86/supolicy' to '/system/xbin/supolicy': Read-only file system
failed to copy 'x86/libsupol.so' to '/system/lib/libsupol.so': Read-only file sy
stem
failed to copy 'x86/99SuperSUDaemon' to '/system/etc/init.d/99SuperSUDaemon': Re
ad-only file system
failed to copy 'x86/install-recovery.sh' to '/system/etc/install-recovery.sh': R
ead-only file system
cp: system/xbin/su: No such file or directory
cp: system/xbin/su: No such file or directory
cp: system/xbin/su: No such file or directory
cp: /system/xbin/sugote-mksh: Read-only file system
ln: /system/bin/su: Read-only file system
ln: /system/bin/install-recovery.sh: File exists
rm: /system/bin/app_process: Read-only file system
ln: /system/bin/app_process: File exists
mv: rename /system/bin/app_process32 to /system/bin/app_process32_original: Read
-only file system
ln: /system/bin/app_process32: File exists
cp: /system/bin/app_process32_original: No such file or directory
Unable to chmod /system/app/SuperSU: No such file or directory
Unable to chmod /system/app/SuperSU/SuperSU.apk: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/lib/libsupol.so: No such file or directory
Unable to chmod /system/bin/.ext: No such file or directory
Unable to chmod /system/bin/.ext/.su: No such file or directory
Unable to chmod /system/etc/init.d/99SuperSUDaemon: No such file or directory
Unable to chmod /system/xbin/daemonsu: No such file or directory
Unable to chmod /system/xbin/sugote: No such file or directory
Unable to chmod /system/xbin/sugote-mksh: No such file or directory
Unable to chmod /system/etc/install-recovery.sh: No such file or directory
Unable to chmod /system/xbin/supolicy: No such file or directory
Unable to chmod /system/bin/app_process32_original: No such file or directory
Unable to chmod /system/bin/app_process_init: No such file or directory
chcon: Could not label /system/xbin/su with ubject_r:system_file:s0: No such
file or directory
chcon: Could not label /system/bin/.ext/.su with ubject_r:system_file:s0: No
such file or directory
chcon: Could not label /system/lib/libsupol.so with ubject_r:system_file:s0:
No such file or directory
chcon: Could not label /system/etc/init.d/99SuperSUDaemon with ubject_r:syste
m_file:s0: No such file or directory
chcon: Could not label /system/bin/sh with ubject_r:system_file:s0: Read-onl
y file system
chcon: Could not label /system/xbin/sugote with ubject_r:zygote_exec:s0: No
such file or directory
chcon: Could not label /system/xbin/supolicy with ubject_r:system_file:s0: N
o such file or directory
chcon: Could not label /system/xbin/sugote-mksh with ubject_r:system_file:s0:
No such file or directory
chcon: Could not label /system/bin/app_process32_original with ubject_r:zygot
e_exec:s0: No such file or directory
chcon: Could not label /system/bin/app_process_init with ubject_r:system_file
:s0: No such file or directory
Finished, you can now exit the installer
Press any key to continue . . .
Edit: Fixed it! I had to manually do "adb root" then "adb remount" and remount succeeded that time and I was able to run the rest of the script and saw all the file transfers.
prsterero said:
Alright so I just got around to running the script, and none of the commands work after booting back up. There's a failure for every rmdir and mkdir command that's used, so the device doesn't get rooted. I tried doing a adb remount, but the device isn't allowing that.
Edit: Fixed it! I had to manually do "adb root" then "adb remount" and remount succeeded that time and I was able to run the rest of the script and saw all the file transfers.
Click to expand...
Click to collapse
Glad to hear that!
bunchies said:
Glad to hear that!
Click to expand...
Click to collapse
The first time around I got into the bootloop so I had to start over. Second time and it worked now it seems that I can't get apps to install through the adb install command. I'm mainly trying to get es file explorer and stick mount so I can use an external flash drive. Is it possible that the root method somehow nuked this functionality? I've already restarted the adb server numerous times, rebooted the player, turned debugging off and back on, etc. Even after all that it just sits after displaying the transfer rate and never finishes.
Edit: Nevermind. Looks like this issue also goes back to having to do adb root and adb remount. Gotta do it for everything apparently
prsterero said:
The first time around I got into the bootloop so I had to start over. Second time and it worked now it seems that I can't get apps to install through the adb install command. I'm mainly trying to get es file explorer and stick mount so I can use an external flash drive. Is it possible that the root method somehow nuked this functionality? I've already restarted the adb server numerous times, rebooted the player, turned debugging off and back on, etc. Even after all that it just sits after displaying the transfer rate and never finishes.
Edit: Nevermind. Looks like this issue also goes back to having to do adb root and adb remount. Gotta do it for everything apparently
Click to expand...
Click to collapse
Weird, windows 8?