help to unbrick my P970 - LG Optimus Black

i tried many ways like:
Smart Flasher, KDZ flasher (or UpTestEX_mod2_marwin) using different techniques like using small server, and also tried official LG Mobile Updater. all flashing procedures were successful BUT with the same result. i'm stocked in Bootloop or LG logo only.
is there any other way to unbrick this phone? i'm pretty sure it's not hardware.

it's strange, smartflash should perform a reset. try the rooting method 3 here :
http://forum.xda-developers.com/showthread.php?t=1111771
it should fix

thanks for fast reply: im exactly a noob here...a favor...kindy in simple terms what do i need in this method. kindly check below is that method what you mean? and i'll be using the smart flasher right?
Method 3 - V20N (DEU) Gingerbread
Caution, this method is a full flash ! EVERYTHING will be lost !
- Required : installed drivers, SmartFlash, patched FW binaries (*.fls et *.bin) and Superuser archive firstly copied in your SDC
- Follow guide procedure (UPK)
- Phone will reboot into Recovery, do a wipe / reset, "install zip from sdcard" then "choose zip from sdcard" and select Superuser archive (will install AnReboot + ES Explorer)
- Validate on "reboot system now", your phone is rooted

download the kit, binarie files and superuser archive, that's all you need

I cannot install UPK
it tall me you may not have permissions to access the item
What is supposed to do

nothing is new to UPK procedure given. all were tested successful flashing but same result. i need a different solution, and maybe this time LG Service Center turn.
i don't think it's a flashfile problem. i downgraded and upgraded but same negative result.
but no choice i have to proceed to LG Service Center and i'll just update this thread if they're able to repair this unit.
bye2x thanks for the help....

@owdli well if you're not admin that means you miss privileges. Otherwise it's probably your antivirus or anti-something else which block the access to the file. don't forget that it contains exploits and is seen as potentially dangerous by AVs.
@LIBIZKIT78 yes nothing really new but there was nothing really new to integrate too. I have had to put smartflash because of the kdz flashing issue. It's still the quickest and the easiest way to flash / unbrick yet. If you can make your phone boiting into recovery, it's won.

i believe aside from the main S/W files like AP&CP or the compacted kdz format, there is perhaps a different special part of SW sometimes called eeprom, like in Nokia it is known as PM files that differs from MCU&PPM. In Nokia when eeprom is corrupted it will cause Contact Service. this area contains imei and security areas.
what had happened to my P970 is something like that. so whatever flashing i did is vain. my P970 is already in LG Service Center, i'm on a waiting mode.

Related

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

Only fastboot accessible

Hi there, first time post on XDA
I believe my problem to be similar to the one found here posted recently but wasn't sure of protocol and didn't want to hijack the thread.
In short, all I can Access is fastboot.
I was attempting to downgrade from lollipop with Emui 3(ish) to KitKat with Emui 2.3. Whilst Trying to follow the weird downgrade upgrade process (I'm used to flashing .zips on my HTC rather than .APPs) of using the intermittent packages to go between releases I seem to have soft bricked it.
I have a number of UPDATE.APP files (B609, 620, 805, 839) and at some point one of them was working. I have since run all of these through the Huawei Update Extractor and extracted the Boot and Recovery images for each build.
I can use "fastboot flash [boot/recovery] [img file here]" perfectly fine and am told that everything finished OKAY when flashing a recovery and boot for a specific build however I am still unable to access any other partitions, either by holding down the hardware buttons ( vol + & power for recovery, vol + & vol - & power for the Huawei thing).
When using the extractor tool I am given and image and an image header file for each partition, I have been discarding the image header file and only flashing the image, it this the correct thing to do?
Thanks,
Birchall
P.s I have an SDcard and I can easily put the UPDATE.apps on there in a dload folder but that is no help as I cannot access the recovery area which forced updates from this file.
Hi, welcome! ?
Do you remember, if the last working firmware was based on lollipop (B8xx) or kitkat (B6xx)?
You may then extract system.img/cust.img/userdata.img/boot.img/recovery.img of a B6xx or B8xx based rom and flash it in this order through fastboot. (make sure to use the full rom, B620 is also available as an update I think, so just have a quick look on the file size)
Thanks for your response, I've done as you suggested, using Build 839 as I think lollipop was the last working.
There seems to be no difference with the phone. Still the only accessible area is fastboot and when rebooting through fastboot the phone reboots and appears to hang on the boot logo. I'll try a KitKat build now for completeness, is it worth trying different build versions of Lollipop?
Edit: Tried B609 now too, no success.
Hm, sad to hear that. B805 was a beta firmware, so there's a small chance that it may work. Sorry, I have no other idea what do try at the moment. So I'd just attempt it.
I appreciate your help anyway I'll go through and attempt to flash some others the same way.
I am left with a few questions though:
1. Why the need to flash in a specific order, or is that just standard practice?
2. What are the use of the header files that are also obtained when using the extractor tool?
3. Where has your knowledge of the Huawei firmware variants come from - Is it from a database of all released builds and type of release?
1) Somebody once told me to keep that order, and I hadn't any problems since, so I stick with it. Anyway, I'm not sure if the order is important, but I doubt changing it would help.
2) I have no idea. But I didn't use them, and flashing still went fine, so I don't think they're the problem. Maybe someone more experienced can help you there.
3) There is none, unfortunately. So it was basically just trial & error, I nearly lost hope to recover my phone minimum two times, but was lucky in the end. Often the problem is, that you have to go the "big steps" (emui2.3 to 3.0 to 3.1, or sometimes between L10, and L00/L03 roms) per dload. Flashing any rom of another "big version" per twrp/adb results in a not working system. But your problem seems worse, since you can't even access the recovery.
I wish you good luck! Let us know if you can fix it somehow.

Proper ROM:s for Asus Memo Pad 7 - and how to flash it!

I am trying to flash my Asus Memo Pad 7 me176cx for a clean start. The device had a standard Kit Kat factory installation. It worked well for about a year, but then started to lag and act up. Eventually, it just got stuck on the Asus logo during startup. I wasn't trying to go into recovery, it was just the pad's next way of not really working.
I googled for a bit and found a number of ways to flash ny pad into a fresh start. None of them worked. I shall try below to describe the ways in which the various methods failed. Perhaps someone out there can see what I did wrong or lead me in the right direction regarding downloading a valid ROM (which seems to be the big snag for me).
But before that, I'd just like to point out that I only need the darn thing to function again. It does not have to be with the latest coolest custom ROM, it does not have to be with ASUS stock ROM. I just want to make an 8-year old really happy again...
FAILED METHOD 1
Android Debugging Bridge. This seems to require putting the ROM on an SP card and have it inserted during the installation process. I haven't managed to properly format and prepare such a card, because it does not seem to be recognized. I moved on with the below methods that seemed more promising.
FAILED METHOD 2
Smart Phone Flash Tool. It seems to need a so-called Download Agent and Scatter-loading File. I haven't found any instructions on how to identify such files. I have made a few feeble attempts at browsing the ROM zip:s I have downloaded, but I didn't find anything that worked.
FAILED METHOD 3
ASUS Flash Tool. The installer seems to be on Rapidgator, some scam-ish looking site that only entangles me in a myriad of account setting up and payment activities. No.
FAILED METHOD 4
Intel Phone Flash Tool. This method somehow seems the most promising. But it requires the following files (text copied from an XDA thread that methodically describes step by step how to unbrick your device):
CLVp_CSAX_FWR_DnX_20.3E.bin
IFWI_v64.25_CSAX_PROD.bin
CLVp_CSAX_OS_DnX_20.3E.bin
fastboot.img
I have tried the Intel Tool with stock Asus ROM as well as a ROM for Intel Atom processor I found on Intel's website. None of the worked.
In all cases, I have used ROM's named UL-K013-WW-12.10.1.17_KK-user.zip or similarly (different versions) that I have downloaded from Asus. Alternatively, I used Kernel_V12_10_1_17.zip from Intel.
It seems to me that whichever method I use, I am unable to extract the correct files. Are these zip:s even proper ROM:s? I am afraid I musk as You marines out there for detailed instructions on how to obtain the correct files!
Thanks in advance!
Take a look here: https://forum.xda-developers.com/memo-pad-7/general/me176c-x-collection-roms-updates-t3012965 . It comes with all images (updates from Asus are delta's, so you need to follow the complete path) and instructions on how to upgrade to L.
IT-Grandpa said:
I am trying to flash my Asus Memo Pad 7 me176cx for a clean start. The device had a standard Kit Kat factory installation. It worked well for about a year, but then started to lag and act up. Eventually, it just got stuck on the Asus logo during startup. I wasn't trying to go into recovery, it was just the pad's next way of not really working.
I googled for a bit and found a number of ways to flash ny pad into a fresh start. None of them worked. I shall try below to describe the ways in which the various methods failed. Perhaps someone out there can see what I did wrong or lead me in the right direction regarding downloading a valid ROM (which seems to be the big snag for me).
But before that, I'd just like to point out that I only need the darn thing to function again. It does not have to be with the latest coolest custom ROM, it does not have to be with ASUS stock ROM. I just want to make an 8-year old really happy again...
FAILED METHOD 1
Android Debugging Bridge. This seems to require putting the ROM on an SP card and have it inserted during the installation process. I haven't managed to properly format and prepare such a card, because it does not seem to be recognized. I moved on with the below methods that seemed more promising.
FAILED METHOD 2
Smart Phone Flash Tool. It seems to need a so-called Download Agent and Scatter-loading File. I haven't found any instructions on how to identify such files. I have made a few feeble attempts at browsing the ROM zip:s I have downloaded, but I didn't find anything that worked.
FAILED METHOD 3
ASUS Flash Tool. The installer seems to be on Rapidgator, some scam-ish looking site that only entangles me in a myriad of account setting up and payment activities. No.
FAILED METHOD 4
Intel Phone Flash Tool. This method somehow seems the most promising. But it requires the following files (text copied from an XDA thread that methodically describes step by step how to unbrick your device):
CLVp_CSAX_FWR_DnX_20.3E.bin
IFWI_v64.25_CSAX_PROD.bin
CLVp_CSAX_OS_DnX_20.3E.bin
fastboot.img
I have tried the Intel Tool with stock Asus ROM as well as a ROM for Intel Atom processor I found on Intel's website. None of the worked.
In all cases, I have used ROM's named UL-K013-WW-12.10.1.17_KK-user.zip or similarly (different versions) that I have downloaded from Asus. Alternatively, I used Kernel_V12_10_1_17.zip from Intel.
It seems to me that whichever method I use, I am unable to extract the correct files. Are these zip:s even proper ROM:s? I am afraid I musk as You marines out there for detailed instructions on how to obtain the correct files!
Thanks in advance!
Click to expand...
Click to collapse
sp flash tools is only for MTK(mediatek) devices..

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

hi everyone,
i bought a 2nd-hand xz1c and it's been great but it had a custom rom installed and was rooted then reflashed with stock rom when i got it, that's what the seller said anyway but i can't get in touch with him anymore.
i haven't been able to update anything since i got it. the system downloads and fails to install the update over and over. i have no idea how to unroot the phone if that's possible or what programs to use to do it, is there a guide where i can just get it to stop downloading and trying to download the newer firmware? ideally i'd like to install the update, failing that just to get it to stop trying would be "ok"... probably not from a security point of view though.
i'm a complete noob sorry. ly
As the phone was rooted, the bootloader is unlocked and the OTA update will fail. It's impossible to relock the bootloader, so you'll have to manually flash the updates.
You can use a tool called xperifirm to download new firmware version and newflasher to flash them. Search the forum for guides.
To stop the updater from tryung, go to settings/apps, check show system apps, find the app called Software update and force stop it. It will restart on phone boot, so you'll have to close it again once in a while.
You can also use ADB to disable the updater for good - again, search the forum for a more specific guide...
If you really feel there is some sort of advantage to having the latest firmware on your phone, then upgrade it yourself, you won't damage the phone or change your warranty status.
Look on Xperiafirm and find a 47.2.A.10.62 customised build - CE1 would be a good option
Download Newflasher and put it in the same folder as the firmware you downloaded from Xperiafirm
Delete Userdataxxx.sin and files ending in .ta (but not in the boot folder) . This will ensure that you don't lose any personal data. Also delete persist*.sin to avoid losing android attest key.
Then start newflasher.exe and follow instrctions.
You might need a copy of the Sony driver
I would make a backup with Xperia transfer before you do anything, if the phone is glitchty after your rebuild, then factory reset it and then restore from the backup.
You'd probably need to read up on janjan's kernel fix to get you working without a green camera.
You'll also need TWRP

[GUIDE] Unlock bootloader, root the device and install any custom ROM! (ALE-L23/21)

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?

Categories

Resources