Related
[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.
[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
Hi,
I got MTCC-KLD6-V2.97 auto unit and most things work fine but I have some issues and need some answers:
1. Google play services keep crashing. Tried to clean cache/data but it still crashing, usually at starting the car (booting device). Any suggestion to fix this issue.
2. Music app crashes 1-2 times when device boots up. After that it works ok. App has poor interface, no search, lists all folders on the right so navigation is slow. Any replacement app with more features?
I mostly use Rocket player instead of default Music app but only drawback is that steering wheel next/prev buttons do not work with rocket player but triggers default Music app to start.
Any way to replace default Music app with Rocket player app and make those buttons work?
3. Radio app looses stations memory from time to time, and it has that search button at the middle that is easily pressed and easily looses memorized stations. Any alternative/modified Radio app for MTCC-KLD6?
4. If there are alternative Music/radio apps for MTCC-KLD6, how to replace them since my ROM is not rooted?
5. How to root my device?
6. I found newer MTCC KLD9 v2.98 mcu.img and xupdateKLD1024x600LP5.1.1.rk3188.MTCC.October ROM for my radio. Is it worth to make upgrade to those? What are the changes? What would be exact procedure to make upgrade.
Sorry for so many noob questions, hope you can help
Thank you.
Best regards,
Z
grgart said:
Hi,
6. I found newer MTCC KLD9 v2.98 mcu.img and xupdateKLD1024x600LP5.1.1.rk3188.MTCC.October ROM for my radio. Is it worth to make upgrade to those? What are the changes? What would be exact procedure to make upgrade.
Click to expand...
Click to collapse
This would fix 1-5. MCU update probably wouldnt do a whole lot. Just update rom first.
Procedure is easy, put update.img onto microsd, put it in your gps slot, boot into recovery, wipe all and update.
Actually come to think of it, I think MCU 2.98 has a radio station fix in it. Does it @typos1
miffymiffy said:
This would fix 1-5. MCU update probably wouldnt do a whole lot. Just update rom first.
Procedure is easy, put update.img onto microsd, put it in your gps slot, boot into recovery, wipe all and update.
Actually come to think of it, I think MCU 2.98 has a radio station fix in it. Does it @typos1
Click to expand...
Click to collapse
Sure does, well at least on KLD3-9, not sure about non numbred KLDs and KLD2s.
miffymiffy said:
This would fix 1-5. MCU update probably wouldnt do a whole lot. Just update rom first.
Procedure is easy, put update.img onto microsd, put it in your gps slot, boot into recovery, wipe all and update.
Click to expand...
Click to collapse
Thank you, will try.:good:
Same preocedure for mcu.img ?
I would like to backup some apps with data before update, but for that I probably need root to use titanium backup.
how to root this one or is there other way to backup some apps and data?
Also is there TWRP for this one to make full backup if something goes wrong??
Thanx again.
grgart said:
Thank you, will try.:good:
Same preocedure for mcu.img ?
I would like to backup some apps with data before update, but for that I probably need root to use titanium backup.
how to root this one or is there other way to backup some apps and data?
Also is there TWRP for this one to make full backup if something goes wrong??
Thanx again.
Click to expand...
Click to collapse
Yes same procedure as MCU, there is no need to back anything up if you are flashing the MCU. TWRP is not recommended for these units either, but even if it was you cannot flash or backup the MCU with it.
typos1 said:
Yes same procedure as MCU, there is no need to back anything up if you are flashing the MCU. TWRP is not recommended for these units either, but even if it was you cannot flash or backup the MCU with it.
Click to expand...
Click to collapse
I ment apps backup. I installed and setup some apps (torque, rocket player, igo...) and after I flashing ROM I need to install and setup those apps all over again, don't I?
Also do I need to flash mcu and then ROM or it does not matter which is flashed first?
Thank you.
typos1 said:
Sure does, well at least on KLD3-9, not sure about non numbred KLDs and KLD2s.
Click to expand...
Click to collapse
I did it on my kld2 so should be good.
grgart said:
I ment apps backup. I installed and setup some apps (torque, rocket player, igo...) and after I flashing ROM I need to install and setup those apps all over again, don't I?
Also do I need to flash mcu and then ROM or it does not matter which is flashed first?
Thank you.
Click to expand...
Click to collapse
Separately or together, either way is fine, its good practise to update the MCU as well.
miffymiffy said:
I did it on my kld2 so should be good.
Click to expand...
Click to collapse
Cool, just non numbered KLDs it doesnt work on then.
So there is no way to keep/backup installed apps and data?
Flash procedure should be like this?
1 boot to recovery
2 select option "update system/mcu image from sdcard"
3 select mcu.img from sdcard and flash
4 reboot to recovery
5 select option "update system/mcu from sdcard and clear all"
6 select rom.img from sdcard and flash
7 reboot to system
8 install apps again
grgart said:
So there is no way to keep/backup installed apps and data?
Flash procedure should be like this?
1 boot to recovery
2 select option "update system/mcu image from sdcard"
3 select mcu.img from sdcard and flash
4 reboot to recovery
5 select option "update system/mcu from sdcard and clear all"
6 select rom.img from sdcard and flash
7 reboot to system
8 install apps again
Click to expand...
Click to collapse
If youre using the standard ROM, other than Titanium or similar no.
I had the same problems with the same product.. and more.. i don't get to install the android auto app... could you help me? Did you have to root your device? Thanks Gustavo
Question regarding KLD, I'm confused about numbers.
What that number after KLD represents?
My device is KLD6-V2.97 and on repository there is KLD9-V2.98 mcu.img
Is that KLD9 img compatible with my KLD6 or do i flash only KLD6 imgs?
Thanx.
lgclopes said:
i don't get to install the android auto app... could you help me?
Click to expand...
Click to collapse
Not sure I understand what do you mean by this "android auto app". Can you clarify the question?
grgart said:
Question regarding KLD, I'm confused about numbers.
What that number after KLD represents?
My device is KLD6-V2.97 and on repository there is KLD9-V2.98 mcu.img
Is that KLD9 img compatible with my KLD6 or do i flash only KLD6 imgs?
Thanx.
Click to expand...
Click to collapse
Maybe. It appears that numbered kld mcus are interchangeable. It is the non numbered that seem not to be. I have a kld2 that I have flashed both on and it works. Just need to change key options in factory settings(MCU)
lgclopes said:
I had the same problems with the same product.. and more.. i don't get to install the android auto app... could you help me? Did you have to root your device? Thanks Gustavo
Click to expand...
Click to collapse
Android Auto will not work installed on these units. It is intended to be installed on the phone.
Installed KLD9 2.98 mcu and malaysk rom, and all works fine.
If you flash mcu, take screengrab of all factory settings (pass 126), you'll need to setup it again.
Only thing I noticed is about Igo Nextstep, everithing is smaller on malaysk rom, like DPI is different. Will fix DPI at sys.txt
Also, seams that GPS audio mixing is not exactly as set, even level is 0 music level gets lower when voice is activated.
grgart said:
Installed KLD9 2.98 mcu and malaysk rom, and all works fine.
If you flash mcu, take screengrab of all factory settings (pass 126), you'll need to setup it again.
Click to expand...
Click to collapse
You can also backup your MCU config and restore it as you would flash an MCU or ROM.
grgart said:
Hi,
I got MTCC-KLD6-V2.97 auto unit and most things work fine but I have some issues and need some answers:
1. Google play services keep crashing. Tried to clean cache/data but it still crashing, usually at starting the car (booting device). Any suggestion to fix this issue.
2. Music app crashes 1-2 times when device boots up. After that it works ok. App has poor interface, no search, lists all folders on the right so navigation is slow. Any replacement app with more features?
I mostly use Rocket player instead of default Music app but only drawback is that steering wheel next/prev buttons do not work with rocket player but triggers default Music app to start.
Any way to replace default Music app with Rocket player app and make those buttons work?
3. Radio app looses stations memory from time to time, and it has that search button at the middle that is easily pressed and easily looses memorized stations. Any alternative/modified Radio app for MTCC-KLD6?
4. If there are alternative Music/radio apps for MTCC-KLD6, how to replace them since my ROM is not rooted?
5. How to root my device?
6. I found newer MTCC KLD9 v2.98 mcu.img and xupdateKLD1024x600LP5.1.1.rk3188.MTCC.October ROM for my radio. Is it worth to make upgrade to those? What are the changes? What would be exact procedure to make upgrade.
Sorry for so many noob questions, hope you can help
Thank you.
Best regards,
Z
Click to expand...
Click to collapse
I found the MTCC KLD9 v2.98, but can't seem to find the correct ROM... Here is my MCU Version:
MTCC-KLD6-V2.97
Aug 02 2016 10:35:08
Android version：
5.1.1
1024*600
Kernel version：
3.0.101+
[email protected] #110
Mon Aug 22 17:20:57 CST 2016
Build number：
rk3188-userdebug 22082016.17:29:44
It's an Eonon and would like to put another ROM on it, Malaysk or maybe something else
dlsc2111 said:
I found the MTCC KLD9 v2.98, but can't seem to find the correct ROM... Here is my MCU Version:
MTCC-KLD6-V2.97
Aug 02 2016 10:35:08
Android version：
5.1.1
1024*600
Kernel version：
3.0.101+
[email protected] #110
Mon Aug 22 17:20:57 CST 2016
Build number：
rk3188-userdebug 22082016.17:29:44
It's an Eonon and would like to put another ROM on it, Malaysk or maybe something else
Click to expand...
Click to collapse
Its not an Eonon, theres no such thing as an Eonon, Eonon sell Klyde units - your is a Klyde, you can tell from the "KLD" bit in the MCU identifier.
Your MCU version is not important when it comes to the ROM.
What do you mean that you cant find the correct ROM ? - you can use ANY 1024x600 RK3188 ROM that you want.
Google play services keep crashing with Malaysk ROM also.
Tried to clean cache/data but it still crashing, usually after car turon and starting it after short time.
There is some "Play Store Fix/" folded at huifei.fs-fileserver.de/content/, does those apps fix that problem?
Any suggestion to fix this issue?
Thank you.
Hi all! So, you have a P8 lite in your pocket and you hate EMUI? Well, that was my case too, it's uncustomizable, ugly, and removes plenty of features from android stock. I do not like it one bit, and I like even less the fact that this phone is getting no more updates, ever. This sucks, it all sucks, luckily we can say "F all that" and do whatever we want with this device, provided you follow this guide.
I am making this guide because I want to condensate every single thing I know about this device in one single thread. One big guide to help all of you out installing custom ROMs. Without this, you would have to do research along multiple threads, often with conflicting information, and what's even worse, DEAD LINKS! There's nothing more frustrating than finally finding the solution to your problem, just one download away, just to be greeted by a dead link, and you would need to scout for another file that may or may not work... ugly stuff.
So, the point of this is to bring up to date info so you can make this device rock. This guide assumes you have Huawei's EMUI 4.0 installed which runs on Android 6.0. I'm also assuming you have your bootloader locked, and I will explain how to unlock it FOR FREE. No need to pay to some shady site in order to access what effectively belongs to you.
These are the requirements for this guide:
Code:
#USB cable
#A PC
#Some charge on the device to ensure nothing goes wrong
#An SD Card
#Patience
Before beggining, a quick disclaimer:
Code:
#It's not my objective to break your device, however there's always a risk when doing these kind of things.
#When you follow this guide's steps your are accepting the risks and are taking full responsiblity for whatever may happen to your device.
#Don't blame me for breaking your stuff if that happens, all I'm listing here worked for me, and should work for you.
#I won't be babysitting anybody to help solve their specific problems, don't PM me asking me why X doesn't work.
#I am unaware if this works in other versions of this device, but I'm positive this works on both ALE-L23 and ALE-L21
#If you have a "CAM-XXX" device, it's highly likely this works for you too, but as with everything, TRY AT YOUR OWN RISK.
#YOU HAVE BEEN WARNED!
Ok, so let's begin. As the title says, the guide is applicable to any custom ROM. However, I will be installing Lineage OS 14.1 which runs on (almost stock) Android 7.1.2. Regardless, the final step where we install the custom ROM is interchangable, and you can use whichever you please.
This process WILL wipe all of your data (except SD card). Make sure to make a backup of everything you want to save (app configs, photos, videos and whatever else).
1. DOWNGRADING TO ANDROID 5
As you may know, Huawei has stopped providing bootloader unlock codes for very stupid reasons. This has led to many unable to unlock their bootloader and having to pay for third party apps in hopes they don't get scammed. There are some trustworthy sites where you can get these at a fee tho (mainly DC Unlocker at 4 bucks), so if you want to pay up to avoid having to downgrade to Android 5, you can do so. However, I understand that you may not want to pay at all, I didn't want to either.
To get the bootloader unlock code, we need root, and to get root, we need Android 5. Why? Because getting root in Android 6 requires us to flash some zips, and for that we need TWRP, and for that we need an unlocked bootloader, everyhing closes up very nicely. So, we have no choice but to downgrade.
An SD card is not needed for this process, but it is going to be required at a later point, so why not use it now too?
NOTE: It may be a good idea to make a factory reset at this point, to avoid issues. For that, do the following:
Turn your phone off.
Boot the phone by holding the power button and the volume up button at the same time.
Wait untill the Huawei logo appears, then let go of both buttons.
You should be in recovery mode, navigate with the volume keys to the "Wipe data/factory reset" option.
Select it with the power button and wipe everything.
Reboot the device with the option in the menu.
Once the device has booted up, follow the guide.
Alright, once that's done, connect your phone to the PC to transfer some files:
NOTE: There's two Stock Android 5s downloads ("HW_Android_5_Transition.zip" and "HW_Stock_Android_5.zip"). One is a transition package, as the name implies, and the other is Huawei's EMUI 3.1 in all of it's glory. What's the difference? The transition package is a much smaller file that is designed to downgrade the phone from EMUI 4.0 (Android 6) to EMUI 3.1 (Android 5). If you are running EMUI 4.0 (which should be the case) then you can use the transition package which will take less to download. If you have another version (i.e. EMUI 4.1) you should use "HW_Stock_Android_5.zip". However, the latter is the safe bet. If you are not sure which one to use, use "HW_Stock_Android_5.zip". The process is exactly the same for both packages.
Extract the "UPDATE.APP" file from "HW_Stock_Android_5.zip" or "HW_Android_5_Transition.zip".
Navigate to your phone's internal memory or SD card (whichever you want to use) and locate a folder called "dload". If there's not one, create it.
Put the "UPDATE.APP" file inside of the "dload" folder.
Turn your phone off.
Once it's off, press the power button and the two volume buttons until you see the Huawei logo.
That should make the phone recognize the "update" and start flashing it. Once it finishes, it will try to boot by itself, so pressing those 3 buttons was your last input until the phone boots into Android 5. It will take a long time for it to both finish and boot, don't be afraid, the phone is not bricked. If you think the phone is indeed bricked because it has been stuck at the logo screen for way to long (longer than an hour) then proceed to the "Unbricking" section of this guide. However, it's highly unlikely that this will happen, as Huawei checks the file before flashing it, so if it's incompatible with your device it should not do anything and boot again into Android 6 with everything untouched.
2. ROOTING ON ANDROID 5 AND EXTRACTING BOOTLOADER UNLOCK CODE
Once you are in Android 5, we will need to root the device. Download KingRoot (proved to work) or another one click root app of your choice. I'm aware of KingRoot's bad reputation because of the spyware accusations, but the phone will be wiped anyway and we are sure it works, so it doesn't really harm at all. If you still don't want to use it, check with other apps, I haven't done so myself so I don't know what else works.
Once your phone is rooted, we will need to use the terminal for the first time. We will need to setup ADB and Fastboot, if you already have that, skip this step.
Extract the "platform-tools" folder from the zip and place it somewhere nice.
Shift right click on a blank space INSIDE of the "platform-tools" folder.
Select "Open command window here".
This should be enough to get ADB working, but we need to make some config on the phone itself too.
Go to Settings -> About Phone
Look for a line that says "Build Number" and tap it multiple times.
When the message saying "You are now a developer" pops up, go back and enter the new "Developer Options" menu.
In there, look for an option called "USB Debugging" and turn it on.
Connect the phone to your PC via USB cable.
A message should have popped up on the phone asking for permission to use USB Debugging, tap on "Always allow from this PC" and then on "Allow".
NOTE: If the message doesn't pop up, you can try a number of things. I prefer to tap the "Revoke USB debugging authorizations" button to ensure that no PC is authorized, so the message must pop up at some point. Once you revoked authorizations, disconnect and connect the phone again, if you still don't see it, try to select MTP as the transfer protocol. If not, then PTP, if you still don't see it install Hi Suite on your PC and open it, it should pop up now.
Once you have everything working, type the following in the terminal in your PC:
Code:
adb devices
If you see a serial number there, that's your phone, and that means everything is set up correctly (make sure you don't have any other device attached to your PC, or you could confuse the two and make bad stuff happen for that other device). If you don't see it, make sure USB Debugging is enabled. You can try to use different cables if you still have problems. Now type:
Code:
adb shell
And then:
Code:
su -c "grep -m1 -aoE 'WVLOCK.{14}[0-9]{16}' /dev/block/mmcblk0p7 |grep -aoE '[0-9]{16}'"
KingRoot (or the app you used to root) should prompt you (in your phone) if you want to give ADB root access, make sure to allow it to make this work. This should give you your unlock code. SAVE IT INTO A TXT FILE AND COPY THAT FILE TO ALL OF YOUR PCS, ALL OF YOUR CLOUD ACCOUNTS AND ALL OF YOUR MOBILE DEVICES.
(Maybe the terminal gets stuck at this point, press CTRL + D (or C) to get it unstuck).
Seriusly tho, it didn't happen to me, but it is a possibility that your Bootloader can re lock after doing some of the things that follow, in which case you will need to unlock it again, and if you don't have that code... it's back to square one.
3. GOING BACK TO ANDROID 6
Now that we have done all that we wanted on Android 5, it's time to go back. The process is exactly the same.
Extract the "UPDATE.APP" file from the "HW_Stock_Android_6.zip" file and move it to the dload folder (SD card or Internal).
Turn off your phone and turn it on again with all three buttons pressed.
Wait.
???
Profit.
So, we're back on Android 6. Why did we go back you may ask? Why did we not just flash our precius custom ROM? Well, for once, this gives people the chance to stay on EMUI if all they wanted was to unlock the bootloader and maybe root on Android 6 (which I will explain how to do too, in case you want to). Another, more important reason, we need Android 6 to install the B895/B896 update, which is a requirement for any custom ROM (mainly Android 7.0+) if you don't want any problems with your SIM card (and others that may arise).
4. UNLOCKING BOOTLOADER AND FLASHING TWRP
Now, we need to turn on USB Debugging again, and to allow our PC... again. Do so, and check that everything is right with:
Code:
adb devices
If that's the case, then type the following:
Code:
adb reboot bootloader
Your phone will reboot, and you should see a white screen with a wasted android above a green text saying "PHONE LOCKED". If that's the case, take a moment to say goodbye to that green text, because it will soon turn very red. We will need to unlock the bootloader with the code you got from the previous steps, for that type the following:
Code:
fastboot oem unlock ****************
In place of the "****************" you must enter your code, of course. And that was it, now the green text is replaced with a red "PHONE UNLOCKED". This are good news. Now, we need to flash our custom recovery if we want to do anything fancy with the device. For that, extract the "recovery.img" file from the "TWRP_3.1.1.zip" file and paste it into the same folder where all of the ADB files are located (where "adb.exe" is). Now type:
Code:
fastboot flash recovery recovery.img
This will flash TWRP into your device, hooray! Now type:
Code:
fastboot reboot
And your device should turn back on, today is a bright day my son. Now you must take a decision, do you want to flash a custom ROM and get very nice and fancy features or do you want to stay with what you have? If you prefer Huawei's EMUI 4.0, then follow to the next step. If you want to flash custom ROMs, then skip the next one.
5. ROOTING ON ANDROID 6 (OPTIONAL)
I don't know why you would prefer EMUI over... anything else really, but it's your call. I'll tell you how to root it so you can at least take some advantage of it. You see that file called "HW_Android_6_Root.zip"? Extract it, inside there will be... another folder called Root... huh? Redundant. Anyway, inside of that there should be two zips. 1.zip and 2.zip. You will need to place the folder called "Root" inside of your SD card or your internal storage. Then, go back to the terminal and type:
Code:
adb reboot recovery
You should reboot into TWRP, isn't it nice? Anyway, we have to flash some zips! Go to "wipe" first and wipe the "Cache" partition and the "Dalvik" partition. Once that's done, go to install and navigate to the Root folder your placed... well, you know where. Select 1.zip and flash it, once it's finished reboot the device. If TWRP prompts you to install it's app, DO NOT DO IT. Once the phone has rebooted (it will take longer because of the cache and dalvik wipe), repeat the process but flash 2.zip this time, reboot and your phone should be rooted. This is the end of the line for you now, as you don't want to make anything else to the phone. However, you can go to the final chapter where I explain how to install Xposed framework, if you want more customization. EMUI doesn't like Xposed very much, so there's little you can do with it, but it's something I guess.
6. INSTALLING THE B895/B896 UPDATE
So, you followed the power user path, the one we all really want deep down. That's cool, I respect you. We gotta use that custom recovery we just flashed, but first we need to transfer some files into our phone's memory. We need to install an update to the phone, for which you need Android 6 (that you should already have anyway). There's two different updates, B895 and B896. As you may guess, B896 is newer. However, any of these two will (or rather should) work without issues. I personally used B896, but some people claim B895 is more stable. I can't find a difference really, but the process is the same regardless of which you choose. Once you have made that decision, move "B895_update.zip" or "B896_update.zip" to your phone's internal storage or SD card AS IS (don't extract it). Then type into the terminal:
Code:
adb reboot recovery
You should be in TWRP now. Go to wipe and select the "Cache" and "Dalvik" partitions ONLY, then wipe them. Once that's done, go to install and flash your update of choice. Once finished, reboot the device. If TWRP prompts you to install it's app, DO NOT DO IT. The boot should take longer than usual because of the "Cache" and "Dalvik" wipe... and because of the update too. Once booted, you should be in EMUI 4.1. Go to settings and into "About Phone". In there, look for a field called "IMEI". If you see a number, that means you did everything properly, if you see "unkown" or nothing at all, then that means you lost your IMEI... which means you will have connectivity issues. To fix this, you will need to do a full wipe (so, boot into recovery (we lost TWRP due to the update) and then go to wipe, in there select everything except SD card) and follow the steps again starting from 3, this time flashing the other update (so if you flashed B895, flash B896 this time and vice versa)).
Now, this last step we made has wiped our custom recovery... so sad. We have to flash it again, but we are almost finished!! Now it's time for you to move the custom ROM you want to your SD card (SD card is mandatory, as we will wipe internal storage). You should also move your custom ROM of choice. If you want root, also move the "SuperSUv82.zip" file.
OPTIONAL:
If you want Gapps, that means the Google apps, so PlayStore, Google services and such (and you really should want them, as Android without PlayStore is kinda rough), then you need to download them separately.
So, go to the Gapps website and select the pacakge you want. You NEED to choose the ARM64 platform, the android version depends on the ROM you are flashing, so check which version it runs, and the package itself is personal preference. Here you can see a comparison of each package, detailing what each one contains so you can make a decision. The aroma package is kinda bugged, I would avoid it. Choose wisely, as flashing another Gapps package once you have flashed a different one can and most likely will cause issues. If you want my opinion, I would stick to the nano package. It offers the basic Google functionality and allows you to download other Google apps you may need/use with the PlayStore once you are booted up.
Once you choose your package, move it to your phone's SD card along with the ROM and the SuperSU zip if you want it.
Check that USB Debugging is still enabled, and then type:
Code:
adb reboot bootloader
Once into the bootloader, flash the custom recovery once again with:
Code:
fastboot flash recovery recovery.img
Then:
Code:
fastboot reboot
Once booted up again, type:
Code:
adb reboot recovery
And now it's time to drop the bomb, say bye bye to EMUI, and say hello to... whatever it is you are installing.
7. FLASHING YOUR CUSTOM ROM OF CHOICE
MOST CUSTOM ROMS REQUIRE AN LTE CAPABLE SIM IN ORDER TO HAVE CELLULAR NETWROK WORKING CORRECTLY, THIS DEPENDS ON A ROM TO ROM BASIS, DO YOUR RESEARCH BEFORE FLASHING
Once in TWRP, go to wipe and check every box, I'm serius, check everything except the SD card. Once that's finished, the moment of glory has come. Go to install and flash your ROM. It will take a while, and when that's done reboot. The phone should boot into your ROM. If you want either Gapps or SuperSU, make a quick setup and enable USB Debugging again, then reboot to recovery with:
Code:
adb reboot recovery
Once in TWRP, go to install and flash the Gapps package and the SuperSU zip (in that order) if you want it. Reboot. That should be it! You are done!
8. UNBRICKING
I don't know why, but with all the flashing and the testing I've done you would have thinked that I should have suffered of a brick state at least once... that was, luckily, not the case. I haven't suffered a single brick. I don't know if I'm extremely lucky or if this phone is tremendously resilient, but the case is I haven't had any issues of this kind.
However, I can understand that it is a possibility, so if this happens to you my best advice is to do the following: Boot into recovery mode (either stock or TWRP depending on where in the whole process you got stuck), make a full wipe and apply the update from "HW_Stock_Android_6.zip" with the dload folder and the three buttons method. That should get it unstuck, if not... try the same with the "HW_Stock_Android_5.zip" 's "UPDATE.APP".
9. INSTALLING XPOSED FRAMEWORK (OPTIONAL)
What? A custom ROM is not enough for you? Getting freed from EMUI is not enough? Well fear not then, because there's one last step for the true power user, for that man who thinks that everything is not enough, the good old Xposed Framework *queue fireworks and trumpets.
So, you need to install the Xposed Installer apk. Get it from here, and ONLY THERE. I once installed an apk from another source... ended up being adware, not fun. The apk is at the very bottom of the thread. You will also need the framework itself, get it from here.
Get the latest (arm64) version for your ROM. This depends on what Android version it is running on:
Code:
SDK21 = Android 5.0
SDK22 = Android 5.1
SDK23 = Android 6.0
SDK24 = Android 7.0
SDK25 = Android 7.1
SDK26 = Android 8.0
SDK27 = Android 8.1
You should also get the uninstaller in case things go south.
Once you got the files, install the apk on your phone. Open the app once. Transfer the framework and the uninstaller into your SD or internal storage. Boot into TWRP recovery and install the framework, reboot the device.
NOTE: Android 6.0 takes about 20 mins to boot, wait about an hour before deciding that it's bricked. Android 7.1.2 took me about 2 mins. I'm unaware of the boot times of other versions, but be aware that it can take LONG. If you think it really got bricked, boot into TWRP again and flash the uninstaller. That should get it unstuck and you can either try again or leave it as is.
----------------------------------------------------------------------------
Well guys, that's all I got, quite a big write up huh? I don't really have nothing else to say, just remember that what you are doing here is at your own risk and I don't want anybody blaming me for the bad things that can happen. I will proceed to leave you with the download links so you can try this yourself. I'm currently running Lineage OS 14.1 which features Android Nougat 7.1.2 on my Huawei P8 lite ALE-L23, I've never been happier to be free from the manufacturer's ROM.
DOWNLOADS
(The B895 and B896 update's links are not mine)
Huawei's Stock Android 5:
Android Filehost
Mediafire
Huawei's Android 5 Transition:
Android Filehost
Mediafire
Huawei's Stock Android 6:
Android Filehost
Mediafire
Huawei's Android 6 Root:
Android Filehost
Mediafire
EMUI 4.1 (B895):
Android Filehost
EMUI 4.1 (B896):
Android Filehost
Platform-Tools:
Android Filehost
Mediafire
TWRP 3.1.1:
Android Filehost
Mediafire
Gapps:
Open Gapps
SuperSU:
Android Filehost
Google Drive
Hi,
I didn't understand what do you mean whan you write: Once booted, you should be in EMUI 4.1. If you retained your IMEI, you are in good path, if not... then do a factory reset (wipe everything) and repeat the steps starting from 3.
Could you explain it better?
Thank you
ilmatte said:
Hi,
I didn't understand what do you mean whan you write: Once booted, you should be in EMUI 4.1. If you retained your IMEI, you are in good path, if not... then do a factory reset (wipe everything) and repeat the steps starting from 3.
Could you explain it better?
Thank you
Click to expand...
Click to collapse
Yes, it's basically this: If you go into the "About Phone" section you will see that there's a field detailing your IMEI. I won't lie, I don't know exactly what it is, but it's a unique number for every phone and has something to do with your cellular network connection.
If you messed up at some point, you can lose your IMEI (i.e. you won't see it in that field or it will say "unknown" or something of the sort). If that happens, then it means you did something wrong, and proceeding in this state will make you have problems with your connection. The signal would be really unstable and it would be practically unusable.
To make a simpler check, if you have a cellular network connection, and can make calls and send/receive SMS on EMUI 4.1, then you won't have any problems.
Ah ok it wasn't so clear but I know what an imei is luckily it didn't erase it in my case. Anyway, I don't know how to thank you bro! You saved my life. I beleived to be screwed when I learned that Huawei stopped releasing the bootloader unlock code. How stupid they are. I blamed them through the customer support. I'm running lineage now! Kiss my ass Huawei!
ilmatte said:
Ah ok it wasn't so clear but I know what an imei is luckily it didn't erase it in my case. Anyway, I don't know how to thank you bro! You saved my life. I beleived to be screwed when I learned that Huawei stopped releasing the bootloader unlock code. How stupid they are. I blamed them through the customer support. I'm running lineage now! Kiss my ass Huawei!
Click to expand...
Click to collapse
Glad to hear I helped! Mind dropping a thank on the main thread? Hope you enjoy your phone
Thanks <3 -notes
Thank you tralph3, you make my life so easy, great easy guide. I have a few suggestions for improving clarity:
Step 1. "Stock_Android_5.zip" contains "transitional" android 6.0 ALE-L21C900B500 firmware According to including Spanish documentation "3., 3.1 Download the Android5.0 update package" It must be downloaded another 5.0 firmware. I use this 5.0 firmware to make kingroot preform root.
Firmware: huaweidl.com/download/p8-lite/ale-l21/b204/
Look for a line that says "Compilation Number" and tap...
Click to expand...
Click to collapse
Step 2. second point 2. Change to "Build Number"
su -c "grep -m1 -aoE 'WVLOCK.{14}[0-9]{16}' /dev/block/mmcblk0p7 |grep -aoE '[0-9]{16}'"
Click to expand...
Click to collapse
Step 2. getting unlock code. After executing command. Add step -Kingsroot display root access prompt ALLOW it.
t
Thanks for your work.
BelisTT said:
Thank you tralph3, you make my life so easy, great easy guide. I have a few suggestions for improving clarity:
Step 1. "Stock_Android_5.zip" contains "transitional" android 6.0 ALE-L21C900B500 firmware According to including Spanish documentation "3., 3.1 Download the Android5.0 update package" It must be downloaded another 5.0 firmware. I use this 5.0 firmware to make kingroot preform root.
Firmware: huaweidl.com/download/p8-lite/ale-l21/b204/
Step 2. second point 2. Change to "Build Number"
Step 2. getting unlock code. After executing command. Add step -Kingsroot display root access prompt ALLOW it.
t
Thanks for your work.
Click to expand...
Click to collapse
Thanks for pointing this stuff out, I'll make those changes you suggested and try to fix some typos too. So, what I gather from what you told me about that Android 5 thing is that in order to correctly flash the update I'm providing you NEED to be in Android 6, right? Whereas with the one you are providing me it should boot into Android 5 regardless of what you currently have. If that's the case, I'll include both and tell people of the distinction between the two so they can use the one they want/need (after all, the transition package is much smaller and easier to download). I'll download the package and upload it to Android Filehost along with everything else. I think I'll keep the mediafire downloads as a mirror. I'll get to that, thanks.
tralph3 said:
.... in Android 6, right? Whereas with the one you are providing me it should boot into Android 5 regardless of what you currently have.
Click to expand...
Click to collapse
Yes, exactly. Thanks for curating this additional download, good idea.
Does this also work for the PRA-LX1 version?
I have Android 8.0 on it and absolutely no idea what EMUI version or eben the firmware version.
I want to put crDroid on this phone because EMUI ... you know, it's bad.
Otherwise: I am ok with paying these 4€ if this payed unlock works.
WHICH of all these DC Unlocker Apps do I need for getting the unlock code?
Badoolo said:
Does this also work for the PRA-LX1 version?
I have Android 8.0 on it and absolutely no idea what EMUI version or eben the firmware version.
I want to put crDroid on this phone because EMUI ... you know, it's bad.
Otherwise: I am ok with paying these 4€ if this payed unlock works.
WHICH of all these DC Unlocker Apps do I need for getting the unlock code?
Click to expand...
Click to collapse
DON'T TRY ANY OF THIS. All of what I've detailed is for the P8 lite 2015, your phone is a different 2017 version that's basically another completely different phone with the same name, because Huawei doesn't know how to namr their devices. You have a different chipset, doing anything of what's described here will most likely brick your phone. With that said, maybe the bootloader unlock method works IF YOU FIND ANOTHER WAY TO ROOT YOUR PHONE. DON'T ROLL BACK TO ANDROID 5 WITH THE FILES I'M PROVIDING PLEASE.
This forum is dedicated to P8 lite 2015, you can see there's a different forum for 2017. Good luck.
Hello, I have ALE-L21 with EMUI 4.0.3 - MM 6.0 - version B633 and i can not downgrade to android 5, phone says : update failed, or stuck on 5%. could someone help me please ?
I tried a lot of stock ROMs, 5.0 , 6.0 etc, nothing worked for me.
Thanks,
Ax1qwer said:
Hello, I have ALE-L21 with EMUI 4.0.3 - MM 6.0 - version B633 and i can not downgrade to android 5, phone says : update failed, or stuck on 5%. could someone help me please ?
I tried a lot of stock ROMs, 5.0 , 6.0 etc, nothing worked for me.
Thanks,
Click to expand...
Click to collapse
Are you using the stock package or the transition package? If you are using the transition package, try stock.
I tried both, with no success. And many others.
I tried to update via internal storage and SDcard too, with no success.
If phone is connected to pc, updating stuck on 5%, if not connected to PC, update fails.
Ax1qwer said:
I tried both, with no success. And many others.
I tried to update via internal storage and SDcard too, with no success.
If phone is connected to pc, updating stuck on 5%, if not connected to PC, update fails.
Click to expand...
Click to collapse
Did you wipe all of your data with the stock recovery? If nothing works then I could suggest you to try to apply the downgrade with sideload. (Boot into recovery and select to apply update from adb, then you type adb sideload <filename>)
I'm clueless on why it doesn't work on your device, it should.
Also, you can try to flash the stock android 6 rom first, that's an older emui version (4.0). If you can flash that, then maybe you can flash android 5 after it.
i have tried intalling both the 5.0 stock roms but it always fails at 5%. i got ALE-L21C02B896 with emui 4.1 and android 6.0. i've been trying different guides but all lead me to dead ends. please help
thanks in advance
Wazu786 said:
i have tried intalling both the 5.0 stock roms but it always fails at 5%. i got ALE-L21C02B896 with emui 4.1 and android 6.0. i've been trying different guides but all lead me to dead ends. please help
thanks in advance
Click to expand...
Click to collapse
I have the exact same firmware(ALE-L21C02B896) that you have and I also cant downgrade to android 5.0 using any of the tutorials that I found in XDA Furum.
razorfancy said:
I have the exact same firmware(ALE-L21C02B896) that you have and I also cant downgrade to android 5.0 using any of the tutorials that I found in XDA Furum.
Click to expand...
Click to collapse
Yeah it very frustrating, please let me know if you find a way and ill do the same.
Wazu786 said:
Yeah it very frustrating, please let me know if you find a way and ill do the same.
Click to expand...
Click to collapse
Told you guys, try to flash android 6 and see if that works, afterwards you can flash android 5.
tralph3 said:
Told you guys, try to flash android 6 and see if that works, afterwards you can flash android 5.
Click to expand...
Click to collapse
I tried your Huawei's Stock Android 5, Huawei's Android 5 Transition and Huawei's Stock Android 6 and all failed to install giving error at 5 percent.
tralph3 said:
Told you guys, try to flash android 6 and see if that works, afterwards you can flash android 5.
Click to expand...
Click to collapse
i tried android 6 also and it also failed at 5%, please is there anything else i can try?
This thread is how I have managed to upgrade a Samsung S5 with Android 6.01 to LineageOS 16 with a Mac laptop running Sierra, in an attempt to keep on using it with my car infortaintment system.
First of all it's important to leave very clear 2 things:
ALL THIS INSTRUCTIONS APPLY TO A SAMSUNG S5 SM-G900F kltexx device. I don't know how it will work in any other device . This is what has worked for me and I'm sharing this with you all just hoping that will be useful for someone else.
YOU ARE THE SOLE RESPONSIBLE FOR ANYTHING THAT MIGHT HAPPEN TO YOUR DEVICE.
So let's get started.
Prepare your system:
You must have the Samsung USB drivers installed (I used the latest ones from Samsung - https://developer.samsung.com/mobile/android-usb-driver.html).
You need to allow your device to debug it using the USB. Instructions here: https://androidcure.com/enable-usb-debugging-samsung-galaxy-s5/
You need to install adb in your computer. The easiest way to do it is this one: https://www.cyanogenmods.org/minimal-adb-and-fastboot-windows/ although another option would be to install Android SDK platform tools, but thats much heavier (https://developer.android.com/studio/releases/platform-tools). Usually the first option is enough.
You need to ensure that your Samsung will always trust your computer. So connect your Samsung with your computer and when it asks if your computer can be trusted, make sure that you click on the checkbox with the option "Always".
ODIN:
You need to install a Recovery System in your device and for that you will need ODIN which is a tool created by Samsung to flash files to Samsung devices. It has a version for Mac which has worked for me. Go to this site to learn how to use it and to download it: https://macmetric.com/odin-for-mac/ or you can right jump to this site (https://forum.xda-developers.com/devdb/project/dl/?id=20803) to just download the version that worked for me.
ROOT : (Optional)
By default your device has the bootloader unlocked. This was something that drove me crazy as I couldn't find anywhere to show me if it was. I ended up rooting my device to confirm that it was unlocked and also to confirm the real name of my device. So it's almost 100% certain that your Samsung S5 has the bootloader unlocked, but in case you want to confirm it, as I did, follow the instructions from this thread https://forum.xda-developers.com/showthread.php?t=2696537.
Basically, I ended up on this page, CF-Auto-Root homepage
http://autoroot.chainfire.eu/ downloading the file to root my device from there and flashing it with JOdin. Keep in mind that you might think that your device is version klte and there are at least 5 klte: kltedx, kltexx, kltezh, klteduosxx and kltejv. Mine ended up being kltexx
In my case I followed the process described in that thread and tried to root my device with the file for kltedx and it didn't wok out. Then I tried again with the file for kltexx and it worked. That's how I discovered that mine was kltexx.
TWRP :
You need to install a custom recovery system to your Samsung S5 device to be able to flash the LineageOS ROM. This site has the instructions that I followed to install it: https://www.cyanogenmods.org/forums/topic/install-twrp-recovery-samsung-android-using-odin/
It is extremely important to highlight that the latest version of TWRP didn't work for me. I installed the latest one and everything seemed to be OK but it was not. I couldn't flash any ROM with it. I ended up discovering that for my case, the best option was to install an older version. To be more precise, version 3.0.2.2 (https://eu.dl.twrp.me/klte/twrp-3.0.2-2-klte.img.tar.html).
To make sure that you have been able to install TWRP do the following. There are 3 ways to boot your Samsung S5: Normal boot, Download mode (ODIN) and Recovery mode. We need to start up on recovery Mode and see a screen menu similar to the one we've seen in the previous thread (https://www.cyanogenmods.org/forums/topic/install-twrp-recovery-samsung-android-using-odin/).
To do so, start the device on Recovery mode:
For the Normal mode you just click the Power Up key and wait. No magic here.
For the Download mode you have to switch off your device and then click at the same time the Power Up key, the Volumen Down key and Home key. It comes with the standard installation, so no magic here either.
Home Key
For the Recovery mode, you have to switch off your device and then click at the same time Power Up key, Volumen Up key and Home key. After a couple of seconds, the screen will say at the top "Recovery option..." and you should be able to see the touch screen menu of TWRP.
Flashing LineageOS 16 :
This is suppose to be an easy step but it ended up being very complicated because my device name was not properly being exposed by my device. So I ended up modifying the installation script to ensure it didn't matter.
So, you have to download not only the LineageOS version but also some other packages like Google apps, that are not installed and that you will need, and also the rooting package, which is always handy.
So the instructions and the links to download the packages are here. You might go there, read them and download all the packages: https://wiki.lineageos.org/devices/klte/install under the section Installing from Recovery....
Once you have all the packages ready to install, before you follow their instructions, you will have to do some hacking that you will find here explained here: http://www.lineageosdownloads.com/fix-error-7-lineage-os/ under section METHOD 1: UPDATER SCRIPT HACK TO FIX ERROR 7.
Basically, what I did was to edit the zip file using vim editor from the command line. You type "vim lineage-16.0-20200726-nightly-klte-signed.zip" (being lineage-16.0-20200726-nightly-klte-signed.zipand the name of the lineageOS image) and then go to "META-INF/com/google/android/updater-script" and then edit the file removing all the lines where it has any reference to the device name which are usually the first lines of the script containing the getprop(...) lines of code. To remove them, just click "dd" and they will be removed. Once they are removed, click on "Esc". Then type ":wq", it will go back to the previous screen, and then click ":q" and taht will be it, you have the package ready to be installed.
Now follow the instructions that you read previously and you should be able to have your Samsung S5 updated to LineageOS 16.
And now comes the part that I haven't resolved yet. How to install Mirrorlink in this device. So far I have managed to get several version of the Driverlink APK from Samsung but I'm not able to install them because when I try to do it using adb in root mode, I get the following message: "Package com.sec.android.automotive.drivelink has no signatures that match those in shared user android.uid.phone; ignoring!".
I know it has something to do with the signatures of LineageOS and that I need to sign the APK file with the LineageOS ROM signatures, but so far I haven't been able to find how to do it.
So I'll keep on trying and posting my discoveries here. Anyway, if anyone is willing to help me, it will be very welcome!!
I really hope that this helps others to take back from the closet their forgotten Samsung S5 and put it back to work.
I dont think it would help even if u did manage to install mirrorlink as samsung did drop support for mirrorlink.
Mirrorlink needs a new security certificate from samsung every month, and last certificate works until 2020-07-31
guroth said:
I dont think it would help even if u did manage to install mirrorlink as samsung did drop support for mirrorlink.
Mirrorlink needs a new security certificate from samsung every month, and last certificate works until 2020-07-31
Click to expand...
Click to collapse
I'm still working on it. Anyway, the certificate is not a problem. Once I have mirrorlink working, I will install some applications that will install the certificate (like RockScout - "https://play.google.com/store/apps/details?id=com.carconnectivity.mlmediaplayer&hl=en_US") or LG Mirrorlink. And with them I will use other apps to take control of the screen like for example Full Mirror for Mirrorlink - "https://play.google.com/store/apps/details?id=full.mirrorlink&hl=en_US"
The main challenge is to be able to create the connection between the cellphone and the car.
There is a button "Translation" in notification bar in LOS, that is a mirrorlink by itself if I do understand this correctly. But klte SM-G900F on LOS 17.1 and lentislte SM-G906S on LOS 16.0 doesn't discover a mirrorlink device that is working properly with Samsung A50 on stock ROM (Anydata device, Windows 10 PC). One day I have managed to establish a mirrorlink connection between A50 (it was a transmittor) and SM-G900F (receiver) via some (can't recall it's name) app. But still I haven't managed to use S5 as a transmittor for mirrorlink...