[Z1 Compact][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 Z1 Compact 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:
 
Last edited:

Riyal

Senior Member
Dec 16, 2011
3,038
1,769
Iloilo City
@[NUT]
Would like to report that your TWRP recovery log font seems a little too large for Z1 Compact screen. Can you resize the font size just on the log window of TWRP?

I think the issue is because the DPI set in default.prop is

# Graphics
ro.sf.lcd_density=480

where Z1 Compact only uses 320 DPI.
 
Last edited:
  • Like
Reactions: [NUT]

[NUT]

Senior Member
@[NUT]
Would like to report that your TWRP recovery log font seems a little too large for Z1 Compact screen. Can you resize the font size just on the log window of TWRP?

I think the issue is because the DPI set in default.prop is

# Graphics
ro.sf.lcd_density=480

where Z1 Compact only uses 320 DPI.

Thanks for the report, I'll have that fixed next version.
 

[NUT]

Senior Member
Hi @[NUT] ! I tried changing the default.prop to ro.sf.lcd_density to 320 and it's still the same. So the issue is not with the default.prop. Now I don't know what the issue is.

The default.prop actually reflects the setting used at compile time. So changing that will have no effect indeed.

Like I said, I'll have it fixed in the next version :)
 

Riyal

Senior Member
Dec 16, 2011
3,038
1,769
Iloilo City
The default.prop actually reflects the setting used at compile time. So changing that will have no effect indeed.

Like I said, I'll have it fixed in the next version :)
@[NUT]
Ahh thanks for the info! :p Have compiled twrp 2 times now but never got that in my head.


Anyways another bug report. Seems like TWRP can't fetch system time. I would assume that this is a kernel issue? Won't stock kernel work with TWRP recovery?


UPDATE: Just checked the rc files when android boots and I can see that Xperia Phones use a binary called time_daemon to fetch the system time. And when I rechecked your recovery I noticed that it also tries to use time_daemon but noticed that the binary file is missing.
 
Last edited:

[NUT]

Senior Member
@[NUT]
Ahh thanks for the info! :p Have compiled twrp 2 times now but never got that in my head.


Anyways another bug report. Seems like TWRP can't fetch system time. I would assume that this is a kernel issue? Won't stock kernel work with TWRP recovery?


UPDATE: Just checked the rc files when android boots and I can see that Xperia Phones use a binary called time_daemon to fetch the system time. And when I rechecked your recovery I noticed that it also tries to use time_daemon but noticed that the binary file is missing.

It's missing because I use the roms own version by mounting system and data for it to work, then when it did it's job I kill it again and unmount them again.
 

Riyal

Senior Member
Dec 16, 2011
3,038
1,769
Iloilo City
Ahh yes you're right.. But still it doesn't work though...

Code:
Anti-Filesystem-Lock completed.
Correcting system time: Wed Feb 18 05:14:06 GMT 1970
Set GMT timezone...
Corrected system time: Wed Feb 18 05:14:10 GMT 1970

Also doesn't it kill itself when it's done?

Code:
[email protected]:/ # /system/bin/time_daemon
/system/bin/time_daemon
Killed
 

[NUT]

Senior Member
Nope, it's a daemon which is supposed to keep running to keep the time synced.

I could only get it to work correctly while running it from the on init stage.

Did you grab my recovery to test or did you build it yourself?

Once in recovery, you could connect to it by adb and run the script by hand to see if it will work ok.

/sbin/xzdualrecovery.sh is responsible for it to do that job.
 
  • Like
Reactions: 1jkan

Riyal

Senior Member
Dec 16, 2011
3,038
1,769
Iloilo City
I am using your own recovery to test this. Strangely though adb doesn't work. So can't test it directly from recovery. I might unpack and repack your recovery to add logging on time_daemon later when I have time :D And maybe try fixing adb. So far that's all the bugs I could notice.

1. DPI issue on log window.
2. ADB doesn't work
3. Incorrect time.

Everything works :D

Nope, it's a daemon which is supposed to keep running to keep the time synced.

I could only get it to work correctly while running it from the on init stage.

Did you grab my recovery to test or did you build it yourself?

Once in recovery, you could connect to it by adb and run the script by hand to see if it will work ok.

/sbin/xzdualrecovery.sh is responsible for it to do that job.
 

[NUT]

Senior Member
I am using your own recovery to test this. Strangely though adb doesn't work. So can't test it directly from recovery. I might unpack and repack your recovery to add logging on time_daemon later when I have time :D And maybe try fixing adb. So far that's all the bugs I could notice.

1. DPI issue on log window.
2. ADB doesn't work
3. Incorrect time.

Everything works :D

You can force windows to install the sony composite adb driver. it will work.
 
  • Like
Reactions: 1jkan

[NUT]

Senior Member
I see! But how? Should I use device manager on windows for this? Hmmm by the way does TWRP use a custom graphics.c for it to work?

In device manager, connect usb, device with exclamation mark, right click it and choose install driver, then click let me choose from a list, untick the show only compatible drivers, then pick athe driver from Sony.

On twrp, yes it uses a custom graphics.c compared to cwm. But I never changed anything on it though, I only created a device repo for it and set the correct resolution. Just forgot to change the DPI setting.
 
  • Like
Reactions: 1jkan and Riyal

Riyal

Senior Member
Dec 16, 2011
3,038
1,769
Iloilo City
Heya @[NUT]

Here's some updates :D


Code:
~ # ←[6ndate
date
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Fri Feb 20 04:51:10 GMT 1970
~ # ←[6nxzdualrecovery.sh
xzdualrecovery.sh
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
~ # ←[6ndate
date
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Thu Mar  6 17:34:28 GMT 2014
~ # ←[6ndate
date
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
Thu Mar  6 17:35:16 GMT 2014
~ # ←[6n

It works if I manually execute xzdualrecovery.sh when it's already in recovery mode so what do you think? What I think is you need to create a post recovery init script in order for time daemon to actually work.


Or maybe adjust the init.rc of your recovery to execute first the recovery service before the xzdualrecovery.sh like this? Although then the LED prompt would be delayed too :p

Code:
service recovery /sbin/recovery

service xzdualrecovery /sbin/xzdualrecovery.sh
    oneshot
    disabled
 

Top Liked Posts