-=[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!
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!
XZDualRecovery User Manual
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:
[Locked Bootloader]CWM recovery 6.0.2.8 for locked bootloaders v4[25-03] by Krabappel2548
[APP/RECOVERY] TWRP 2.4.3.0 for lockled bootloaders installer by Cpasjuste
[KERNEL][Z] DooMKernel {JB}(v06)[20130414] by DooMLoRD
Your thanks (and donations) should (also) go out to them, they deserve it! :highfive:
i need to be rooted for this right?
Frodo07 said:
i need to be rooted for this right?
Click to expand...
Click to collapse
Yes, that's correct
Thanks for the optional recoveries and helping this great phone kick off in style
Sent from my D5503 using Tapatalk
tr1gg3r84 said:
Thanks for the optional recoveries and helping this great phone kick off in style
Sent from my D5503 using Tapatalk
Click to expand...
Click to collapse
Thanks my friend
@[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.
Riyal said:
@[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.
Click to expand...
Click to collapse
Thanks for the report, I'll have that fixed next version.
[NUT] said:
Thanks for the report, I'll have that fixed next version.
Click to expand...
Click to collapse
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.
Riyal said:
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.
Click to expand...
Click to collapse
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] said:
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
Click to expand...
Click to collapse
@[NUT]
Ahh thanks for the info! 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.
Riyal said:
@[NUT]
Ahh thanks for the info! 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.
Click to expand...
Click to collapse
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.
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
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.
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 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
[NUT] said:
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.
Click to expand...
Click to collapse
Riyal said:
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 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
Click to expand...
Click to collapse
You can force windows to install the sony composite adb driver. it will work.
[NUT] said:
You can force windows to install the sony composite adb driver. it will work.
Click to expand...
Click to collapse
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?
Riyal said:
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?
Click to expand...
Click to collapse
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.
Heya @[NUT]
Here's some updates
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
Code:
service recovery /sbin/recovery
service xzdualrecovery /sbin/xzdualrecovery.sh
oneshot
disabled
Related
Warning: This is very advanced, if you do not know what it is, dont play play.
I'm not responsible if your device bricked during deodexing process.
This method has been commonly used, I just improved it and included important cautions and precautions.
Requirements:
- Clean Rom (best with data wiped, orelse FCs)
- Rooted firmware (Root with Root Many Droid : here)
- Busybox installed (included when root with Root Many Droid)
- ADB correctly set up on computer *(sdk + environment variables setup)* ? - if u dont know what it is, as long as sdk installed is ok *(only sdk installed)*
- Xperia acro S with coresponding firmware version.
- In phone, usb debugging enabled, unknown sources enabled
- Downloaded app and framework zips
Downloads:
LT26w - 6.1.A.2.45 deodexed **working**
http://www.androidfilehost.com/?fid=9390225151984927323
http://www.androidfilehost.com/?fid=9390225151984927324
LT26w - 6.1.A.2.50 deodexed **working**
http://www.androidfilehost.com/?fid=9390244042945593435
http://www.androidfilehost.com/?fid=9390244042945593436
LT26w - 6.1.A.2.55 deodexed **working**
http://www.androidfilehost.com/?fid=9390244042945593453
http://www.androidfilehost.com/?fid=9390244042945593454
Instructions:
1. Extract downloaded done_app and done_frame zips
2. Copy done_app and done_frame to /sdcard/ (via MTP acceptable)
3. Make sure debugging mode connected
4. (i) Open Command Prompt on PC (Ctrl + R > cmd) *(sdk + environment variables setup)*
4. (ii) Go to /android-sdk/platform-tools/ folder, hold Shift button and right click mouse, 'Open Command window here' (Win 7) *(only sdk installed)*
5. Enter lines ony by one:
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
busybox cp /sdcard/done_app/* /system/app/
busybox rm /system/app/*.odex
busybox cp /sdcard/done_frame/* /system/framework/
busybox rm /system/framework/*.odex
chmod 644 /system/app/*
chmod 644 /system/framework/*
busybox mount -o ro,remount /system/ /system/
reboot
6. Close Command Prompt
7. Wait for phone to reboot, you'll see "Android Upgrading, Optimizing aplications..."
8. If optimizing aplications succeed, congratulations, ur stock rom is deodexed! Done.
Note: Every time u put apks into /system/app/ and restart, Android Upgrading will appear for once.
Credits:
Deodexed using dsixda's kitchen
Compressed using Winrar
Hosted by androidfilehost.com
Hi, very nice guide But I am noob at android stuff, I just know how to root, unlock bootloader, make flashable zips and stuff...
Can you deodex the latest 6.1.A.2.55 firmware for our Acro S? An awesome guy uploaded the .55 ROM flashable .zip here - http://forum.xda-developers.com/showthread.php?t=2035445
I'm not forcing you to do it but... It'll be a great help for the Acro S community
ItBankRock said:
Hi, very nice guide But I am noob at android stuff, I just know how to root, unlock bootloader, make flashable zips and stuff...
Can you deodex the latest 6.1.A.2.55 firmware for our Acro S? An awesome guy uploaded the .55 ROM flashable .zip here - http://forum.xda-developers.com/showthread.php?t=2035445
I'm not forcing you to do it but... It'll be a great help for the Acro S community
Click to expand...
Click to collapse
Sure, but deodexing the rom is very tricky, easily get bootloop.
I'll need some time. Currently doing .45
zhuhang said:
Sure, but deodexing the rom is very tricky, easily get bootloop.
I'll need some time. Currently doing .45
Click to expand...
Click to collapse
Thanks my friend! Take your time developing I'm sure everyone will be happy with the results of your work.
Good luck!
.45 deodexed files uploaded, link added at 1st post.
Good luck deodexing!
Will start work on .55 & .50 after my vacation (26 Dec)
Updated 27/12/12
Added:
LT26w - 6.1.A.2.50
Not tested, let me know the result.
EDIT: Should be LT26w
I'm gonna test for .55. Waiting for it. Thanks.
2nd Updated 27/12/12
Added:
LT26w - 6.1.A.2.55
Not tested, let me know the result.
EDIT: Should be LT26w
Deodex .55 successfully. Thanks.
Successfully worked on .55! Thanks dude! Keep up the good work!
ItBankRock said:
Successfully worked on .55! Thanks dude! Keep up the good work!
Click to expand...
Click to collapse
Thanks for your support
HItted thanks. Working on .55
bluerain28 said:
HItted thanks. Working on .55
Click to expand...
Click to collapse
Great! Anyone tested 50?
Sent from my LT26i using xda app-developers app
Updated 3/1/12
- Tested changing permission before reboot
- Shorter Procedure
Good job bro...
Sent from my LT26w using xda premium
i can confirm 6.1.A.2.50 is working, excellent work OP. Peace.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Alright? Added first post.
Sent from my LT26i using xda app-developers app
Yep no problems or fc's. Perfect.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Is there a way to deodex the rom in pc?
info:
this is based on the XZU recovery for locked bootloaders by @Krabappel2548
This thread will stay a dev and discussion thread for further development issues and fixes!
Download link can be found here: XZU recovery for locked bootloaders
THIS IS INTENDED FOR LOCKED BOOTLOADER DEVICES! But works on Unlocked bootloader too
THIS IS STILL IN DEVELOPMENT STAGE!
DO NOT EXPECT IT TO WORK PROBLEM FREE!
requirements:
rooted Xperia Z1
how to enter recovery:
when you see the Sony bootlogo and when device vibrates/leds light up u can use the entry keys to enter the corresponding recovery
VOLUME UP -> CWM
VOLUME DOWN -> TWRP
what works:
BOTH CWM 6.0.3.6 and TWRP 2.6.3.0 work
you can enter both recoveries and flash small files
what doesnt work:
in this particular version of CWM, adb doesnt work; it will be fixed later.. for debugging use TWRP
Shoudl be fixed:
TWRP and CWM both can destroy /cache and /system when trying to format it. Restoring your phone using an FTF is the only option left if that happens. You can however try to not format but use rm -rf instead in TWRP (TIC BOX!!), which will do for now.
regards,
Krabappel2548,
[NUT]
DooMLoRD
Last edit by Krabappel2548 on 19-10-'13
XDA:DevDB Information
Dual Recovery for Xperia Z1 (LOCKED BOOTLOADERS), a Tool/Utility for the Sony Xperia Z1
Contributors
DooMLoRD, [NUT], krabappel2548
Version Information
Status: Testing
Current Beta Version: 0.3
Beta Release Date: 2013-10-15
Created 2013-09-23
Last Updated 2013-10-19
Reserved
For anyone who does not own a Z1 (like me) and wants to search through the init actions.
Look also L2 Error detected! in 1089 Line. Usb don't work right and i think because we can't write in memory stack stack(0xe4859e70 to 0xe4859eb8) for lock bootloader. Problem it's in arch / arm / mach-msm but i don't find where!
As DooMLoRD's OP somehow does not fire the mention system... repeat for function
@Kali- @Bin4ry we need your help guys!
Oh now I got marked. I'll take a look at the weekend I don't have time Today sorry!
But just for me to know, ist that selfcompiled or a copy n paste version with a unpacked -> repacked ramdisk?
Have you checked against my posted recovery in Z Ultra forums? I can remember there was a similar problem on the locked bl recovery, you guys really seem to screw it somehow.
Also can i get a gdrive link to the files? Then I can grab it over my different systems more easy
Gesendet von meinem C6903 mit Tapatalk 4
Bin4ry said:
Oh now I got marked. I'll take a look at the weekend I don't have time Today sorry!
But just for me to know, ist that selfcompiled or a copy n paste version with a unpacked -> repacked ramdisk?
Have you checked against my posted recovery in Z Ultra forums? I can remember there was a similar problem on the locked bl recovery, you guys really seem to screw it somehow.
Also can i get a gdrive link to the files? Then I can grab it over my different systems more easy
Gesendet von meinem C6903 mit Tapatalk 4
Click to expand...
Click to collapse
It was a self-compiled version by @DooMLoRD, with a ramdisk slightly modified to get it to work for the Z1. What did you do to get it to work on the ZU? @krabappel2548 tried and failed there too...
EDIT: Just to be clear: it's not that the recovery does not work, it does, it's the kernel which triggers a reboot after 40 seconds because it seems to be unable to initialize the modem.
Bin4ry said:
Oh now I got marked. I'll take a look at the weekend I don't have time Today sorry!
But just for me to know, ist that selfcompiled or a copy n paste version with a unpacked -> repacked ramdisk?
Have you checked against my posted recovery in Z Ultra forums? I can remember there was a similar problem on the locked bl recovery, you guys really seem to screw it somehow.
Also can i get a gdrive link to the files? Then I can grab it over my different systems more easy
Gesendet von meinem C6903 mit Tapatalk 4
Click to expand...
Click to collapse
the boot hijack scripts, chargemon, are based on the ones for Xperia Z by @[NUT], with the necessary modifications, if any, for Xperia Z1
the ramdisks for the recoveries are using the same CPIO as the ones for unlocked bootloader...
recovery works well on unlocked bootloader with recovery integrated in kernel ramdisk...
will send u link over gtalk
did u post recovery for LOCKED bootloaders for Z Ultra?
Ok i did some first tests!
My own recovery works (see cm boot.img !). But this one does not work when ramdisk-recovery is integrated into your dualboot script!
So it is definetly a problem with the services from the "host" system. The ramdisks which get extracted also work fine when integrated into cm boot.img!
So wild guess here: You try to stop all services from host system but it seems not to work, since you dont really need anything running for recovery, but some of the host services dont want to stop here and waiting for the system to bootup. SOMETHING seems to reboot it then when nothing is happening
Need to see deeper whats happening, its quite a funny problem i think
Regards
I came to the same conclusion, but I had to give up as I had no idea what services could have been responsible
It might be the RIL service as it slingshots a lot of the radio/modem functionality... But I'm really not too sure...
Sent from my C6603 using xda app-developers app
Deleted
original ramdisk and the files from /system/etc are now in post 3 for anyone without a Z1 to check them.
Bin4ry said:
Ok i did some first tests!
My own recovery works (see cm boot.img !). But this one does not work when ramdisk-recovery is integrated into your dualboot script!
So it is definetly a problem with the services from the "host" system. The ramdisks which get extracted also work fine when integrated into cm boot.img!
So wild guess here: You try to stop all services from host system but it seems not to work, since you dont really need anything running for recovery, but some of the host services dont want to stop here and waiting for the system to bootup. SOMETHING seems to reboot it then when nothing is happening
Need to see deeper whats happening, its quite a funny problem i think
Regards
Click to expand...
Click to collapse
Did you find anything useful yet?
I've been wandering around in the files again myself, i've checked the qcom modem init already but i rechecked it, it seems that before chargemon is started, it already initialized a lot of the radio/modem hardware... it seems that at least one service is responsible for the communications layer between the kernel and modem, but I have been unable to determine which one... seeing the 40 second timeout before a reboot occurs it probably accounts for the service needing some time to start up.
Since kernel have initiated the modem, is it possible to write a procedure to set smem_get_entry flag. most likely to assign flag one to it.. New to android development..When i program a micro controller..we will be checking a flag in modem to see if it is initiated.. or sometimes.. i assigns a variable or memory address...so instruction will check that location for status rather than checking modem flag...as it takes more cycles...so i think this may be clearing some flags or memory or variable....
I did not had time yet to continue working but boyhood you guys should be correct. I am just thinking of the easiest way to fix it. Give me some more days please
Gesendet von meinem C6833 mit Tapatalk 4
Bin4ry said:
I did not had time yet to continue working but boyhood you guys should be correct. I am just thinking of the easiest way to fix it. Give me some more days please
Gesendet von meinem C6833 mit Tapatalk 4
Click to expand...
Click to collapse
I've had a chat about it with Dees Troy from TWRP about it, he suggested RIL as a possible culprit, or maybe watchdogd...
I don't have a z1 so I'm unable to test it on my own...
Sent from my C6603 using xda app-developers app
[NUT] said:
I've had a chat about it with Dees Troy from TWRP about it, he suggested RIL as a possible culprit, or maybe watchdogd...
I don't have a z1 so I'm unable to test it on my own...
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
For watchdog to reset an unexpected condition should occur.. for that something else have to go wrong...
and not sure- Radio Interface Layer is it not part of baseband?
jos_031 said:
For watchdog to reset an unexpected condition should occur.. for that something else have to go wrong...
and not sure- Radio Interface Layer is it not part of baseband?
Click to expand...
Click to collapse
Yes, it is: so it's tied in with the modem hardware...
Where do I download that recovery??
Jacob_Bentzen said:
Where do I download that recovery??
Click to expand...
Click to collapse
It's on the download tab in the project bar
Sent from my C6603 using xda app-developers app
Hi, here is tool for making flashable zip in few commands! No need root! In few commands your rom is ready for sharing or flashing with CMW ! You can dump any rom! NOTE: all your rom changes which is in your phone will be included in rom.zip (for example busybox, su...etc)! Tool will be usefull for dumping next Sony stock rom, but allso all rom is supported! Enjoy!
For no rooted devices:
adb push romgen /data/local/tmp/
adb shell
cd /data/local/tmp
chmod 755 romgen
Code:
./romgen C6903 honami /dev/block/platform/msm_sdcc.1/by-name/system /dev/block/platform/msm_sdcc.1/byname/userdata /dev/block/platform/msm_sdcc.1/by-name/cache [COLOR="Red"]/dev/null[/COLOR] /storage/removable/sdcard1/rom.zip
/dev/null must be used as a boot partition since no rooted devices have no access to these device!
For rooted devices:
adb push romgen /data/local/tmp/
adb shell
su
cd /data/local/tmp
chmod 755 romgen
Code:
./romgen C6903 honami /dev/block/platform/msm_sdcc.1/by-name/system /dev/block/platform/msm_sdcc.1/byname/userdata /dev/block/platform/msm_sdcc.1/by-name/cache [COLOR="Red"]/dev/block/platform/msm_sdcc.1/by-name/boot[/COLOR] /storage/removable/sdcard1/rom.zip
Download tool:
http://forum.xda-developers.com/showthread.php?t=2533585
munjeni said:
Hi, here is tool for making flashable zip
Click to expand...
Click to collapse
is it stable already?
I mean the Meta-INF generated completely?
thanks gonna try this if the tool complete
nelikp said:
is it stable already?
I mean the Meta-INF generated completely?
thanks gonna try this if the tool complete
Click to expand...
Click to collapse
Yesterday I noticed bug There is bug when folder is empty or when symlink is inside folder but there no other files! So when tool generate zip these folder is missing in zip but updater-script have line "set perm to folder" which not exist, so installation aborting because a missing folder Will try to solve them soon! Do not flash generated zip since you will get boot loop (you can only if you add missing folders to zip)! I will make new version soon, hope clean!
New version is out! Hope all bugs solved! Bug is solved by creating empty file .placeholder to all existing folders so zip for sure now have all mised folders, than placeholders is auto removed at finish of the installation
I am hope eerything is right now, but I will test and let you know if generated zip is installable with sucess!
New working version finaly, sorry! Now I tested tool and found another 2 bugs, first one was "zip fail to store file which contain special characters like *()...etc", and seccond one was wrong format of the permssions in updater-scrip. Now all things is solved, I have tested tool, tried to install generated zip, installed zip, and bum. Everything is ok now, enjoy!
Hi mate...nice to see you here
If I'm correct, you have some great work and kernels in your biography
Sent from my C6903 using Tapatalk
funky0308 said:
Hi mate...nice to see you here
If I'm correct, you have some great work and kernels in your biography
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
No space left in my signature :laugh: One oftopic question, anyone have info when Sony will anounce 4.4.2 ?
munjeni said:
No space left in my signature :laugh: One oftopic question, anyone have info when Sony will anounce 4.4.2 ?
Click to expand...
Click to collapse
Yeah...I'm using Tapatalk so can't see...but, as I said, I know who you are and we will be very happy if you join Z1 development :thumbup:
It should be out (most likely) in a first few days on april (let just hope it won't be first April and we.won't be April's fools )
Some of Z2 apk files are already out and if that guy who already post few things managed to post Z2 system dump - we could have something even earlier
Sent from my C6903 using Tapatalk
I am allready in development on Z1 Compact but curently I have problem in semc_colorizable (going to start working in MIUI), so first of all I need to solve all things related to the recompiling framework-res and full removal of the semc_generic_uxp... by now have no luck Did you have luck on framework-res on Z1 using apktool ? I have managed to recompile/compile them by now, but boot loop on colorizable things since my modificaions on framework / framework-res is not complete .
munjeni said:
I am allready in development on Z1 Compact but curently I have problem in semc_colorizable (going to start working in MIUI), so first of all I need to solve all things related to the recompiling framework-res and full removal of the semc_generic_uxp... by now have no luck Did you have luck on framework-res on Z1 using apktool ? I have managed to recompile/compile them by now, but boot loop on colorizable things since my modificaions on framework / framework-res is not complete .
Click to expand...
Click to collapse
@munjeni bro, you can try out the Advanced APKtool by @BDFreak bro for the framework-res issues. It's compatible with z1 Compact.
http://forum.xda-developers.com/showthread.php?t=2639400
@munjeni, nice tool, but I need help. I get this error in CWM log every time I try to install my zip; "l:Can't partition non mmcblk device: /devices/msm_sdcc.2/mmc_host
What do I need to do to the updater script? I tried replacing the mount system bit with;
run_program("/sbin/busybox", "mount", "/system");
package_extract_dir("system", "/system");
but I had no luck.
Probably you pased bad command to the romgen since you say /devices/msm_sdcc.2/mmc_host !!! Double check first post before you going to generate zip! Or probably you using an bad cwm which have bad fstab! If no of these 2 simptoms is true than for sure you have modified updater-script by your own way which probably is not ok! Hope this help.
munjeni said:
Probably you pased bad command to the romgen since you say /devices/msm_sdcc.2/mmc_host !!! Double check first post before you going to generate zip! Or probably you using an bad cwm which have bad fstab! If no of these 2 simptoms is true than for sure you have modified updater-script by your own way which probably is not ok! Hope this help.
Click to expand...
Click to collapse
Okay so it's the bad fstab, thanks man
Can anyone make rom for my karbon a39 HD
Introduction
BDFreak said:
[What is this? Let me explain you. It will Bypass the signature checking of sony. Sometimes when we mod any system app and put it back in to system with correct permission but the app doesn't work or doesn't install or force closes. Most of the time these problems are happening because of signature checking.
Click to expand...
Click to collapse
I saw some themes in cross dev section which needed this mod to run so I made it for our devices. Thanks to BDFreak for the TUT.
Installation
- Download the modded services.jar from here.
- Push it to /system/frameworks
Code:
adb push services.jar /system/framework/
- Give correct permissions(644)
Code:
adb shell chmod 0644 /system/framework/services.jar
- Reboot
Code:
adb reboot
Now let the OS be adapted to new services.jar. Once it ready use it and enjoy.
it is great to see you abhinav sir:victory:
hope very soon we will see roms kernel and mods from your master side
thanks a lot for joining t2 ultra forum
chauhanjayc said:
it is great to see you abhinav sir:victory:
hope very soon we will see roms kernel and mods from your master side
thanks a lot for joining t2 ultra forum
Click to expand...
Click to collapse
Will build ROMs for the device Currently CyanogenMod for our device is way toooo smooth but still most things aren't working and major issue of it is audio. I spent 5-6 hours yesterday on it trying to figure our problem, taking logs and using some vendor from stock to see if I can get it to work but I got nothing. I'll try to debug it tonight also and its my assumption that if I can get audio to work, I can fixup most stuff Also waiting for sony to release kernel sources for latest firmware which I can merge and then try to fix with it
Cheers,
AJ
Abhinav2 said:
Will build ROMs for the device Currently CyanogenMod for our device is way toooo smooth but still most things aren't working and major issue of it is audio. I spent 5-6 hours yesterday on it trying to figure our problem, taking logs and using some vendor from stock to see if I can get it to work but I got nothing. I'll try to debug it tonight also and its my assumption that if I can get audio to work, I can fixup most stuff Also waiting for sony to release kernel sources for latest firmware which I can merge and then try to fix with it
Cheers,
AJ
Click to expand...
Click to collapse
no words to say thank you very very very much dear DEV:good:
my bad that i cant get you a bear personally
Can you make this mod for 4.4.3 ( 19.1.1.C.56 ) ?
lungtung123 said:
Can you make this mod for 4.4.3 ( 19.1.1.C.56 ) ?
Click to expand...
Click to collapse
Send me services.jar from deodexed firmware.
AJ
Q&A for [T2 Ultra][TWRP][PhilZ Touch][CWM] XZDualRecovery Q&A
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [T2 Ultra][TWRP][PhilZ Touch][CWM] XZDualRecovery Q&A. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
can i use it for unrooted 4.4.3 device?
[NUT] said:
-=[XZDualRecovery]=-
PhilZ Touch & CWM & TWRP
*** For Locked and Unlocked BOOTLOADERS! ***
Welcome to the Xperia T2 Ultra Questions & Answers thread!
I proudly present you the first and only DUAL RECOVERY for locked boot loaders on our lovely Xperia phones!
If you have an unlocked bootloader and chose to keep the STOCK Sony kernel, you can also use this MOD.
Currently supported XPERIA models:
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
Xperia Tablet Z2: SGP511, SGP512, SGP521
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
To follow development, be sure to check the DevDB thread![/QUOTE
can i use it for unrooted 4.4.3 d5322
Click to expand...
Click to collapse
Mike_Abosin said:
[NUT] said:
-=[XZDualRecovery]=-
PhilZ Touch & CWM & TWRP
*** For Locked and Unlocked BOOTLOADERS! ***
Welcome to the Xperia T2 Ultra Questions & Answers thread!
I proudly present you the first and only DUAL RECOVERY for locked boot loaders on our lovely Xperia phones!
If you have an unlocked bootloader and chose to keep the STOCK Sony kernel, you can also use this MOD.
Currently supported XPERIA models:
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
Xperia Tablet Z2: SGP511, SGP512, SGP521
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
To follow development, be sure to check the DevDB thread![/QUOTE
can i use it for unrooted 4.4.3 d5322
Click to expand...
Click to collapse
No, u need superuser access to install recovery
Click to expand...
Click to collapse
Chena_22 said:
Mike_Abosin said:
No, u need superuser access to install recovery
Click to expand...
Click to collapse
but i read that it might run with unrooted
but my problem is my phone doesn't supported bt twler root
Click to expand...
Click to collapse
Mike_Abosin said:
Chena_22 said:
but i read that it might run with unrooted
but my problem is my phone doesn't supported bt twler root
Click to expand...
Click to collapse
Well, you can try using it.. To root your device there is already a thread un the general section...
Click to expand...
Click to collapse
Chena_22 said:
Mike_Abosin said:
Well, you can try using it.. To root your device there is already a thread un the general section...
Click to expand...
Click to collapse
is there any danger if id didn't work??
because it is my first time with sony i have agood history with samsung i flashed a custom rom . mods and more on it
Click to expand...
Click to collapse
Rooting xperia t2 ultra dual getting struck, pls help
Hi,
i have been follwing ur instrcution and all looked fine till , creating vm (loljavasucks) . it gets struck at this point and nothing happens after that. pls help
Don't work on T2 Ultra D5303 19.3.A.0.470
On T2 Ultra Dual working perfectly!
Please, fix it
Issues with D5303 LP 5.0.2
Hi Nut
First let me congratulate you for all your great job, I've been using your XZDual Recovery in my T2 Ultra with KK and it worked flawlessly. However recently I decided to upgrade to LP and I created a prerooted version of the 19.3.A.0.470 FW using PRF.
In my first attempt I include your XZDual Recovery but it didn't work, I had the rooted LP but no recovery. Then I created a new preooted version but without your recovery included and i flashed both zips separately but again no working recovery. Then a read your threads and i decided to share my logs.
In the first place this is what I get when I tried to use the installer:
PHP:
==============================================
= =
= 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]?1
* 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 D5303
Firmware is 19.3.A.0.470
=============================================
Step2 : Sending the recovery files.
=============================================
1 KB/s (31 bytes in 0.025s)
768 KB/s (18101 bytes in 0.023s)
163 KB/s (501 bytes in 0.003s)
432 KB/s (11966 bytes in 0.027s)
2300 KB/s (65965 bytes in 0.028s)
103 KB/s (3082 bytes in 0.029s)
1471 KB/s (30148 bytes in 0.020s)
110 KB/s (1357 bytes in 0.012s)
1683 KB/s (34473 bytes in 0.020s)
53 KB/s (1089 bytes in 0.020s)
884 KB/s (13592 bytes in 0.015s)
3777 KB/s (719520 bytes in 0.186s)
5012 KB/s (3403408 bytes in 0.663s)
4788 KB/s (2324302 bytes in 0.474s)
4708 KB/s (1976995 bytes in 0.410s)
546 KB/s (11760 bytes in 0.021s)
=============================================
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 719520 Apr 22 14:09 /data/local/tmp/recover
y/busybox
Press any key to continue . . .
mkdir: can't create directory '/storage/sdcard1/XZDualRecovery': Read-only file
system
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.14 RELEASE
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to al
low installation.
The byeselinux module exists, testing if the kernel accepts it.
insmod: can't insert '/system/lib/modules/byeselinux.ko': Invalid argument
That module is not accepted by the running kernel, will replace it now.
Module installed succesfully.
rmmod: delete_module 'byeselinux' failed (errno 2)
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.
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event3!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event1!
grep: /cache/XZDualRecovery/XZDR.prop: No such file or directory
grep: /cache/XZDualRecovery/XZDR.prop: No such file or directory
XZDualRecovery will unload byeselinux every boot.
Speeding up 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.
=============================================
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 . . .
C:\adb\lockeddualrecovery>
Then I checked the root via ADB and remount the /system and the /storage/sdcard1 directories but I got the same resut. Then I read somewhere in one of the threads that the Ric Killer do the trick but not for me.
Final info:
T2 UItra D5303 (originally was a D5316 but I changed because of the Lollipop)
Firmware Lollipop 19.3.A.0.470 (prerooted using PRF)
SuperSU Free v2.46
Attached Files: The first one was in the /cache/recovery folder, the other two were in the /storage/sdcard1/XZDualRecovery directory and in the /tmp/XZDualRecovery I couldn't find anything.
Any help will be appreciated and let me thank you one more time.
Not able to install recovery
I have rooted my t2 ulta dual without unlocking bootloader. When i try this tool there is an error in the command prompt as " adb server is out of date. killing... "
Please help why should i do to install dual recvery
---------- Post added at 01:22 PM ---------- Previous post was at 01:17 PM ----------
sunilmahadevan said:
Hi,
i have been follwing ur instrcution and all looked fine till , creating vm (loljavasucks) . it gets struck at this point and nothing happens after that. pls help
Click to expand...
Click to collapse
Hey, you need to flash the older kernel 4.4.2 to root your device. After successfully runnig easy root toolkit again you need to flash 4.4.3 kernel to start your mobile
Note: When you flash 4.4.2 kernel your device will stuck at start up in black screen don't be worried again flash newer kernel.. You ll b rooting your device
Thumb's up if helpfull
Recovery does not start on lollipop 19.3.A.0.472, I think the logs help you. Thanks in advance!