Related
Just got my sony version - can say this phone is beast mode. There is a pending update to .257 and someone told me that if I update to this, i will be locked out of any ROMs, including any google edition ROM. Can anyone verify this or comment? I have NOT updated to .257 yet.
Thanks in advance.
It's not that dramatic. If you update now, you'll have to downgrade again to 532 if you want to root. You'll need root and Recovery if you want to flash the GPE ROM when it gets released, so you're only saving yourself one step by not updating to 257 now
LordManhattan said:
It's not that dramatic. If you update now, you'll have to downgrade again to 532 if you want to root. You'll need root and Recovery if you want to flash the GPE ROM when it gets released, so you're only saving yourself one step by not updating to 257 now
Click to expand...
Click to collapse
Lord, good to see you again - remember you from the GT-N7000 forum! So since of course I want root, I shouldn't update to .257. Am I understanding this correctly?
LxMxFxD said:
Lord, good to see you again - remember you from the GT-N7000 forum! So since of course I want root, I shouldn't update to .257. Am I understanding this correctly?
Click to expand...
Click to collapse
Correct. There are currently no way to root 257, so we have to root 532 and update through OTA to keep root on 257.
- Use this tool to root
- Install OTA Root Keeper from the Play Store
- Since you've already received the OTA, you don't need to change the CDA in build.prop (to force the OTA), so...
- Update to 257
- The root app (i'm not sure what app it installs) may be gone, so just install SuperSU from the Play Store if it's not in your app drawer.
And you're done...
... unless you also want to unlock the bootloader:
But let's not get ahead of ourselves. You really want to take a backup of your TA partition. It holds all your unique DRM keys, and X-Reality won't work without it. Once you lose it, you can't get it back, so back it up and upload it to your Dropbox or something. So how do you backup your TA partition?
- Download this tiny tool on your computer and run it.
Are you done? Great! Let's move on to the bootloader:
- Go to Sony's dev site
- Request the unlock key and check your mail.
- Install Flashtool on your computer (follow the guide)
- Click the "lightning" icon
- Follow the steps and enter your unlock key
This may wipe your phone, so backup your stuff
And you're done...
... unless you want to install Recovery and TWRP!
Installing Recovery and TWRP is easy. Just run this tool on your computer.
Now you're all set to flash custom ROMs and all that stuff
Lord,
Thanks again. And for anyone googling this thread, you'll need the android SDK to get these scripts running. The android SDK can be downloaded here:
http://developer.android.com/sdk/index.html
Once downloaded and extracted, add it to your environment path.
Actually... You only need ADB and Fastboot. You can install this Windows installer which will do all the work for you. I'm sorry if you installed the entire SDK I should have included it in the guide.
http://forum.xda-developers.com/showthread.php?t=2317790
Sent from my C6833 using Tapatalk
Firmware link (532)
http://forum.xda-developers.com/showthread.php?t=2463701
If the Hong Kong firmware is flashed would the interface be in english?
If not, does anyone have a link to 532 ftf english/international. Thanks.
CptAwesomeTT said:
Firmware link (532)
http://forum.xda-developers.com/showthread.php?t=2463701
If the Hong Kong firmware is flashed would the interface be in english?
If not, does anyone have a link to 532 ftf english/international. Thanks.
Click to expand...
Click to collapse
You can select your language from set up wizard after installing rom. i too downloaded HK fw.
techpal said:
You can select your language from set up wizard after installing rom. i too downloaded HK fw.
Click to expand...
Click to collapse
Thank you very much.
I'm new to Sony flashing. Recently bought a XZU (6833) after learning about GPe release. I havent gotten it as yet but i've spent the last few days reading up on preparing for flashing AOSP roms. I'm still not 100% solid on the steps as information is all over the XZU section, not really organised too well. A lot of the information is out of date and there are many gaps that left me scratching my head...
As far as I can gather, these are the steps a new XZU non GPe edition owner should undergo if they would like to flash GPe roms(or any other)...please correct me if I am wrong.
1) Use flashtool 0.9 to flash older 532 firmware ftf file. (does not require root and can be done on a bone stock device non GPe device regardless of installed firmware version). Link here http://forum.xda-developers.com/showthread.php?t=2463701. Now I know Hong Kong version is ok. 532 is older than 257. 257 cannot be rooted directly hence the need to downgrade first.
2) Root using the Japanese rootkitZ Link: http://forum.xda-developers.com/showthread.php?t=2559009 (I assume this installs Superuser as there is a Superuser APK in the folder)
3) Install root keeper to retain root privilege. https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper. (temporary, must be kept installed at all times or only after OTA? If not doing OTA to 257, is this even necessary?)
4) Backup TA partition with TA backup tool 9.9 to retain original keys for xreality etc.(must be rooted to do this), If partition isnt backed up, these features would be lost forever. This works only with Sony roms anyway so if you plan on only running GPe roms, this isnt necessary?
5) Unlock bootloader using Sony method. Link:http://unlockbootloader.sonymobile.com/
6) Performing OTA update not manditory if flashing to an AOSP rom anyway? I saw mention of changing some build.prop entries for this to before OTA update shows when you check for updates? Is that necessary? If so, what are the changes?
7) Flash cwm/twrp using xzu recovery 4. Link: http://forum.xda-developers.com/showthread.php?t=2426739. The instructions specify to run superuser.bat or supersu.bat. There is only a run.bat file in the folder and this is what you must run After launching there are several options. (If using the root method from step 2, I assume you have to use the SuperUser (option2) when running the tool).
8) Flash any rom (If going back to a Sony rom, must flash to 532 first to get root. Then update through OTA.
Please can someone edit and/or add details where necessary.
---------- Post added at 03:54 PM ---------- Previous post was at 03:40 PM ----------
LxMxFxD said:
Lord,
Thanks again. And for anyone googling this thread, you'll need the android SDK to get these scripts running. The android SDK can be downloaded here:
http://developer.android.com/sdk/index.html
Once downloaded and extracted, add it to your environment path.
Click to expand...
Click to collapse
To what scripts are you referring? Can you help me by fleshing out my above post?
3) Install root keeper to retain root privilege. https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper. (temporary, must be kept installed at all times or only after OTA? If not doing OTA to 257, is this even necessary?)
Click to expand...
Click to collapse
If you're not planning on keeping the stock ROM, and you want to jump straight to a custom ROM, then no, it's not necessary to install OTA Root Keeper.
4) Backup TA partition with TA backup tool 9.9 to retain original keys for xreality etc.(must be rooted to do this), If partition isnt backed up, these features would be lost forever. This works only with Sony roms anyway so if you plan on only running GPe roms, this isnt necessary?
Click to expand...
Click to collapse
You don't need to back it up, but it's recommended even if you're going to use custom ROMs. What if you're having some issues with your ZU, and you have to send it in for repairs? Sony will notice if the DRM keys aren't there and they'll then know that you've unlocked the bootloader.
6) Performing OTA update not manditory if flashing to an AOSP rom anyway? I saw mention of changing some build.prop entries for this to before OTA update shows when you check for updates? Is that necessary? If so, what are the changes?
Click to expand...
Click to collapse
No, this part isn't necessary if you don't want to.
7) Flash cwm/twrp using xzu recovery 4. Link: http://forum.xda-developers.com/showthread.php?t=2426739. The instructions specify to run superuser.bat or supersu.bat. There is only a run.bat file in the folder and this is what you must run After launching there are several options. (If using the root method from step 2, I assume you have to use the SuperUser (option2) when running the tool).
Click to expand...
Click to collapse
Yes, run the bat-file and choose SuperSU in the terminal.
8) Flash any rom (If going back to a Sony rom, must flash to 532 first to get root. Then update through OTA.
Click to expand...
Click to collapse
Before you start flashing custom ROMs, make a NAND backup of the stock ROM. This way, if you want to go back, all you have to do is to flash a boot.img and restore it, and you'll end up exactly where you left off (with root).
I thank you for your patience I understand what you've said so far.Please bear with me a while longer.
Pertaining to point 7, that xzu recovery uses supersu apk so one would have to choose the supersu option and not superuser right?
Next, looking at the omni rom thread (http://forum.xda-developers.com/showthread.php?t=2548107), I am seeing one single download available in the OP (which is the rom itself), however on the last page (http://forum.xda-developers.com/showpost.php?p=48441587&postcount=273), I am seeing people referencing editing changing biuld.prop and flashing boot.img images.
1) How does one know when it is necessary to do any of the above.
2) I am comfortable with editing build.prop but where is the boot.img come from. How do I know when this needs to be flashed?
3) How do you flash the boot.img files? Through cwm or the flashtool?
4) Some gapps come with recovery? Why is that necessary?
A million thanks.
I gotta say, now having the phone for about 12 hours, this phone is simply impressive. I had a nexus 5 briefly which had the same cpu and ram, but it was not as smooth and speedy as the xperia z ultra. I miss the black contrast of the screen of samsung's super amoled but that is about the only thing I miss. Extremely satisfied with my purchase. First sony device.
And thanks to lord and the rest of this community for making getting root so easy!
LxMxFxD said:
I gotta say, now having the phone for about 12 hours, this phone is simply impressive. I had a nexus 5 briefly which had the same cpu and ram, but it was not as smooth and speedy as the xperia z ultra. I miss the black contrast of the screen of samsung's super amoled but that is about the only thing I miss. Extremely satisfied with my purchase. First sony device.
And thanks to lord and the rest of this community for making getting root so easy!
Click to expand...
Click to collapse
I see you're being taken care of welcome dude, good choice of phone, it's a screamer!
Sent from my C6833 using XDA Premium 4 mobile app
CptAwesomeTT said:
I thank you for your patience I understand what you've said so far.Please bear with me a while longer.
Click to expand...
Click to collapse
No problem. I quite enjoy this (yes, i'm weird)
Pertaining to point 7, that xzu recovery uses supersu apk so one would have to choose the supersu option and not superuser right?
Click to expand...
Click to collapse
That depends on which superuser app you're ending up with after rooting. I haven't used that root tool, so i don't know if it installs SuperSu or something else. If it installs SuperSU, then just choose SuperSU when you're going to install Recovery. Superuser isn't really being used that much these days.
Next, looking at the omni rom thread (http://forum.xda-developers.com/showthread.php?t=2548107), I am seeing one single download available in the OP (which is the rom itself), however on the last page (http://forum.xda-developers.com/showpost.php?p=48441587&postcount=273), I am seeing people referencing editing changing biuld.prop and flashing boot.img images.
Click to expand...
Click to collapse
Yeah, there's currently a newer build being built right now, but that shouldn't stop you from flashing it. The thing with the current build is that data isn't working, so that's why you're seeing the talk about build.prop. By modifying the build.prop you'll get the data working again, so after flashing Omni, you should kick it into Airplane Mode ASAP (thorugh the notification center), use a file explorer to move the new build.prop to /system and overwrite the old one (remember to set the correct permissions to 644 or RW-R-R). After that you reboot and data will work again
- Open QuickIMG on your computer and execute fastboot on your Ultra (Power it off and hold Vol Up and plug your USB in at the same time. A Blue LED will turn on over you screen)
- Flash boot.img and after you're done, boot into Recovery (Power + Vol Up [or power it on as usual and when the Green LED turns on press and hold VOL UP until the light turns purple])
- Wipe everything
- Flash Omni and gapps
- Reboot
2) I am comfortable with editing build.prop but where is the boot.img come from. How do I know when this needs to be flashed?
Click to expand...
Click to collapse
The only times you'll have to flash boot.img is when you're coming from stock ROM and you want to jump over to AOSP (Omni, CM etc.) and when you want to go back to stock. You'll have to do it now when you're going to flash Omni. You don't have to do it when you're updating the ROM, or if you're going to flash CM, PAC or any other AOSP builds.
3) How do you flash the boot.img files? Through cwm or the flashtool?
Click to expand...
Click to collapse
You can use QuickIMG, which is probably the easiest way. After you've flashed boot.img, flash Omni and gapps as usual. Have both of them on your device before you flash the boot.img
4) Some gapps come with recovery? Why is that necessary?
Click to expand...
Click to collapse
That's not right. Kernels come with recovery. Gapps are only Google Apps (Play Store, Maps etc.)
I'm thinking of flashing Omni today myself, so you'll probably read a lot (of cursing) from me around these parts later today :laugh: If you have some other questions, feel free to ask.
LordManhattan said:
No problem. I quite enjoy this (yes, i'm weird)
That depends on which superuser app you're ending up with after rooting. I haven't used that root tool, so i don't know if it installs SuperSu or something else. If it installs SuperSU, then just choose SuperSU when you're going to install Recovery. Superuser isn't really being used that much these days.
Yeah, there's currently a newer build being built right now, but that shouldn't stop you from flashing it. The thing with the current build is that data isn't working, so that's why you're seeing the talk about build.prop. By modifying the build.prop you'll get the data working again, so after flashing Omni, you should kick it into Airplane Mode ASAP (thorugh the notification center), use a file explorer to move the new build.prop to /system and overwrite the old one (remember to set the correct permissions to 644 or RW-R-R). After that you reboot and data will work again
- Open QuickIMG on your computer and execute fastboot on your Ultra (Power it off and hold Vol Up and plug your USB in at the same time. A Blue LED will turn on over you screen)
- Flash boot.img and after you're done, boot into Recovery (Power + Vol Up [or power it on as usual and when the Green LED turns on press and hold VOL UP until the light turns purple])
- Wipe everything
- Flash Omni and gapps
- Reboot
The only times you'll have to flash boot.img is when you're coming from stock ROM and you want to jump over to AOSP (Omni, CM etc.) and when you want to go back to stock. You'll have to do it now when you're going to flash Omni. You don't have to do it when you're updating the ROM, or if you're going to flash CM, PAC or any other AOSP builds.
You can use QuickIMG, which is probably the easiest way. After you've flashed boot.img, flash Omni and gapps as usual. Have both of them on your device before you flash the boot.img
That's not right. Kernels come with recovery. Gapps are only Google Apps (Play Store, Maps etc.)
I'm thinking of flashing Omni today myself, so you'll probably read a lot (of cursing) from me around these parts later today :laugh: If you have some other questions, feel free to ask.
Click to expand...
Click to collapse
Oh man you are so damn helpful!
Ok again I got 95% of what you said. Just to clarify:
Coming from a stock rom, going to an AOSP rom requires you to flash boot.ini prior to flashing the aosp rom. Is it correct to assume that that the boot.img in this case should be extracted from the destination (aosp) rom?
Lastly, other than the rootkitZ Japanese method of rooting an older firmware (532), what is your recommended method of acquiring root?
CptAwesomeTT said:
Oh man you are so damn helpful!
Ok again I got 95% of what you said. Just to clarify:
Coming from a stock rom, going to an AOSP rom requires you to flash boot.ini prior to flashing the aosp rom. Is it correct to assume that that the boot.img in this case should be extracted from the destination (aosp) rom?
Lastly, other than the rootkitZ Japanese method of rooting an older firmware (532), what is your recommended method of acquiring root?
Click to expand...
Click to collapse
Yeah, just do this (i did it myself 30 minutes ago)
- Download the boot.img from here (this one is from the PAC ROM and works great)
- Download QuickIMG from here (and just follow the short guide)
Once you've flashed the boot.img:
- Unplug your Ultra and power it off (in case it powers on, press and hold POWER + VOL UP until you notice some rapid vibrations)
- Now Power it on again and press and hold VOL UP when the LED lights up (green i believe, and it should go purple)
- Once you're in Recovery, flash Omni and gapps (don't forget to wipe data and dalvik (under advance) before rebooting
This one is something i learned myself half an hour ago; pull your SIM out until you've had the chance to replace the build.prop, or else it'll just reboot by itself.
And yes, the japanese rooting tool is the recommended tool. The other ones aren't safe (IMEI collectors)
LordManhattan said:
Yeah, just do this (i did it myself 30 minutes ago)
- Download the boot.img from here (this one is from the PAC ROM and works great)
- Download QuickIMG from here (and just follow the short guide)
Once you've flashed the boot.img:
- Unplug your Ultra and power it off (in case it powers on, press and hold POWER + VOL UP until you notice some rapid vibrations)
- Now Power it on again and press and hold VOL UP when the LED lights up (green i believe, and it should go purple)
- Once you're in Recovery, flash Omni and gapps (don't forget to wipe data and dalvik (under advance) before rebooting
This one is something i learned myself half an hour ago; pull your SIM out until you've had the chance to replace the build.prop, or else it'll just reboot by itself.
And yes, the japanese rooting tool is the recommended tool. The other ones aren't safe (IMEI collectors)
Click to expand...
Click to collapse
You've been so helpful. I think that's all my questions until I actually get the device in hand and start working on it. Thanks a mill.
atm the jap root method is the one I'd use. kingo might be safe and vroot might not be...
Use the one in the zip or download the v4 or v5 boot.img
v4 http://forum.xda-developers.com/showthread.php?t=2426739
v5 http://forum.xda-developers.com/showthread.php?t=2426736
if going to omni i would flash the revolution kernel http://forum.xda-developers.com/showthread.php?t=2548092
No problem!
CptAwesomeTT said:
Firmware link (532)
http://forum.xda-developers.com/showthread.php?t=2463701
If the Hong Kong firmware is flashed would the interface be in english?
If not, does anyone have a link to 532 ftf english/international. Thanks.
Click to expand...
Click to collapse
Link to .532 is gone. Is there another?
Thanks!
All you need to know about Owning a Z2
-------------------------
INDEX
How to root
How to Unlock your bootloader
How to "Unbrick your Device"
Guide to Flashing Custom ROMs
How to install Custom Recovery"[UB]"
FAQ
FTF Compilation
-------------------------
DisclaimerBy following any guides on this thread you are doing this at your own will so if you brick your device i am not at fault as you chose to do this. only your self can be blamed for incorrectly following the steps a guide
-Introduction to this threadthis thread is a help/info/reference thread to where you can find alot of what you need to know, if there isnt what you know ask or point out ill update the thread as soon as
Also Feel free to ask any questions here, even if they may be as silly! this is XDA and XDA developers is a place of learning and teaching and many other things
-Introduction to who i amnothing special here
move along citizen
-1.
How to Root
By modifying your device you are voiding your warrenty, unlocking your bootloader is concidered modifying your device and will void your Warrenty from seller and your Default Xperia Z2, 2 year warrrenty
Downgrade PRF Creator Method
http://forum.xda-developers.com/showthread.php?t=2933155
Easy Root Tool(this has been noted to work on the latest update)
http://forum.xda-developers.com/showthread.php?t=2784900
Root Tool For locked Bootloaders
http://forum.xda-developers.com/showthread.php?t=2559009
Bin4ry Root
http://forum.xda-developers.com/showthread.php?t=1886460
Recovery For locked bootloaders:
http://forum.xda-developers.com/showthread.php?t=2785598
Downgrade method
1. Flash a Older Version of firmware that can be rooted via root tool
2. Install recovery for locked bootloader
3. Make a PreRooted Zip using PRF CREATOR
4. Flash that zip along with recovery.
5. done.
-2.
-Commonly Asked Questions
Q. Why do my Apple Earphones not work?
A. Alot of headphones dont work, it seems they work on 314 fw but not 402, perhaps try upgrading?
Q. Why does my NC headphones get Quieter when i turn on Nc
A. i do believe that because the Nc headphones are shooting counteracting wave frequencys which affect your ears but cant hear, they limit the volume for safety.
Q. What would you recomend to a newbie flasher?
A. ALWAYS keep a copy of a stock rom on your device
A. Backup often, sometimes you have to lose your data
A. Keep flashtool and a FTF at hand, it will save your Z2
A. Come here for info, your here reading this and learning arent you now?
A. Unlock your bootloader before flashing non stock based roms please
A. Non stock based example: CM11 , Slim Rom, AOSP, Envi-OS Touch, Ubuntu touch!
A. NEVER blame the devs unless they LIED TO YOU!
A. READ THE INSTRUCTIONS
A. READ THE DISCLAIMER
A. BUY ME ICE CREAM
A. Any thing else SEARCH, cant find it, SEARCH AGAIN, still cant find it?, ASK!!!
Q. I have flash CM11 but the camera does not work and the touch doesn't work after the screen turns off, what is the problem?
A. Its CM11, official, Unofficial and FXP unofficial all are not fully working, i recommend you go back to stock for now.
(10th of July 2014)
Q. How do i debrand my device
A. Debranding is just the removal of branding, you can debrand by flashing a unbranded FTF/Rom or by deleting branded apps and/or files from your ROM using root
Q. If i flash a branded FTF to an unbranded Device, do i have to worry about simlock or anything to do with the brand?
A. Nope.. Not at all, you will have apps n stuff but there shouldn't be any simlock
Q. i have a problem and im not sure if its normal how do i tell
A. It depends on what realy, post here or in the QnA section your question
Q. Why should i Buy a Z2 over a S5 or M8
A. Its down to what you want more, xperia Z2 has a simple, elegant and stylish look with a Lightweight UI which is packed with features whilst not being overpacked or left empty
Q. WHY is overclocking dangerous
A. Because you can burn out your CPU and any device without that is useless!
Q.Why shouldent i ask for ETA From a dev?
A. Because Usualy Devs dont even know when they are going to be done
Q. Can i use an xposed module made for another xperia?
A. Yes if that xperia has the same version of android as yours
Q. What is a bootloader?
A.it is a program that loads an operating system when a computer or phone is turned on.
Q. Could you explain a bootloader, locked or unlocked or well whats it about.
A. like mentioned in the FA Question above its the program that starts your system now with android the kernel is contained within the bootloader where as just the bootmanager which would be a PC, your bootloader is locked by a sort of verifacation system so when you remove of that it doesent verify or when it does it doesnt have anything to copare it to, that is unlocking your bootloader ( or what ive been told )
Q. Can i install a custom kernel on a locked bootloader?
A. not at all! dont even try it either, it will brick your xperia!
Q. What do you mean brick your device?
A. read this http://en.wikipedia.org/wiki/Brick_(electronics)
A. Brick in simple words means a dead phone
Q. Does unlocking your bootloader break X-Reality?
A. it Apears to Break X-Reality and Bionz
Q. Can i flash A Z2 kernel on to Z2 tablet or vice versa?
A. kernels are device specific. you cant flash a Z2 kernel to Z2 tablet or any other device.
Q. If my bootloader isnt unlockable is there a way to root?
A. There is a link at the top of the thread called index
Q. can i make my bootloader unlockable if it isn't?
A. no.
(try swapping your Z2 for a unlockable one)
Q. is there any ways to fix the overheating with my Z2?
A. as far as i have seen and know ... No not yet
Q. if i flash a rom from my Samsung to my Z2 will it work?
A. Never, it will brick you phone, Z2 roms only work on Z2 and Samsung or any other device roms wont work on a Z2 unless they are ported to Xperia Z2.
Q. my Xperia Z2 overheats when im using the camera, is there any fix
A. there is a workaround but its dangerous and i do not recoment
(this can be found in development sections)
if a question isnt up here ASK!
Recovering from a brick
-3.
How to recover your device from almost any kind of brick
Requirements
Flashtool
FTF of choice for your device
2 Rubber bands (I am serious but only if your device has no response)
Downloads
FTFs
http://forum.xda-developers.com/showthread.php?t=2759934
Flashtool
http://www.flashtool.net/download.php
Requirements
Flashtool downloaded and installed
a FTF file downloaded
your ftf file placed in /flashtool/firmwares/ folder
drivers installed (check drivers.exe in the drivers folder)
Part 1
1. unplug your device from anything
2. open flashtool on your pc
3. plug your cable into your PC
4. do not plug the cable into your device
Part 2
1. Open the Flap on the Left Side of your device
2. Press and hold the RED Button for 30 secionds
3. Your device should buzz 3 times
4. If this does NOT work then find 2 rubber bands
5. once you have found 2 rubber bands put them around your device holding the volume up and power buttons
6. Wait for it to buzz 3 times.
7. continue.
if it does not take a few seconds then you need to put a rubber band around your device holding your power button and your volume up button, DO NOT LEAVE MORE THAN IT NEEDS TO BE LEFT, wait patiently for your device to buzz 3 times
Part 3
1. once your device has buzzed 3 times you are free to flash a FTF as your device is powered off
Part 4
1. if you dont know how to flash a FTF but have gotten as far as installing flashtool,Z2 drivers and downloading a FTF FOR YOUR DEVICE... then folow this step
2. within your flashtool window click on the lightning icon at the top left
3. select flashmode
4. navigate to where you downloaded your FTF (OR put your FTF in your /flashtool/firmwares folder)
5. select your FTF
6. Flashtool should give you a prompt to plug in your device
7. hold volume down and plug in your device
Part 5
1. wait for it to finish flashing
Part 6
1. your device is now recovered, enjoy...
Part 7 - Aditional Info
if all fails contact your insurance and ask for a replacement as sony may give you a replacement however you may be charged
if you cant afford it you can buy a new xperia Z2
if this happened without any modifacations aka by its self, then contact sony support as you are entitled to a free repair under Sony Xperia warrenty (2 years) which is given to all Sony Mobile Xperia Phones
-4.
- Unlocking your bootloader
Unlocking your bootloader is the allows custom kernels to be installed. it apears only X-Reality is broken along with Few Xperia Services Such as PlayStation Remote Play.
Unlocking your bootloader does wipe your TA partition and also your data and internal storage
Take note that Unlocking your bootloader will void your warrenty. some services do not care if your bootloaders are relock however some check if your DRM keys are existent.
Any modifacation to your device will imediately void your 2 year warrenty that comes with all Xperias given that you have proof of purchase.
-- How to unlock your bootloader
you can follow these instructions
http://unlockbootloader.sonymobile.com/
or
these instructions
http://forum.xda-developers.com/showthread.php?t=2440597
Note that with the Xpria Z2 you can root without unlocking your bootloader this means that you can back up your TA (Check Index for how to root )
-- How to Relock your bootloader
http://forum.xda-developers.com/showpost.php?p=45496437&postcount=2
Relocking your bootloader does not get your DRM keys back
Guide to Flashing
Guide to Flashing For Locked BootLoaders
1. Root and Recover
http://forum.xda-developers.com/showpost.php?p=53220418&postcount=2
to get a recovery which is needed to flash a rom you will need root first.
There is a link above which provides more links to 3 Different root Tools and a Recovery installer for Locked bootloader And unlocked
2. Pick a Rom
So once you have rooted and installed Recovery you can go ahead and find your self a rom to flash
Here is an Index of Roms/mods/tweaks/kernels -> Click me
3. Pre-Flashing stuff
so once you've downloaded it, you want to go and put the ZIP file on your Xperia Z2
you also want to download this and put it on your phone too -> click me Credit to @[NUT] as this is his creation ->Click Me for the full thread
Now that we have everything Ready to GO, lets Get flashing!
4. Flashing the Rom
this will be the Common process for flashing any Stock-Based Custom roms since all Stock-Based roms are for locked bootloader.
Flashing a Rom for Unlocked bootloader only on your Locked bootloader Device will brick your device.
A. Download ROM
B. Put ROM on Phone
C. Turn off Phone
D. Power on the phone and press volume Down when the light shows or keep pressing it while the Sony Logo Shows
#this will enter the recovery menu you installed earlier
~ you may want to click backup and backup your current System and Data
- You can restore at a later date if the rom your using is causing you problems
E. Click Install
F. Navigate to where you put your ROM and The Second file we Downloaded
G. Select the ROM then Click "Add more Zips" and add the other file we downloaded
H. simply Swipe to Confirm Flash
J. Once thats done click on "wipe cache/dalvik" and Swipe to confirm
K.. finaly you are good to go
-Simply Click Reboot and Enjoy your Custom rom
L. if your phone keeps starting up halfway and turning off and then restarting then you will have to go back into your Recovery
M. once your in the recovery menu again, Click Wipe and then Swipe, you are Wiping the user Data because some Stock bases roms such as "MIUI" may need it
N. if you installed a Rom for Unlocked bootloader and your Device isnt responding, try this guide to fix that -> Click here
O. not sure what else to put here
P. if i remember ill put something here
Useful Links
Forum Rules and guidelines (for new people)
http://forum.xda-developers.com/showthread.php?t=2668689
A bunch of FTFs (some useful for someone )
http://forum.xda-developers.com/showthread.php?t=2759934
How to Fix Noise Canceling
http://forum.xda-developers.com/showpost.php?p=54730368&postcount=5
Digital Rights Management info(DRM keys - information)
http://forum.xda-developers.com/showthread.php?t=2743240
SuperSU thread
http://forum.xda-developers.com/showthread.php?t=1538053
Flashtool website
http://flashtool.net
info about android and linux
http://en.wikipedia.org/wiki/Android_(operating_system)
http://en.wikipedia.org/wiki/Linux
Index of roms/kernels and tweaks thanks to @sud.vastav
http://forum.xda-developers.com/showthread.php?t=2765461
probably add some others if i remember to
Can Philz recovery be used instead of the standard CWM one? I know DoomLord made a thread saying it had been ported over unofficially but there hasn't really been any posts in that thread since 30th May. Philz recovery was always my fav to use on my GS3. Ideally I would like to flash Philz recovery & just keep the stock rom & kernel & root to block ads & change DPI & also use MyBackup Pro to it's full potential.
Thanks for posting all the info in one centralised thread though
BanziBaby said:
Can Philz recovery be used instead of the standard CWM one? I know DoomLord made a thread saying it had been ported over unofficially but there hasn't really been any posts in that thread since 30th May. Philz recovery was always my fav to use on my GS3. Ideally I would like to flash Philz recovery & just keep the stock rom & kernel & root to block ads & change DPI & also use MyBackup Pro to it's full potential.
Thanks for posting all the info in one centralised thread though
Click to expand...
Click to collapse
,yes Philz can be used too instead of cwm, if you know how to flash and so on
Ill update OP thread
Sent from my D6503 using XDA Premium 4 mobile app
Envious_Data said:
Q. Can i flash A Z2 kernel on to Z2 tablet or vice versa?
A. no kernels are device specific
Click to expand...
Click to collapse
Do you mean "no, kernels are device specific" or that no kernel is device specific, meaning you can use kernels made for Z2 and the Z2 tablet?
leocooper said:
Do you mean "no, kernels are device specific" or that no kernel is device specific, meaning you can use kernels made for Z2 and the Z2 tablet?
Click to expand...
Click to collapse
Oh grammar, kernels are device spesific aka Z2 kernel only works on Z2 and not tablet although they are almost the same on the inside
Time to update the thread thanks for pointing that out
Sent from my D6503 using XDA Premium 4 mobile app
Great guides! Thank you so much for doing this
Envious_Data said:
All you need to know about Owning a Z2...
Click to expand...
Click to collapse
Great info! Reckon you could also add, like, a section with obscure/hidden general productivity tips for the phone as well?
For example:
If you press and hold the right-hand side of the notification bar, it will change to quick settings allowing you to then swipe down for the quick settings.
From the home page, if you swipe from the very edge of a side of the screen, you can scroll 2 pages at once.
Etc.
@PulpDood
If you could write a post here with a list of secret features ill add to the index of the thread
Here is one for you
Press the page indicators to quickly scroll across pages in your home screen
Thanks if you do, credits to you
Edit-ill do later
Sent from my D6503 using XDA Premium 4 mobile app
Screen rotation
Not sure if this is for on here or not but is it possible to have the screen rotation for the stock launcher on all the time and not just when a magnetic charger is connected? (I know other launchers are available)
evolutionisbad said:
Not sure if this is for on here or not but is it possible to have the screen rotation for the stock launcher on all the time and not just when a magnetic charger is connected? (I know other launchers are available)
Click to expand...
Click to collapse
It seems there is a bug when you force rotate however ive found a soution. The problem is that you need root
You need to download and install
Xposed installer
Xperia rotation and multiline lables (this is the module name btw)
Gravity box(KK) can be used to rotate the lockscreen of which this require xposed too
Hope this helps
Sent from my D6503 using XDA Premium 4 mobile app
Envious_Data said:
It seems there is a bug when you force rotate however ive found a soution. The problem is that you need root
You need to download and install
Xposed installer
Xperia rotation and multiline lables (this is the module name btw)
Gravity box(KK) can be used to rotate the lockscreen of which this require xposed too
Hope this helps
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, disappointing I have to root. I like to use stock for a while before I start to tamper with it
Actually thought I wouldn't need to root this as all I used root for was greenify but stamina mode seems to have better results.
Edit - found an app seems to work https://play.google.com/store/apps/details?id=com.spydiko.rotationmanager
Thanks again
I have already spammed the thanks button for you mate in this thread but your great simple guide now has my bootloader unlocked & rooted & booted as they say
Does yourself or anyone else knowa good app to edit the DPI to a setting that wont cause issues with play store or apps or games or what would be the best setting to use for editing the build prop file? I know the default is about 480 Previous device was galaxy s3 which by default was 320 but I always changed it to 240 or 245.
BanziBaby said:
I have already spammed the thanks button for you mate in this thread but your great simple guide now has my bootloader unlocked & rooted & booted as they say
Does yourself or anyone else knowa good app to edit the DPI to a setting that wont cause issues with play store or apps or games or what would be the best setting to use for editing the build prop file? I know the default is about 480 Previous device was galaxy s3 which by default was 320 but I always changed it to 240 or 245.
Click to expand...
Click to collapse
I usualy use xplore, you have to enable superuser in the settings but the app is functional enough for file management
Default DPI is 480, some people said 460 n stuff like that is a nicer dpi to use, hvnt realy tried my self
Edit- you also have to give credit to the ppl who wrote the other threads who i liked here
Sent from my D6503 using XDA Premium 4 mobile app
Of course mate, credits to all that wrote the info in your links, I just found the way you laid your guide out was much easier to follow, the thanks to yourself was collecting all the info in one handy thread
What is this?
This is my Custom Rom built from Unova Ironman Firmware V1.1(2.2) 20141016
-This use a 3.4.67 Kernel
-For all those who have problems in installing via SP Flash Tool this is the easiest solution for updating the device to version 4.4.2. Besides being the basis for a custom rom is easily editable and customizable by anyone who wants
-Includes "Unova +" App for bluetooth notifications ( must install on your phone Unova Remind from Playstore and pairing the two devices)
Changes:
• Fix local setting
• Fix Auto reboot in startup
• Fix SystemUI crash
• Remove chinese App
• Include micro Gapps
• Volume control with Home button
• Home button replacing with Swipe App
• Fully rooted
• Flashable Zip Rom
Whats working:
• Phone
• Companion
• Data: 2G/3G
• Wi-Fi
• Bluetooth
• GPS/AGPS
• All other
Not Working/Bugs:
• SENSORS
Requires
• Latest TWRP installed on device
• Highly recommended flash the Rom starting from your Stock Rom (preserve the original partitions, NVRAM, etc) but not strictly necessary as it can also be installed on any version of firmware
Installation Instructions - DOWNLOAD ROM VERSION 1.1
1. download: Google-Drive - Mirror: Dev-Host
2. Copy "X201-KK-V1.1.zip" to Internal Storage
3. Restart device in recovery mode
4. Full Wipe
5. Install "X201-KK-V1.1.zip"
6. Wait for the installation
7. Restart after the first boot
Disclamer
This ROM is tested by me on Iconbit Callisto 100 but it can work on all units (4GB / 512MB 2100MHZ)
Obviously I do not assume any responsibility
Credits
-TeamWin Projects for TWRP
-User "acidbr" for sharing the Ironman Firmware http://forum.xda-developers.com/showpost.php?p=58693313&postcount=225
Can you post the Unova+ app here?
Never mind. Found it on Play Store.
Can you please post it somewhere where not EZDownloaderPro infects the download?
It takes ages to clean, I consider that a virus...
For the documentation:
Is the upgrade working when going directly from 4.2?
I have always had to Upgrade in SPFT.
Good if it is working using SPFT to only flash TWRP.
Have you noticed any changes in the ROM compared to the package kuronosan put together?
(You have done some changes to.)
I tried the Ironman ROM but did not see anything really.
gerhardo said:
Can you please post it somewhere where not EZDownloaderPro infects the download?
It takes ages to clean, I consider that a virus...
For the documentation:
Is the upgrade working when going directly from 4.2?
I have always had to Upgrade in SPFT.
Good if it is working using SPFT to only flash TWRP.
Have you noticed any changes in the ROM compared to the package kuronosan put together?
(You have done some changes to.)
I tried the Ironman ROM but did not see anything really.
Click to expand...
Click to collapse
I'll see if can upload somewhere else when I have time.
If any user wants to go before I can do that easily. thank him
You no longer need to use SPFT, you just flash my Rom. (Contains everything you need for a Firmware Upgrade) Council from stock 4.2 to get everything sorted but not strictly necessary. Can flash any version of departure.
I do not know which changes from the previous Unova Firmware because I come from the firmware Zgpax s8 modified by me.
Greetings
Hello
First of all, thanks you for your hard work.
I'd like to update my Truesmart 4.2 (512MB 2100MHZ) to 4.4 using your firmware. I'm quite ashamed to say it, but can you give me a step by step instructions please?
Not like I didn't try to search, but I find it quite hard. I don't know how to install TWRP. My unit is not rooted.
Can you confirm the step that I'm going to take ?
1) downloading openrecovery-twrp-2.7.1.0-omatesmartwatch2.img
2) Flashing my omate with this image thanks to MTK Flash Tool
3) Following your instructions
=> Concerning the 'Install Zip', do you mean 'ZipInstaller 5.0.3' ?
Between, I don't have window at all, I'm only using linux on my computer. I got a virtual console with windows, but the com and ADP port are not working there, if you have a solution to install TWRP not to using MTK Flash Tool (or windows), I'd be glad.
Thanks you for your advices !
shideneyu said:
Hello
First of all, thanks you for your hard work.
I'd like to update my Truesmart 4.2 (512MB 2100MHZ) to 4.4 using your firmware. I'm quite ashamed to say it, but can you give me a step by step instructions please?
Not like I didn't try to search, but I find it quite hard. I don't know how to install TWRP. My unit is not rooted.
Can you confirm the step that I'm going to take ?
1) downloading openrecovery-twrp-2.7.1.0-omatesmartwatch2.img
2) Flashing my omate with this image thanks to MTK Flash Tool
3) Following your instructions
=> Concerning the 'Install Zip', do you mean 'ZipInstaller 5.0.3' ?
Between, I don't have window at all, I'm only using linux on my computer. I got a virtual console with windows, but the com and ADP port are not working there, if you have a solution to install TWRP not to using MTK Flash Tool (or windows), I'd be glad.
Thanks you for your advices !
Click to expand...
Click to collapse
I proceeded to further clarify the installation instructions.
As for the installation of the Recovery google is your friend. Will surely find a way to install the recovery using Linux terminal
gerhardo said:
Can you please post it somewhere where not EZDownloaderPro infects the download?
It takes ages to clean, I consider that a virus...
For the documentation:
Is the upgrade working when going directly from 4.2?
I have always had to Upgrade in SPFT.
Good if it is working using SPFT to only flash TWRP.
Have you noticed any changes in the ROM compared to the package kuronosan put together?
(You have done some changes to.)
I tried the Ironman ROM but did not see anything really.
Click to expand...
Click to collapse
Upload rom on Google Drive :good:
rik81 said:
What is this?
This is my Custom Rom built from Unova Ironman Firmware V1.1(2.2) 20141016
-This use a 3.4.67 Kernel
-For all those who have problems in installing via SP Flash Tool this is the easiest solution for updating the device to version 4.4.2. Besides being the basis for a custom rom is easily editable and customizable by anyone who wants
-Includes "Unova +" App for bluetooth notifications ( must install on your phone Unova Remind from Playstore and pairing the two devices)
Changes:
• Fix local setting
• Fix Auto reboot in startup
• Fix SystemUI crash
• Remove chinese App
• Include micro Gapps
• Volume control with Home button
• Home button replacing with Swipe App
• Fully rooted
• Flashable Zip Rom
Whats working:
• Phone
• Companion
• Data: 2G/3G
• Wi-Fi
• Bluetooth
• GPS/AGPS
• All other
Not Working/Bugs:
• SENSORS
Requires
• Latest TWRP installed on device
• Highly recommended flash the Rom starting from your Stock Rom (preserve the original partitions, NVRAM, etc) but not strictly necessary as it can also be installed on any version of firmware
Installation Instructions - DOWNLOAD ROM VERSION 1.1
1. download: Google-Drive - Mirror: Dev-Host
2. Copy "X201-KK-V1.1.zip" to Internal Storage
3. Restart device in recovery mode
4. Full Wipe
5. Install "X201-KK-V1.1.zip"
6. Wait for the installation
7. Restart after the first boot
Disclamer
This ROM is tested by me on Iconbit Callisto 100 but it can work on all units (4GB / 512MB 2100MHZ)
Obviously I do not assume any responsibility
Credits
-TeamWin Projects for TWRP
-User "acidbr" for sharing the Ironman Firmware http://forum.xda-developers.com/showpost.php?p=58693313&postcount=225
Click to expand...
Click to collapse
Does this method stop 2G EDGE and make the signal appear?
Does not work for me on my north american model. I only get the boot logo forever.
stanelie said:
Does not work for me on my north american model. I only get the boot logo forever.
Click to expand...
Click to collapse
Sorry, only 512/4GB 2100Mhz EU version
rik81 said:
Sorry, only 512/4GB 2100Mhz EU version
Click to expand...
Click to collapse
Why does the Rom not work the 1GB EU version?
rik81 said:
Sorry, only 512/4GB 2100Mhz EU version
Click to expand...
Click to collapse
Works fine with my 1/8 May EU edition.
(still kind of testing, not noting much difference to the x202 ROM. I do not like HomeSwipe, that is a personal preference...)
gerhardo said:
Works fine with my 1/8 May EU edition.
(still kind of testing, not noting much difference to the x202 ROM. I do not like HomeSwipe, that is a personal preference...)
Click to expand...
Click to collapse
Well thank you for your feedback. I can only guarantee the version 512 / 4GB because in my possession, and I have personally tested. I do not know if the system partition and the kernel are the same. Now we know it.
Regarding the Home button could make a fix
rik81 said:
Well thank you for your feedback. I can only guarantee the version 512 / 4GB because in my possession, and I have personally tested. I do not know if the system partition and the kernel are the same. Now we know it.
Regarding the Home button could make a fix
Click to expand...
Click to collapse
Great ROM.
The Home button action can be overridden with Xposed Addtions module. It's good enough for me.
I wrote a small Xposed module to permanently enable the status bar in Nova Launcher (and most other launchers):
http://forum.xda-developers.com/xposed/modules/truesmart-status-bar-custom-launchers-t3063624
The module is only tested with your ROM. It might not work if GravityBox is enabled as well, I'm investigating that issue.
If you don't want to install Xposed I can provide recovery flashable zip's for enabling the status bar in either all apps or a specific launcher.
Help! my x201 is blocked on the logo UNOVA
Hello
I was on last firmware inconbit Callisto 100 and I tried to install "X201-KK-V1.1.zip" but I probably failed installing last TWRP. My watch is fixed on logo UNOVA and is not recognized on usb neither with SPFlash tool or MtkDroïd tools. The TWRP recovery dont see my Sdcard where I have my backup (Titanium). What can I do to awake my watch UMEOX x201 512/4 2100EU ?
Thanks a lot for helping me!
Hello,
What do i have to do with my omate truesmart after have change the file system\usr\keylayout\mtk-kpd.kl to the changes take effect?
I want key 102 to home button, like it is by default on the watch in the origin and every other roms.
I have already save and overwrite the file after changes, and then reboot omate, but still not working.
Thank you
My felicitations for your great job on this rom, and i have a question
First of all, i want to give you all my felicitations for your work and your rom unova kk for omate truesmart, it is very stable, fast, and battery saver compared to a lot of other roms.
I have European Model 2100 mhz of omate truesmart with 1 gb ram and 8 bg rom.
The only problem that i have with your rom is that i don't want that the home button put volume up, and i want it to go home like default.
How can i do to change it?
I already go to system\usr\keylayout\mtk-kpd.kl and changed the button 102 to HOME instead of VOLUME_UP and write WAKE_DROPPED instead of WAKE.
Also i reput the button 115 to VOLUME_UP instead of HOME and then i save and overwrite the file with es text editor in es explorer in root mode with supersu, and then i reboot the watch, but this still not working.
How do you have make to change the home button to volume_up?
Tell me please, so i can do it in the inverse way, and i'm sure this will work.
Thank very much for your work, you are a great dev
alvespassospaulo85 said:
My felicitations for your great job on this rom, and i have a question
First of all, i want to give you all my felicitations for your work and your rom unova kk for omate truesmart, it is very stable, fast, and battery saver compared to a lot of other roms.
I have European Model 2100 mhz of omate truesmart with 1 gb ram and 8 bg rom.
The only problem that i have with your rom is that i don't want that the home button put volume up, and i want it to go home like default.
How can i do to change it?
I already go to system\usr\keylayout\mtk-kpd.kl and changed the button 102 to HOME instead of VOLUME_UP and write WAKE_DROPPED instead of WAKE.
Also i reput the button 115 to VOLUME_UP instead of HOME and then i save and overwrite the file with es text editor in es explorer in root mode with supersu, and then i reboot the watch, but this still not working.
How do you have make to change the home button to volume_up?
Tell me please, so i can do it in the inverse way, and i'm sure this will work.
Thank very much for your work, you are a great dev
Click to expand...
Click to collapse
Ok i uploaded fix in attached files in the first post .
You may notice the difference by opening the file
Really very good rom, I installed it on TS 1gb/8gb 2100Mhz (I changed the baseband from original 1900Mhz). But with this rom I have some problem, in recovery TWRP I can't use my external SD card (twrp presents empty external_sd). With other variants of roms I didn't have this problem. If someone knows how to fix it?
Baseband
Any way you could post directions for baseband change? I have 2100 and live in US where 1900 mhz is needed for 3g data?
Thanks
Hey everyone,
I hope i'm not being a pain in the toot for asking this, but I have the above issue. I've been trying for the past several weeks to resolve it but no luck.
I've unlocked my boot loader (worst decision ever) and installed a custom recovery; TWRP in that case. After some time I decided to go back to the official firmware. I already knew about Sony's flash tool which I tried but for some weird reason the flash tool (emma) doesn't recognise the f5122 model just the single sim variant f5121.
I've also tried to download the firmware manually using xperifirm which for some idiotic reason never worked (connection keeps getting messed up and the download fails)
I've managed to get my hands on the .tft file for nougat firmware and once I started the flash tool (developed independently by some awesome guy) it would also fail. Something about needing to enable debugging over usb (which is duh enabled) and enabling Unknown Sources (also duh enabled)
Any idea if there's something else that I didn't try/paid attention to?
P.S i'm currently running the Poison rom (found it here on xda) which works well but I've read that I won't receive any OTA updates.
Thanking you all in advance :fingers-crossed:
-=-=- first, Did you backup DRM before unlock bootloader ?
second, You can flash any x firmware with flashtool on flashmode ( search to find how to turn it on).
third, xperia firm can download well on day time, i think so because i live in vietnam and it only work between 8am to 4pm after that the connection lost.
1. No i didn't backup this thing (didn't know why I needed to)
2. I tried flash tool on windows and mac but without success, maybe I need to load a firmware downloaded with xperifirm in order to make it work
3. I'll keep trying with the xperifirm thingy
Any ideas if there's something that I missed?
1. Sometime Sony release some new Firmware and you need that backup to restore DRM key for full function of sony like xreal...
2. you miss flash scipt ( I guest) so to make it more clearly please give me the image when you flash stock rom
See that there is not ftfs fo X or X Dual on XDA. Strange.
If You cannot download it through XperiFirm, try my upload for my polish forum:
http://www.xperiasite.pl/forum/341-xperia-x/
I'm trying to add every firmware - one unbranded (usually one of the firsts which get) and for all polish carriers - for every Sony device.
There are GDrive and MEGA links, so choose which suits You better.
Excellent news people (at least for me )
I've managed to get stock firmware from xperifirm
Flashed the bastard and locked the bootloader!
Thank you all for your kind support )
Hello all,
Im after purchasing a Z5c but before i do i was wanting to know a few things. Im coming from a samsung device which i find so simple to flash. The Z5c will probably be running MM.
I will be wanting to root the device and run xposed from the moment i get it. If i follow this guide:- https://forum.xda-developers.com/z5-compact/general/guide-how-to-root-z5c-painful-using-t3549388
Is this the best guide to use for a sony noob?
1. Will i still be running the stock sony firmware (inc kernal)?
2. All aspects of phone working (finger print, BionZ, x-reality engine, camera de-noise etc)
3. A custom recovery.
Thanks In advanced
OK, so i went for it any way after a lot more reading and hitting problems along the way. So i'll update this with what ive learnt. I did use the guide i've linked above.
I had to downgrade so went through the downgrade instructions and then followed the guide.
At Step 1 - Backup the TA partition, it took me three tries for it to work & a reboot after the first try, only hint i can give is just to try it a few times as is mentioned in the guide.
At Step 2 - Unlock the boot loader I had an issue with the command. The -i command was not recognised in the latest version of platformtools. I had to use a previous version (will update this post with a link).
At Step 6 - Patch the kernel. (1) I had a few issues. superuser.zip was not properly intergrated so i had to flash the zip in recovery after finishing the rest of the guide. (2) I believe the integrated TWRP has issues with backup (ref) so either skip it and flash this version or add it, its up to you. If you do add it and encounter an error similar to this " Skipping TWRP recovery. No kernel modules for 3.10.84-perf-XXXXXXX available" follow this guide.
I skipped putting xposed in the kernel and just flashed the zip via recovery & installed the installer all from the official xposed page after everything was setup.
Thanks for reporting your experiences. I have had my Z5C for a month now. I am wanting to root it, so your experiences are helpful and encouraging.
Does the camera continue to work? I do not want to lose the camera.
Keep on reporting please!
You wont lose the camera, every stock-based custom kernel here has a DRM fix to emulate the keys if they are not found.