[Q] A Problem when root using Easy Root Tool - Xperia Z2 Q&A, Help & Troubleshooting

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

Related

[Q] From cdimage-touch to ubuntu-system to update directly using the phone

Hey all!
Yesterday my new Nexus 4 arrived and I flashed Ubuntu Touch on it following the official instruciotns (on wiki.ubuntu.com/Touch/Install) using
Code:
phablet-flash cdimage-touch -b
It worked like a charm. But today I figured out that I should use "ubuntu-system" instead, because I would be able to update directly out of Ubuntu Touch using my phone.
Unfortunately this didn't work.
At first I tried to use this command
Code:
phablet-flash ubuntu-system -b
but this didn't work.
Code:
[email protected]:~$ sudo phablet-flash ubuntu-system -b
usage: phablet-flash [-h] ...
phablet-flash: error: unrecognized arguments: -b
Google couldn't help me so I tried it without the
Code:
-b
At the beginning everything looked good and basically it was done
Code:
INFO:phablet-flash:Installation complete
but than it started to use the recovery!
Here is the full Terminal output:
Code:
[email protected]:~$ sudo phablet-flash ubuntu-system
INFO:phablet-flash:Device detected as mako
INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): system-image.ubuntu.com
INFO:phablet-flash:Download directory set to /home/max/Downloads/phablet-flash/imageupdates
INFO:phablet-flash:Downloading https://system-image.ubuntu.com/gpg/image-master.tar.xz to /tmp/tmpayL2tR/image-master.tar.xz
--2013-09-10 21:06:14-- https://system-image.ubuntu.com/gpg/image-master.tar.xz
Resolving system-image.ubuntu.com (system-image.ubuntu.com)... 91.189.88.35
Connecting to system-image.ubuntu.com (system-image.ubuntu.com)|91.189.88.35|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 884 [application/x-tar]
Saving to: `/tmp/tmpayL2tR/image-master.tar.xz'
100%[======================================>] 884 --.-K/s in 0s
2013-09-10 21:06:14 (33,1 MB/s) - `/tmp/tmpayL2tR/image-master.tar.xz' saved [884/884]
INFO:phablet-flash:Downloading https://system-image.ubuntu.com/gpg/image-signing.tar.xz to /tmp/tmpayL2tR/image-signing.tar.xz
--2013-09-10 21:06:14-- https://system-image.ubuntu.com/gpg/image-signing.tar.xz
Resolving system-image.ubuntu.com (system-image.ubuntu.com)... 91.189.88.35
Connecting to system-image.ubuntu.com (system-image.ubuntu.com)|91.189.88.35|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 904 [application/x-tar]
Saving to: `/tmp/tmpayL2tR/image-signing.tar.xz'
100%[======================================>] 904 --.-K/s in 0s
2013-09-10 21:06:15 (34,5 MB/s) - `/tmp/tmpayL2tR/image-signing.tar.xz' saved [904/904]
INFO:phablet-flash:Downloading https://system-image.ubuntu.com/daily/ubuntu/ubuntu-20130905.1.full.tar.xz.asc to /home/max/Downloads/phablet-flash/imageupdates/daily/ubuntu/ubuntu-20130905.1.full.tar.xz.asc
--2013-09-10 21:06:15-- https://system-image.ubuntu.com/daily/ubuntu/ubuntu-20130905.1.full.tar.xz.asc
Resolving system-image.ubuntu.com (system-image.ubuntu.com)... 91.189.88.35
Connecting to system-image.ubuntu.com (system-image.ubuntu.com)|91.189.88.35|:443... connected.
HTTP request sent, awaiting response... 416 Requested Range Not Satisfiable
The file is already fully retrieved; nothing to do.
INFO:phablet-flash:Downloading https://system-image.ubuntu.com/daily/mako/mako-20130905.1.full.tar.xz.asc to /home/max/Downloads/phablet-flash/imageupdates/daily/mako/mako-20130905.1.full.tar.xz.asc
--2013-09-10 21:06:15-- https://system-image.ubuntu.com/daily/mako/mako-20130905.1.full.tar.xz.asc
Resolving system-image.ubuntu.com (system-image.ubuntu.com)... 91.189.88.35
Connecting to system-image.ubuntu.com (system-image.ubuntu.com)|91.189.88.35|:443... connected.
HTTP request sent, awaiting response... 416 Requested Range Not Satisfiable
The file is already fully retrieved; nothing to do.
INFO:phablet-flash:Downloading https://system-image.ubuntu.com/daily/mako/version-4.tar.xz.asc to /home/max/Downloads/phablet-flash/imageupdates/daily/mako/version-4.tar.xz.asc
--2013-09-10 21:06:15-- https://system-image.ubuntu.com/daily/mako/version-4.tar.xz.asc
Resolving system-image.ubuntu.com (system-image.ubuntu.com)... 91.189.88.35
Connecting to system-image.ubuntu.com (system-image.ubuntu.com)|91.189.88.35|:443... connected.
HTTP request sent, awaiting response... 416 Requested Range Not Satisfiable
The file is already fully retrieved; nothing to do.
INFO:phablet-flash:Downloading https://system-image.ubuntu.com/gpg/image-master.tar.xz.asc to /tmp/tmpayL2tR/image-master.tar.xz.asc
--2013-09-10 21:06:15-- https://system-image.ubuntu.com/gpg/image-master.tar.xz.asc
Resolving system-image.ubuntu.com (system-image.ubuntu.com)... 91.189.88.35
Connecting to system-image.ubuntu.com (system-image.ubuntu.com)|91.189.88.35|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 836 [text/plain]
Saving to: `/tmp/tmpayL2tR/image-master.tar.xz.asc'
100%[======================================>] 836 --.-K/s in 0s
2013-09-10 21:06:15 (28,0 MB/s) - `/tmp/tmpayL2tR/image-master.tar.xz.asc' saved [836/836]
INFO:phablet-flash:Downloading https://system-image.ubuntu.com/gpg/image-signing.tar.xz.asc to /tmp/tmpayL2tR/image-signing.tar.xz.asc
--2013-09-10 21:06:15-- https://system-image.ubuntu.com/gpg/image-signing.tar.xz.asc
Resolving system-image.ubuntu.com (system-image.ubuntu.com)... 91.189.88.35
Connecting to system-image.ubuntu.com (system-image.ubuntu.com)|91.189.88.35|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 490 [text/plain]
Saving to: `/tmp/tmpayL2tR/image-signing.tar.xz.asc'
100%[======================================>] 490 --.-K/s in 0s
2013-09-10 21:06:16 (16,6 MB/s) - `/tmp/tmpayL2tR/image-signing.tar.xz.asc' saved [490/490]
INFO:phablet-flash:Saving backup to /tmp/tmpt8NMk2
INFO:phablet-flash:Pulling /tmp/backup.tar.gz to /tmp/tmpt8NMk2
3702 KB/s (9366352 bytes in 2.470s)
INFO:phablet-flash:Restarting device... wait
INFO:phablet-flash:Restarting device... wait complete
INFO:phablet-flash:Clearing /data and /cache
INFO:phablet-flash:Pushing /home/max/Downloads/phablet-flash/imageupdates/daily/ubuntu/ubuntu-20130905.1.full.tar.xz to /cache/recovery/
5606 KB/s (285224820 bytes in 49.677s)
INFO:phablet-flash:Pushing /home/max/Downloads/phablet-flash/imageupdates/daily/ubuntu/ubuntu-20130905.1.full.tar.xz.asc to /cache/recovery/
12 KB/s (490 bytes in 0.039s)
INFO:phablet-flash:Pushing /home/max/Downloads/phablet-flash/imageupdates/daily/mako/mako-20130905.1.full.tar.xz to /cache/recovery/
5692 KB/s (37087976 bytes in 6.362s)
INFO:phablet-flash:Pushing /home/max/Downloads/phablet-flash/imageupdates/daily/mako/mako-20130905.1.full.tar.xz.asc to /cache/recovery/
11 KB/s (490 bytes in 0.040s)
INFO:phablet-flash:Decompressing partitions/recovery.img from /home/max/Downloads/phablet-flash/imageupdates/daily/mako/mako-20130905.1.full.tar.xz
INFO:phablet-flash:Pushing /home/max/Downloads/phablet-flash/imageupdates/daily/mako/version-4.tar.xz to /cache/recovery/
7 KB/s (288 bytes in 0.039s)
INFO:phablet-flash:Pushing /home/max/Downloads/phablet-flash/imageupdates/daily/mako/version-4.tar.xz.asc to /cache/recovery/
11 KB/s (490 bytes in 0.040s)
INFO:phablet-flash:Pushing /tmp/tmpayL2tR/image-master.tar.xz to /cache/recovery/
21 KB/s (884 bytes in 0.040s)
INFO:phablet-flash:Pushing /tmp/tmpayL2tR/image-master.tar.xz.asc to /cache/recovery/
20 KB/s (836 bytes in 0.040s)
INFO:phablet-flash:Pushing /tmp/tmpayL2tR/image-signing.tar.xz to /cache/recovery/
21 KB/s (904 bytes in 0.040s)
INFO:phablet-flash:Pushing /tmp/tmpayL2tR/image-signing.tar.xz.asc to /cache/recovery/
11 KB/s (490 bytes in 0.040s)
INFO:phablet-flash:Pushing /tmp/tmpBaPjCx to /cache/recovery/ubuntu_command
8 KB/s (353 bytes in 0.039s)
INFO:phablet-flash:Restarting device... wait
INFO:phablet-flash:Restarting device... wait complete
INFO:phablet-flash:Flashing recovery to /tmp/tmpME9mUn/partitions/recovery.img
< waiting for device >
sending 'recovery' (8604 KB)...
OKAY [ 0.540s]
writing 'recovery'...
OKAY [ 0.446s]
finished. total time: 0.986s
INFO:phablet-flash:Booting /tmp/tmpME9mUn/partitions/recovery.img
downloading 'boot.img'...
OKAY [ 0.546s]
booting...
OKAY [ 0.025s]
finished. total time: 0.572s
INFO:phablet-flash:Waiting for install to finish on device. Please do not unplug device until phablet-flash finishes.
INFO:phablet-flash:Installation complete
WARNING:phablet-flash:Restoring from backup
INFO:phablet-flash:Pushing /tmp/tmpt8NMk2 to /tmp/backup.tar.gz
3995 KB/s (9366352 bytes in 2.289s)
INFO:phablet-flash:Restoring from /tmp/tmpt8NMk2
INFO:phablet-flash:Restarting device... wait
INFO:phablet-flash:Restarting device... wait complete
Removing directory /tmp/tmpME9mUn
Removing directory /tmp/tmpayL2tR
So where is the problem? How do I switch over to the ubuntu-system build?
Looking forward to your help!
Greetings
Max
edit:
I although checked my current phablet-tools version but it's up to date
Code:
[email protected]:~$ dpkg -s phablet-tools | grep Version
Version: 1.0+13.10.20130909.2-0ubuntu1
edit2:
Found a newer version and updated but the problem is still the same
Code:
[email protected]:~$ dpkg -s phablet-tools | grep Version
Version: 1.0+13.10.20130910.4-0ubuntu1
Open the terminal on your device and run
sudo apt-get update && sudo apt-get dist-upgrade
No need really to do full image updates.
Sent from my LG-LS970 using xda app-developers app
What is wrong with using the recovery? To flash the new image it needs CWM. Just wait and let it reboot and you'll have the ubuntu-system image on your device.
To98 said:
What is wrong with using the recovery? ...
Click to expand...
Click to collapse
I think now I get it. He's flashing the new image and afterwards he's using the personal data (settings, networks etc.) from the recovery? I thought that if he's using the recovery, it would mean that he would undo all changes and bring me back to the initial stage.
blmvxer said:
Open the terminal on your device and run
sudo apt-get update && sudo apt-get dist-upgrade
Click to expand...
Click to collapse
I could try this to be sure.
Is there a way to find out that I now have the ubuntu-system build? Or do I have to wait for an update and if the update process is working directly from the phone, than it's the ubuntu-system build?
Greetings
Max
edit:
Code:
sudo apt-get dist-upgrade
Code:
W: Not using locking for read only lock file /var/lib/dpkg/lock
E: Unable to write to /var/cache/apt/
E: The package lists or status file could not be parsed or opened.
edit 2:
Okay, I'm confused here but I can install updates from the phone now. So I guess it's working
Thank you guys!
Even if you have solved it already you can see if you are using the system-image with copying one file into /etc.
sudo cp /home/phablet/{filename} /etc/
Click to expand...
Click to collapse
If it doesn't work everything is OK.

[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.

[Q] Z2 running .690 firmware won't root with community root kit v01

Hi guys,
So I have an Xperia z2 (android 5.0.2) running on firmware 23.1.A.0.690 (downgraded from 23.1.A.0.726)
I'm attempting to my root my .690 fw using community rootkit v01, however it is with no avail, despite having the correct adb drivers installed, USB debugging & unknown sources enabled & ADK installed. Here is what rootkit keeps telling me...
# Semi-Automated script written by Sacha.
# With exploit method developed by GranPC.
# I assume you have adb installed, etc etc..
# I also assume you are using a Z2 on .69 firmware
# with contributions from DooMLoRD, norti and RyokoN
Installing exploit app.
3616 KB/s (348942 bytes in 0.094s)
pkg: /data/local/tmp/exploit.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Copying small files...
4538 KB/s (1109128 bytes in 0.238s)
3378 KB/s (121260 bytes in 0.035s)
3336 KB/s (13672 bytes in 0.004s)
93 KB/s (569 bytes in 0.005s)
1306 KB/s (9496 bytes in 0.007s)
401 KB/s (2050 bytes in 0.004s)
18 KB/s (97 bytes in 0.005s)
1478 KB/s (13672 bytes in 0.009s)
82 KB/s (505 bytes in 0.005s)
66 KB/s (404 bytes in 0.005s)
123 KB/s (764 bytes in 0.006s)
2906 KB/s (83364 bytes in 0.028s)
991 KB/s (3089 bytes in 0.003s)
122 KB/s (629 bytes in 0.005s)
5 KB/s (33 bytes in 0.006s)
5089 KB/s (2326385 bytes in 0.446s)
Copying BIG file... please have patience, this might take a while...
6223 KB/s (63931904 bytes in 10.031s)
Correcting permissions...
Starting Part 1
--- DooMing device: PART 1!
--- Correcting permissions
--- Running services
/data/local/tmp/vdcCreate[5]: vdc: not found
ln: /data/app-lib/ServiceMenu/libservicemenu.so: No such file or directory
ln: /data/local/tmp/vlib: Permission denied
Starting: Intent { act=android.intent.action.MAIN cmp=com.sonyericsson.android.s
ervicemenu/.ServiceMainMenu }
Test VDC #1:
Failure
PART 1 complete!
Complete!
----------------[ ATTENTION ]----------------
Please 'crash' the Service Menu app to complete.
For example: Service Info - Configuration.
The screen will probably blink when it has worked.
Press any key to continue . . .
Click to expand...
Click to collapse
I cannot 'crash' the service menu. When I hit 'configuration', the screen does not blink, despite restarting the entire process. I've tried this probably 20 times.
Any help would be greatly appreciated.
if i'm not mistaken the rootkit v01 is for Kitkat firmwares not for Lollipop, to root Lollipop you could try this http://forum.xda-developers.com/xperia-z2/general/root-t3108230

Unlocking Sony Xperia M4 Aqua (Android) bootloader with Debian?

i found these tools in Synaptic:
fastboot
ddms (sdk)
&
adb
Can i use these to unlock the bootloader instead of downloading a bunch of stuff from websites? i found the device using fastboot and the unlock code from sony but thats about as far as i got.
Sure, you also need the linux version of flashtool, which you can get from the site (no need to install), and you are good to go. :thumbup:
Sent from my E2303 using XDA Free mobile app
would anyone mind guiding me through the steps?
xinjian said:
would anyone mind guiding me through the steps?
Click to expand...
Click to collapse
There is a linux version of Flashtool and its an sh script so the command would be
sudo bash LocationOfFlashtool/Flashtool
Click to expand...
Click to collapse
And then when the bootloader is unlocked and you want to flash recovery
sudo fastboot flash recovery LocationOfRecovery/recovery.img
Click to expand...
Click to collapse
xinjian said:
i found these tools in Synaptic:
fastboot
ddms (sdk)
&
adb
Can i use these to unlock the bootloader instead of downloading a bunch of stuff from websites? i found the device using fastboot and the unlock code from sony but thats about as far as i got.
Click to expand...
Click to collapse
I just rooted my phone under Gentoo using adb commands from install.bat file which I downloaded from here: http://www.mediafire.com/download/awrsi78ddjl0x2r/rootkitXperia_E23xx_26.1.X.3.xxx.zip
Just unpack this zip, change directory to where you unzipped it and run:
Code:
adb push files/getroot /data/local/tmp/
adb push files/su /data/local/tmp/
adb push files/supolicy /data/local/tmp/
adb push files/libsupol.so /data/local/tmp/
adb push files/Superuser.apk /data/local/tmp/
adb push files/busybox /data/local/tmp/
adb push files/99SuperSUDaemon /data/local/tmp/
adb push files/install-recovery.sh /data/local/tmp/
adb push files/install_tool.sh /data/local/tmp/
adb shell "chmod 0755 /data/local/tmp/getroot"
adb shell "chmod 0755 /data/local/tmp/busybox"
adb shell "chmod 0755 /data/local/tmp/install_tool.sh"
adb shell "/data/local/tmp/getroot /data/local/tmp/install_tool.sh"
After last command you should get something like this:
Code:
Patching address 0xffffffc00112a9d0
Start map/unmap thread.
Start write thread.
Spraying kernel heap.
100 200 300 400 500 600 700 800 900 1000
Start read thread.
Done.
Patching address 0xffffffc058b34008
Start map/unmap thread.
Start write thread.
Spraying kernel heap.
100 200 300 400 500 600 700 800 900 1000
Start read thread.
10000
Done.
2047+1 records in
2047+1 records out
1048328 bytes transferred in 0.057 secs (18391719 bytes/sec)
203+1 records in
203+1 records out
104368 bytes transferred in 0.009 secs (11596444 bytes/sec)
203+1 records in
203+1 records out
104368 bytes transferred in 0.004 secs (26092000 bytes/sec)
203+1 records in
203+1 records out
104368 bytes transferred in 0.004 secs (26092000 bytes/sec)
203+1 records in
203+1 records out
104368 bytes transferred in 0.004 secs (26092000 bytes/sec)
58+1 records in
58+1 records out
30168 bytes transferred in 0.005 secs (6033600 bytes/sec)
613+1 records in
613+1 records out
314232 bytes transferred in 0.016 secs (19639500 bytes/sec)
11948+1 records in
11948+1 records out
6117378 bytes transferred in 0.189 secs (32367079 bytes/sec)
1+1 records in
1+1 records out
629 bytes transferred in 0.003 secs (209666 bytes/sec)
0+1 records in
0+1 records out
55 bytes transferred in 0.001 secs (55000 bytes/sec)
Actually you don't need to have Flashtool to unlock the bootloader since the device is officially supported by Sony
Just follow the instructions in its webpage

Read-only filesystem - Tired everything - SGP312

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.

Categories

Resources