[T/V/TL/TX][TWRP][PhilZ Touch][CWM] XZDualRecovery Q&A

Search This thread

[NUT]

Senior Member
-=[XZDualRecovery]=-
PhilZ Touch & CWM & TWRP
*** For Locked and Unlocked BOOTLOADERS! ***


Welcome to the Xperia T/V/TX/TL Questions & Answers thread!

I proudly present you the first and only DUAL RECOVERY for locked boot loaders on our lovely Xperia phones! :cool:

If you have an unlocked bootloader and chose to keep the STOCK Sony kernel, you can also use this MOD.

Currently supported XPERIA models:
These are also links to the device specific Q&A threads.
Xperia Z: SO-02E, C6602, C6603, C6606, C6616
Xperia ZL: C6502, C6503, C6506
Xperia Tablet Z: SO-03E, SGP311, SGP312, SGP321, SGP351
Xperia Z Ultra: C6802, C6806, C6833, C6843
Xperia Z1: C6902, C6903, C6906, C6943, C6916
Xperia Z1 Compact: D5502, D5503, D5506
Xperia Z2: D6502, D6503, D6506, D6543, D6563
Xperia Tablet Z2: SGP511, SGP512, SGP521, SGP551, SGP561
Xperia ZR: C5602, C5603, C5606
Xperia T, TX, TL and V: LT30p, LT29, LT30at, LT25i
Xperia S: LT26i
Xperia SP: C5302, C5303
Xperia T2 Ultra: D5303, D5322
Xperia Z3: D6603, D6633, D6643, D6653, D6616
Xperia Z3 Compact: D5803, D5833
Xperia Tablet Z3 Compact: SGP621, SGP641, SGP651

To follow development, be sure to check the DevDB thread!
 
Last edited:

[NUT]

Senior Member
Special Thanks:
  • @DooMLoRD for all his excellent work on our much loved Sony phones!
  • The Team Win developers for TWRP
  • The ClockWorkMod developers for CWM
  • @alexocean for his awesome job testing almost all FW releases and the discovery of SuperSU causing problems for the installation of this recovery!
  • @RoberM for testing
  • @surdu_petru for testing and handy pointers
  • @Androxyde for allowing to use his linux and mac adb binaries.
  • @lancebukkake for finding the TWRP 'fix' to use exFAT formatted sdcards!
  • @delewer for the final fix for TWRP and its use of exFAT formatted sdcards
  • @DevShaft for some code help on the windows installer (the menu!)
  • @Androxyde again, but now for his bash code/script suggestions... oh boy this guy is a genius! :highfive:
  • @Tamirwig and @shoey63 for their excellent job at testing early BETA's (Xperia Z)
  • @gregbradley for his extensive testing on the Xperia Z1

Well, enjoy! :fingers-crossed:

The origins of this XZDualRecovery package are in the packages done by:
Krabappel2548, Cpasjuste and DooMLoRD
Thank you for your excellent work guys! :victory:
Your thanks (and donations) should (also) go out to them, they deserve it! :highfive:
 

[NUT]

Senior Member
Is it possible to flash this recovery by using and overwriting this one ?

Yes, it should work ok. Just check if /system/bin/chargemon exists. If it does you can use xzdualrecovery. I know @peetr_ used taimport as the replacement for chargemon, so until you remove the replacement taimport and rename the binary you will have 2 recovery packages installed and working :angel:
 

BreckZeBoulay

Senior Member
Oct 23, 2012
1,364
634
Boulay in Frankreich :D
I've got a weird issue with this recovery (tested with the three ones include) and not with the one of peetr_.
I've made my own rom, and i can't flash the zip, there's "error argument" when formating system.

my script :
Code:
ui_print("- Formating /system");
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/System", "0", "/system");
ui_print("- Copying to /system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p12", "/system");
package_extract_dir("system", "/system");

if i mod the script like this :
Code:
ui_print("- Formating /system");
format("ext4", "EMMC", "/dev/block/mmcblk0p12");
ui_print("- Copying to /system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p12", "/system");
package_extract_dir("system", "/system");
Formating is done but after system is not copy into /system, the flash is too fast (not a second), but there's no error ^^


May be it's not the right place to post this and may be it's a known issue....
 

[NUT]

Senior Member
I've got a weird issue with this recovery (tested with the three ones include) and not with the one of peetr_.
I've made my own rom, and i can't flash the zip, there's "error argument" when formating system.

my script :
Code:
ui_print("- Formating /system");
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/System", "0", "/system");
ui_print("- Copying to /system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p12", "/system");
package_extract_dir("system", "/system");

if i mod the script like this :
Code:
ui_print("- Formating /system");
format("ext4", "EMMC", "/dev/block/mmcblk0p12");
ui_print("- Copying to /system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p12", "/system");
package_extract_dir("system", "/system");
Formating is done but after system is not copy into /system, the flash is too fast (not a second), but there's no error ^^


May be it's not the right place to post this and may be it's a known issue....

Actually, it sounds like a problem I had a while back. Can you enter recovery (any will do) and then adb shell to the device to type:

Code:
busybox lsof

You'll get a list with files 'locking' anything anywhere. See if you can find a lock on '/system' or just simply '/bin'

Also, I ususally steer clear from the edify format and just do:

Code:
unmount("/system");
run_program("/sbin/make_ext4fs", "/dev/block/platform/msm_sdcc.1/by-name/System");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/System", "/system");

This has worked flawlessly on any device I have ever owned or built anything for, except when there are file locks still lurking of course :p
 
Last edited:
  • Like
Reactions: DodgeWooW

BreckZeBoulay

Senior Member
Oct 23, 2012
1,364
634
Boulay in Frankreich :D
Actually, it sounds like a problem I had a while back. Can you enter recovery (any will do) and then adb shell to the device to type:

Code:
busybox lsof

You'll get a list with files 'locking' anything anywhere. See if you can find a lock on '/system' or just simply '/bin'

I never try but I try to do this after children time ;)

Another question : there are two different versions :
XT-lockeddualrecovery2.7.101-BETA.flashable.zip (6.5MB)
and
XT-lockeddualrecovery2.7.102-BETA.installer.zip (8.23MB)

which one i prefer ?
 
Last edited:

BreckZeBoulay

Senior Member
Oct 23, 2012
1,364
634
Boulay in Frankreich :D
Actually, it sounds like a problem I had a while back. Can you enter recovery (any will do) and then adb shell to the device to type:

Code:
busybox lsof

You'll get a list with files 'locking' anything anywhere. See if you can find a lock on '/system' or just simply '/bin'
Code:
C:\Users\Pierre\Desktop\sdk\platform-tools>adb shell
~ # ←[6nbusybox lsof
busybox lsof
1       /init   /dev/__null__ (deleted)
1       /init   /dev/__null__ (deleted)
1       /init   /dev/__null__ (deleted)
1       /init   /dev/__kmsg__ (deleted)
1       /init   /dev/__properties__
1       /init   /dev/log/main
1       /init   /dev/log/radio
1       /init   /dev/log/events
1       /init   /dev/log/system
1       /init   socket:[6740]
1       /init   socket:[6742]
1       /init   socket:[6743]
1       /init   pipe:[6808]
1       /init   pipe:[6808]
1       /init   socket:[6753]
336     /sbin/busybox   /dev/__null__ (deleted)
336     /sbin/busybox   /dev/__null__ (deleted)
336     /sbin/busybox   /dev/__null__ (deleted)
336     /sbin/busybox   /sbin/init.sh
336     /sbin/busybox   /dev/__properties__
963     /init   /dev/__null__ (deleted)
963     /init   /dev/__null__ (deleted)
963     /init   /dev/__null__ (deleted)
963     /init   /dev/__kmsg__ (deleted)
963     /init   /dev/__properties__
963     /init   socket:[21673]
963     /init   socket:[21675]
963     /init   socket:[21676]
963     /init   socket:[23627]
963     /init   /dev/__properties__
964     /init   /dev/__null__ (deleted)
964     /init   /dev/__null__ (deleted)
964     /init   /dev/__null__ (deleted)
964     /init   /dev/__kmsg__ (deleted)
964     /init   /sys/fs/selinux/status
964     /init   /dev/__properties__
964     /init   socket:[23136]
964     /init   /dev/__properties__
976     /sbin/recovery  /dev/null
976     /sbin/recovery  /tmp/recovery.log
976     /sbin/recovery  /tmp/recovery.log
976     /sbin/recovery  /dev/tty0
976     /sbin/recovery  /dev/graphics/fb0
976     /sbin/recovery  /dev/log/main
976     /sbin/recovery  /dev/input/event0
976     /sbin/recovery  /dev/input/event9
976     /sbin/recovery  /dev/__properties__
976     /sbin/recovery  /dev/input/event8
976     /sbin/recovery  /dev/input/event7
976     /sbin/recovery  /dev/input/event6
976     /sbin/recovery  /dev/__properties__
976     /sbin/recovery  /dev/input/event5
976     /sbin/recovery  /dev/input/event4
976     /sbin/recovery  /dev/input/event3
976     /sbin/recovery  /dev/input/event2
976     /sbin/recovery  /dev/input/event1
976     /sbin/recovery  /dev/log/radio
976     /sbin/recovery  /dev/log/events
976     /sbin/recovery  /dev/log/system
1057    /sbin/adbd      /dev/null
1057    /sbin/adbd      /dev/null
1057    /sbin/adbd      /dev/null
1057    /sbin/adbd      socket:[23632]
1057    /sbin/adbd      socket:[23633]
1057    /sbin/adbd      socket:[23634]
1057    /sbin/adbd      /dev/android_adb
1057    /sbin/adbd      socket:[23635]
1057    /sbin/adbd      /dev/__properties__
1057    /sbin/adbd      socket:[23636]
1057    /sbin/adbd      socket:[21775]
1057    /sbin/adbd      socket:[23637]
1057    /sbin/adbd      /dev/__properties__
1057    /sbin/adbd      socket:[21778]
1057    /sbin/adbd      socket:[21779]
1057    /sbin/adbd      /dev/ptmx
1061    /sbin/busybox   /dev/pts/0
1061    /sbin/busybox   /dev/pts/0
1061    /sbin/busybox   /dev/pts/0
1061    /sbin/busybox   /dev/__properties__
1061    /sbin/busybox   socket:[21775]
1061    /sbin/busybox   /dev/tty
1061    /sbin/busybox   /dev/__properties__
~ # ←[6n

is it good for you ?
 

BreckZeBoulay

Senior Member
Oct 23, 2012
1,364
634
Boulay in Frankreich :D
@BreckZeBoulay yes, flashing should work fine now.
No it doesn't work.
Same error : format () expects 3 args, got 5
And after a few seconds (just have time to tape the error ^^), the screen turn black and reboot.

Just to be clear, what is installed at the moment :
- TX with stock deodex rooted .199 FW
- XT-lockeddualrecovery2.7.103-BETA installed with installer
- PhilZ Touch CWM Advanced Edition v1.7 by peetr_
 

[NUT]

Senior Member
No it doesn't work.
Same error : format () expects 3 args, got 5
And after a few seconds (just have time to tape the error ^^), the screen turn black and reboot.

Just to be clear, what is installed at the moment :
- TX with stock deodex rooted .199 FW
- XT-lockeddualrecovery2.7.103-BETA installed with installer
- PhilZ Touch CWM Advanced Edition v1.7 by peetr_

Does it do this on both twrp and Philz?

-Edit-

Try it using my format command to see if it will work that way. It could be a problem with the fact this is built against cm11.
 
Last edited:

BreckZeBoulay

Senior Member
Oct 23, 2012
1,364
634
Boulay in Frankreich :D
Does it do this on both twrp and Philz?

-Edit-

Try it using my format command to see if it will work that way. It could be a problem with the fact this is built against cm11.

with Philz (the one include in XT-lockeddualrecovery), error :
E: can't make /tmp/update_binary
EDIT : and after a few seconds, screen turning black and reboot.


I just put this command in my script updater ?

I stop test for this evening, my battery is too low.
 
Last edited:

[NUT]

Senior Member
with Philz (the one include in XT-lockeddualrecovery), error :
E: can't make /tmp/update_binary
EDIT : and after a few seconds, screen turning black and reboot.


I just put this command in my script updater ?

I stop test for this evening, my battery is too low.

If you could continue testing using both PhilZ Touch AND TWRP and let me know what does and doesn't work in either recoveries?

I'll try to update XZDR tonight with the latest version of PhilZ, hoping it might have been fixed in the mean time...

on the format command subject:

Replace this code:
Code:
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/System", "0", "/system");
with:
Code:
unmount("/system");
run_program("/sbin/make_ext4fs", "/dev/block/platform/msm_sdcc.1/by-name/System");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/System", "/system");

Besides this code change... in your update script, do you unmount the system partition before you try to format it?
If you don't it might be the cause of the reboot... (it will cause a kernel panic based on dramatic changes on the filesystem...)
 
Last edited:

Top Liked Posts