Read-only filesystem - Tired everything - SGP312 - Xperia Tablet Z Q&A, Help & Troubleshooting

Device: Sony Xperia Tablet Z
Model: SGP312
Android: 4.4.4
Problem started from 3 days ago. I had custom rom and had custom recovery: xzdualrecovery
I had some issue so wanted back to the official firmware. But unfortunately, i failed to restore the backup using TWRP.
So i needed to flash official firmware using Flashtool.
Didn't working Lolipop firmware so i flashed kitkat.
But the problem started after flashing firmware, that system is only Read-Only. I cannot able to use Internal Memory and also playstore not working.
So i wanted to again root and install "xzdualrecovery".
But getting error cause of the read-only issue.
Here is the log:
Code:
==============================================
= =
= XZDualRecovery =
= 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 an unrooted (Lollipop 5.0) ROM using rootkitXperia
4. Install ADB drivers to windows
5. Open an ADB shell
6. Exit
Please choose install action.
[1,2,3,4,5,6]?1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
=============================================
Getting device and ROM info
=============================================
Device model is SGP312
Firmware is 10.5.1.A.0.292
Android version is 4.4.4
=============================================
Step2 : Sending the recovery files.
=============================================
10 KB/s (31 bytes in 0.002s)
2219 KB/s (18170 bytes in 0.007s)
163 KB/s (501 bytes in 0.002s)
1788 KB/s (12812 bytes in 0.006s)
2623 KB/s (65965 bytes in 0.024s)
771 KB/s (3159 bytes in 0.003s)
2378 KB/s (29204 bytes in 0.011s)
227 KB/s (699 bytes in 0.002s)
2406 KB/s (34473 bytes in 0.013s)
293 KB/s (1202 bytes in 0.003s)
2826 KB/s (96956 bytes in 0.033s)
3916 KB/s (870760 bytes in 0.217s)
3416 KB/s (3559894 bytes in 1.017s)
3528 KB/s (2426224 bytes in 0.671s)
2803 KB/s (14346 bytes in 0.004s)
=============================================
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 870760 Feb 22 2016 [1;32m/data/local/tmp/recovery/busybox[0m
Press any key to continue . . .
mkdir: can't create directory '/storage/sdcard1/XZDualRecovery': Read-only file system
mkdir: can't create directory '/cache/XZDualRecovery': Read-only file system
touch: /cache/XZDualRecovery/XZDR.prop: No such file or directory
grep: /cache/XZDualRecovery/XZDR.prop: No such file or directory
grep: /cache/XZDualRecovery/XZDR.prop: No such file or directory
grep: /cache/XZDualRecovery/XZDR.prop: No such file or directory
grep: /cache/XZDualRecovery/XZDR.prop: No such file or directory
##########################################################
#
# Installing XZDR version 2.8.26 RELEASE
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to allow installation.
This firmware does not require byeselinux, will not install it.
Creating /system/.XZDualRecovery and subfolders.
Copy recovery files to system.
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Copy busybox to system.
Copy init's *.rc files in to /system/.XZDualRecovery.
Creating the XZDR properties file.
touch: /cache/XZDualRecovery/XZDR.prop: No such file or directory
chmod: /cache/XZDualRecovery/XZDR.prop: No such file or directory
Updating installed version in properties file.
dr.recovery.boot will be set to TWRP (default)
dr.initd.active will be set to false (default)
dr.ramdisk.boot will be set to false (default)
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event5!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event0!
Speeding up CWM backups.
mkdir: can't create directory '/sdcard1/clockworkmod/': Read-only file system
touch: /sdcard1/clockworkmod/.hidenandroidprogress: No such file or directory
Make sure firstboot goes to recovery.
mkdir: can't create directory '/cache/recovery/': Read-only file system
touch: /cache/recovery/boot: No such file or directory
=============================================
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 . . .
Yes had rooting issue but rooted successfully using kernel: SGP312_10.5.A.0.230_kernel.ftf
So i have SuperSU and rooted using flashtool.
I tired by chaning flashfile:
SGP312_10.4.1.B.0.109_US_CA_PR_R1C.ftf
SGP312_10.5.1.A.0.283_HK-SA-SG-MY-AE-KW.ftf
SGP312_10.5.1.A.0.292_VMo UK-IE.ftf
SGP312_10.6.A.0.454_VMo US-CA-PR.ftf
SGP312_10.7.A.0.222_1273-3888_HK-SA-SG-MY-AE-KW.ftf
SGP312_10.7.A.0.222_VMo_US_CA_PR.ftf
Still no luck. Stucking permission issue.
I tired to remount using adb shell but again it's getting read-only issue after the restart.
So i want to know how can i resolve this read-only filesystem issue? I need to use TWRP to restore my backup too.
Please help me, save my tablet.
Update: Fixed.

Related

Sony Ericsson Wallkman wt19i Root Problem

After update Android on 4.0.2.A.0.62 my root wont work at all,i downloaded more root toolkits but seams non of one works.
Does any one have this problem and how to fix this???
Plz help and thanks ppl!!!
Same
Hello, i have the same problem and this post, i hope, is going to draw some attention. I have tried DooMLord's v3 and v4 rooter and it says basically the same thing.
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
Tryk på en vilkårlig tast for at fortsætte . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
1732 KB/s (23060 bytes in 0.013s)
--- 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
3301 KB/s (1075144 bytes in 0.318s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
85 KB/s (439 bytes in 0.005s)
--- Free space on /system : 156112 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!!!
Tryk på en vilkårlig tast for at fortsætte . . .
I really hope that someone would help, and reply to this...
Regards Mads
EDIT: Don't mind the danish, it says "Press any key to continue"
Westerdahl said:
Hello, i have the same problem and this post, i hope, is going to draw some attention. I have tried DooMLord's v3 and v4 rooter and it says basically the same thing.
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
Tryk på en vilkårlig tast for at fortsætte . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
1732 KB/s (23060 bytes in 0.013s)
--- 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
3301 KB/s (1075144 bytes in 0.318s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
85 KB/s (439 bytes in 0.005s)
--- Free space on /system : 156112 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!!!
Tryk på en vilkårlig tast for at fortsætte . . .
I really hope that someone would help, and reply to this...
Regards Mads
EDIT: Don't mind the danish, it says "Press any key to continue"
Click to expand...
Click to collapse
Hope this will help you out:
1.Unzip firmware and put it in flashtool firmware (Drag and drop the firmware into the flash tool window). If you cannot drag and drop, extract firnware into the firmware folder located inside the flash tool application folder usually located at the program files folder.
2.Go to flashtool. Power off phone and connect USB cable while pressing volume down before connecting to PC usb port. You ll see green led (youre now in flash mode). Flash firmware (from the running flash window on the PC). Wait for setup complete and then boot up your phone.
3.Extract Doomlord root kitt .Before root make sure usb debugging is tick and display screen timeout at hp set to 10 or 30 minutes. Run runme.bat.check whether superuser is there. If yes, you have successfully rooted your phone, also you may want to check settings>about phone>build number (If your last two digits is reverted to 0.58 then things went well.
4.Now you must update to new firmware using update on air (OTA). In your phone, go to setting>about>software update. Download and install.
WARNING : DONT UPDATE USING PC COMPANION OR YOU WILL LOSE YOUR ROOT
5. After update.Unzip cwm install and run the second file script for wt19i.install-cmw2.cmd.This proses like the 3rd step. Make sure usb debugging mode and displays screen timeout set to 10min
And done...u have newer version root firmware + cwm without unlock bootloader.Thank to doomlord and nobodyAtall
The step i posted here is the same procedure i perfomed to root my phone since i don't want to unlock my boot loader.
Click Thanks, if my post was helpful to you.
Guys I also Have The Same Problem....Where to Get the Firmware for wt19i and How to Root...Please Explain Us Clearly......
Luiphilip 10x bro,i flashed phone on 58,root and over OTA update to 62 without loosing root.
Sent from my WT19i using xda premium

[Q] Pleeeeease Help me ... problem rooting sk17i

Hello ...
I'v recently downgraded my mini pro to .42 to do a root, I am new to this and I found a way using zergrush.
whenever I try rooting I have the following error:
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
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
--- pushing zergRush
721 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
[+] Found a ... mode
[*] 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
731 KB/s (1075144 bytes in 1.435s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
0 KB/s (439 bytes in 1.000s)
df: /mnt/.lfs: Function not implemented
--- Free space on /system : 433300 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 . . .
Any one can help please????
I used the files in this thread:
http://forum.xda-developers.com/showthread.php?t=1695514
and every thing is ok now
Just to be sure, did you enable USB debugging and Unknown sources?
Feanor88 said:
Just to be sure, did you enable USB debugging and Unknown sources?
Click to expand...
Click to collapse
Yes Of course
u might have flushed rooted ftf file to ur fone.dwnld root checker 4m google play.
Sent from my ST15i using xda app-developers app
I had same problems, try rooting with flashtool. Download from here and install. Then klick on the open padlock, right next to the flash. This will root your device. Very great tool, if zergrush/Doomlords didn't work for you!

[Q] DooMLoRD's easy rooting toolkit not working on Samsung Galaxy Y Pro (Galaxy Txt)

Right. Hi. First post.
I wanted to post this in the actual thread, but since I'm not allowed, having not 10 posts, I'll just post this here.
It says the Samsung Galaxy Y Pro (2.3.5) is supported, and in fact I was able to root my phone earlier before I updated it (not sure which version I was at back then, before my last update it was still on 2.3.6 too so I'm guessing that hasn't changed.) using a different exploit. I'll be darned if I can remember which it was, but it did required me to run a .zip file in recovery mode of my phone.
I own this phone (Well it's called a Galaxy Txt here, but it's the same device.) and it's running Gingerbread 2.3.6
Kernel: 2.3.6.35.7
[email protected] #1
Build: GINGERBREAD.CELK2
The tool gave me this output:
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
Druk op een toets om door te gaan. . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
643 KB/s (23060 bytes in 0.035s)
--- 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
4467 KB/s (1075144 bytes in 0.235s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
107 KB/s (439 bytes in 0.004s)
df: /mnt/.lfs: Function not implemented
--- Free space on /system : 16148 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!!!
I'd like root access again, so I figured I'd post my report anyways.
Thanks.
(By the way, nobody has cyanogen'd it, have they?)

[Q] A Problem when root using Easy Root Tool

Hello,
I'm using EasyRootTool v11.zip from http://forum.xda-developers.com/showthread.php?t=2784900. When I run it, it shows that:
Code:
=============================================
Getting device variables
=============================================
Device model is L50u
Firmware is 17.1.1.F.0.39
=============================================
Sending files
=============================================
36 KB/s (1585 bytes in 0.042s)
25 KB/s (1133 bytes in 0.042s)
207 KB/s (9496 bytes in 0.044s)
275 KB/s (13672 bytes in 0.048s)
2788 KB/s (657704 bytes in 0.230s)
Copying kernel module...
819 KB/s (34473 bytes in 0.041s)
17 KB/s (767 bytes in 0.042s)
291 KB/s (13592 bytes in 0.045s)
Kernel version is 3.4.0-perf-g1cb2b9a-01879-gd0acb0a
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: patched to 0xCFADE050
__aeabi_unwind_cpp_pr1: match
kallsyms_lookup_name: not found
printk: not found
mem_text_write_kernel_word: not found
__aeabi_unwind_cpp_pr0: match
successfully patched
=============================================
Loading geohot's towelroot (modified by zxz0O0)
=============================================
281 KB/s (13592 bytes in 0.047s)
2660 KB/s (197320 bytes in 0.072s)
=============================================
Waiting for towelroot to exploit...
towelzxperia by zxz0O0 (EasyRootTool Version)
libexploit by geohot
libzxploit.so created
doing the magic
creating vm (loljavasucks)
insmod: init_module '/data/local/tmp/wp_mod.ko' failed (Exec format error)
mount: Operation not permitted
/system/bin/chcon: Could not label /system/xbin/su with u:object_r:system_file:s0: No such file or directory
chcon: Could not label /system/xbin/su with u:object_r:system_file:s0: No such file or directory
sh: /system/xbin/su: not found
cleaning up
done
Checking if device is rooted...
Error: device not rooted
yanjingtao said:
Hello,
I'm using EasyRootTool v11.zip from http://forum.xda-developers.com/showthread.php?t=2784900. When I run it, it shows that:
Code:
=============================================
Getting device variables
=============================================
Device model is L50u
Firmware is 17.1.1.F.0.39
=============================================
Sending files
=============================================
36 KB/s (1585 bytes in 0.042s)
25 KB/s (1133 bytes in 0.042s)
207 KB/s (9496 bytes in 0.044s)
275 KB/s (13672 bytes in 0.048s)
2788 KB/s (657704 bytes in 0.230s)
Copying kernel module...
819 KB/s (34473 bytes in 0.041s)
17 KB/s (767 bytes in 0.042s)
291 KB/s (13592 bytes in 0.045s)
Kernel version is 3.4.0-perf-g1cb2b9a-01879-gd0acb0a
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: patched to 0xCFADE050
__aeabi_unwind_cpp_pr1: match
kallsyms_lookup_name: not found
printk: not found
mem_text_write_kernel_word: not found
__aeabi_unwind_cpp_pr0: match
successfully patched
=============================================
Loading geohot's towelroot (modified by zxz0O0)
=============================================
281 KB/s (13592 bytes in 0.047s)
2660 KB/s (197320 bytes in 0.072s)
=============================================
Waiting for towelroot to exploit...
towelzxperia by zxz0O0 (EasyRootTool Version)
libexploit by geohot
libzxploit.so created
doing the magic
creating vm (loljavasucks)
insmod: init_module '/data/local/tmp/wp_mod.ko' failed (Exec format error)
mount: Operation not permitted
/system/bin/chcon: Could not label /system/xbin/su with u:object_r:system_file:s0: No such file or directory
chcon: Could not label /system/xbin/su with u:object_r:system_file:s0: No such file or directory
sh: /system/xbin/su: not found
cleaning up
done
Checking if device is rooted...
Error: device not rooted
Click to expand...
Click to collapse
You cannot use EasyRootTool for the newest ROM's - you might be able to use How To Root the newest firmware (.314)
Btw. .39 is for the Chinese Z2?
Well I rooted my Z2. 314 firmware last night and it worked. I used ERT V11. It took 2 attempts mind you, cause I wasn't watching what I was doing the 1st time lol ?
Sent from my D6503 using xda premium from "Somewhere, but not here..."
harfot said:
You cannot use EasyRootTool for the newest ROM's - you might be able to use How To Root the newest firmware (.314)
Btw. .39 is for the Chinese Z2?
Click to expand...
Click to collapse
Thanks, is this tool unlocked the bootloader? I don't want to unlocked the bootloader.
.39 is Chinese Z2 LTE version's last fireware.
Z2 in China has three version, 3G/TD-LTE/LTE

[Q] Missing recovery

Hello guys!
Simply I screwed up. I Installed existenz rom and simply forgot to install dual recovery before rebooting.... Of course system doesn't show up, but i flashed stock rom from ftf file. My problem is simply - how to again install double recovery? I tried this: http://teamw.in/project/twrp2/232
Of Course i tried installing by NUT installer but without any success.
Any thoughts about this?
Thx
PS. My Log from nut installer
==============================================
= =
= 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 D6503
Firmware is 17.1.2.A.0.314
=============================================
Step2 : Sending the recovery files.
=============================================
mkdir failed for /data/local/tmp/recovery, File exists
7 KB/s (29 bytes in 0.004s)
1923 KB/s (15757 bytes in 0.008s)
97 KB/s (501 bytes in 0.005s)
1445 KB/s (11842 bytes in 0.008s)
2522 KB/s (56834 bytes in 0.022s)
752 KB/s (3082 bytes in 0.004s)
93 KB/s (385 bytes in 0.004s)
3869 KB/s (657704 bytes in 0.166s)
4332 KB/s (3158546 bytes in 0.712s)
5432 KB/s (2319570 bytes in 0.417s)
4382 KB/s (1875988 bytes in 0.418s)
2170 KB/s (8889 bytes in 0.004s)
=============================================
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
=============================================
307 KB/s (1572 bytes in 0.005s)
1474 KB/s (13592 bytes in 0.009s)
cannot stat 'easyroottool\libexploit.so': No such file or directory
1854 KB/s (9496 bytes in 0.005s)
1483 KB/s (13672 bytes in 0.009s)
Copying kernel module...
2244 KB/s (34473 bytes in 0.015s)
186 KB/s (765 bytes in 0.004s)
1327 KB/s (13592 bytes in 0.010s)
Kernel version is 3.4.0-perf-g35f9635
Version does not match 3.4.0-perf-ge4322cd, needs patching...
1+0 records in
0+1 records out
19 bytes transferred in 0.001 secs (19000 bytes/sec)
Kernel module patched.
modulecrcpatch (by zxz0O0)
module_layout: patched to 0xCFADE050
__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
doing the magic
error: could not open libzxploit/system/bin/sh: /system/xbin/busybox: not found
=============================================
Installation finished. Enjoy the recoveries!
=============================================
Aby kontynuować, naciśnij dowolny klawisz . . .
PS2. I'm already at 17.1.2.A.0.314 rom (4.4.2) without root
Is your bootloader locked or unlocked?
The TWRP you were posting works only with FOTAKernel-Partition, which you can only use with modified LP kernel...
Problem solved, just rooted with exploit then i installed nut dual recovery.

Categories

Resources