Related
-=[XZDualRecovery]=-
PhilZ Touch & CWM & TWRP
*** For Locked and Unlocked BOOTLOADERS! ***
Welcome to the Xperia ZL 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 just used this, and after finishing the process by restarting phone after the CWM prompt, and I restart again and try to press either up or down volume buttons during the green light, nothing happens it just keeps booting to ROM, I've tried rapidly pressing the volume keys or holding it down nothing would activate recovery. It boots into safe mode if I keep holding it down.
XDA STATUS UPDATE:
I'm at a TAPAsBar, flashing around my ZL.
ehBrY said:
I just used this, and after finishing the process by restarting phone after the CWM prompt, and I restart again and try to press either up or down volume buttons during the green light, nothing happens it just keeps booting to ROM, I've tried rapidly pressing the volume keys or holding it down nothing would activate recovery. It boots into safe mode if I keep holding it down.
XDA STATUS UPDATE:
I'm at a TAPAsBar, flashing around my ZL.
Click to expand...
Click to collapse
Can you please do a new attempt and include your logs (if any) mentioned in the OP? I have nothing to work with now!
Sent from my C6603 using xda app-developers app
I am also not able to get into recovery by pressing either of the volume buttons
ehBrY said:
I just used this, and after finishing the process by restarting phone after the CWM prompt, and I restart again and try to press either up or down volume buttons during the green light, nothing happens it just keeps booting to ROM, I've tried rapidly pressing the volume keys or holding it down nothing would activate recovery. It boots into safe mode if I keep holding it down.
XDA STATUS UPDATE:
I'm at a TAPAsBar, flashing around my ZL.
Click to expand...
Click to collapse
R4GE199 said:
I am also not able to get into recovery by pressing either of the volume buttons
Click to expand...
Click to collapse
To both above:
Open a root explorer app, see if there is a folder called 'lost+found' inside /cache ... if it's not there, you need to use an FTF to restore it (just cache, nothing else!).
If it's there you can see the folders 'recovery' and 'XZDualRecovery' if an external SDCard (sdcard1) is absent, otherwise this last folder will be on your external SDCard. Create a file called 'boot' inside either one of directories. You will be able to boot to CWM that way. If you create a file called 'default' inside the XZDualRecovery folder and put in just the word 'twrp' (without quotes and no new line) to make it boot into TWRP when the 'boot' file is found.
Open CWM at first and do the advanced -> key test and provide me with the codes it produces while pressing the UP volume key once and the DOWN volume key once. Open the lid where your SIM is and with a paper-clip or pointy pen press the 'reset' button there to reboot your phone.
That way i know what to fix and what to check for during the boot of the script.
Don't worry guys, I'll get it fixed
[NUT] said:
If it's there you can see the folders 'recovery' and 'XZDualRecovery' if an external SDCard (sdcard1) is absent, otherwise this last folder will be on your external SDCard. Create a file called 'boot' inside either one of directories. You will be able to boot to CWM that way.
...
Open CWM at first and do the advanced -> key test and provide me with the codes it produces while pressing the UP volume key once and the DOWN volume key once.
Click to expand...
Click to collapse
Code:
CWM-based Recovery v6.0.3.2
Outputting key codes.
Go back to end debugging.
Key: 115
Key: 114
File "boot" after rebooting the system are removed.
Bird40 said:
Code:
CWM-based Recovery v6.0.3.2
Outputting key codes.
Go back to end debugging.
Key: 115
Key: 114
File "boot" after rebooting the system are removed.
Click to expand...
Click to collapse
Thats funny, the keycodes are the same on C6603 ... hmmm stuff to ponder on.
The boot file will be removed indeed, otherwise you would never be able to boot your phone in a normal way
-- EDIT --
I've found what is causing this... i'll do a ZL patch release soon.
[XZDualRecovery] Version 2.2 BETA released!
BETA Change log:
BETA releases will only appear on http://www.fun-industries.nl/xda/ and as soon as enough people report it to be working fine will it move in to the OP as a RELEASE version.
Version 2.2:
Fixed ZL Keycheck, again... :silly:
Did some more code cleaning, simplifying the SDCard1 mounting process.
Released the LINUX installer (Requires root privileges, so it will prompt for a sudo password) - Thanks go to @Androxyde for the adb binary!
Please update and test!
[NUT] said:
BETA releases
...
Version 2.2
...
Please update and test!
Click to expand...
Click to collapse
Thanks, it works.
I was able to get into CWM and TWRP 3 times.
[NUT] said:
How to remove:
...
Then inside /system/bin/ rename chargemon.stock to chargemon check its permissions (should be 755 or otherwise visible as -rwxr-x-r-x). ...
Click to expand...
Click to collapse
May be rwxr-xr-x?
Bird40 said:
May be rwxr-xr-x?
Click to expand...
Click to collapse
Nice spotting
Sent from my C6603 using xda app-developers app
2.2 is still not working for me. I noticed at the first attempt of this recovery modification, the restart message asked me if I wanted it to prevent the boot from changing my recovery again. And now when I'm trying to reinstall 2.2 over it, it never asked me that. Could that be why? How do I start from scratch if that's whats needed. It hasn't asked me that message again, just a normal restart phone message. I am anxious to do my TWRP backups, please advise! Again, the green light still comes on after 2.2 attempt, but still no luck on the volume key presses. Will the person that got it working with 2.2 please tell me what you did to get it working? Thanks ahead of time.
[NUT] said:
BETA Change log:
BETA releases will only appear on http://www.fun-industries.nl/xda/ and until enough people report it to be working fine will it move in to the OP as a RELEASE version.
Version 2.2:
Fixed ZL Keycheck, again... :silly:
Did some more code cleaning, simplifying the SDCard1 mounting process.
Released the LINUX installer (Requires root privileges, so it will prompt for a sudo password) - Thanks go to @Androxyde for the adb binary!
Please update and test!
Click to expand...
Click to collapse
ehBrY said:
2.2 is still not working for me. I noticed at the first attempt of this recovery modification, the restart message asked me if I wanted it to prevent the boot from changing my recovery again. And now when I'm trying to reinstall 2.2 over it, it never asked me that. Could that be why? How do I start from scratch if that's whats needed. It hasn't asked me that message again, just a normal restart phone message. I am anxious to do my TWRP backups, please advise! Again, the green light still comes on after 2.2 attempt, but still no luck on the volume key presses. Will the person that got it working with 2.2 please tell me what you did to get it working? Thanks ahead of time.
Click to expand...
Click to collapse
If you downloaded straight after the initial release, re-download it and try again. I made a mistake in the first BETA of 2.2...
There is a guide in the OP on how to remove this recovery modification.
Before you do try, check if you can remount /system as 'rw' using root explorer or es file explorer. If you phone goes into a reboot you probably said 'yes' where you never should in CWM.
If thats the case then try this:
Create the file 'default' in the XZDualRecovery folder in either /cache or /sdcard1 and put in the single word 'twrp'. Then create an empty file called 'boot' inside /sdcard1/XZDualRecovery/ or /cache/XZDualRecovery and reboot your phone. You will go in to TWRP the next boot.
Go to advanced -> file manager and navigate to /system/etc/ and look for a file called install-recovery.sh and fix it's permissions to be 755.
Reboot your phone and try the remount test again.
So just to clarify is the latest 2.2 Beta. Windows. Update or beta with nothing else? It would help if to ur file list shows the upload date. Thx I'll give it a try, so I should not say yes to that message in CWM on first boot? But that's the only option it gives me to reboot, if I press one of the many NOs it will still reboot?
XDA STATUS UPDATE:
I'm at a TAPAsBar, flashing around my ZL.
---------- Post added at 12:50 AM ---------- Previous post was at 12:46 AM ----------
When you say remount the system folder as RW do you mean changing the permissions to all RW? I just did that on solid explorer so that it is now 777 is that actually safe? Please advise thanks.
XDA STATUS UPDATE:
I'm at a TAPAsBar, flashing around my ZL.
ehBrY said:
So just to clarify is the latest 2.2 Beta. Windows. Update or beta with nothing else? It would help if to ur file list shows the upload date. Thx I'll give it a try, so I should not say yes to that message in CWM on first boot? But that's the only option it gives me to reboot, if I press one of the many NOs it will still reboot?
XDA STATUS UPDATE:
I'm at a TAPAsBar, flashing around my ZL.
---------- Post added at 12:50 AM ---------- Previous post was at 12:46 AM ----------
When you say remount the system folder as RW do you mean changing the permissions to all RW? I just did that on solid explorer so that it is now 777 is that actually safe? Please advise thanks.
XDA STATUS UPDATE:
I'm at a TAPAsBar, flashing around my ZL.
Click to expand...
Click to collapse
You can use the update package to get it up to the latest BETA release. I'm working on refining the download page, it will probably also contain the file date in that version. Thanks for the tip!
Oh after re-reading your question... whoops: you need to remount, not set permissions... Download root explorer or es file explorer to do so.
Just keep saying no, it will reboot no problem.
If you tried 2.2 beta and find it working, let us all know if it did!
Same in reverse, I need you people to feed me feedback whichever way it goes!
Sent from my C6603 using xda app-developers app
[NUT] said:
If you tried 2.2 beta and find it working, let us all know if it did!
Click to expand...
Click to collapse
Thanks, it works
Bird40 said:
Thanks, it works
Click to expand...
Click to collapse
Heh, I knew it worked for you, thanks for that and the testing, but I was actually referring to others downloading and getting no feedback
Sent from my C6603 using xda app-developers app
UPDATED INSTRUCTIONS 23/3/2014
Thought I would share this for anyone that's looking for a complete and full root of this phone, this is not my work I was given these instructions for full root of Sony Xperia M Phone by member xzn credits go to him and others mentioned within method here is the method as follows
- FULL ROOT XPERIA M -
material
- Download Framaroot 1.5.3(http://www.2shared.com/file/x5aus8Wd/comalephzainframaroot_153.html?)
- Busybox Pro v9.7.3 (http://www.2shared.com/file/gPQlU2-Q/BusyBox_Pro_9_7_3.html?)
- Busybox Free (https://play.google.com/store/apps/details?id=stericson.busybox)
- Tool By Anto Kus (download here http://www.2shared.com/file/e9sDTGJk/rootfixer.html?)
- some snacks and soda
steps
1. Install framaroot 1.5.3 ,open , then select install supersu, then select gandalf, if its failed, try, try n try until success notification appear and ask to reebot,your phone will reboot, after your phone on again , look for supersu app in menu , if supersu not appear in menu try,try n try again until supersu appears
2. Install BusyBox Pro v9.7.3 , if busybox ask for backup, select yes, then busyboz will loading, after 100%, MAKE SURE BUSYBOX IS INSTALLED IN SYSTEM/XBIN select install, select normal install, after success,reboot your XM
up here, Your phone was half rooted (what is half rooted? its mean that your phone can not edit system file, if you try to edit your system file your XM will sudden reboot) (THIS STEP IS SO YOU CAN CREATE A BACKUP OF YOUR SYSTEM SETTINGS BEFORE BUSYBOX IS INSTALLED BUT IF YOUR NOT BOTHERED ABOUT A BACKUP THEN YOU CAN SKIP INSTALLING THIS BUSYBOX VERSION AND DOWNLOAD THE BUSYBOX FREE AND USE THAT ONE TO INSTALL THE LATEST VERSION STRAIGHT AWAY)
3. eat your snack and drink your soda, stay relax 
4. Extact Tool by Anto Kus to your pc (you will get superuser.bat and supersu.bat), then connect your XM (connect by msc and you must have install pcc on your pc), then run supersu.bat when prompted grant root access on phone
your xm will reboot
Once phone reboots wait for pc to detect phone again then finish supersu.bat then unplug device, MAKE SURE TO RERUN THE. bat FILE AGAIN AFTER FIRST REBOOT TO DOUBLE CHECK THAT THE REBOOT FIX HAS BEEN INSTALLED CORRECTLY, BEFORE RUNNING THE SCRIPT AGAIN AFTER PHONE HAS BEEN DETECTED BY THE PC UNPLUG THE PHONE THEN RERUN THE .bat FILE.
5. DOWNLOAD THE LATEST BUSYBOX FREE FROM PLAY MARKET AND LET SMART INSTALL FINISH LOADING, ONCE LOADED SELECT LATEST BUSYBOX VERSION (CURRENTLY AT V1.22.1-stericson) AND MAKE SURE ITS INSTALLED IN SYSTEM/XBIN. ONCE INSTALLED REBOOT PHONE THEN YOUR DONE
Credit to
- Xzn
- Anto Kus
- Hendrico Andre and Muhammad Arif
from Sony Xperia M Indonesia :highfive:
EXTRA
1: BUSYBOX MUST BE INSTALLED TO SYSTEM/XBIN TO WORK IF NOT AND SYSTEM/BIN IS SELECTED THE PHONE WILL REBOOT AND BUSYBOX WILL NOT BE INSTALLED
2: ALL DRIVERS MUST BE INSTALLED ADB ETC...
3: USB DEBUGGING AND MSC MUST BE SELECTED AND TURNED ON
HOW TO UNROOT LONG VERSION:
*only if you used busybox pro*
1. go into busybox and click on restore, let it do its job. A confirmation popup will appear
2. Go into supersu>settings and scroll down to unroot, click it and let it finish
3. Reboot device (NOTE IF YOU'VE RESTORED VIA BUSYBOX THEN SYSTEM WILL BE VERY LAGGY)
4. Go into settings and carry out a factory reset to clear the device fully.
HOW TO UNROOT SHORT VERSION:
1. Refresh stock firmware via flashtool and select wipe cache and wipe data
2. Let device boot up, can take upto 5+ minutes to boot up.
Sent from My Sony Xperia M C1905
Indeed anyone tried binary4u?
Thanks for this detailed guide..
I have problem ( or better - my brother ) after succesfull root, run rootfixer, but thats not fix anything... phone still rebooting if i want change some in /system ...please help
icoolguy1995 said:
Indeed anyone tried binary4u?
Click to expand...
Click to collapse
Did you install busybox I have tried and tested this method several times and never had any problems follow instructions closely
Sent from my C2005 using xda premium
Ignore the quote as xda app giving me.issues and not selecting the correct post to quote
Sent from my C2005 using xda premium
yes, installed... (and backed up, and wait for 100% loading, then install - normal)
i folowed closely, and still have problem.
Installed busybox to system/xbin?
Sent from my C2005 using xda premium
dont know... but when i now open busybox pro, its pointing to system/bin ...So you think i have to change destination to xbin and install it again ?
Install busybox to system/xbin
You'll get a confirmation screen saying busybox has been installed successfully then reboot your phone once booted up rerun root fix for the superuser app you installed then once phone has booted up again try then
Sent from my C2005 using xda app-developers app
Any luck did that work?
Sent from my C2005 using xda app-developers app
Many THANKS !!! It working now !!!
mmm273 said:
Many THANKS !!! It working now !!!
Click to expand...
Click to collapse
Not a problem I'll try and update that section of the guide
My xda app is playing up everytime I click on original post it FC. I'll try on my laptop
Sent from my C2005 using xda app-developers app
Hello
I have installed supersu, and BusyB to xbin and after running supersu.bat (xm is connected in msc mode and pcc is installed correctly) i have that message like on scrrenshot and nothing happens
new version
delete:
Im using framaroot 1.6.0 (even 1.6.1 is out there) and its hals rooting my device (like in the guide)
After all operations i cant edit system files :crying:
Do i have to turn on USB Debugging ? Its not mentioned in the guide but i find it in this thread
http://forum.xda-developers.com/showthread.php?t=2450265
Im asking because i cant check it since 7 pm
i cannot access the server to the tool by anto kus
can anyone provide mirror for that link
thanks
Found it usb debugging needs to be enabled for root fix so enable it
I'll upload the tool when I get in from work I have it on my laptop
Sent from my C2005 using xda premium
aser44 said:
Hello
I have installed supersu, and BusyB to xbin and after running supersu.bat (xm is connected in msc mode and pcc is installed correctly) i have that message like on scrrenshot and nothing happens
Click to expand...
Click to collapse
Make sure USB debugging is enabled and that PCC has installed the drivers. It didn't work for me either but after PCC installed the drivers it found my device.
This message was brought to you by my Sony Xperia M (C1905), using the XDA app.
OK, finally it worked. Everything like in the guide + enabling USB Debugging
Read the full topic before doing anything, I am not responsible for any problem that this may cause to your device!
Information
This will deodex 14.3.A.0.681 firmware for Xperia Z1.
This will work on C6902 / C6903 / C6906 / C6943 (be sure to use the correct version).
Requirements
Xperia Z1 with 14.3.A.0.681 stock KitKat.
Working recovery (Don't have recovery? Try XZDualRecovery by @[NUT])
Instructions
Flash the zip on recovery.
Clear dalvik-cache.
Reboot to system.
Additional info
Before you flash, create a backup on your recovery (in case anything goes wrong).
This won't root your device!
Base files
C6902_14.3.A.0.681_Customized_IN_1277-2364_R4C.ftf
C6903_14.3.A.0.681_Generic_FR_1276-5833_R5C.ftf
C6906_14.3.A.0.681_Generic_CA_1276-7484_R4C.ftf
C6943_14.3.A.0.681_Generic_BR_1276-7099_R4C.ftf
Downloads
For C6902:
File: C6902_14.3.A.0.681_deodex.zip
Size: 440.4 MB
MD5: 599B0631DF52B3509198D3382883529E
For C6903:
File: C6903_14.3.A.0.681_deodex.zip
Size: 449.8 MB
MD5: 74D7CD5F9A9A1B619C65633EB56F8866
For C6906:
File: C6906_14.3.A.0.681_deodex.zip
Size: 426.3 MB
MD5: 1DECD72A08F945DA9C01A4CC2B7F27D7
For C6943:
File: C6943_14.3.A.0.681_deodex.zip
Size: 452.8 MB
MD5: C159CDF636F53A46AB1291E25FEEF431
Enjoy your deodexed KitKat ROM! And please hit "Thanks" if you liked it.
Thank you for bringing Deodexed package for C6902 and all other variants. :good:
Thank you.
Can you write up a quite guide how to deodex for xperia? I tried, but i got error.
tiunilohmu said:
Thank you.
Can you write up a quite guide how to deodex for xperia? I tried, but i got error.
Click to expand...
Click to collapse
I used Android Kitchen v0.224, with smali/baksmali v2.0.3 on a Ubuntu 12.04 environment.
Take a look: http://forum.xda-developers.com/showthread.php?t=633246
Do I have to do a full wipe before flashing a deodex patch?
Is the dedoxed rom pre rooted?
Suryasis said:
Is the dedoxed rom pre rooted?
Click to expand...
Click to collapse
rpcherrera said:
Do I have to do a full wipe before flashing a deodex patch?
Click to expand...
Click to collapse
Deodex patch has script (installer script) which will delete your framework/app/priv-app folder/files (dex and apk) and copy deodexed apk files with right permissions.
So no, you don't have to delete anything, just flash patch and restart
BTW - in 99.9% it's not prerooted because that's not ROM, that's patch.
To be sure you'll preserve recovery and root you can always flash latest recovery by NUT and superSU after flashing deodex patch but before you restart.
Sent from my C6903 using Tapatalk
funky0308 said:
Deodex patch has script (installer script) which will delete your framework/app/priv-app folder/files (dex and apk) and copy deodexed apk files with right permissions.
So no, you don't have to delete anything, just flash patch and restart
BTW - in 99.9% it's not prerooted because that's not ROM, that's patch.
To be sure you'll preserve recovery and root you can always flash latest recovery by NUT and superSU after flashing deodex patch but before you restart.
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Forgive my ignorance, I'm on Stock rooted .681, so if I flash this patch I will lose recovery and root?
rpcherrera said:
Forgive my ignorance, I'm on Stock rooted .681, so if I flash this patch I will lose recovery and root?
Click to expand...
Click to collapse
No...I just said that...
Just flash patch and you'll be fine .
If you are not sure, flash latest recovery after deodex patch and restart to be 100%.
Sent from my C6903 using Tapatalk
funky0308 said:
No...I just said that...
Just flash patch and you'll be fine .
If you are not sure, flash latest recovery after deodex patch and restart to be 100%.
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Done! Also flashed the latest XZDualRecovery.
On 6906 flashing the deodex rom causes FC on both Location service (when choosing Detection accuracy) and on language/input option in settings. Tryed with and without the deodex rom and it is working fine without.
slayer2333 said:
On 6906 flashing the deodex rom causes FC on both Location service (when choosing Detection accuracy) and on language/input option in settings. Tryed with and without the deodex rom and it is working fine without.
Click to expand...
Click to collapse
Can I have the MD5 hash of the zip that you downloaded?
MD5.exe
Place md5.exe and the deodex zip on the same folder, open an elevated prompt window and type:
Code:
md5 C6906_14.3.A.0.681_deodex.zip >> md5.txt
Then open the file md5.txt that is in the same folder now.
I think you downloaded an old zip that was in the topic on the first day, which had Settings.apk deodexed with API 19, which is the right API for KitKat but it force closes in some menus.
The solution come from @krabappel2548 he suggested to deodex Settings.apk using API 16, then I updated the packages for the 4 variants.
Instead of downloading and applying the entire zip you can replace your Settings.apk
Settings.apk
Using a root file explorer, place it on "/system/priv-app" and set the permissions to 0644 (rw-r--r--).
Sent from my Xperia Z1 using Tapatalk Pro
RHBH said:
Can I have the MD5 hash of the zip that you downloaded?
MD5.exe
Place md5.exe and the deodex zip on the same folder, open an elevated prompt window and type:
Code:
md5 C6906_14.3.A.0.681_deodex.zip >> md5.txt
Then open the file md5.txt that is in the same folder now.
I think you downloaded an old zip that was in the topic on the first day, which had Settings.apk deodexed with API 19, which is the right API for KitKat but it force closes in some menus.
The solution come from @krabappel2548 he suggested to deodex Settings.apk using API 16, then I updated the packages for the 4 variants. ]
Instead of downloading and applying the entire zip you can replace your Settings.apk
Settings.apk
Using a root file explorer, place it on "/system/priv-app" and set the permissions to 0644 (rw-r--r--).
Sent from my Xperia Z1 using Tapatalk Pro
Click to expand...
Click to collapse
Here's what i get with your command
Code:
BF0770C607FE311B832D98EE79C3F452 C6906_14.3.A.0.681_deodex.zip
You're right, its different from the actual one. Thanks !
When I flash zip file for my C6902 with CWM (6.0.4.7), my screen is of and on suddenly, nothing happen.
When I do with TWRP, it says "unable to mount system".
My rom's still not deodexed.
What should I do?
Raxtinhax said:
When I flash zip file for my C6902 with CWM (6.0.4.7), my screen is of and on suddenly, nothing happen.
When I do with TWRP, it says "unable to mount system".
My rom's still not deodexed.
What should I do?
Click to expand...
Click to collapse
Are you using XZDualRecovery? Take a look at the version number > External SD Card > XZDualRecovery > XZDR.prop
If it shows something between 2.7.96~2.7.98
Run this as administrator with your phone connected to the computer with Debug mode ON, this will update your XZDualRecovery to version 2.7.99 which fix system mount as writable on KitKat.
C69XX_14.3.A.0.681.patch.zip (9.15MB)
RHBH said:
Are you using XZDualRecovery? Take a look at the version number > External SD Card > XZDualRecovery > XZDR.prop
If it shows something between 2.7.96~2.7.98
Run this as administrator with your phone connected to the computer with Debug mode ON, this will update your XZDualRecovery to version 2.7.99 which fix system mount as writable on KitKat.
C69XX_14.3.A.0.681.patch.zip (9.15MB)
Click to expand...
Click to collapse
I can't find folder XZDualRecovery in my Sdcard folder.
I use this rom so I thought my version is 2.7.99 already.
http://forum.xda-developers.com/showthread.php?t=2687443
Raxtinhax said:
I can't find folder XZDualRecovery in my Sdcard folder.
Click to expand...
Click to collapse
How did you installed recovery on your device?
RHBH said:
How did you installed recovery on your device?
Click to expand...
Click to collapse
I use this rom so I thought my version is 2.7.99 already.
http://forum.xda-developers.com/showthread.php?t=2687443
Oh, I see now. My fault, I was searching in Sdcard while it in Extcard. It doen't say anything about version.
Raxtinhax said:
I use this rom so I thought my version is 2.7.99 already.
http://forum.xda-developers.com/showthread.php?t=2687443
Oh, I see now. My fault, I was searching in Sdcard while it in Extcard. It doen't say anything about version.
Click to expand...
Click to collapse
If you're already on KitKat, flash the patch I posted.
RHBH said:
If you're already on KitKat, flash the patch I posted.
Click to expand...
Click to collapse
But I can't flash your patch.
Just like I said. :crying:
UPDATE: check out TowelRoot app by @geohot! One-click root solution that works with latest firmware released for Xperia M single/dual (provides half-root only, don't forget to apply root fixer)
Nicki Root is deprecated, it got merged in my new dd Flasher tool and works across many devices, not only Xperia M. The attachments and changelog from Nicki Root were kept below for archiving history, but I won't provide support for it anymore. For any problem you may encounter, go to dd Flasher thread. If you want to root Xperia M through dd Flasher, downgrade your device to Android 4.1 or 4.2.2 firmware, root it with Cydia Impactor and follow the instructions from dd Flasher thread.
Changelog
Version 2.0
• Nicki Root now is called dd Flasher
Old versions
Version 1.3.3
• Bugfixes for Linux script
• Updated SuperSU to 2.02
Version 1.3.2
• Make sure the temporary folder exists before pushing the script
Version 1.3.1
• Now compatible with Linux
Version 1.3
• Implement log capabilities (users can pull last log by selecting appropriate option in main menu)
• Drop "reboot in flash mode" (after using dd, system partition layout is different and device can't be rebooted)
• Check if LED can be used to indicate status, otherwise disable it
• Minor code changes
Version 1.2
• Rewrote most of the code
• Script now uses LED to indicate status
• By popular demand, dropped choice command in favour of set command (should work with Windows XP again)
• For every single command, script will now check if it failed or not and warn the user if anything get wrong
• Rewrote the mount/umount routine, loop device is selected automatically and resource busy issues are fixed now
• Can be used with half-rooted devices now (script check if device is fully rooted and apply root fixer at runtime if needed)
• Implemented "reboot in flash mode" command to avoid needing to pull/reinsert battery manually (experimental, sometimes doesn't work)
Version 1.1
• Make sure busybox is installed after first boot (previous versions pushed busybox but didn't install it)
• Drop choice32/choice64 applets and use built-in OS command (Windows XP no longer supported)
Version 1.0.1
• Typo fix (Nicky => Nicki)
• Updated busybox to 1.22.1
Version 1.0
• Initial release
Will test as soon as Indian Firmware Update show up...
Sent from my C2004 using Tapatalk
Well done @mbc07, this is great news. Dont forget to give credit to @joemarshall, afterall, he cane up with the idea . Thanks for testing it and creating this thread, nevertheless
sent from wadiya using my mafroom
I'll be trying this (probably) in the next hour, I'll post results for the Single SIM afterwards.
RESULTS TIME: This method of rooting worked and I am now running 4.3 with root access. Thank you.
Sent from my C1905 using xda app-developers app
Gonna test after I download 4.1.2 ftf, hope it works
rizla2 said:
Gonna test after I download 4.1.2 ftf, hope it works
Click to expand...
Click to collapse
It works perfectly, I'm now rooted on 4.3 thanks to this. The only error I had was when the tool first tried to push the system.ext4 to the SD Card, it said there wasn't enough space, I just deleted the incomplete copy and then ran the tool again and it worked.
Hmm, I'd not thought of mounting the image and doing dd, that is pretty tidy.
Balls, It didn't work for me first try, error mounting the loopback device, said it was busy. I'm re-flashing the phone back to 4.1 now. I've split the shell scripts into 2, first one does the modifications of system.ext4, second one does the dd flash, with a press any key between. That way if the modifications to system.ext4 fail, you're not stuck with an unrooted phone where system partition has already been written, and you can happily start again. I was flashing from sd card if that makes any difference.
Also, would it be possible to copy the reboot executable into your temp folder before you do the dd, so that you don't have to do the battery out reset in the middle of the process, or won't reboot work once you're in that state?
Edit: Second time lucky, thanks ever so much. Maybe I just needed to start from a blank slate version of 4.1, blimey that first boot takes some time though!
cheers,
Joe
mbc07 said:
It took me a lot of time and I tried a lot of methods but I finally managed to root the new 4.3 update without unlocking the bootloader, let's root that thing.
Requirements:
You will need FlashTool and the FTF file of 4.3 update for your phone
You should be running Android 4.1.2/4.2.2 firmware with full root. If you already updated to 4.3, sorry, you'll need to downgrade to 4.1.2/4.2.2 and root it, otherwise this method won't work
You should have at least 1.5GB of free space in your Internal Storage or in your SD Card. If you don't have enough space, the installation will be aborted and your phone will be left intact
Make sure you have full root (eg. your phone doesn't reboot when you remount /system with RW access). Using this method without full root may reboot your phone during the procedure, getting you in a bootloop
Currently the script works only on Windows, I'll try to get a Linux version soon
Getting system.ext4 file: before continuing, we'll need to extract system.ext4 from system.sin present in the update. Open the FTF it with WinRAR or 7-zip and extract system.sin somewhere, then open FlashTool, go to Tools => Sin Editor, locate the system.sin file extracted previously and then click in "Extract Data". You'll get system.ext4 in the same folder you extracted system.sin. Now you're good to go
Procedure:
Download the attached ZIP and unzip its contents somewhere
Move system.ext4 extracted previously to the same folder where root.bat is
Open root.bat and follow the instructions
After the process finished, the script will tell you and your phone will be in a frozen state (it's normal). At that point, you should manually remove the USB cable and then pull/reinsert your battery. DON'T TURN IT ON, we haven't finished yet (turning it on now will get you in a bootloop).
Open FlashTool again and flash the entire 4.3 FTF, but exclude system (if you forget to do so, the root will be removed and you'll need to start over)
After flashing finished, disconnect the USB cable and start your phone. If everything went well you should be in 4.3 now, with full root access
NOTE: I'm not that good with BASH/Shell scripts, and although I had implemented some sanity checks, something may have escaped that checks. So, if you do this procedure and the shell script finish with errors, it's better to start over since something may have not worked and you may be in a partial root state...
Click to expand...
Click to collapse
It worked for me thanks to you
About flashing 4.3 can I do a data and cache wipe?
Wysłane z mojego GT-P3110 przy użyciu Tapatalka
iks8 said:
About flashing 4.3 can I do a data and cache wipe?
Wysłane z mojego GT-P3110 przy użyciu Tapatalka
Click to expand...
Click to collapse
Flashtoll wil wipe data and cache when you flash 4.3 You don't need to do anything else.
paper13579 said:
Well done @mbc07, this is great news. Dont forget to give credit to @joemarshall, afterall, he cane up with the idea . Thanks for testing it and creating this thread, nevertheless
sent from wadiya using my mafroom
Click to expand...
Click to collapse
I still need to rework the OP, many people from Root for FTF 4.3 Update 15.4.A.0.23 LOCKED BOOTLOADER deserves credits, after all I wouldn't have that idea without their replies... Will get these guys credited in the OP soon
joemarshall said:
Hmm, I'd not thought of mounting the image and doing dd, that is pretty tidy.
Balls, It didn't work for me first try, error mounting the loopback device, said it was busy. I'm re-flashing the phone back to 4.1 now. I've split the shell scripts into 2, first one does the modifications of system.ext4, second one does the dd flash, with a press any key between. That way if the modifications to system.ext4 fail, you're not stuck with an unrooted phone where system partition has already been written, and you can happily start again. I was flashing from sd card if that makes any difference.
Also, would it be possible to copy the reboot executable into your temp folder before you do the dd, so that you don't have to do the battery out reset in the middle of the process, or won't reboot work once you're in that state?
Edit: Second time lucky, thanks ever so much. Maybe I just needed to start from a blank slate version of 4.1, blimey that first boot takes some time though!
cheers,
Joe
Click to expand...
Click to collapse
Thank you for the feedback, I'll try to add some sanity checks before using dd. About reboot, I tried using busybox reboot but nothing happened, the same for adb reboot. Apparently after using stop, the reboot command doesn't seems to work
Uh, I forgot... Anybody tried pushing to SD Card? Did it worked?
mbc07 said:
Uh, I forgot... Anybody tried pushing to SD Card? Did it worked?
Click to expand...
Click to collapse
Yes it did, sort of. The first time I did it I got an error saying there wasn't enough space (I had over 10GB free however). Once I got the error I deleted the incomplete file from my SD Card and then I ran the script again, this time it copied the file fully and then installed properly.
This occurred on the Single SIM C1905 Xperia M by the way.
Yes! Finally rooted. Thanks a lot!
Btw don't forget to change usb mode to mtp instead msc (I've tried msc and it can't copy files)
mbc07 said:
I still need to rework the OP, many people from Root for FTF 4.3 Update 15.4.A.0.23 LOCKED BOOTLOADER deserves credits, after all I wouldn't have that idea without their replies... Will get these guys credited in the OP soon
Thank you for the feedback, I'll try to add some sanity checks before using dd. About reboot, I tried using busybox reboot but nothing happened, the same for adb reboot. Apparently after using stop, the reboot command doesn't seems to work
Click to expand...
Click to collapse
At first time i've had also 'mount: mounting /dev/block/loop0 on /data/local/tmp/system failed: Device or res
ource busy'
Flash new, clean Android 4.1 solve problem.
Thank you very much.
Hey guys, does this give you full root?
sent from wadiya using my mafroom
paper13579 said:
Hey guys, does this give you full root?
sent from wadiya using my mafroom
Click to expand...
Click to collapse
Yes it does.
I'll check about the loop device errors (apparently they may occur in Xperia M single SIM), thanks for reporting guys...
paper13579 said:
Hey guys, does this give you full root?
sent from wadiya using my mafroom
Click to expand...
Click to collapse
Yes. I implemented the disable ric service method from [NUT] root fixer too
Man, this is a great achievement, you should be proud. Im about to try it now. Wish me luck
sent from wadiya using my mafroom
Before your script use dd it should check:
1. That there is no any apps mounted in /dev/block/loop0 (for example Swift Key). If yes, you will see 'mount: mounting /dev/block/loop0 on /data/local/tmp/system failed: Device or resource busy' (you can it by type losetup)
2. Phone is in MTP USB MODE. If you set to memory storage mode, Android will not access to sd card with system.ext4 image (script would check that can it access to /sdcard) and you will get mount argument error
well friends, its my first post here on xda.
Eventually I found the easiest way to root D5322 (.472 lollipop 5.0.2 firmware)
and
that is
just run kingroot (I tried english version)
kinguser works like a charm
no need to have superuser or superSU
every app that requires root, works as smooth as butter
like busybox force2SD and all.
I attached the english version of kingroot with this post
those who had rooted their (.470) phone with kingroot and repented later , can also try..
well..
.
.
and if you want to get rid of kinguser that had gotten installed after rooting with kingroot
here is a trick..
I am attaching a zip (thanks to @edwuard )
download that zip
put it in internal memory
extarct that zip in internal memory
now you will get a folder named mrw in your internal memory
..
..
install terminal emulator from market
write the following commands
su
(now grant superuser access)
$ will change in to #
now write the second command
sh /sdcard/mrw/root.sh
(there is space after sh . You can copy this command from here and paste to terminal emulator)
after some sequences in terminal emulator..it will launch SuperSU
and ofcourse remove kinguser
update the binary of superSU
verify root with root checker
.
.
that's it !!
Sequel: Rooting D5322 (Android 5.1.1) :
Well it's for those who have a rooted phone (any previous version) [/COLOR]
Download the ftf file of latest firmware 19.4.A.0.182
Download latest version or V 0.8 of prf creator
Download SuperSU.zip
Now put the prf creator somewhere in your PC (let's say on desktop) extract it there.
Add ftf file and superSU.zip in prf creator
Mark all the boxes on right side of prf creator window
Hit create. In 15-20 minutes you will get a zip file named "flashable" in prf folder
Copy this flashable zip and put it in root of SD card of your phone.
Now reboot your phone in recovery
Follow in sequence :
Wipe>Advanced wipe >select cache,dalvik,system,data, internal memory >swipe to wipe>go back to recovery home>tap install>select external sd card >select that flashable zip>swipe to flash>wipe dalvik>reboot to system.
To install recovery:
Download latest nut's xzdr installer zip
Put it somewhere in your computer
Extract it, you will get a folder of same name
Connect your phone to pc in USB debugging mode
Open the extracted folder
Double click the windows installer batch file
Grant superuser access on your phone's screen
Follow the instructions on terminal
(press 1 on your pc as you have SuperSU in your phone)
After successful instalation of recovery, your phone will reboot into recovery.
Reboot the phone into system
.
.
Now you have a rooted 5.1.1 D5322 with latest Dual recovery.
Thanks alot it's so easy way and it work with me
So easy way
Kinguser Not going off
And i am not able to update to 19.3.A.0.472 stuck on 19.3.A.0.470
I have uploaded the Attachment for it...
plzzzz help
read threads before post
there is already a thread for the same and ask dev before sharing his work
XDA rules
excellent.. 5 stars
awesome... working great
aniket553 said:
And i am not able to update to 19.3.A.0.472 stuck on 19.3.A.0.470
I have uploaded the Attachment for it...
plzzzz help
Click to expand...
Click to collapse
1st I had same problem..
Stucked on . 470
Then I relocked bootloader
Then flashed .472
Then tried above method
Working like charm
Sent from my D5322 using XDA mobile app
Bro did I need to unlock my bootloader to follow this prosiser
............
Zx9. said:
Bro did I need to unlock my bootloader to follow this prosiser
Click to expand...
Click to collapse
No.. You don't need to unlock the bootloader
I'm really interested on following your instructions on how to root this, but first... Will this trick also work on the LTE version?
Sent from my D5303 using XDA Free mobile app
rituraj_singh said:
No.. You don't need to unlock the bootloader
Click to expand...
Click to collapse
Thnx bro ur guide is really easy I successfully rooted my phone yeppy??
kyu0911 said:
I'm really interested on following your instructions on how to root this, but first... Will this trick also work on the LTE version?
Sent from my D5303 using XDA Free mobile app
Click to expand...
Click to collapse
Well.. I don't have D5303, so I haven't tried it on that. You may try.
Zx9. said:
Thnx bro ur guide is really easy I successfully rooted my phone yeppy??
Click to expand...
Click to collapse
That was something I had eventually found..I just shared..
aniket553 said:
And i am not able to update to 19.3.A.0.472 stuck on 19.3.A.0.470
I have uploaded the Attachment for it...
plzzzz help
Click to expand...
Click to collapse
copy the command below
sh /sdcard/mrw/root.sh
paste it to terminal emulator after "su" command
Thank you so much!
Thank you so much for sharing. I can now transfer some of my apps to ext sd card. I can now install more games. Though it can't be changed to supersu using the script and the file you've provided due to unable to update binary, foldermount is working perfectly with kingroot. By the way, I'm using the LTE version D5303 with lollipop .472 and it's now rooted.
Great
Hey can anyone tell how to backup ta partition(dmr keys) on t2 ultra dual d5322 i want to unlock my bootloader.
http://forum.xda-developers.com/showthread.php?t=2292598 use Backup Ta from above link. To backup ta partition
everything working great with this method...
can anyone succeeded installing Xposed properly, working?
rrd84 said:
everything working great with this method...
can anyone succeeded installing Xposed properly, working?
Click to expand...
Click to collapse
The Xposed is not working in our unit, the installation makes the device has bootloops.