I have Semc sim free phone.
when i use the msm7227_semc, it opens the console and when i press the buttons it wirtes:
"
press any key to continue...
Getting Root Rights.
1157 Kb/s (585731 bytes in 0.949s)
- exec '/system/bin/sh' failed: no such file or directory(2)-
- exec '/system/bin/sh' failed: no such file or directory(2)-
Waiting...
"
and so on on everything else it's trying to write.
I'm using GingerDX v.013.
what do to??
moseschrist said:
I have Semc sim free phone.
when i use the msm7227_semc, it opens the console and when i press the buttons it wirtes:
"
press any key to continue...
Getting Root Rights.
1157 Kb/s (585731 bytes in 0.949s)
- exec '/system/bin/sh' failed: no such file or directory(2)-
- exec '/system/bin/sh' failed: no such file or directory(2)-
Waiting...
"
and so on on everything else it's trying to write.
I'm using GingerDX v.013.
what do to??
Click to expand...
Click to collapse
Visit this guide first post step 7 to see if you have bootloader successfully unlocked: http://forum.xda-developers.com/showthread.php?t=1254225
If not, disable antivirus and try unlocking your phone's bootloader again.
Remember that you have to use a rooted phone and that you must have phone dricers already installed.
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.
I followed this guide http://forum.xda-developers.com/showthread.php?t=1254225 and after running msm7227_semc.cmd i got this:
process requires standard 2.x android firmware.
Press any key to continue . . .
Getting ROOT rights.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
cannot stat 'bootTools\rageagainstthecage': No such file or directory
Waiting ...
Removing NAND MPU restrictions via SEMC backdoor. Permanent. Require ROOT rights
.
120 KB/s (3087 bytes in 0.025s)
Unable to open router port: Permission denied
Diag_LSM: Diag_LSM_Init: Failed to open handle to diag driver, error = 13 ERR :
MSG Open handle failed, unable to open program 30eeeeee ver 10001 NOT FOUND
:FILE vendor/qcom-proprietary-msm7k/oncrpc/oncrpc/oncrpc_cb.c:LINE 231:ARG1 82
0965102:ARG2 65537:ARG3 0:
ERR :MSG Couldn't setup RPC call :FILE vendor/qcom-proprietary-msm7k/oncrpc/on
crpc/oncrpc_cb.c:LINE 276:ARG1 0:ARG2 0:ARG3 0:
Error: Failed to lookup client for 0x30EEEEEE 0x00010001
FATAL :MSG Failed to lookup RPC client. prog = 820965102, vers = 65537, tout =
0 :FILE vendor/semc/system/core/miscta/libmiscta/rpc_service.c:LINE 65:ARG1 820
965102:ARG2 65537:ARG3 0:
reboot: Operation not permitted
Waiting ...
Getting ROOT rights.
Waiting ...
Writing patched semcboot. Two step process
First, we need get access to semcboot area
246 KB/s (8064 bytes in 0.032s)
insmod: init_module '/data/local/tmp/mapper_2.6.29.ko' failed (Operation not per
mitted)
Second, we need to write semcboot
2340 KB/s (596916 bytes in 0.249s)
can't find userdate partition
Press any key to continue . . .
Can someone help me with this please?
Found solution, which is:
http://forum.xda-developers.com/showthread.php?t=1117100
Somehow x8toolbox managed to successfully unlock my phone
hi, i unlocked my bootloader with this tutorial
http://forum.xda-developers.com/showthread.php?t=1254225
but it won't recorgnise the SIM card and it won't connect to the network.
at the topic it says: 1.
My SIM Card is not recognised after unlocking phone with msm7227_setool2.cmd!
Ans: Redo unlocking procedure (step 5 onwards) using msm7227_semc.cmd.
but i get this error.
Code:
process requires standard 2.x android firmware.
Πιέστε ένα πλήκτρο για συνέχεια. . .
Getting ROOT rights.
1047 KB/s (585731 bytes in 0.546s)
Failed to set prot mask (Inappropriate ioctl for device)
Waiting ...
Removing NAND MPU restrictions via SEMC backdoor. Permanent. Require ROOT rights
.
193 KB/s (3087 bytes in 0.015s)
success
Waiting ...
Getting ROOT rights.
Failed to set prot mask (Inappropriate ioctl for device)
Waiting ...
Writing patched semcboot. Two step process
First, we need get access to semcboot area
504 KB/s (8064 bytes in 0.015s)
insmod: can't insert '/data/local/tmp/mapper_2.6.29.ko': invalid module format
Second, we need to write semcboot ;)
812 KB/s (596916 bytes in 0.717s)
can't find userdate partition
Πιέστε ένα πλήκτρο για συνέχεια. . .
instead of
Code:
process requires standard 2.x android firmware.
Press any key to continue . . .
Getting ROOT rights.
1743 KB/s (585731 bytes in 0.328s)
error: protocol fault (no status)
Waiting ...
Removing NAND MPU restrictions via SEMC backdoor. Permanent. Require ROOT rights.
192 KB/s (3087 bytes in 0.015s)
success
Waiting ...
Getting ROOT rights.
Waiting ...
Writing patched semcboot. Two step process
First, we need get access to semcboot area
504 KB/s (8064 bytes in 0.015s)
Second, we need to write semcboot ;)
1130 KB/s (596916 bytes in 0.515s)
successfully wrote 0003ff00
Press any key to continue . . .
can u help me fix it? just installed MiniCM7 on this X8
please somebody.. respond :/
What is your phone's simlock certificate? Is it SEMC SIMLOCK Certificate or Not Recognized SIMLOCK Certificate? And have you tried to relock your phone's bootloader and check whether your SIM Card is recognized?
before i install MiniCm7 i think it was saying SEMC SIMLOCK Certificate...
and if i relock it the phone will be bricked :/
edit: made it sure. it's SEMC SIMLOCK Certifticate
respond please :/ i really need a solution
You can go back to stock ROM and stock kernel and then relock the bootloader. Please make sure though.
really good idea
that's the right kernel? http://forum.xda-developers.com/showthread.php?t=1567687&highlight=stock+kernel
and that the right rom? http://forum.xda-developers.com/showthread.php?t=1099931
i know how to flash the kernel, but how the rom? or do i have to flash the stock rom with the recovery from the custom kernel before i flash the stock kernel?
msm7227_setool.cmd
try this
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: