I ran the runme.bat and everything seemed to run just fine, no errors. after reboot, I'm still at unroot. no SU permissions. BTW, I just want to root, not flash a custom ROM. Sorry I'm posting here. XDA wouldnt' let me add to the current thread about zergrush.
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
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
720 KB/s (23060 bytes in 0.031s)
--- 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 ...
[+] Zerglings found a way to enter ! 0x10
[+] Overseer found a path ! 0x000151e0
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x40119cd4 0x0054
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd193a3 0xafd3908f
[*] Popping 24 more zerglings
[*] Sending 173 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
--- 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
1222 KB/s (1075144 bytes in 0.859s)
--- correcting permissions
--- remounting /system
--- checking free space on /system
0 KB/s (439 bytes in 1.000s)
--- Free space on /system : 12380 bytes
--- no cleanup required
--- copying busybox to /system/xbin/
2099+1 records in
2099+1 records out
1075144 bytes transferred in 0.503 secs (2137463 bytes/sec)
--- correcting ownership
--- correcting permissions
--- installing busybox
--- pushing SU binary
694 KB/s (22228 bytes in 0.031s)
--- correcting ownership
--- correcting permissions
--- correcting symlinks
--- pushing Superuser app
1169 KB/s (785801 bytes in 0.656s)
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
i had the same problem i downloaded super one click and rooted my phone using that method it worked like a charm on the first try
Or you could just unlock it..
superoneclick is easy and quick
http://forum.xda-developers.com/showthread.php?t=803682
Sent from my Nexus One using Tapatalk
Thanks for the advice. I forgot to mention that I tried SuperOneClick as well. It told me that I was already rooted and did I want to run it anyway. I said yes. I tried Root Check Baisc and it said I'm rooted as well. the problem is when I open Terminal Emulation I get a $. If I type SU, I get permission denied. SU binary is up to date.
BTW, I'm primarily doing all this so I can clear dalvik-cache and perhaps move some of my apps to SD. Still can't do that.
If I open ADB shell on my computer, I can change $ to #, but after I reboot phone, it's back to no permissions.
what abt your firmware version? its impossible to root .62. you must downgrade it first to .58. Same was the case with and after downgrading it worked like a charm.
this helped me get there:
http://forum.xda-developers.com/showthread.php?t=1695514
and i try to unlock uing the megatron....
and i keep getting error..
already tried with 2 comptuers...
[*]
[*] Megatron: LG Optimus 3D/Thrill Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest LG drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
[*] Device found.
[*] Deploying payload...
2078 KB/s (564396 bytes in 0.265s)
pkg: /data/local/tmp/evil.apk
Success
[*] Owning phone...
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Writing to block device...
4 KB/s (4322 bytes in 1.000s)
[*] Searching block device for string, this may take a minute.
[*] Pushing root tools to device...
* daemon not running. starting it now *
* daemon started successfully *
1399 KB/s (22364 bytes in 0.015s)
2112 KB/s (843503 bytes in 0.390s)
[*] Rebooting device again...
[*] Waiting for phone to reboot.
[*] Getting root...
cp: cannot create '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
link failed Read-only file system
cp: cannot create '/system/app/Superuser.apk': Read-only file system
Unable to chmod /system/app/Superuser.apk: No such file or directory
[*] Cleaning up...
cp: cannot stat '/data/local/run-as.bak': No such file or directory
su: permission denied
su: permission denied
rm failed for /data/local/run-as.bak, No such file or directory
Success
[*] Rebooting...
error: protocol fault (no status)
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
davidliu21 said:
and i try to unlock uing the megatron....
and i keep getting error..
already tried with 2 comptuers...
[*]
[*] Megatron: LG Optimus 3D/Thrill Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest LG drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
[*] Device found.
[*] Deploying payload...
2078 KB/s (564396 bytes in 0.265s)
pkg: /data/local/tmp/evil.apk
Success
[*] Owning phone...
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Writing to block device...
4 KB/s (4322 bytes in 1.000s)
[*] Searching block device for string, this may take a minute.
[*] Pushing root tools to device...
* daemon not running. starting it now *
* daemon started successfully *
1399 KB/s (22364 bytes in 0.015s)
2112 KB/s (843503 bytes in 0.390s)
[*] Rebooting device again...
[*] Waiting for phone to reboot.
[*] Getting root...
cp: cannot create '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
link failed Read-only file system
cp: cannot create '/system/app/Superuser.apk': Read-only file system
Unable to chmod /system/app/Superuser.apk: No such file or directory
[*] Cleaning up...
cp: cannot stat '/data/local/run-as.bak': No such file or directory
su: permission denied
su: permission denied
rm failed for /data/local/run-as.bak, No such file or directory
Success
[*] Rebooting...
error: protocol fault (no status)
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
Click to expand...
Click to collapse
try this one
that's the one i used....
Try super one click I don't remember how I rooted I can try later maybe I would have to flash it tho
sent from my acidhazard thrill
I rooted m lg thrill with megatron in windows 7. I didnt have any problem. You can try this.
Ok finally ive tried 3 comouters , non of them works all windows 7 and i use a old computer running windows xp. And it works like a charm lol
Sent from my LG-P925 using XDA
I'm glad ya got it working, but it should of worked fine on win7. Ive been on 7 sense it came out and use nothing else.
davidliu21 said:
and i try to unlock uing the megatron....
and i keep getting error..
already tried with 2 comptuers...
[*]
[*] Megatron: LG Optimus 3D/Thrill Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest LG drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
[*] Device found.
[*] Deploying payload...
2078 KB/s (564396 bytes in 0.265s)
pkg: /data/local/tmp/evil.apk
Success
[*] Owning phone...
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Writing to block device...
4 KB/s (4322 bytes in 1.000s)
[*] Searching block device for string, this may take a minute.
[*] Pushing root tools to device...
* daemon not running. starting it now *
* daemon started successfully *
1399 KB/s (22364 bytes in 0.015s)
2112 KB/s (843503 bytes in 0.390s)
[*] Rebooting device again...
[*] Waiting for phone to reboot.
[*] Getting root...
cp: cannot create '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
link failed Read-only file system
cp: cannot create '/system/app/Superuser.apk': Read-only file system
Unable to chmod /system/app/Superuser.apk: No such file or directory
[*] Cleaning up...
cp: cannot stat '/data/local/run-as.bak': No such file or directory
su: permission denied
su: permission denied
rm failed for /data/local/run-as.bak, No such file or directory
Success
[*] Rebooting...
error: protocol fault (no status)
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
Click to expand...
Click to collapse
Spent hours and hours spread across many days trying to find out what happened. All you need to do is hard reset your phone and take out Micro SD card. Restart your computer to eliminate any usb driver conflicts (don't really need to do this step but you never know). Then run megatron_windows.
Im trying to root my galaxy mini 2.3.6 with DooMLoRD_v4_ROOT-zergRush-busybox-su and can't get it work. When I start rooting it shows me this msg:
Code:
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
--- pushing zergRush
1443 KB/s (23060 bytes in 0.015s)
--- 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
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] 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
3831 KB/s (1075144 bytes in 0.274s)
--- 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/.lfs: Function not implemented
df: /mnt/secure/asec: Permission denied
--- Free space on /system : 17244 bytes
--- no cleanup required
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
what's wrong?
first, wrong section
trx it with a update.zip root package via stock recovery to get root.
cause your problem is the firmware u wanr to root!
Sent from my GT-S5660 using xda app-developers app
But my phone have no recovery. I bought it few days ago and I get it with 2.3.6 by default. what to do?
it has one, a stock samsung one,
which makes hlupdate.zip's aviable
Sent from my GT-S5660 using xda app-developers app
There's something noobs don't always understand: THERE IS A ****ING GENERAL SECTION.
how can I get that recovery?
i tried with pressing some buttons but cant get it in
wrong section
press and hold volume up AND home button, while pressing buttons turn the phone on and apply update.zip from menu
Just a reminder, the only things that belong in Development are things that you have created yourself. Not questions. Your thread has been moved.
no problem about topic
Hello all,
I just acquired a T679 and am having some trouble rooting it.
I have tried ZergRush with no luck
> USB debugging is enabled. So is 'Uknown Sources'
> Here is the output from the ZergRush session
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush"
2814 KB/s (23056 bytes in 0.008s)
--- 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 ! 0x00029118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] 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
4929 KB/s (1075144 bytes in 0.213s)
--- 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 . . .
Click to expand...
Click to collapse
Is it currently possible to root this phone?
To make sure we are all on teh same page, here is the About Phone info.
Model: SGH-T679
Android: 2.3.6
Build: GINGERBREAD.UVLE1
Is there an updated ZergRush?
whiteghetto said:
Hello all,
I just acquired a T679 and am having some trouble rooting it.
I have tried ZergRush with no luck
Is it currently possible to root this phone?
To make sure we are all on teh same page, here is the About Phone info.
Model: SGH-T679
Android: 2.3.6
Build: GINGERBREAD.UVLE1
Is there an updated ZergRush?
Click to expand...
Click to collapse
http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
Install a new recovery and then flash Jocala's custom rooted kernel. Zergrush doesn't work on 2.3.6.
use the jocalas mod men
http://forum.xda-developers.com/showpost.php?p=26859796
Thanks a ton guys. This info was very hard to find in a coherant manner. I was able to flash CWM with the stock recovery. Then flashed the 'stock root' ZIP from jocale.
I am not rooted
Hey guys,
i have rooted many phones before, however i am having a problem with a previously rooted Sony Z1.
The previous happenings:
I rooted the device by unlocking the bootloader on the sony site. I then loaded on clockwork recovery and slapped cyanogen mod on it.
The phone was fine and working nicely, but recently stopped updating Cyanogen mod. I attempted to boot into recovery to install the latest version but all combinations of button pushing lead to nothing for a good few seconds before it starts to boot back into cyanogenmod again.
I tried using apps and various other methods to boot into fastboot, recovery and bootloader but it all goes right back into the OS.
I now have no way of updating the OS and tried using ADB to load on recovery again. ADB can see the device, and pushes successfully but when trying to boot into it, again, it does nothing but go back to the OS.
Can anyone give me a hand in popping on a recovery and somehow installing the latest Cyanogen back on? This is by far the biggest pain in the butt phone to root to begin with, but any help is much appreciated.
Tex0gen said:
Hey guys,
i have rooted many phones before, however i am having a problem with a previously rooted Sony Z1.
The previous happenings:
I rooted the device by unlocking the bootloader on the sony site. I then loaded on clockwork recovery and slapped cyanogen mod on it.
The phone was fine and working nicely, but recently stopped updating Cyanogen mod. I attempted to boot into recovery to install the latest version but all combinations of button pushing lead to nothing for a good few seconds before it starts to boot back into cyanogenmod again.
I tried using apps and various other methods to boot into fastboot, recovery and bootloader but it all goes right back into the OS.
I now have no way of updating the OS and tried using ADB to load on recovery again. ADB can see the device, and pushes successfully but when trying to boot into it, again, it does nothing but go back to the OS.
Can anyone give me a hand in popping on a recovery and somehow installing the latest Cyanogen back on? This is by far the biggest pain in the butt phone to root to begin with, but any help is much appreciated.
Click to expand...
Click to collapse
I've ran into almost exactly the same issue. Only difference is that I'm yet to install a custom ROM.
If anyone has a solution it would be greatly appreciated.
spiritonline said:
I've ran into almost exactly the same issue. Only difference is that I'm yet to install a custom ROM.
If anyone has a solution it would be greatly appreciated.
Click to expand...
Click to collapse
Just reflash dual recovery. I had the same issue before just flash dual recovery from the install batch or shell file and should work
JustPlayingHard said:
Just reflash dual recovery. I had the same issue before just flash dual recovery from the install batch or shell file and should work
Click to expand...
Click to collapse
I've tried this to no avail unfortunately.
if your cm rom 's zip got boot.img flash it
Sent from my C6903 Xperia Z1 using Tapatalk
---------- Post added at 09:02 AM ---------- Previous post was at 09:00 AM ----------
using fastboot flash it
i think the boot .img include kernel with recovery
==============================================
fastboot flash boot boot.img
Sent from my C6903 Xperia Z1 using Tapatalk
JustPlayingHard said:
Just reflash dual recovery. I had the same issue before just flash dual recovery from the install batch or shell file and should work
Click to expand...
Click to collapse
Dual recovery is for stock roms, it won't work on CM.
Sent from my C6903 using XDA Premium 4 mobile app
gregbradley said:
Dual recovery is for stock roms, it won't work on CM.
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Whoops I'm so sorry didn't read it was CM. Try flash a kernel with Recovery in it?
gregbradley said:
Dual recovery is for stock roms, it won't work on CM.
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm on the stock Vodafone rom.
I've tried running the dual recovery again it says it succeeds but I still can't boot into flash mode.
The weird thing is that I previously could.
I've also tried flashing boot.img but still no luck
Any other suggestions?
Thanks in advance!
spiritonline said:
I'm on the stock Vodafone rom.
Click to expand...
Click to collapse
have you rooted it?
I've tried running the dual recovery again it says it succeeds but I still can't boot into flash mode.
Click to expand...
Click to collapse
You do not need recovery or root to enter flashmode. Flashmode is a boot mode that completely stock phones can boot into in order to perform updates via PCCompanion
The weird thing is that I previously could.
I've also tried flashing boot.img but still no luck
Click to expand...
Click to collapse
Have you unlocked the bootloader?
Any other suggestions?
Click to expand...
Click to collapse
Yes, please post the output of the command window when you try to install dual recovery
Thanks in advance!
Click to expand...
Click to collapse
gregbradley said:
have you rooted it?You do not need recovery or root to enter flashmode. Flashmode is a boot mode that completely stock phones can boot into in order to perform updates via PCCompanionHave you unlocked the bootloader?Yes, please post the output of the command window when you try to install dual recovery
Click to expand...
Click to collapse
I'm not sure how to quote inline as you just did but:
- Yes I've rooted the phone
- You're right I'm mixing things up. I can't enter recovery I can go to flash mode. (blue led)
- No I haven't unlocked the boot loader
- Dual fails on my Mac, I will boot into my windows install and come back with the output.
Thanks for your time.
spiritonline said:
I'm not sure how to quote inline as you just did but:
- Yes I've rooted the phone
- You're right I'm mixing things up. I can't enter recovery I can go to flash mode. (blue led)
Click to expand...
Click to collapse
Wrong, Blue LED is fastboot, green LED is flashmode. This may be your issue.
- No I haven't unlocked the boot loader
Click to expand...
Click to collapse
then you wont be able to flash the boot.img
- Dual fails on my Mac, I will boot into my windows install and come back with the output.
Click to expand...
Click to collapse
It is a windows based installer, so that may help
Thanks for your time.
Click to expand...
Click to collapse
gregbradley said:
Wrong, Blue LED is fastboot, green LED is flashmode. This may be your issue.then you wont be able to flash the boot.imgIt is a windows based installer, so that may help
Click to expand...
Click to collapse
You're quick!
Here's the output:
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 C6903
Firmware is 14.4.A.0.133
=============================================
Step2 : Sending the recovery files.
=============================================
mkdir failed for /data/local/tmp/recovery, File exists
13 KB/s (29 bytes in 0.002s)
3710 KB/s (15757 bytes in 0.004s)
297 KB/s (501 bytes in 0.001s)
3952 KB/s (11842 bytes in 0.002s)
5157 KB/s (56834 bytes in 0.010s)
1914 KB/s (3082 bytes in 0.001s)
187 KB/s (385 bytes in 0.002s)
5708 KB/s (657704 bytes in 0.112s)
5432 KB/s (2965179 bytes in 0.533s)
5374 KB/s (2598631 bytes in 0.472s)
5795 KB/s (1875928 bytes in 0.316s)
3093 KB/s (8759 bytes in 0.002s)
=============================================
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 Jul 31 17:09 /data/local/tmp/recover
y/busybox
Press any key to continue . . .
##########################################################
#
# Installing XZDR version 2.7.154 BETA
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to al
low installation.
mount: permission denied (are you root?)
mount: permission denied (are you root?)
Copy recovery files to system.
cp: can't create '/system/bin/recovery.twrp.cpio.lzma': File exists
cp: can't create '/system/bin/recovery.cwm.cpio.lzma': File exists
cp: can't create '/system/bin/recovery.philz.cpio.lzma': File exists
chmod: /system/bin/recovery.twrp.cpio.lzma: Read-only file system
chmod: /system/bin/recovery.cwm.cpio.lzma: Read-only file system
chmod: /system/bin/recovery.philz.cpio.lzma: 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': File exists
chmod: /system/bin/dualrecovery.sh: Read-only file system
Copy rickiller.sh to system.
cp: can't create '/system/bin/rickiller.sh': File exists
chmod: /system/bin/rickiller.sh: Read-only file system
Installing NDRUtils to system.
cp: can't create '/system/app/NDRUtils.apk': File exists
chmod: /system/app/NDRUtils.apk: Read-only file system
Copy disableric to system.
cp: can't create '/system/xbin/disableric': File exists
chmod: /system/xbin/disableric: Read-only file system
Copy busybox to system.
cp: can't create '/system/xbin/busybox': Read-only file system
cp: can't create '/system/.XZDualRecovery/busybox': File exists
chmod: /system/xbin/busybox: No such file or directory
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.
=============================================
/system/bin/sh: /system/xbin/busybox: not found
=============================================
Installation finished. Enjoy the recoveries!
=============================================
Press any key to continue . . .
There is an issue with your root. Can you remount the system partition into read/write?
Please goto
sys/kernel/security/sony_ric
and look in the file that is there (If there is one). Please tell me if it says 1 or 0.
Can you let me know how you rooted?
gregbradley said:
There is an issue with your root. Can you remount the system partition into read/write?
Please goto
sys/kernel/security/sony_ric
and look in the file that is there (If there is one). Please tell me if it says 1 or 0.
Can you let me know how you rooted?
Click to expand...
Click to collapse
I'm not sure how to remount the system partition into read/write.
The folder you suggested is indeed empty.
I've rooted trough this guide: http://forum.xda-developers.com/xperia-z1/development/c6903-14-4-0-133-deodex-patch-root-t2848466
I can imagine something being wrong but it worked to some extend since I have superSU working.
Thanks again.
spiritonline said:
I'm not sure how to remount the system partition into read/write.
Click to expand...
Click to collapse
Use any root explorer and goto system and try to create a file or folder. If you are not mounted as RW it will prompt you to do so. Let me know if you can create a file or folder in the system partition
The folder you suggested is indeed empty.
I've rooted trough this guide: http://forum.xda-developers.com/xperia-z1/development/c6903-14-4-0-133-deodex-patch-root-t2848466
Click to expand...
Click to collapse
That should be ok and install dual recovery. The issue is getting the system to be RW. Try running it again and use option 3.
I can imagine something being wrong but it worked to some extend since I have superSU working.
Thanks again.
Click to expand...
Click to collapse
If it still does not work, then you can try flashing the stock 133 FTF again and going through the process of rooting again using option 3
gregbradley said:
Use any root explorer and goto system and try to create a file or folder. If you are not mounted as RW it will prompt you to do so. Let me know if you can create a file or folder in the system partition That should be ok and install dual recovery. The issue is getting the system to be RW. Try running it again and use option 3.
If it still does not work, then you can try flashing the stock 133 FTF again and going through the process of rooting again using option 3
Click to expand...
Click to collapse
Thanks for your continues support on this.
I'm unable to create a new folder in the system directory as you predicted.
I just tried to do recovery option 3 but it hangs on "libdvm opend <lol javasucks>
I've posted everything bellow. (I will now try to flash 133 again.)
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]?3
* 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 C6903
Firmware is 14.4.A.0.133
=============================================
Step2 : Sending the recovery files.
=============================================
mkdir failed for /data/local/tmp/recovery, File exists
4 KB/s (29 bytes in 0.006s)
1837 KB/s (15757 bytes in 0.008s)
132 KB/s (501 bytes in 0.003s)
1667 KB/s (11842 bytes in 0.006s)
2784 KB/s (56834 bytes in 0.019s)
625 KB/s (3082 bytes in 0.004s)
123 KB/s (385 bytes in 0.003s)
2788 KB/s (657704 bytes in 0.230s)
3484 KB/s (2965179 bytes in 0.830s)
4140 KB/s (2598631 bytes in 0.612s)
3605 KB/s (1875928 bytes in 0.508s)
1487 KB/s (8759 bytes in 0.005s)
=============================================
Step3 : Setup of dual recovery.
=============================================
=============================================
Attempting to get root access for installation using TowelRoot now.
NOTE: this only works on certain ROM/Kernel versions!
If it fails, please check the development thread (Post #2) on XDA for more detai
ls.
REMEMBER THIS:
XZDualRecovery does NOT install any superuser app!!
You can use one of the recoveries to root your device.
=============================================
=============================================
Sending files
=============================================
505 KB/s (1572 bytes in 0.003s)
3929 KB/s (13592 bytes in 0.003s)
5716 KB/s (197320 bytes in 0.033s)
2356 KB/s (9496 bytes in 0.003s)
2973 KB/s (13672 bytes in 0.004s)
Copying kernel module...
3693 KB/s (34473 bytes in 0.009s)
342 KB/s (765 bytes in 0.002s)
2778 KB/s (13592 bytes in 0.004s)
Kernel version is 3.4.0-perf-gf96f13d-00901-g5169043
Version does not match 3.4.0-perf-ge4322cd, needs patching...
1+0 records in
0+1 records out
34 bytes transferred in 0.001 secs (34000 bytes/sec)
Kernel module patched.
modulecrcpatch (by zxz0O0)
module_layout: match
__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
=============================================
Installing using zxz0O0's towelzxperia
(using geohot's towelroot library)
=============================================
towelzxperia (by zxz0O0)
thanks to geohot for libexploit
creating libzxploit.so
libzxploit.so created
doing the magic
creating vm (loljavasucks)
libdvm opened (loljavasucks)
spiritonline said:
Thanks for your continues support on this.
I'm unable to create a new folder in the system directory as you predicted.
I just tried to do recovery option 3 but it hangs on "libdvm opend <lol javasucks>
I've posted everything bellow. (I will now try to flash 133 again.)
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]?3
* 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 C6903
Firmware is 14.4.A.0.133
=============================================
Step2 : Sending the recovery files.
=============================================
mkdir failed for /data/local/tmp/recovery, File exists
4 KB/s (29 bytes in 0.006s)
1837 KB/s (15757 bytes in 0.008s)
132 KB/s (501 bytes in 0.003s)
1667 KB/s (11842 bytes in 0.006s)
2784 KB/s (56834 bytes in 0.019s)
625 KB/s (3082 bytes in 0.004s)
123 KB/s (385 bytes in 0.003s)
2788 KB/s (657704 bytes in 0.230s)
3484 KB/s (2965179 bytes in 0.830s)
4140 KB/s (2598631 bytes in 0.612s)
3605 KB/s (1875928 bytes in 0.508s)
1487 KB/s (8759 bytes in 0.005s)
=============================================
Step3 : Setup of dual recovery.
=============================================
=============================================
Attempting to get root access for installation using TowelRoot now.
NOTE: this only works on certain ROM/Kernel versions!
If it fails, please check the development thread (Post #2) on XDA for more detai
ls.
REMEMBER THIS:
XZDualRecovery does NOT install any superuser app!!
You can use one of the recoveries to root your device.
=============================================
=============================================
Sending files
=============================================
505 KB/s (1572 bytes in 0.003s)
3929 KB/s (13592 bytes in 0.003s)
5716 KB/s (197320 bytes in 0.033s)
2356 KB/s (9496 bytes in 0.003s)
2973 KB/s (13672 bytes in 0.004s)
Copying kernel module...
3693 KB/s (34473 bytes in 0.009s)
342 KB/s (765 bytes in 0.002s)
2778 KB/s (13592 bytes in 0.004s)
Kernel version is 3.4.0-perf-gf96f13d-00901-g5169043
Version does not match 3.4.0-perf-ge4322cd, needs patching...
1+0 records in
0+1 records out
34 bytes transferred in 0.001 secs (34000 bytes/sec)
Kernel module patched.
modulecrcpatch (by zxz0O0)
module_layout: match
__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
=============================================
Installing using zxz0O0's towelzxperia
(using geohot's towelroot library)
=============================================
towelzxperia (by zxz0O0)
thanks to geohot for libexploit
creating libzxploit.so
libzxploit.so created
doing the magic
creating vm (loljavasucks)
libdvm opened (loljavasucks)
Click to expand...
Click to collapse
Ok don't forget to flash the .108 kernel. It hangs there if you are on the .133 kernel.
gregbradley said:
Ok don't forget to flash the .108 kernel. It hangs there if you are on the .133 kernel.
Click to expand...
Click to collapse
Ok, so I flash the .108 first, then root, then flash 133?
Yes, but kernel only
Sent from my C6903 using XDA Premium 4 mobile app
gregbradley said:
Yes, but kernel only
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok, so I
1. flashed .108
2. rooted user dualrecovery
3. verified permissions by creating a new file in system and recovery was working fine.
I then tried to install darkCM per instructions but after flashing in recovery the phone wont boot.
It will just show a a blinking red LED when it's on a charger.
The only way I could find to fix it was to install stock vodafone firmware.
I retried the above twice with the same result, I hope I'm not to much a nuisance but if you could help me any further i'd appreciate it.:good: