[D5503][Stock][PRF+FTF][Lollipop]14.6.A.1.216_CustomizedIN_Pre-Rooted with recovery

Mirhawk

Senior Member
Jan 31, 2014
1,453
635
113
Details:
Code:
Firmware: 14.6.A.1.216_CustomizedIN (R3D)
SuperSU version: STABLE v2.46
Recovery: Z1C-lockeddualrecovery 2.8.21-RELEASE with system mountable patch.
PRF Created using FTF from XperiFirm.

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research or ask questions here if you have any concerns about the work done here
* before flashing it.  Remember that you are choosing to make these modifications,
* and I'm not responsible for what you are doing with your device, and I don't take any
* responsibility of bricked devices or any sort of damage that may be caused by you.
*/
Instructions for flashing:


- Backup your data using recovery or as You always do. Sony Backup and restore may work if You will be backing up on Lollipop and then restoring on Lollipop again.

If You don't have root:

If You are on Lollipop
  1. Flash any 14.4.A.0.108 FTF. You can find one here.
  2. Root using the exploit. You can find the root exploit here.
    • Since You are one .108 firmware already, there it no need to flash the kernel ftf again. Simply run the install.bat in "Root kernel .157.zip>rootkitXperia_20140719.zip"
  3. Install Locked bootloader Dual Recovery by NUT from here. Use Z1C-lockeddualrecoveryX.X.XX-RELEASE.installer.zip.
  4. Download and copy the PRF zip to phone.
  5. Boot into recovery
  6. Wipe the System, Data, Cache, Dalvik cache partitions.
  7. Flash the copied PRF zip.
  8. Wipe Cache and Dalvik Cache
  9. Reboot to phone!
  10. You have got a rooted Lollipop firmware!

If You are on Kitkat:
  1. Root using the exploit. You can find the root exploit here.
    • If You are on .108 firmware, simply run the install.bat in "Root kernel .157.zip>rootkitXperia_20140719.zip".
    • If not, then flash the .108 kernel ftf via flashtool, and then run the install.bat .
  2. Install Locked bootloader Dual Recovery by NUT from here. Use Z1C-lockeddualrecoveryX.X.XX-RELEASE.installer.zip.
    Once You have recovery:
  3. Download and copy the PRF zip to phone.
  4. Boot into recovery
  5. Wipe the System, Data, Cache, Dalvik cache partitions.
  6. Flash the copied PRF zip.
  7. Wipe Cache and Dalvik Cache
  8. Reboot to phone!
  9. You have got a rooted Lollipop firmware!



If You have root:

  1. Backup Your apps and their data. Take only user apps backups, system apps backups are not recommended.
  2. Go to recovery, take a nandroid backup.(optional, but recommended)
  3. Wipe system, data, cache and dalvik cache.(Wiping data can be optional, but is recommended)
  4. Flash the PRF zip.
  5. Restore apps and their data.
  6. At least one reboot is recommended for phone to settle after restoring apps.
  7. Done!



Download Links:
Flashable zip: D5503_14.6.A.1.216_Generic_India-SuperSU_V2.46-lockeddualrecovery_2.8.21-.zip
Firmware used: D5503_14.6.A.1.216_Generic_India.ftf

Credits:
@zxz0O0 for PRFCreator
@Chainfire for SuperSU
@Nut for Recovery

NOTE: If You were using xposed on 5.0.2, it is compulsory that You must uninstall it first. Else You will have bootloops when You enable Xposed on 5.1.1 You might also need to unsinstall SDK21 to install SDK22 for xposed on 5.1.1 .
If Xposed is needed, You can go here.


14.6.A.0.368 version can be found here.
 
Last edited:

awojtas

Senior Member
Apr 20, 2005
334
68
48
Wellington
I've installed it from the previous 5.1.1 and all went smoothly. Xposed works fine.

I feel like the notification bar slides down slightly differently, but that could just be me not noticing the difference before.
The camera opens very quickly.

It appears - very early days yet - to have fixed a wifi <-> mobile data transition issue I had where it would take a minute for mobile data to connect after wifi was disabled. Perhaps if this is a carrier update, then maybe this was a bug that was fixed and only happened on certain carriers.

Haven't noticed any other changes so far.