[DEVDB][TWRP][PhilZ Touch] XZDualRecovery 2.8.26 RELEASE

Sebi673

Senior Member
Oct 11, 2013
381
139
0
29
Bucharest
TWRP won't mount system partition on the 5.1 update for xperia Z. Still I remembered having the same issue when 5.0 appeared and @McBane87 worked out a nice workaround to mount twrp system partition.
You'll have to go in recovery (TWRP) and pop these lines into the Terminal Emulator. (below) System Partition should be mounted (and working).

mount -o ro /system
mount -o rw,remount /system
umount /system
mount /system
 

ibis69

Senior Member
Mar 1, 2010
145
94
0
LYON
TWRP won't mount system partition on the 5.1 update for xperia Z. Still I remembered having the same issue when 5.0 appeared and @McBane87 worked out a nice workaround to mount twrp system partition.
You'll have to go in recovery (TWRP) and pop these lines into the Terminal Emulator. (below) System Partition should be mounted (and working).

mount -o ro /system
mount -o rw,remount /system
umount /system
mount /system
+1, Same issue on my Tablet Z with 5.1.1, mount -rw /system in terminal as workaround
 
Last edited:
  • Like
Reactions: jeebspawnshop

McBane87

Senior Member
Jun 29, 2012
292
258
0
TWRP won't mount system partition on the 5.1 update for xperia Z. Still I remembered having the same issue when 5.0 appeared and @McBane87 worked out a nice workaround to mount twrp system partition.
You'll have to go in recovery (TWRP) and pop these lines into the Terminal Emulator. (below) System Partition should be mounted (and working).

mount -o ro /system
mount -o rw,remount /system
umount /system
mount /system
But remember that this was causing other problems with corrupted system partition if you installed a hole image. Better find out why system partition isn't able to mount rw.
 
  • Like
Reactions: Sebi673

[NUT]

Senior Member
TWRP won't mount system partition on the 5.1 update for xperia Z. Still I remembered having the same issue when 5.0 appeared and @McBane87 worked out a nice workaround to mount twrp system partition.
You'll have to go in recovery (TWRP) and pop these lines into the Terminal Emulator. (below) System Partition should be mounted (and working).

mount -o ro /system
mount -o rw,remount /system
umount /system
mount /system
+1, Same issue on my Tablet Z with 5.1.1, mount -rw /system in terminal as workaround
Are you both 100% sure to be using 2.8.21?
 

[NUT]

Senior Member
It looks like there is an issue with the 'kernel builder' tool. Ive tried multiple times uploading boot.img for CM-12.1-20150906-NIGHTLY-Z3C and I get "Something went wrong uploading the file, please start over and try again."
It's a freaking mystery, for some reason a temporary storage location keeps disappearing without any obvious reason... I restored it, it should now be working again.
 
  • Like
Reactions: Bird40

Sebi673

Senior Member
Oct 11, 2013
381
139
0
29
Bucharest
Are you both 100% sure to be using 2.8.21?
It was 1 am so i downloaded a PRF someone else made (it says it has 2.8.21). I'm gonna make my own PRF with the latest xzdr and see then :D Anyway it's not a huge issue as long as it's usable.

Source of prf - http://forum.xda-developers.com/xperia-z/general/rom-pre-rooted-supersu-xposed-framework-t3195782

---------- Post added at 10:53 AM ---------- Previous post was at 10:48 AM ----------

But remember that this was causing other problems with corrupted system partition if you installed a hole image. Better find out why system partition isn't able to mount rw.
Oh... I remember now.... Restoring a backup or flashing another zip was a *****. Is there something I can do to work around this? Or even better, what can I do to help? :D
 

sigprof

Senior Member
Jan 5, 2012
180
234
0
The Xperia ZR C5503 ROM 10.7.A.0.222 uses two separate mounts for odex files — /system/odex.app and /system/odex.priv-app (there are two separate squashfs images for them, and framework odex files are in /system/framework/arm and no longer stored in a compressed squashfs image). The previous ROM release (10.6.A.0.454) had just a single mount for odex files (/system/odex).

Unmounting those new mounts before starting the recovery fixes the /system mount problem in TWRP:
View attachment dualrecovery.sh.diff
Code:
--- dualrecovery.sh.orig
+++ dualrecovery.sh
@@ -305,6 +305,8 @@
 		export PATH="/sbin"
 
 		EXECL busybox umount /system/odex
+		EXECL busybox umount /system/odex.app
+		EXECL busybox umount /system/odex.priv-app
 		EXECL busybox umount /system	# System
 
 		# AS OF HERE NO MORE BUSYBOX SYMLINKS IN $PATH!!!!
Mounting /system in TWRP works for me now; testing backup/restore will take some minutes.

Update: Tested backup/restore in TWRP after applying this fix; as expected, it works.
 
Last edited:

McBane87

Senior Member
Jun 29, 2012
292
258
0
It was 1 am so i downloaded a PRF someone else made (it says it has 2.8.21). I'm gonna make my own PRF with the latest xzdr and see then :D Anyway it's not a huge issue as long as it's usable.

Source of prf - http://forum.xda-developers.com/xperia-z/general/rom-pre-rooted-supersu-xposed-framework-t3195782

---------- Post added at 10:53 AM ---------- Previous post was at 10:48 AM ----------



Oh... I remember now.... Restoring a backup or flashing another zip was a *****. Is there something I can do to work around this? Or even better, what can I do to help? :D
Well, first of all. Just install the newest XZDR (flashable) from NUT's Website (see OP). You should be able to install it over the existing one. If this isn't resolving the issue, then please post the output of "mount" while you are normally running android.

EDIT:
Ok, thanks to @sigprof. I think he found the problem.
 
Last edited:

Sebi673

Senior Member
Oct 11, 2013
381
139
0
29
Bucharest
Well, first of all. Just install the newest XZDR (flashable) from NUT's Website (see OP). You should be able to install it over the existing one. If this isn't resolving the issue, then please post the output of "mount" while you are normally running android.

EDIT:
Ok, thanks to @sigprof. I think he found the problem.
I redid the installation, and same output. twrp log in attach. Also the logcat with "mount" filter. Hope it helps ;)
 

Attachments

luxman_1

Senior Member
Jan 28, 2015
79
3
0
Brussels
Bootloop Xperia z Lollipop (logo sony)

HELP !!!!!

I made an installation "XZDualRecovery 2.8.21" on my xperia z with lollipop (bootloader locked).

The script has restarted the device. and it will not start (bootloop on sony logo).
Can not start in recovery mode

Please help me!!!!
 

Attachments

v7

Retired Forum Moderator / Recognized Contributor
May 17, 2014
7,959
8,407
263
Arkham
HELP !!!!!

I made an installation "XZDualRecovery 2.8.21" on my xperia z with lollipop (bootloader locked).

The script has restarted the device. and it will not start (bootloop on sony logo).
Can not start in recovery mode

Please help me!!!!
Flash Firmware FTF from Flashtool.

Tapped from my ①+②=❸ ;)
 

luxman_1

Senior Member
Jan 28, 2015
79
3
0
Brussels
Flash Firmware FTF from Flashtool.

Tapped from my ①+②=❸ ;)
I tried but it does nothing. here is the log:
08/024/2015 16:24:45 - INFO - Flashtool Version 0.9.19.0 built on 29-07-2015 12:00:00
08/024/2015 16:24:45 - INFO - Executing search strategies to find proxy selector
08/024/2015 16:24:46 - INFO - No proxy found for IE. Trying next one
08/024/2015 16:24:46 - INFO - Strategy firefox failed trying next one : No Firefox installation found
08/024/2015 16:24:46 - INFO - No proxy found for java. Trying next one
08/024/2015 16:24:46 - INFO - Syncing devices from github
08/024/2015 16:24:46 - INFO - Scanning devices folder for changes.
08/024/2015 16:24:53 - INFO - Pulling changes from github.
08/024/2015 16:24:53 - INFO - Devices sync finished.
08/024/2015 16:24:57 - INFO - Device disconnected
08/025/2015 16:25:29 - INFO - Selected Bundle for Sony Xperia Z (C6603). FW release : 10.6.A.0.454. Customization : Customized_FR
08/025/2015 16:25:29 - INFO - Preparing files for flashing
08/025/2015 16:25:50 - INFO - Please connect your device into flashmode.
08/025/2015 16:25:56 - INFO - Device connected in flash mode
08/025/2015 16:25:56 - INFO - Opening device for R/W
08/025/2015 16:25:56 - INFO - Reading device information
08/025/2015 16:25:56 - INFO - Phone ready for flashmode operations.
08/025/2015 16:25:56 - INFO - Opening TA partition 2
08/025/2015 16:25:56 - INFO - Current device : C6603 - - 1270- - 1269- _10.6.A.0.454 - GLOBAL-LTE_10.6.A.0.454
08/025/2015 16:25:56 - INFO - Closing TA partition
08/025/2015 16:25:56 - INFO - Start Flashing
08/025/2015 16:25:56 - INFO - Processing loader.sin
08/025/2015 16:25:56 - INFO - Checking header
08/025/2015 16:25:56 - INFO - Flashing data
08/025/2015 16:25:57 - INFO - Loader : S1_Root_5ca3 - Version : APQ8064_39 / Boot version : S1_Boot_Lagan_1.1_10 / Bootloader status : ROOTABLE
08/025/2015 16:25:57 - INFO - Transfer buffer size : 262144
08/025/2015 16:25:57 - INFO - Parsing boot delivery
08/025/2015 16:25:57 - INFO - You must have the according fsc script to flash this device.
08/025/2015 16:25:57 - INFO - Flashing finished.
08/025/2015 16:25:57 - INFO - Please unplug and start your phone
08/025/2015 16:25:57 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings:crying:
 

toudas

Member
Jan 14, 2013
33
7
0
Last edited:

theduke7

Senior Member
Apr 8, 2011
1,604
1,109
143
Cairo
The Xperia ZR C5503 ROM 10.7.A.0.222 uses two separate mounts for odex files — /system/odex.app and /system/odex.priv-app (there are two separate squashfs images for them, and framework odex files are in /system/framework/arm and no longer stored in a compressed squashfs image). The previous ROM release (10.6.A.0.454) had just a single mount for odex files (/system/odex).

Unmounting those new mounts before starting the recovery fixes the /system mount problem in TWRP:
View attachment 3466538
Code:
--- dualrecovery.sh.orig
+++ dualrecovery.sh
@@ -305,6 +305,8 @@
 		export PATH="/sbin"
 
 		EXECL busybox umount /system/odex
+		EXECL busybox umount /system/odex.app
+		EXECL busybox umount /system/odex.priv-app
 		EXECL busybox umount /system	# System
 
 		# AS OF HERE NO MORE BUSYBOX SYMLINKS IN $PATH!!!!
Mounting /system in TWRP works for me now; testing backup/restore will take some minutes.

Update: Tested backup/restore in TWRP after applying this fix; as expected, it works.
so, adding these line to the existing 2 lines on dualrecovery.sh (in the installable version) will fix the mount issue?