Database Develop

[Q] Am I ready to install CM11 M10 Snapshot???

I have done most of the initial steps required to install CM11 but still I want to conform if I am going in the right path...
Model : Xperia SP C5302
Built number : 12.1.A.1.207 (Stock)
Kernel version : 3.4.0 (July 8 2014)
I have done the following things:
- Rooted using Towelroot (Verified root using a few root checking apps)
- Installed SuperSU (Chainfire) and BusyBox
- Installed CWM 4.4.1
And have not done the following:
- Yet to Unlock Bootloader
- Did not flash any Kernel
So I have a few Questions
Question 1:
Unlocking the Bootloader will lead to permanent loss of DRM keys... So will I be able to access Bravia Engine by any means after installing CM11???
Question 2:
Is it necessary to flash a kernel before installing CM11???
Question 3:
Is it safe to install CM11 by booting in Recovery mode or Flashboot mode (or whatever they call that, in which we do not need the help of PC) or using flashtool in PC is much safer and better???
Question 4:
Is there anything else for Me to do other than what I have already done (all those I have mentioned)???
Question 5:
There are a lot of Bootloop complaints about the recently released CM11 M10 Snapshot... So is it safe to install it or is it better to go with Nighties??? Is Nighties Stable (around)???
Question 6:
Is there any method to bring back the use of the Illumination bar in the mobile as a visualizer in Music n Photos app after Installing CM11???
Question 7:
In case I mess up, is what is the method to return to stock firmware (and what should I do now, i.e. before Unlocking Bootloader)???
If not all, please help Me clear at least some of My doubts
And if possible, It will be great if You give a complete tutorial (video or post) form a stock, unrooted, locked mobile to a mobile running a custom ROM...
Thank You all a Lot :victory:​

bharathulaganathan said:
I have done most of the initial steps required to install CM11 but still I want to conform if I am going in the right path...
Model : Xperia SP C5302
Built number : 12.1.A.1.207 (Stock)
Kernel version : 3.4.0 (July 8 2014)
I have done the following things:
- Rooted using Towelroot (Verified root using a few root checking apps)
- Installed SuperSU (Chainfire) and BusyBox
- Installed CWM 4.4.1
And have not done the following:
- Yet to Unlock Bootloader
- Did not flash any Kernel
So I have a few Questions
Question 1:
Unlocking the Bootloader will lead to permanent loss of DRM keys... So will I be able to access Bravia Engine by any means after installing CM11???
Question 2:
Is it necessary to flash a kernel before installing CM11???
Question 3:
Is it safe to install CM11 by booting in Recovery mode or Flashboot mode (or whatever they call that, in which we do not need the help of PC) or using flashtool in PC is much safer and better???
Question 4:
Is there anything else for Me to do other than what I have already done (all those I have mentioned)???
Question 5:
There are a lot of Bootloop complaints about the recently released CM11 M10 Snapshot... So is it safe to install it or is it better to go with Nighties??? Is Nighties Stable (around)???
Question 6:
Is there any method to bring back the use of the Illumination bar in the mobile as a visualizer in Music n Photos app after Installing CM11???
Question 7:
In case I mess up, is what is the method to return to stock firmware (and what should I do now, i.e. before Unlocking Bootloader)???
If not all, please help Me clear at least some of My doubts
And if possible, It will be great if You give a complete tutorial (video or post) form a stock, unrooted, locked mobile to a mobile running a custom ROM...
Thank You all a Lot :victory:​
Click to expand...
Click to collapse
First I will suggest you to leave your Bootloader locked and just install Paranoid or PAC ROMs.
1. Yes, you will lose your DRM Keys. No you wont be able to.
2. It's good to flash latest .207 kernel before/after you install the ROM (if your bl is locked).
3. Just install it from CWM/TWRP
4. Root→install recovery→wipe data/cache etc.→install ROM→install GAPS→flash kernel→reboot→you Gucci
5. Your phone can always explode if you're dumb enough or you just don't like to read. (as I said PAC or Paranoid are better options than CM11)
6. Not really sure.
7. If you have your bl locked then just put your phone in flashmode and flash stock .ftf with flashtool. If not relock your bootloader then do the same.
So, if you ask me go for PAC ROM and locked bootloader. I think it's the best ROM so far for our device. I'm with Paranoid and it's quite Gucci as well, everything works like a charm, the ROM is fast and stable. I'm only suggesting you to install Greenify and DS Battery Saver Xposed Modules cause the battery isn't as good as the stock one.
As for tutorial, just read the guide in the thread. It's pretty simple and straight forward. You have to be really dumb to mess up five simple steps.
Good luck!

For Q6, it is possible to use the illumination lights via U-Disco, here.
You can unlock your bootloader and use custom kernels, but I personally recommend staying away from that and using locked bootloader roms, there are many good ones. The risk (hardbrick :crying: ) is not worth it-if you mess it up.

eSu.Matix said:
First I will suggest you to leave your Bootloader locked and just install Paranoid or PAC ROMs.
1. Yes, you will lose your DRM Keys. No you wont be able to.
2. It's good to flash latest .207 kernel before/after you install the ROM (if your bl is locked).
3. Just install it from CWM/TWRP
4. Root→install recovery→wipe data/cache etc.→install ROM→install GAPS→flash kernel→reboot→you Gucci
5. Your phone can always explode if you're dumb enough or you just don't like to read. (as I said PAC or Paranoid are better options than CM11)
6. Not really sure.
7. If you have your bl locked then just put your phone in flashmode and flash stock .ftf with flashtool. If not relock your bootloader then do the same.
So, if you ask me go for PAC ROM and locked bootloader. I think it's the best ROM so far for our device. I'm with Paranoid and it's quite Gucci as well, everything works like a charm, the ROM is fast and stable. I'm only suggesting you to install Greenify and DS Battery Saver Xposed Modules cause the battery isn't as good as the stock one.
As for tutorial, just read the guide in the thread. It's pretty simple and straight forward. You have to be really dumb to mess up five simple steps.
Good luck!
Click to expand...
Click to collapse
Thanx a lot... I flashed PACman ROM... Its really Osm :laugh:

103
ShinOrochiX said:
For Q6, it is possible to use the illumination lights via U-Disco, here.
You can unlock your bootloader and use custom kernels, but I personally recommend staying away from that and using locked bootloader roms, there are many good ones. The risk (hardbrick :crying: ) is not worth it-if you mess it up.
Click to expand...
Click to collapse
Will try U-Disco... Thanx 4 d suggestion...

ShinOrochiX said:
For Q6, it is possible to use the illumination lights via U-Disco, here.
You can unlock your bootloader and use custom kernels, but I personally recommend staying away from that and using locked bootloader roms, there are many good ones. The risk (hardbrick :crying: ) is not worth it-if you mess it up.
Click to expand...
Click to collapse
U-Disco is OSM but U need 2 buy it 4 it 2 run in the background...

Can someone tell me if I can flash this on my locked sp? http://forum.xda-developers.com/showthread.php?t=2868398
I have been a hardcore custom rom user (nexus 4), but sony's implementation of things confuses me a lot, that is why I have been refraining to install CM

tj_droid said:
Can someone tell me if I can flash this on my locked sp? http://forum.xda-developers.com/showthread.php?t=2868398
I have been a hardcore custom rom user (nexus 4), but sony's implementation of things confuses me a lot, that is why I have been refraining to install CM
Click to expand...
Click to collapse
Yes you can ! The LBL tag means locked bootloader (opposed to UB or UBL for unlocked). You can flash any ROM that has it but just check the instructions in op for any ROM specific recommendation.

pec0ra said:
Yes you can ! The LBL tag means locked bootloader (opposed to UB or UBL for unlocked). You can flash any ROM that has it but just check the instructions in op for any ROM specific recommendation.
Click to expand...
Click to collapse
Is there any basic disadvantage of flashing ROMs on a locked bootloader(like some features not working?) or is the similar to unlocked bootloader roms?

DOCOMO XPERIA A (Japanese ZR, aka SO-04E) - UPDATED ROOT AND CUSTOM ROM TUTORIAL

[NOTE as of July 2016: the below is provided as-is. I'm no longer watching this thread and I don't provide support for this. You do this at your own risk.]
This is an updated tutorial (as of Oct 2015) to root and upgrade the Japanese Sony Xperia A (SO-04E, Android 4.1.2 or 4.2.2) to Android 4.4.4 and then to Android 5. The Xperia A is the Japanese version of the globally released ZR. In terms of hardware there are two differences: the Xperia A has 32GB internal memory; and its NFC chip set is different from the one in the ZR - which is why NFC applications such as digital wallet (osaifu-keitai) will not work after going through the below steps. The Xperia A has a locked bootloader that cannot be unlocked.
I did not come up with the most important moves here. That was done by others in this thread and this one, notably aperception and mgg4000 (a big thanks to those two!). I only updated some steps that no longer work due to DoCoMo updating their firmware and closing the loopholes exploitable in earlier versions, files getting lost, software features changing etc. I also broke this down into more detail for people who are less familiar with the process of rooting and installing unauthorized ROMs. I have to warn that this will take an inexperienced person at least a few hours, possibly a full day. With complications arising, it could be more.
Also, you need an extra (external) microSD card in your phone for this to work. If you don't have one, you can buy one at convenience or electronics stores. Min 4GB should be fine but more is better considering future need for nandroid backups etc.
Anyway, here we go. In case a file linked to in the tutorial is missing, please see if it's among those I backed up in a Mega account, list at bottom of post.
1. Be sure you have an external SD card as per the comment in the above preamble. Note that at various points in the process the phone will ask you whether to install the Sony PC Companion link. Always skip this.
2. Write down all APN settings of your phone – you will need to manually enter them later.
3. Make sure your phone’s Developer Options are enabled, USB debugging is enabled, and Installing from Unknown Sources is enabled (google if you don’t know this stuff).
4. Install the minimal ADB and Fastboot tools from here: http://forum.xda-developers.com/showthread.php?t=2317790
5. Install Flashtool from here: http://www.flashtool.net/downloads.php . Watch this tutorial to do this and the next steps right: https://www.youtube.com/watch?v=ZfD9kT1DVz0
6. Power down your phone, hold down the Lower Volume key and connect phone to PC via USB cable. Flashtool will now show your phone as connected in Flashboot mode.
7. Using Flashtool, flash this to your phone: https://www.dropbox.com/s/p0m8fzv22m..._Hong_Kong.ftf
(or another C5503 Android 4.2.2 firmware – find one on XDA) . In the Flashtool settings, make sure you wipe the APPS_LOG and USERDATA
8. Disconnect and reboot.
9. You should now have a clean install of a Sony C5503 stock firmware. Confirm this in /Settings/About Phone.
10. If you check your Storage now, you will see only 4.59GB available internal memory, even though the Xperia A has 32GB total. To fix this, use Flashtool to flash back one part of the original SO-04E firmware here:
https://ftf.あんどろいどのこと.みんな/
I used 10.3.1.B.2.13 which worked fine. When flashing this, you must wipe the APPS_LOG and USERDATA again, and exclude EVERYTHING except PARTITION. In other words, all items in the Exclude list must be checked, except PARTITION.
11. When this is done, reboot once more and check your storage again. You should now see ~25GB of usable internal space. Yay!
12. Now make sure you have wifi or phone network access. Wifi is easiest. For 4G/LTE you will need to manually enter the APN settings from Step 2 above first. Just one of them, the one you usually use is fine (in the case of DoCoMo, the most common one is moperaU)
13. Once your phone has mobile network (or wifi) access, go through the process of enabling Developer Options, USB Debugging and Installing from Unknown Sources again.
14. Log into the Google Playstore and install SuperSU
15. Now root your device with this: http://rootkitxperia.com/
16. Start SuperSU and set it up. Grant permissions as requested. If the installation is succesful, you have root.
17. Now install custom recovery. Get the latest dual recovery for ZR (installation file, not flashable file) from here: http://nut.xperia-files.com/). With the phone connected, run the English language install .bat
18. When done, power down device. Power it back up. As soon as the LED lights up (in other words, when the Sony logo appears) and until after you feel a brief vibration press any button on the phone repeatedly (e.g. the volume buttons) to enter recovery. The Recovery service will boot up.
At this point, if you haven’t yet, you need to familiarize yourself with Clockwork Recovery.
Wipe the cache partition, the dalvik cache (under Advanced), and wipe data/factory reset.
19. Reboot, connect USB cable and place the following file on your external SD card
https://mega.co.nz/#!4o0jlQ6b!ZVxOj-...9paCqsR1EQBlGU
20. Boot into Recovery, go to the Wipe options and Clean To Install New ROM. Then install the above file from the external SD card (the device has two SD cards, one external and one internal). This will install Android 4.4.4. Once done, choose the option to reboot the device. (When I did this the first time, Recovery warned that Root may be lost and asked whether to fix this. I chose “Yes, fix it” and rebooted. The good news was that Android 4.4.4 was installed correctly. The bad news was that Root was lost. WTH??? You may want to try NOT fixing it, see if that goes any better. The second time I went through these steps with someone else's Xperia A, this problem did not occur.) When the device has rebooted (and root was not lost), SuperSU should be present which means that you still have root. You can also double-check with an application called "Root Checker" from the Playstore. You may also want to check if Recovery is still on the phone and working (by rebooting the phone and pressing the volume keys when the Sony logo appears.) If Recovery is no longer present, go back to step 17 and repeat. Then come back here. If you have both root and Recovery, you can now skip to step 22.
[21. ONLY if you have lost root like I did, follow these instructions to regain Root (the root kit from step 15 will no longer work on this new version you now have; you can use the Flashtool we installed in step 5, no need to download the official Sony one)
http://techbeasts.com/2014/09/18/how-root-sony-xperia-z-zr-zl-1051a0283-android-444-locked-unlocked/
After flashing the two firmwares and rebooting, each time a “repairs in progress” type of screen appeared and shortly thereafter the phone seemed to power down. I had to remove the battery each time to get the thing started again. Also, while on the Nordic firmware, the phone kept vibrating for no reason. This problem disappears when flashing back the second firmware from the above instructions.]
22. You now have a rooted Android 4.4.4. Presumably you will want to move on to the very latest Android version which is Android 5.1.1. Keep in mind that the Xperia A has a locked bootloader so only ROMs that are designed for a LB will work. I installed this one, works perfectly except for NFC:
http://forum.xda-developers.com/xperia-zr/development/rom-purex-z-v1-0-port-rajeev-t3215063
That’s it. Unfortunately, links included in this tutorial are liable to go dead after a while. Here are the ones likely to vanish, duplicated in a Mega account I set up for this.
Step 7: C5503 HK firmware (C5503_10.3.1.A.2.67_Hong_Kong.ftf):
https://mega.nz/#!R1p2wKII!rs9UFrMHN-nAnaROy-xe5gu1Zt52ipk-451sZEpzv34
Step 10: SO-04E firmware (10.3.1.B.2.13):
https://mega.nz/#!UwgHTT7Z!kKHlcPyPOH-mHcuDHXB6ZVWkf5xTl5op1IOFZ8fUGIU
Step 19: Pre-rooted 4.3.3 (C5503_10.5.1.A.0.283_NCB_PRE-ROOTED_PRFCreator.zip):
https://mega.nz/#!8tQEEJxY!Xd7HoRwWTe_XKPdL6COlS43xZo9TG2b_LFXsZWRLgBM
Step 21: Nordic firmware (C5503_10.5.A.0.230_Nordic NCB.ftf):
https://mega.nz/#!koIiRISS!fUH-OWT4s26wWgcdJ_HYQ9ctJun48m6N_rSzm9o_m64
Step 21: C5503 Kitkat (C5503_10.5.1.A.0.292_RU.ftf):
https://mega.nz/#!pw4jmIhL!ClHKkkSX1seeB13nb9kwlgpeF-LVVKr9IDfhyiqDT9g

Thanks buddy! You meticulously wrote and setup everything. Hope people will be benefited

Thank for the tutorial
axel007 said:
This is an updated tutorial (as of Oct 2015) to root and upgrade the Japanese Sony Xperia A (SO-04E, Android 4.2.2) to Android 4.4.4 and then to Android 5. The Xperia A is the Japanese version of the globally released ZR. In terms of hardware there are two differences: the Xperia A has 32GB internal memory; and its NFC chip set is different from the one in the ZR - which is why NFC applications such as digital wallet (osaifu-keitai) will not work after going through the below steps. The Xperia A has a locked bootloader that cannot be unlocked.
I did not come up with the most important moves here. That was done by others in this thread and this one, notably aperception and mgg4000. I only updated some steps that no longer work due to DoCoMo updating their firmware and closing the loopholes exploitable in earlier versions, files getting lost, software features changing etc. I also broke this down into more detail for people who are less familiar with the process of rooting and installing unauthorized ROMs. I have to warn that this will take an inexperienced person at least one full day, and possibly more. You may want to plan two full days. If you are one of the totally clueless you might save yourself the trouble and simply buy a newer phone.
Also, you need an extra (external) microSD card in your phone for this to work. If you don't have one, you can buy one at convenience or electronics stores. Min 4GB should be fine but more is better considering future need for nandroid backups etc.
Anyway, here we go. In case a file linked to in the tutorial is missing, please see if it's among those I backed up in a Mega account, list at bottom of post.
1. Cancel all your appointments, hire a dog walker and tell your wife she had best stay with some friends this weekend.
2. Write down all APN settings of your phone – you will need to manually enter them later.
3. Make sure your phone’s Developer Options are enabled, USB debugging is enabled, and Installing from Unknown Sources is enabled (google if you don’t know this stuff).
4. Install the minimal ADB and Fastboot tools from here: http://forum.xda-developers.com/show....php?t=2317790
5. Install Flashtool from here: http://www.flashtool.net/downloads.php . Watch this tutorial to do this and the next steps right: https://www.youtube.com/watch?v=ZfD9kT1DVz0
6. Power down your phone, hold down the Lower Volume key and connect phone to PC via USB cable. Flashtool will now show your phone as connected in Flashboot mode.
7. Using Flashtool, flash this to your phone: https://www.dropbox.com/s/p0m8fzv22m..._Hong_Kong.ftf
(or another C5503 Android 4.4.2 firmware – find one on XDA) . In the Flashtool settings, make sure you wipe the APPS_LOG, and check none of the Exclude items; if after this process the phone keeps rebooting, flash the same thing again, this time also wiping USERDATA)
8. Disconnect and reboot. If any trouble, see my comment above in brackets (under point 7).
9. You should now have a clean install of a Sony C5503 stock firmware. Confirm this in /Settings/About Phone.
10. If you check your Storage now, you will see only 4.59GB available internal memory, even though the Xperia A has 32GB total. To fix this, use Flashtool to flash back one part of the original SO-04E firmware here:
https://ftf.あんどろいどのこと.みんな/
I used 10.3.1.B.2.13 which worked fine. When flashing this, you must wipe the APPS_LOG (and maybe USERDATA) again, and exclude EVERYTHING except PARTITION. In other words, all items in the Exclude list must be checked, except PARTITION.
11. When this is done, reboot once more and check your storage again. You should now see ~25GB of usable internal space. Yay!
12. Now make sure you have phone network access. For 4G/LTE you will need to manually enter the APN settings from Step 2 above first. Just one of them, the one you usually use is fine (in the case of DoCoMo, the most common one is moperaU) (Or, instead of messing around with the LTE and APN settings - which takes time and will need to be repeated several more times if you want to use your mobile network connection for downloads - enable Wifi; this will usually be easier.)
13. Once your phone has mobile network (or wifi) access, go through the process of enabling Developer Options, USB Debugging and Installing from Unknown Sources again.
14. Log into the Google Playstore and install SuperSU
15. Now root your device with this: http://rootkitxperia.com/
16. Start SuperSU and set it up. Use a root checker from the Playstore to confirm it’s done.
17. Now install custom recovery. Get the file from here:
https://onedrive.live.com/?id=D419E7...&action=locate (or presumably the latest dual recovery for ZR from here will also work fine: http://nut.xperia-files.com/). With the phone connected, run the English language install .bat
18. When done, power down device. Power it back up. As soon as the LED lights up (in other words, when the Sony logo appears) and until after you feel a brief vibration press any button on the phone repeatedly (e.g. the volume buttons) to enter recovery. The Clockwork Recovery service will boot up.
At this point, if you haven’t yet, you need to familiarize yourself with Clockwork Recovery.
Wipe the cache partition, the dalvik cache (under Advanced), and wipe data/factory reset. Once you reboot, you will once again need to reestablish Playstore access etc.
19. Now place the following file on your external SD card
https://mega.co.nz/#!4o0jlQ6b!ZVxOj-...9paCqsR1EQBlGU
20. Boot into Recovery, wipe cache and do a factory reset. Then install the above file from the external SD card (the device has two SD cards, one external and one internal). This will install Android 4.4.4. Once done, power off the device using the according command in Recovery. When I did this, Recovery warned that Root may be lost and asked whether to fix this. I chose “Yes, fix it” and rebooted. The good news was that Android 4.4.4 was installed correctly. The bad news was that Root was lost. WTH??? You may want to try NOT fixing it, see if that goes any better. Anyway, install SuperSU and the root checker from the Playstore and see if you have root or not. If yes, skip to step 22.
21. ONLY if you have lost root like I did, follow these instructions to regain Root (the root kit from step 15 will no longer work on this new version you now have; you can use the Flashtool we installed in step 5, no need to download the official Sony one)
http://techbeasts.com/2014/09/18/how...cked-unlocked/
After flashing the two firmwares and rebooting, each time a “repairs in progress” type of screen appeared and shortly thereafter the phone seemed to power down. I had to remove the battery each time to get the thing started again. Also, while on the Nordic firmware, the phone kept vibrating for no reason. This problem disappears when flashing back the second firmware from the above instructions.
22. You now have a rooted Android 4.4.4. Presumably you will want to move on to the very latest Android version which is Android 5.1.1. Keep in mind that the Xperia A has a locked bootloader so only ROMs that are designed for a LB will work. I installed this one, works perfectly except for NFC:
http://forum.xda-developers.com/xper...ajeev-t3215063
That’s it. Unfortunately, links included in this tutorial are liable to go dead after a while. Here are the ones likely to vanish, duplicated in a Mega account I set up for this.
Step 7: C5503 HK firmware (C5503_10.3.1.A.2.67_Hong_Kong.ftf):
https://mega.nz/#!R1p2wKII!rs9UFrMHN...pk-451sZEpzv34
Step 10: SO-04E firmware (10.3.1.B.2.13):
https://mega.nz/#!UwgHTT7Z!kKHlcPyPO...5op1IOFZ8fUGIU
Step 19: Pre-rooted 4.3.3 (C5503_10.5.1.A.0.283_NCB_PRE-ROOTED_PRFCreator.zip):
https://mega.nz/#!8tQEEJxY!Xd7HoRwWT...2b_LFXsZWRLgBM
Step 21: Nordic firmware (C5503_10.5.A.0.230_Nordic NCB.ftf):
https://mega.nz/#!koIiRISS!fUH-OWT4s...m6N_rSzm9o_m64
Step 21: C5503 Kitkat (C5503_10.5.1.A.0.292_RU.ftf): https://mega.nz/#!pw4jmIhL!ClHKkkSX1...Kr9IDfhyiqDT9g
Click to expand...
Click to collapse
2 things:
1. What is the "decryption key" for the mega links?
2. I flashed my so-04e previously in a similar procedure, but SOMEHOW corrupted my TA partition. I think it's the TA because the phone will not acquire a signal and when reflashing in flashtool one of the rolling messages is something about TA I never saw before. I'm wondering if maybe I'm bricked. I think it happened with I wiped the data partition in order for the phone to recognize the extra internal memory.

jatyeo said:
2 things:
1. What is the "decryption key" for the mega links?
2. I flashed my so-04e previously in a similar procedure, but SOMEHOW corrupted my TA partition. I think it's the TA because the phone will not acquire a signal and when reflashing in flashtool one of the rolling messages is something about TA I never saw before. I'm wondering if maybe I'm bricked. I think it happened with I wiped the data partition in order for the phone to recognize the extra internal memory.
Click to expand...
Click to collapse
Jatyeo,
Regarding the second question, I have no idea. I am not technically informed, I just hammered together the tutorial based on what I could find here and there and made it consistent.
Regarding the first question, I did not realize that Mega downloads require a decryption key. Can you please try the following link and let me know if this works? The key is part of the link. This is the HK firmware.
https://mega.nz/#!R1p2wKII!rs9UFrMHN-nAnaROy-xe5gu1Zt52ipk-451sZEpzv34

This link works now, can you fix the rest?

All links updated, pls confirm back that they work for you.

All working

Nice work bro. Keep up the good work..

Any chance you speak Japanese?

By the way, the "above instructions" in 21 don't exist because the link is dead, I see you appended the file at the end of the description but there are no instructions.

jatyeo said:
By the way, the "above instructions" in 21 don't exist because the link is dead, I see you appended the file at the end of the description but there are no instructions.
Click to expand...
Click to collapse
I have no idea what you mean by this.
To answer your other question: yes, I speak Japanese.
And to answer your question from the other thread: as you can see, I am being very detailed with this tutorial. If there were any special points to keep in mind with the PureX ROM I link to in step 22, I would mention them. That is, as far as I know. I had no problems with it. It installed flawlessly and works great.

axel007 said:
I have no idea what you mean by this.
To answer your other question: yes, I speak Japanese.
And to answer your question from the other thread: as you can see, I am being very detailed with this tutorial. If there were any special points to keep in mind with the PureX ROM I link to in step 22, I would mention them. That is, as far as I know. I had no problems with it. It installed flawlessly and works great.
Click to expand...
Click to collapse
You were very detailed, thx (+Thx button =) )... but you've had to repost the many of the links because of issues and I'm saying 21 is no different; the link goes to a 404 error page.
The reason why I asked about Japanese is because there are some articles on fast tracking to lollipop I was curious to know your thoughts about...
http://doroid.org/2015/09/12/xperia-so-04ezr-c5503-5-1-1-根付いた/

jatyeo said:
You were very detailed, thx (+Thx button =) )... but you've had to repost the many of the links because of issues and I'm saying 21 is no different; the link goes to a 404 error page.
The reason why I asked about Japanese is because there are some articles on fast tracking to lollipop I was curious to know your thoughts about...
http://doroid.org/2015/09/12/xperia-so-04ezr-c5503-5-1-1-根付いた/
Click to expand...
Click to collapse
Now I get it. I don't know why these links become garbled like this. I tried to fix it, can you please check if it works for you now?
Regarding the Japanese link you gave above, I have no experience with this method. I am not sure he went to 5.1.1 from 4.2.2 directly.
I really don't have any particular technical knowledge. I'm just some guy who collected information from here and there, checked if it works (and it did for me) and summarized the steps he took. Half of the time I don't understand what I'm doing!

jatyeo said:
You were very detailed, thx (+Thx button =) )... but you've had to repost the many of the links because of issues and I'm saying 21 is no different; the link goes to a 404 error page.
The reason why I asked about Japanese is because there are some articles on fast tracking to lollipop I was curious to know your thoughts about...
http://doroid.org/2015/09/12/xperia-so-04ezr-c5503-5-1-1-根付いた/
Click to expand...
Click to collapse
Now I get it. I don't know why these links become garbled like this. I tried to fix it, can you please check if it works for you now?
Regarding the Japanese link you gave above, I have no experience with this method. I am not sure he went to 5.1.1 from 4.2.2 directly.
I really don't have any particular technical knowledge. I'm just some guy who collected information from here and there, checked if it works (and it did for me) and summarized the steps he took. Half of the time I don't understand what I'm doing!

axel007 said:
Now I get it. I don't know why these links become garbled like this. I tried to fix it, can you please check if it works for you now?
Regarding the Japanese link you gave above, I have no experience with this method. I am not sure he went to 5.1.1 from 4.2.2 directly.
I really don't have any particular technical knowledge. I'm just some guy who collected information from here and there, checked if it works (and it did for me) and summarized the steps he took. Half of the time I don't understand what I'm doing!
Click to expand...
Click to collapse
Thx
What do I exclude when upgrading to 5.1.1, are there any other tips?
This part is where I messed up y last phone, Thx

Exclude? This is a ROM that you flash in its entirety from your SD card. There are no options for exclusion...

What are Newest Xperia A Rom?

I am not sure I understand your question. DoCoMo only upgraded to 4.2.2. After that, you're on your own. That's what this tutorial is about. If you are asking what unofficial ROM is the latest, you can look that up for yourself over in the Xperia ZR development forum. But if you have no experience with custom ROMs, I would recommend you use the one I link to (PureX) as I can confirm that this is stable and works well.

Everything was going very well till step 20
my xperia just keeps on SONY logo screen
Edit/
now it goes till appears the XPERIA and reboot
cant acess the recovery mode

[FTF] C5503_10.7.A.0.222 Fix_for_ZRDocomo Android 5.1.1
[FTF] C5503_10.7.A.0.222 Fix_for_ZRDocomo Android 5.1.1
http://ouo.io/C0smHY
C5503_10.7.A.0.228_Fix_32Gb-ZRdocomo.ftf
http://ouo.io/C0smHY

[Summary] Rooting the Z5

Hi there,
I think we should make a simple thread to sum up everything we know about root, since the main talking thread is long, here are the main informations:
Xperia Z5:
- No locked bootloader root yet
- AndroPlusKernel: http://forum.xda-developers.com/xperia-z5/development/kernel-andropluskernel-v1-t3246100
- TWRP here http://forum.xda-developers.com/xperia-z5/development/twrp-2-8-7-0-z5-rootable-kernel-t3240032
- CWM booting but not usable: http://forum.xda-developers.com/xperia-z5/development/recovery-clockworkmod-recovery-sony-t3249782
- Unlocked BL dirty rooting available and working as intended: http://forum.xda-developers.com/xperia-z5/development/dirty-root-solution-unlocked-bl-t3233274
- Dumped original firmware: http://forum.xda-developers.com/xperia-z5/general/ftf-files-sony-xperia-z5z5-dual-t3214397
- Xposed works but you need to let it bootloop a few times
Xperia Z5 Compact:
- No locked bootloader root yet
- Zombie Kernel testing release here: http://forum.xda-developers.com/z5-compact/orig-development/kernel-zombie-t3224735
- Unlock bootloader root available (http://forum.xda-developers.com/z5-compact/development/dirty-root-solution-unlocked-bl-t3230524)
- Prerooted firmware available for unlocked BL: http://forum.xda-developers.com/z5-...-rooted-32-0-5-32-firmware-one-click-t3231520
- Xposed doesn't work with prerooted firmware
Currently we need to:
- Compile Zombie Kernel for Z5
- Improve TWRP support
- Create prerooted-firmware
- Most obviously and most hardly, find exploit for Locked BL root
Ok I'm not an Xperia pro, just got my first one few days ago, but still a android and linux geek, so if there is mistakes in my post, or update I haven't seen, notify me

Knux14 said:
- Maybe dump the original firmware ?
Click to expand...
Click to collapse
If I'm not mistaken, I think it already has: http://forum.xda-developers.com/xperia-z5/general/ftf-files-sony-xperia-z5z5-dual-t3214397

Need root for Z5, thx for efforts.

Uclydde said:
If I'm not mistaken, I think it already has: http://forum.xda-developers.com/xperia-z5/general/ftf-files-sony-xperia-z5z5-dual-t3214397
Click to expand...
Click to collapse
Updated

Test kernel for Z5:
https://mega.nz/#!15oSGLiA!N-lOlfn8RS9_gN_GcVJrFzXg21nzL1xDdt1xKujl9is
This is stock Z5 kernel modified to disable Sony RIC, dm verity, etc.
It should work together with the Z5C rooting solution:
http://forum.xda-developers.com/z5-compact/development/dirty-root-solution-unlocked-bl-t3230524
Please report back.

nilezon said:
Test kernel for Z5:
https://mega.nz/#!15oSGLiA!N-lOlfn8RS9_gN_GcVJrFzXg21nzL1xDdt1xKujl9is
This is stock Z5 kernel modified to disable Sony RIC, dm verity, etc.
It should work together with the Z5C rooting solution:
http://forum.xda-developers.com/z5-compact/development/dirty-root-solution-unlocked-bl-t3230524
Please report back.
Click to expand...
Click to collapse
You are the man, you saved me
my phone works now with root access

nilezon said:
Test kernel for Z5:
https://mega.nz/#!15oSGLiA!N-lOlfn8RS9_gN_GcVJrFzXg21nzL1xDdt1xKujl9is
This is stock Z5 kernel modified to disable Sony RIC, dm verity, etc.
It should work together with the Z5C rooting solution:
http://forum.xda-developers.com/z5-compact/development/dirty-root-solution-unlocked-bl-t3230524
Please report back.
Click to expand...
Click to collapse
Huge thanks, But I can't get it working...
I open BL, I fastboot flashed the kernel, then I fastboot booted on the recovery (Which doesn't show a black screen as expected but a real non-fully-working twrp for me) and I tried to install Supersu but I write an error then...
EDIT: Kinda glitchy to do, but works.
If anyone has Xposed working, please make a tutorial

Okay so this is my first Xperia device and my second android device (used to have a Nexus 5 so rooting was simple). Can anyone ELI5 the root situation?
I understand that the TA partition contains DRM keys to make X-Reality etc work and that unlocking the bootloader will wipe this TA partition and the features will stop working. My main confusion comes from - if other lollipop devices have rooting methods for locked bootloaders, why don't these methods work on the Z5? Sorry if this is extremely obvious and I'm an idiot.

Most android devices have either already unlocked BL or you have to. For example, Nexus 5 needed to unlock the BL, as well as the OnePlus One, but those devices don't contain DRM so you don't loose anything when unlocking

nilezon said:
Test kernel for Z5:
https://mega.nz/#!15oSGLiA!N-lOlfn8RS9_gN_GcVJrFzXg21nzL1xDdt1xKujl9is
This is stock Z5 kernel modified to disable Sony RIC, dm verity, etc.
It should work together with the Z5C rooting solution:
http://forum.xda-developers.com/z5-compact/development/dirty-root-solution-unlocked-bl-t3230524
Please report back.
Click to expand...
Click to collapse
Worked in second attempt. First time reboot into recovery. New fastboot boot booted into black screen.
In following sequence it was necessary to add destination file name,
D:\DOWNLOADS\Sony\Xperia\Z5\Fastboot>adb push SuperSU-v2.51.zip /data/media/0/
failed to copy 'SuperSU-v2.51.zip' to '/data/media/0/': Is a directory
D:\DOWNLOADS\Sony\Xperia\Z5\Fastboot>adb push SuperSU-v2.51.zip /data/media/0/SuperSU-v2.51.zip
9055 KB/s (3989636 bytes in 0.430s)

harfot said:
Worked in second attempt. First time reboot into recovery. New fastboot boot booted into black screen.
In following sequence it was necessary to add destination file name,
D:\DOWNLOADS\Sony\Xperia\Z5\Fastboot>adb push SuperSU-v2.51.zip /data/media/0/
failed to copy 'SuperSU-v2.51.zip' to '/data/media/0/': Is a directory
D:\DOWNLOADS\Sony\Xperia\Z5\Fastboot>adb push SuperSU-v2.51.zip /data/media/0/SuperSU-v2.51.zip
9055 KB/s (3989636 bytes in 0.430s)
Click to expand...
Click to collapse
I did not had to :/

You guys work fast!
Unsure whether to root myself yet,
Kind of wouldn't mind being able to connect a ps3 pad instead of
Ps4 using the sixaxis app

I'm still confused here. I don't see clear instructions for root process, probably because this is my first Xperia device. Neither do I know if using this modded stock kernel and doing this adb thing few posts back will break the DRM thingy and camera features or not.

Falenone said:
I'm still confused here. I don't see clear instructions for root process, probably because this is my first Xperia device. Neither do I know if using this modded stock kernel and doing this adb thing few posts back will break the DRM thingy and camera features or not.
Click to expand...
Click to collapse
There is nothing clear enough for beginner yet. Sooner or later there will be a TWRP fully working and it will be easy.
Try the dirty method, but don't do things that you are not sure that will work. Ask us if needed

I don't want to lose features because of unlocked bootloader. I guess I'm going to survive without root til there's TWRP and pretty much flash n go root

You will maybe never be able to root without loosing feature. Xperia devices work like this for ages..
The only way you could would be that we find a flaw in Android, which could either arrive soon, or never...

Knux14 said:
You will maybe never be able to root without loosing feature. Xperia devices work like this for ages..
The only way you could would be that we find a flaw in Android, which could either arrive soon, or never...
Click to expand...
Click to collapse
Ages means..? I know that the Z1 is not so fresh anymore but we were able to root 4.2/4.4.4/5.1 without losing anything with locked BL. (I know nothing except following tutorials)
Sent from my E6653

Yes because there were security holes in android. For now we havent found anything yet in this version

harfot said:
Worked in second attempt. First time reboot into recovery. New fastboot boot booted into black screen.
In following sequence it was necessary to add destination file name,
D:\DOWNLOADS\Sony\Xperia\Z5\Fastboot>adb push SuperSU-v2.51.zip /data/media/0/
failed to copy 'SuperSU-v2.51.zip' to '/data/media/0/': Is a directory
D:\DOWNLOADS\Sony\Xperia\Z5\Fastboot>adb push SuperSU-v2.51.zip /data/media/0/SuperSU-v2.51.zip
9055 KB/s (3989636 bytes in 0.430s)
Click to expand...
Click to collapse
I did boot into TWRP (it was like tablet mode) mounted all partitions to be sure, flashed SuperSU from external sd. It is working. Thank you all

ChrissehB said:
Okay so this is my first Xperia device and my second android device (used to have a Nexus 5 so rooting was simple). Can anyone ELI5 the root situation?
I understand that the TA partition contains DRM keys to make X-Reality etc work and that unlocking the bootloader will wipe this TA partition and the features will stop working. My main confusion comes from - if other lollipop devices have rooting methods for locked bootloaders, why don't these methods work on the Z5? Sorry if this is extremely obvious and I'm an idiot.
Click to expand...
Click to collapse
Google "Verified Boot Android" .. there is almost 100% probability that locked bootloader root will never be achieved, because of this security feature. Verified Boot was introduced in KitKat, but almost nobody used it in so strict mode implementation... Until now, no single firmware using Verified Boot was ever rooted without either custom kernel (must unlock bootloader) or leaked engineering bootloader (try ask Sony engineers for it).

Bought 2nd-hand XZ1C, update fail over and over

hi everyone,
i bought a 2nd-hand xz1c and it's been great but it had a custom rom installed and was rooted then reflashed with stock rom when i got it, that's what the seller said anyway but i can't get in touch with him anymore.
i haven't been able to update anything since i got it. the system downloads and fails to install the update over and over. i have no idea how to unroot the phone if that's possible or what programs to use to do it, is there a guide where i can just get it to stop downloading and trying to download the newer firmware? ideally i'd like to install the update, failing that just to get it to stop trying would be "ok"... probably not from a security point of view though.
i'm a complete noob sorry. ly

As the phone was rooted, the bootloader is unlocked and the OTA update will fail. It's impossible to relock the bootloader, so you'll have to manually flash the updates.
You can use a tool called xperifirm to download new firmware version and newflasher to flash them. Search the forum for guides.
To stop the updater from tryung, go to settings/apps, check show system apps, find the app called Software update and force stop it. It will restart on phone boot, so you'll have to close it again once in a while.
You can also use ADB to disable the updater for good - again, search the forum for a more specific guide...

If you really feel there is some sort of advantage to having the latest firmware on your phone, then upgrade it yourself, you won't damage the phone or change your warranty status.
Look on Xperiafirm and find a 47.2.A.10.62 customised build - CE1 would be a good option
Download Newflasher and put it in the same folder as the firmware you downloaded from Xperiafirm
Delete Userdataxxx.sin and files ending in .ta (but not in the boot folder) . This will ensure that you don't lose any personal data. Also delete persist*.sin to avoid losing android attest key.
Then start newflasher.exe and follow instrctions.
You might need a copy of the Sony driver
I would make a backup with Xperia transfer before you do anything, if the phone is glitchty after your rebuild, then factory reset it and then restore from the backup.
You'd probably need to read up on janjan's kernel fix to get you working without a green camera.
You'll also need TWRP

please help flashing my xz1c

hello,
I would like to flash lineage OS and get a phone without google.
can you confirm me what I have to do:
- enable OEM Unlocking ?? (isn't it exactly what we won't do before backup TA ?)
- downgrade in 47.1.A.2.324_CE1 with newflasher (before flashing: Delete Userdataxxx.sin and files ending in .ta)
- backup TA https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
-flash TWRP by adb
-flash lineageOS by TWRP
-flash a kernel ??? what to do with this : https://forum.xda-developers.com/xp...oted-kernel-hiding-bootloader-unlock-t3898711
thanks for helping me.

hazote said:
hello,
I would like to flash lineage OS and get a phone without google.
can you confirm me what I have to do:
- enable OEM Unlocking ?? (isn't it exactly what we won't do before backup TA ?)
- downgrade in 47.1.A.2.324_CE1 with newflasher (before flashing: Delete Userdataxxx.sin and files ending in .ta)
- backup TA https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
-flash TWRP by adb
-flash lineageOS by TWRP
-flash a kernel ??? what to do with this : https://forum.xda-developers.com/xp...oted-kernel-hiding-bootloader-unlock-t3898711
thanks for helping me.
Click to expand...
Click to collapse
Hi, I can help confirm a few things:
1. If by enable OEM unlocking you mean "allow the bootloader to be unlocked" in the developer options then yes, you need to do this and it won't damage your phone.
2. Downgrading to Oreo is a must to unlock the bootloader. You'll need newflasher to do this but it's a very easy and simple process. I think 47.1.A.2.324 is the fw I downgraded to but I can't honestly remember. Make sure to delete all TA files in the main folder but not the TA file in the boot folder. I did that the first time, entered a bootloop and had to use xperifirm to get back to stock pie and a working phone(not horrible but more work than I needed to do).
I also deleted the persist.sin file because I had read it was necessary to keep the android attest key(which I'm not 100% knowledgeable about) but i didn't delete userdataxxx.sin. I just made sure everything was backed up so I could have a clean flash/install every time with as few problems as possible.
3. Once on oreo, use the back up tools for your TA partition. This was the longest and hardest part for me because I didn't read the directions closely enough before hand. My problem was I didn't realize I had to open another command prompt after I established temp root in the first prompt. This sounds complex(at least, to me) but it's really not. Again, follow the instruction and you'll be fine. Now you can unlock the bootloader with your code and then restore the TA partition.
4. At this point, it's all up to you from where to go next. If you want to stay on Oreo, then flash TWRP through ADB and flash a rom, root it and enjoy. If you want a rom based on Pie, flash the latest fw with newflasher(deleting TA files and persist.sin) and then flash TWRP, rom and root.
I hope that little bit helps. I really can't give you any advice on lineage or a kernel as I am on crDroid but the devs are super helpful and hardworking on the forums and there are a lot of experienced members. If anyone can explain it better or I didnt' say it right, please correct me.
A.Karimov

Thanks a lot.
For you, why should I go for carbon and not lineage?

hazote said:
Thanks a lot.
For you, why should I go for carbon and not lineage?
Click to expand...
Click to collapse
No worries, I'm glad to help:good:
I don't have any experience with Lineage other than an old build on a tablet. I had considered flashing it but I really like having more freedom to customize things. CrDroid has been very stable for me. It is a very responsive and fast rom.