[Q] I don't know what to do. - G 2014 Q&A, Help & Troubleshooting

Hello, last night my phone started showing mistakes as "the process com.Google.process.gapps has stopped" or "Google process doesn't answer" without any reason.
I did make a complete wipe through my recovery TWRP (I wouldn't recommend this in base of this experience, CWM is better, really better:crying and it shows "wipe complete" but next to it shows the word "Failed" in red.
- I can turn the phone on sometimes but after the moto boot the screen stays black.
- I installed lollipop again and it says that every process doesn't answer.
- I can't reset the internal memory as I explained before
- I hardly ever used the root with Xposed.
- I have the bootloader unlocked from a while ago.
At least the phone runs the bootloader without problem.
Any solution?
I have never dropped my phone and I have it for months.
P.D. English, is not my native language sorry for the mistakes.

Not sure why it does, but it's been happening to me as well.
Try this:
Go to Settings, Apps, All, and clear data for Downloads. Then disable and enable Downloads. This seems to work.

Try restoring it to kitkat
try this link it works great it will restore your phone to stock kitkat GB version and you can latter update it OTA to lollipop. i have tried it and it works. http://forum.xda-developers.com/moto-g-2014/general/windows-tool-moto-g-2014-xt1068-dual-t2983295 as bootloader is working you will be able to restore i think. just download zip file extract it. it contains instructions too.

Thanks for help me, but still not working.
Actually, what I really need is to be able to delete everything in the phone, I can try changing the system date but I cannot delete the data of the phone.

Related

[Q&A] [ROM][I9295][4.4.2] Super WizCyan - S5 Style [debloated & deodexed + Addon Pac

[Q&A] [ROM][I9295][4.4.2] Super WizCyan - S5 Style [debloated & deodexed + Addon Pac
Q&A for [ROM][I9295][4.4.2] Super WizCyan - S5 Style [debloated & deodexed + Addon Package]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][I9295][4.4.2] Super WizCyan - S5 Style [debloated & deodexed + Addon Package]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hi everyone,
This ROM is great. every things are working well.
But I don't know how to change the "Right hard key's function. I don't want it show the "recent apps" when we press.
It should be a menu key when we using App.
Please support!
Thanks,
lamhcmute said:
Hi everyone,
This ROM is great. every things are working well.
But I don't know how to change the "Right hard key's function. I don't want it show the "recent apps" when we press.
It should be a menu key when we using App.
Please support!
Thanks,
Click to expand...
Click to collapse
In post# 1 under the downloads section, below version 03 you will find revert longpress to recents & menu. You can download and flash this zip through recovery and menu key will be as before.
no root after flashign WizCyan
After flashing WizCyan 4 with update 1 I don't have root access. I've tried reinstalling several times and I've also tried to install superSU on it's own using CWM, both the latest version and older versions, with no success. I've also tried to install just v4 but the problem persists. Does anybody have any clue on what could be wrong? I've had root on the phone using other ROMs. I use the latest CWM.
And yes, I chose no when promted to fix superuser in CWM. Although I have also tried to pres yes during one installation.
What version of cwm are you having? Also when you click on the supersu app what message do you get?
I used version 6.0.3.5. Today I installed 6.0.5 and redid the flashing of the update and also of superSU 2.16 by it self from CWM. No difference
When i press the superSU app I dont get any message really. Looking at the log it's as if though the app denies all apps access without asking. I tried changing the settings in superSU to allow all requests and then the phone passed the check with root checker and root apps also seem to work. No app is added to the SuperSu applist.
Gudiol said:
I used version 6.0.3.5. Today I installed 6.0.5 and redid the flashing of the update and also of superSU 2.16 by it self from CWM. No difference
When i press the superSU app I dont get any message really. Looking at the log it's as if though the app denies all apps access without asking. I tried changing the settings in superSU to allow all requests and then the phone passed the check with root checker and root apps also seem to work. No app is added to the SuperSu applist.
Click to expand...
Click to collapse
I would suggest that you do a clean install of the ROM, now that your recovery has been updated
Excessive consumption of battery
Sorry, but this was translated by google.
I found a big problem in version 4 and is the battery, prior to this version, the battery works well, the battery lasted the whole day, but now the battery hopefully enduring three hours.
Please, give solution to this problem or any suggestions, as I really like this ROM and do not want to change the other.
Thanks in advance.
srDosaps said:
Sorry, but this was translated by google.
I found a big problem in version 4 and is the battery, prior to this version, the battery works well, the battery lasted the whole day, but now the battery hopefully enduring three hours.
Please, give solution to this problem or any suggestions, as I really like this ROM and do not want to change the other.
Thanks in advance.
Click to expand...
Click to collapse
Will suggest to do a clean install and check and if not then report back. Anyone else facing this issue.. kindly report
srDosaps said:
Sorry, but this was translated by google.
I found a big problem in version 4 and is the battery, prior to this version, the battery works well, the battery lasted the whole day, but now the battery hopefully enduring three hours.
Please, give solution to this problem or any suggestions, as I really like this ROM and do not want to change the other.
Thanks in advance.
Click to expand...
Click to collapse
Ok, did some testing and found that some of the init.d scripts were eating battery therefore have posted an update in the OP removing these and battery consumption should be better after flashing this update.
can i install
i have 4.4.2 NE5 but DBT not PHN,can i install this rom on my firmware and do i need install first version 4 and then flash version 4 update 02?and how much memory i have after flashing this rom is ih still around 12 gb or less?
s4active user said:
i have 4.4.2 NE5 but DBT not PHN,can i install this rom on my firmware and do i need install first version 4 and then flash version 4 update 02?and how much memory i have after flashing this rom is ih still around 12 gb or less?
Click to expand...
Click to collapse
Sure, you can install on any firmware, but if you have wifi issues then you may need to flash modem or some other workaround. Just wipe data/factory reset and install version 04 followed by update 02. I am not sure on what you mean by memory but presume that you are referring to internal sd card. This will depend on what apps/features you install from the addon package and playstore. The ROM will not affect your internal sdcard space as it will be installed on the reserved system space.
Problem with Rom Super Wizcyan - S5 Style
Hello, first sorry by my english, its sucks, but ill try to explain my problem, i install the rom wizcyan - s5 style in my I9295 (of course), and follow all the instruction, like de developer says, starts normaly, but for example, when i push the screen mirroring button, the phone freeze an restart, and occasionally shows a message like "android core process stoped". do all the wipes, and install the 6.0.5 rom manager, all the proces finish ok, install the update, and occurs the same problem, i like this rom its cool , faster and light, without all the samsung crap, someone can help me please, thanks in advance.
Kaitenx said:
Hello, first sorry by my english, its sucks, but ill try to explain my problem, i install the rom wizcyan - s5 style in my I9295 (of course), and follow all the instruction, like de developer says, starts normaly, but for example, when i push the screen mirroring button, the phone freeze an restart, and occasionally shows a message like "android core process stoped". do all the wipes, and install the 6.0.5 rom manager, all the proces finish ok, install the update, and occurs the same problem, i like this rom its cool , faster and light, without all the samsung crap, someone can help me please, thanks in advance.
Click to expand...
Click to collapse
In case you want to use screen mirroring then you would need to install allshare from the addon package
I've been tinkering with trying to get WizCyan totally working on my device for a couple of days, but I can't for the life of me get Wifi working (at first it was root access, but that was fixed by upgrading CWM). Here is the exact process I've followed:
Updated CWM to 6.0.5 (PhilZ's version)
Did a factory reset from recovery (I didn't use the "Clean to install new ROM" function)
Installed WizCyan version 4, followed by update 2
Rebooted, attempted to configure WiFi -- failed.
Flashed the NE5 modem package from the links in the dev thread, using Odin 3.07 -- twice each, as instructed
Still can't get my Wifi to enable. The flash was successful, as I can see the correct baseband on the "about" screen, but it refuses to enable. I'm in Australia, but I believe this phone came from UAE -- would that make a difference to the way the modem interacts with the Wifi hardware? I pulled this info from logcat:
Code:
I/WifiManager( 1084): setWifiEnabled : true
I/WifiService( 882): setWifiEnabled: true pid=1084, uid=10008
E/WifiHW ( 882): ##################### set firmware type 0 #####################
E/WifiHW ( 882): Cannot open "/data/.cid.info": No such file or directory
E/WifiHW ( 882): ==========[WIFI] Station firmware load ===========
E/WifiHW ( 882): return of insmod : ret = -1, Exec format error
E/WifiStateMachine( 882): Failed to load driver
E/WifiStateMachine( 882): sendErrorBroadcast code:10
E/WifiController( 882): Wi-Fi driver is unstable. Received CMD_STATEMACHINE_RESET
In the mean time, I'm going to try to source either a local radio, or one from the original region, to see if that helps.
andycore said:
I've been tinkering with trying to get WizCyan totally working on my device for a couple of days, but I can't for the life of me get Wifi working (at first it was root access, but that was fixed by upgrading CWM). Here is the exact process I've followed:
Updated CWM to 6.0.5 (PhilZ's version)
Did a factory reset from recovery (I didn't use the "Clean to install new ROM" function)
Installed WizCyan version 4, followed by update 2
Rebooted, attempted to configure WiFi -- failed.
Flashed the NE5 modem package from the links in the dev thread, using Odin 3.07 -- twice each, as instructed
Click to expand...
Click to collapse
Can't get anything much from the logcat, it refers to a file that gets created on 1st boot you can try doing a factory reset from settings--> backup & restore--> factory data reset. Only backup your internal sd card before doing this as it will wipe your entire phone including internal sdcard and then reflash the modem.
JASONRR said:
Can't get anything much from the logcat, it refers to a file that gets created on 1st boot you can try doing a factory reset from settings--> backup & restore--> factory data reset. Only backup your internal sd card before doing this as it will wipe your entire phone including internal sdcard and then reflash the modem.
Click to expand...
Click to collapse
Well if I'm going to go that far, I may as well do it properly and completely restore the phone to stock and start again. When I bought it, the first thing I did was root, flash CWM and a CM based ROM -- it's probably worth starting fresh anyway, I'm only going to be using it for a couple more weeks until it's replacement arrives.
I'm currently downloading the latest firmware for my region (XSA), a 4.2.2 based MK3 build from the end of last year -- do you think I'd have better chances if I restored to a 4.4.2 build (like NE5), or should it not matter if I completely reset the phone to factory settings/software?
andycore said:
Well if I'm going to go that far, I may as well do it properly and completely restore the phone to stock and start again. When I bought it, the first thing I did was root, flash CWM and a CM based ROM -- it's probably worth starting fresh anyway, I'm only going to be using it for a couple more weeks until it's replacement arrives.
I'm currently downloading the latest firmware for my region (XSA), a 4.2.2 based MK3 build from the end of last year -- do you think I'd have better chances if I restored to a 4.4.2 build (like NE5), or should it not matter if I completely reset the phone to factory settings/software?
Click to expand...
Click to collapse
Generally doing a factory reset from the phone resets the entire firmware and is helpfull to resolve such issues. if you want to install the entire firmware, I would recommend flashing the 4.4.2 PHN firmware you can get the download link in post# 13. But then there were wifi issues after flashing the PHN firmware for which a factory reset from the phone happened to be the solution.
JASONRR said:
Generally doing a factory reset from the phone resets the entire firmware and is helpfull to resolve such issues. if you want to install the entire firmware, I would recommend flashing the 4.4.2 PHN firmware you can get the download link in post# 13. But then there were wifi issues after flashing the PHN firmware for which a factory reset from the phone happened to be the solution.
Click to expand...
Click to collapse
Thanks for that mention of the firmware, I had the radio from that link but forgot you'd also linked the full package. Google Drive is much faster than the websites I'd been trying to get files from, it took 15 hours to download the XSA firmware I was originally going to use.
You were totally correct, resetting the phone was the solution. I got the PHN firmware, flashed it via ODIN only to find it still hadn't fixed the WiFi problem -- even after a factory reset -- however the process of flash/reset/re-flash fixed it for me -- it seems unnecessary to me, but I guess times have changed since I last tinkered with unlocked devices. I'm happy to say that I now have WiFi working under WizCyan now, just wanted to check back in just in case anybody else was facing similar issues. As painful as it is to have to back up and totally restore, sometimes starting completely fresh is the best solution.
Now I'm off to rebuild my SD Card, lol.
andycore said:
Thanks for that mention of the firmware, I had the radio from that link but forgot you'd also linked the full package. Google Drive is much faster than the websites I'd been trying to get files from, it took 15 hours to download the XSA firmware I was originally going to use.
You were totally correct, resetting the phone was the solution. I got the PHN firmware, flashed it via ODIN only to find it still hadn't fixed the WiFi problem -- even after a factory reset -- however the process of flash/reset/re-flash fixed it for me -- it seems unnecessary to me, but I guess times have changed since I last tinkered with unlocked devices. I'm happy to say that I now have WiFi working under WizCyan now, just wanted to check back in just in case anybody else was facing similar issues. As painful as it is to have to back up and totally restore, sometimes starting completely fresh is the best solution.
Now I'm off to rebuild my SD Card, lol.
Click to expand...
Click to collapse
Glad to know that you managed to get the wifi working.
Personally, I did not face the wifi issue after flashing PHN firmware, but know that quite a few have faced this issue as reported in this thread
Normally my understanding and experience is that when you flash different modems / firmware some corruption occurs and factory reset from within the phone resets the partition & firmware. 1st time I experienced this was when I was using a MTK 6575 based device and had amended the EBR, MBR and scatter files to modify the partition sizes, even though these were flashed through mobiuncle tools (similar to odin), the revised partitions did not get changed until I did a factory reset from within the phone. I know that this is irrelevant here but thought that I would share this.

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

touch-screen freezes at lock screen

hi, my friend called me on a different fone to walk them thru the process of rooting/twrp'ing an h811 using this as a guide ( https://www.youtube.com/watch?v=epcXXkMPRWk ).
and it booted up fine and the touchscreen worked. so i suggested they also try cyanogenmod (11.12.2015 nightly). they booted into twrp and did a backup then factory wipe and installed the cm-12.1...zip.
they booted into cyanogenmod and the touchscreen worked. but the t-mobile lte internet wasnt working so they wanted to go back.
good thing they created a backup first...
so they did a factory wipe then restored their image. when they rebooted the got a message process system not responding and the screen doesnt acknowledge any touch.
we tried going into twrp and doing wipe dalvik/cache ... we tried re-rooting using the steps outlined in the youtube video ... but the same problem persists.
after playing around with twrp and wiping random stuff the fone eventually allowed them to unlock the screen but there was no t-mobile service and after about a minute the screen stopped responding while they were scrolling thru the app-drawer.
i think as of now the only os where the touch-screen works is cyanogenmod; is it possible that cyanogenmod/twrp broke the touchscreen or lte modules in android ?
i thought they were two different os's that used different software/firmware ?
suggestions ?
thanks,
It's possibly a corrupt backup file. I would use TWRP to flash the stock ROM & see what happens.
i assumed re-rooting would clean everything since it uses the send-command program (essentially dd's the whole disk) but i guess not.
we also tried installing the rooted stock rom using twrp but still no joy.
Re-rooting doesn't do anything to the rom or drivers unless you're doing the easy root using a system img file. Then you're pretty much replacing your rom with one that has superuser already on it. That being said, did you upgrade to the 10n firmware/bootstack? The easy root is for 10h firmware/bootstack so that could be the source of your issues.
schneidz said:
hi, my friend called me on a different fone to walk them thru the process of rooting/twrp'ing an h811 using this as a guide ( ).
and it booted up fine and the touchscreen worked. so i suggested they also try cyanogenmod (11.12.2015 nightly). they booted into twrp and did a backup then factory wipe and installed the cm-12.1...zip.
they booted into cyanogenmod and the touchscreen worked. but the t-mobile lte internet wasnt working so they wanted to go back.
good thing they created a backup first...
so they did a factory wipe then restored their image. when they rebooted the got a message process system not responding and the screen doesnt acknowledge any touch.
we tried going into twrp and doing wipe dalvik/cache ... we tried re-rooting using the steps outlined in the youtube video ... but the same problem persists.
after playing around with twrp and wiping random stuff the fone eventually allowed them to unlock the screen but there was no t-mobile service and after about a minute the screen stopped responding while they were scrolling thru the app-drawer.
i think as of now the only os where the touch-screen works is cyanogenmod; is it possible that cyanogenmod/twrp broke the touchscreen or lte modules in android ?
i thought they were two different os's that used different software/firmware ?
suggestions ?
thanks,
Click to expand...
Click to collapse
I relatively had the same problem where I flashed CM and did not like it because it was buggy and so I restored an nandroid and the once working nandroid was plagued with errors of the touchscreen not working, the phone would freeze, system crashes... It ended up being caused by the fact that I did not flash the 10N bootstack update before hand. After I flashed the new firmware and then flashed CM; all of CM's bugs disappeared. I haven't gone back to stock LG software since CM works flawlessly and is now my dailydriver so I cant say for sure if it will fix the stock rom but It probably will since it cleared up all my bugs like the camera not working, videos now playing...
btw to get data working in CM go to settings/mobile networks/Access point Names/ then scroll down and click "T-Mobile US LTE IPv6" and that should fix the internet issues you have since it fixed it for me.
they didnt do anything with the 10n bootstack (i dont know what that is).
maybe cyanogenmod automatically does the 10n thing (how to manually go back to 10h) ?
i assumed re-loading the 5 gb .img file would bring us back to square-1 but i guess not.
also, how to know what bootstack they are running. i told them to check about fone but they told me nothing in there mentions 10n or 10h.
About phone > Software Info > software version will will say h81110n if on 10n.
Same here on Stock...
I have this running stock H81110n software, which I flashed using a KDZ. However, it only freezes up occasionally, and turning the screen on and off once or twice always gets rid of the problem. It's not bad enough for me yet to warrant any factory resets or tweaking so far, but the problem is there...

FOTA is not supported

I'm running mrmarzak's stock V8.5 ROM and I got a notification from Wireless Update to download and install the latest update to the ROM. After downloading, I click "Install Now" and I get the message:
"Warning
FOTA is not supported on this device!"
The only way to get rid of the notification is to turn off all notifications for Wireless Updater. Even then, I still get a pop-up reminder every so often to complete the update, but each click-through results in this same message. Can anyone help?
JShan said:
I'm running mrmarzak's stock V8.5 ROM and I got a notification from Wireless Update to download and install the latest update to the ROM. After downloading, I click "Install Now" and I get the message:
"Warning
FOTA is not supported on this device!"
The only way to get rid of the notification is to turn off all notifications for Wireless Updater. Even then, I still get a pop-up reminder every so often to complete the update, but each click-through results in this same message. Can anyone help?
Click to expand...
Click to collapse
Reboot to recovery. Clear cache
Should do it. Might need to clear app data for Fota, or can remove fota.
Don't think you want the full oem ota update anyway.
It updates the preloader and that makes recovering from bad modifications harder (blocks spflash tools)
But if you want the full official ota update, you can restore the "fota reboot apk". It is renamed to ".apk_ " right now to block the install. So you can rename /system/FotaReboot/FotaReboot.apk_ to /system/FotaReboot/FotaReboot.apk
mrmazak said:
Reboot to recovery. Clear cache
Should do it. Might need to clear app data for Fota, or can remove fota.
Don't think you want the full oem ota update anyway.
It updates the preloader and that makes recovering from bad modifications harder (blocks spflash tools)
But if you want the full official ota update, you can restore the "fota reboot apk". It is renamed to ".apk_ " right now to block the install. So you can rename /system/FotaReboot/FotaReboot.apk_ to /system/FotaReboot/FotaReboot.apk
Click to expand...
Click to collapse
Thanks, mrmazak! And thanks for all your work on the R1 HD! I was really in the mood to tinker last night, so I flashed your LIneage port last night... That not only fixed the problem on my phone, but I'm loving the ROM so far. Only thing I've noticed is that the signal indicators for wifi and both SIM cards seem a bit lower than what i remember from the stock ROM (ie. a place that used to give me 4 bars now shows 2 or 3). But I haven't noticed a decline in performance per se. Maybe this is a software glitch and the signals are still read as strongly by the phone?
Again, many thanks for all your efforts!

Question Problem with System updates after unrooting

Hey there,
almost a year ago i rooted my device, tried it for a bit and then realized that i cant use my creditcard app without doing some weird stuff.
so i decided to unroot. everything worked. Now after a long time i wanted to do a normal system update to MIUI 13, but everytime i try to start the update using the devices updater,
i get a dialog saying something like "You device supports seamless system updates. Remember to select Slot A when you get prompted by TWRP" (roughly translated, its in german). I dont really understand why my device is still knowing that i user twrp, even after i removed it and reflashed the original fastboot thingy. (im not too familiar with all the rooting stuff)
I tried to flash again to twrp from my computer and install the update that way but that comes with its own problems and i would prefer to use the system updater rather than twrp.
Does any one have an idea why i get the meantioned dialog and how i can get rid of it to let it update normally?
I just realized that the updater is downloading a file called "xiaomi.eu_multi_HMK40Pro_Mi11i_V14 ... .zip". that looks like some unofficial rom to me, is it pulling it from somewhere else rather than the official xiamo servers maybe?
im really lost at this point.
sorry for some broken english here and there
it also says something about my system being encrypted and that i need to enter a password which never happens.
If it's fetching Xiaomi.eu rom that means you changed the rom from stock to the custom made EU version. If you did not, that most likely means that your device was originally the China version and the seller installed the EU version to provide you with the Google/Play Services.
In short: You are not using the official stock rom. Please post screenshots from your About Phone.

Categories

Resources