Database Users

Huawei Honor 4C Index and Troubleshooting Thread

Due to the fact that all guides, rooting threads about the Huawei Honor 4C are scattered all over the XDA and hence are difficult to be searched for when needed, I decided to create an index thread to keep all ROM updates, rooting and unlocking guides in one neat clean thread.
I’ll try my best to keep this thread updated as soon as new information is released from trusted sources or whenever new mods, ROMs, etc. are released.
You can also post your queries here and I'll try my level best to answer them.
Contents:
1. Device Specifications and Variants
i. Specifications
ii. Variants
2. Stock and Custom ROMs
i. Stock EMUI 3.0 and 3.1 Download Links
ii. Upgrading from Kitkat to Lollipop
iii. Downgrading from Lollipop to Kitkat
iv. Flashing Stock ROM in cases of bootloop
v. Flashing Stock ROM when device unable to boot to recovery or update mode
vi. Stock based Custom ROMs and AOSP based Custom ROMs
3. Unlocking Bootloader, Rooting and Custom Recoveries
i. Custom Recovery and SU zips Download Links
ii. Unlocking Bootloader and Relocking Bootloader
iii. Installing Custom Recovery
iv. Restoring Stock Recovery
v. Installing SU Binary (Rooting your Device)
4. ROM Add Ons and Miscellaneous Guides
i. Xposed Framework on EMUI 3.0 and EMUI 3.1
ii. Viper4Android Sound Mod
iii. L Speed Mod for Android Lollipop
iv. Changing Region
v. Extracting Update.APP
5. Credits
Device Specification and Variants​Device Specification
Processor HiSilicon Kirin 620 1.2 GHz Octa-Core ARM 7a-64-bit
RAM 2 GB SDDR
ROM 8 GB (3.2 GB available to Kitkat users / 2.5 GB available to Lollipop users)
Display 5.0 Inch 1280x720 294 dpi IPS LCD Capacitive Touchscreen with Scratch Resistant Glass
Android Version EMUI 3.0 Android 4.4.2 (upgradeable to EMUI 3.1 Android 5.1.1 / EMUI 4.0 Android 5.0 confirmed and will be available in February 2015)
Battery 2550 mAh Li-on Battery (Non-Removable)
Network GSM / HSPDA+ (No LTE)
Camera 13 MP back Geo-tagging, Paronama, HDR, Time-Lapse, Video Recording 1080p at 30 fps / 5 MP front, Video Recording 720 p
GPU Mali 450-MP4 OpenGLS 2.0
Also see attached CPU-Z screenshots for advanced and complete specs.
Variants
Pakistan CHM-U01 B067 (Kitkat) / B120 (Kitkat) / B310 (Lollipop)
India / Malaysia / Indonesia / South Asia CHM-U01 B063 (Kitkat) / B070 (Kitkat) / B302 (Lollipop) / B330 (Lollipop) / B340 (Lollipop) / B350 (Lollipop) / B360 (Lollipop) / B380 (Lollipop) / B390 (Lollipop)
Russia CHM-U01 B060 (Kitkat) / B120 (Kitkat) / B130 (Kitkat) / 304 (Lollipop) / B310 (Lollipop) / B320 (Lollipop)
China Developer Channel CHM-UL00 CHM–TL00 CHM-TL00H v5.9.1 (Lollipop) / v5.9.16 (Lollipop) / v5.10.1 (Lollipop) / v5.10.16 (Lollipop) / v5.11.1 (Lollipop) / v5.11.16 (Lollipop) / v5.12.1 (Lollipop) / v5.12.16 (Lollipop) / v5.12.16 (Lollipop) / v6.1.1 (Lollipop) / v6.1.16
China Stable Channel CHM-UL00 CHM–TL00 CHM-TL00H B181 (Kitkat) / B191 (Kitkat) / B200 (Kitkat) / B211 (Kitkat) / B220 (Kitkat) / B230 (Kitkat) / B231 (Kitkat) / B419 (Lollipop) / B422 (Lollipop) / B425 (Lollipop)
Stock and Custom ROMs​All guides in this section require you to have Stock Recovery installed and device must be completely unrooted unless specified. If you have a custom recovery installed see Unlocking Bootloader, Recovery and Custom Recovery > Restoring Stock Recovery Section for instructions.​Stock EMUI 3.0 and EMUI 3.1 Download Links
Just click on the Version Number to download the respective ROM.
EMUI Emotion UI 3.0 Kitkat 4.4.2
Pakistan CHM-U01 B067 (Kitkat) / B120 (Kitkat)
India / Malaysia / Indonesia / Asia Pacific CHM-U01 B063 (Kitkat) / B160 (Kitkat) / B063 (Kitkat) / B070 (Kitkat)
Russia CHM-U01 B060 (Kitkat) / B120 (Kitkat) / B130 (Kitkat)
China Stable Channel CHM-UL00 CHM–TL00 CHM-TL00H B181 (Kitkat) / B191 (Kitkat) / B200 (Kitkat) / B211 (Kitkat) / B220 (Kitkat) / B230 (Kitkat) / B231 (Kitkat)
EMUI Emotion UI 3.1 Lollipop 5.1.1
Pakistan CHM-U01 B310 (Lollipop)
India / Malaysia CHM-U01 B330 (Lollipop)
Russia CHM-U01 B310 (Lollipop)
Indonesia CHM-U01 B340 (Lollipop)
Asia Pacific CHM-U01 B360 (Lollipop)
China CHM-UL00 CHM–TL00 CHM-TL00H v5.9.1 (Lollipop)
Upgrading from Kitkat to Lollipop
Always try to take OTA updates whenever possible as user data isn't wiped. However, if you want to start anew, just use the below listed methods. ​Backup all important data on internal storage before performing upgrade. Internal Storage will be completely wiped after upgrade. Ensure battery is fully charged or at least 30%. Do not press any button nor attach your phone to charger after the upgrade process is initiated.​Normal Upgrade (Upgrade using the Software Updater)
Download the Lollipop Stock ROM according to your region. See Stock and Custom ROMs > Download Links section for download links.
Ensure your SD card has atleast 3.0 GB of free space.
Extract the downloaded *.zip or *.rar and copy the dload folder (with the UPDATE.APP in it) to the root of your SD card. (In some update packages, there might be multiple UPDATE.APP. Hence copy the UPDATE.APP with has the largest file size)
Insert the SD card (if not already) and navigate to Settings > Update > Menu > Local Update > Full Package:UPDATE.APP . Now finally press Install.
Your phone will reboot to recovery. Wait for the progress bar to finish. When it does you phone will switch off. Hold the power button to switch it back on.
First boot might take some time due to app optimization hence be patient.
Forced Upgrade
Download the Lollipop Stock ROM according to your region. See above section for download links.
Ensure your SD card has atleast 3.0 GB of free space.
Extract the downloaded *.zip or *.rar and copy the dload folder (with the UPDATE.APP in it) to the root of your SD card. (In some update packages, there might be multiple UPDATE.APP. Hence copy the UPDATE.APP with has the largest file size)
Insert the SD card (if not already) and Power Off your device.
Now while holding Volume Up and Volume Down buttons, hold the Power button to power on the device and boot straight to Software Upgrade Mode.
Wait for the process bar to finish. Device will automatically reboot after the upgrade has completed successfully.
First boot might take some time due to app optimization.
Downgrading from Lollipop to Kitkat
Method 1
Download your current Lollipop ROM (see the first section for download links) and the Kitkat ROM you want to downgrade to.
From Lollipop Stock ROM: First copy UPDATE.APP located in 0_CUSTOM_PACKAGE\MiddlePackage\dload to dload directory in the root of your SD card.
Use any of the method posted in Stock and Custom ROM > Upgrading from Kitkat to Lollipop section to flash the Middle Package UPDATE.APP. Skip the copying stuff in those sections.
After the flash has completed, delete the existing UPDATE.APP.
From Kitkat Stock ROM: Copy the Main UPDATE.APP (one with the larger size) to the dload directory in the root of your SD card..
Use any of the method posted in Stock and Custom ROM > Upgrading from Kitkat to Lollipop section to flash the Main Kitkat UPDATE.APP. Skip the copying stuff in those sections.
Method 2
This method requires ROOT SU privileges on your device. Also please make a backup before proceeding.​
Make a TWRP or CWM backup. If something goes wrong, you must have something to restore from.
Download and install Terminal Emulator from Play Store. Open the app and execute the following commands (grant SU privileges when prompted):
Code:
su
mount -o rw,remount /system
Open your favorite File Manager which supports browsing / partition and obviously Root permissions , and navigate to /system.
Search for build.prop and open it.
Find ro.product.model and change it's value to balong.
Save the file and make sure permissions are set to -rw-r--r--.
Reboot you device, flash Stock Recovery and any Kitkat ROM you want. See Unlocking Bootloader, Rooting and Custom Recoveries > Restore Stock Recovery for flashing Stock Recovery instructions and Stock and Custom ROM > Upgrading from Kitkat to Lollipop for Stock ROM flashing methods and instructions (You have to use the FORCED METHOD to flash).
Flashing Stock ROM in cases of bootloop or otherwise
If you are stuck in a bootloop, device keeps on restarting follow this guide.
Before you follow this guide, perform a FACTORY RESET on your device. If this doesn't work, then continue.
Download the ROM version currently on your device or any newer one. See Stock and Custom ROM > Download Link section for download links.
Ensure that you are on Stock Recovery. If not see Unlocking Bootloader, Rooting and Custom Recovery > Flashing Stock Reovery section to flash Stock Recovery.
Use the Forced Upgrade method in Stock and Custom ROM > Upgrading from Kitkat to Lollipop section to re-flash the Stock ROM.
Flashing Stock ROM when device unable to boot to recovery or update mode
Alright! So your phone is completely messed up and you can't boot to recovery or anything. Well this guide is for you! Resurrect that device!​Always use original data cable that came with your device for flashing stuff. It is not necessary but recommended.​Installing ADB / Fastboot and Necessary Drivers
Download 15 Seconds ADB and Fastboot Drivers. Visit the official XDA forum for download and installation instructions.
Install Fastboot drivers by downloading and installing Huawei HiSuite via this link.
Flashing the ROM through Fastboot
First download and install Huawei Update Extractor. Visit the official XDA Forum for download, installation instructions and usage.
Extract boot.img, recovery.img and system.img from UPDATE.APP and copy it to any directory on your computer. See Miscellaneous Guides > Extracting Update.APP section for instructions.
Open Command Prompt in the directory where you have extracted the files by holding Shift and Right Mouse Button and finally click Open Command Prompt window here in the context menu.
Completely power off your device.
While holding Volume Down button, connect your device to PC via USB cable to boot to Fastboot Mode.
Execute these commands one at a time using the command prompt.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot erase cache
fastboot erase userdata
fastboot reboot
Now hold Volume Up button and Power button simultaneously. As soon as you see the Honor logo, release the power button. Your device will now boot into recovery.
Perform a Factory Reset through recovery.
Availability of Stock based Custom ROMs and AOSP based Custom ROMs
Unfortunately, light is pretty dim here. There are no Custom ROMs available for this device. However KangVIP Custom Stock Based ROM is available for the Chinese Variants but I couldn't get the links because they want you to register first. Also, because Huawei hasn't published the chipset source code, so no CM or AOSP based ROM has been developed for this device.
Unlocking Bootloader, Rooting and Custom Recoveries​Custom Recoveries, Stock Recoveries and SU zips Download Links
Recoveries and SU Zips will work on the respective EMUI version regardless of device region.​For Kitkat 4.4.2 EMUI 3.0
SuperSU Binary 2.46 doesn't worked correctly on Kitkat. It is better to use Kingroot. However, you may try flashing it! ​
Cofface Custom Recovery (CWM Based / Unofficial Port) Download Link
Stock EMUI Recovery Download Link
Kingroot Super User Binary + Manager Download Link
For Lollipop 5.1.1 EMUI 3.1
TWRP 2.8.7.0 (Unofficial Port) Download Link
Stock EMUI Recovery Download Link
SuperSU Binary 2.46 + Superuser App Download Link
Unlocking Bootloader and Relocking Bootloader
Unlocking Bootloader will void your warranty. You have been warned!​Getting the Bootloader Unlock Code
First, visit this link. Accept the Unlocking Agreement and proceed.
In a new tab, visit this link and register for Huawei ID. Make sure you are registering using your mobile number.
After the registration is successful, return to the previous tab and log in using your newly generated Huawei ID.
Now provide the information:
Product Model: Go to Settings > About Phone. For ours it is, CHM-U01.
Product Serial Number: Refer to the original device box for serial number.
Product IMEI: Provide SIM1 IMEI.
Product ID: Dial *#*#1357946#*#* from your device and enter the Product ID displayed on the screen.
Finally enter the verification code and retrieve your Bootloader Unlock Code. Save it in a safe place.
Installing ADB / Fastboot and Necessary Drivers
Download 15 Seconds ADB and Fastboot Drivers. Visit the official XDA forum for download and installation instructions.
Install Fastboot drivers by downloading and installing Huawei HiSuite via this link.
Unlocking Bootloader
Ensure that you have successfully installed all necessary tools and drivers mentioned above.
Power off your device. While holding Volume Down button use a USB cable to attach your device to computer. Device will automatically boot to fastboot mode.
Open a command prompt and execute the following command (replace your_unlock code with yours):
Code:
fastboot oem unlock [I]your_unlock_code[/I]
fastboot reboot bootloader
Voila! You have successfully unlocked your device.
Relocking Bootloader
Relocking the bootloader will not un-void your warranty.​
Ensure that you have successfully installed all necessary tools and drivers mentioned above.
Factory reset your device or reflash the stock ROM. See Stock and Custom ROM > Upgrading from Kitkat to Lollipop section for flash methods.
Power off your device. While holding Volume Down button use a USB cable to attach your device to computer. Device will automatically boot to fastboot mode.
Open a command prompt and execute the following command (replace your_unlock code with yours):
Code:
fastboot oem relock [I]your_unlock_code[/I]
fastboot reboot bootloader
Voila! You have successfully locked your device.
Install Custom Recovery
After installing a custom recovery, you will not be able to take OTA updates nor you will be able to reflash the stock rom.​Installing ADB / Fastboot and Necessary Drivers
Download 15 Seconds ADB and Fastboot Drivers. Visit the official XDA forum for download and installation instructions.
Install Fastboot drivers by downloading and installing Huawei HiSuite via this link.
Installing Custom Recovery
Ensure that you have successfully installed all necessary tools and drivers mentioned above.
Download the custom recovery depending on your Android Version. See the first part of this section for download links.
For Lollipop only: Extract the downloaded RAR archive to get the recovery image.
Power off your device. While holding Volume Down button use a USB cable to attach your device to computer. Device will automatically boot to fastboot mode.
Open Command Prompt in the directory where you have extracted/downloaded the files by holding Shift and Right Mouse Button and finally click Open Command Prompt window here in the context menu.
Now execute the following command one at a time (replace recovery name with the one you downloaded);
Code:
fastboot flash recovery [I]recovery_name.img[/I]
fastboot reboot
Restoring Stock Recovery
Installing ADB / Fastboot and Necessary Drivers
Download 15 Seconds ADB and Fastboot Drivers. Visit the official XDA forum for download and installation instructions.
Install Fastboot drivers by downloading and installing Huawei HiSuite via this link.
Flashing Stock Recovery
Ensure that you have successfully installed all necessary tools and drivers mentioned above
Download Stock Recovery depending upon your Android version. See first part of this section for download links.
For Lollipop only: Extract the downloaded RAR archive to get the recovery image.
Open Command Prompt in the directory where you have extracted/downloaded the file by holding Shift and Right Mouse Button and finally click Open Command Prompt window here in the context menu.
Now execute the following command one at a time (replace recovery name with the one you downloaded);
Code:
fastboot flash recovery [I]recovery_name.img[/I]
fastboot reboot
Installing SU Binary (Rooting your device)
Prior to rooting, ensure you have unlocked your bootloader and installed a custom recovery.
Download flashable root zip depending on your Android version. See first part of this section for download links.
Copy the zip to either internal memory or external SD card.
Power off your device and disconnect it from PC or charger.
Now hold Volume Up button and Power button. As soon as you see the Honor logo, release the power button. Your device will now boot into recovery.
For CWM: Use volume buttons to navigate up and down and power button to select. Go to Install Zip > Chose zip from external or internal storage (depends where you copied the flashable zip). Locate the zip file and hit flash. After successful flashing, wipe cache and dalvik and reboot your device. For TWRP: It's all touch based, hence it's easy to navigate. Touch 'Install Zip', locate the zip file, flash it and finally wipe cache and dalvik.
Congratulations you have successfully rooted your device.
ROM Addons and Miscellaneous Guides​Xposed Framework on EMUI 3.0 and EMUI 3.1
On Kitkat EMUI 3.0, Xposed works only when Use System Hooks is disabled in Xposed Settings. This means that modules such as Gravity Box, Minminguard won't work! However, modules that don't modify the UI work without problems.
On Lollipop EMUI 3.1, Xposed works flawlessly and great! See my thread here for instructions and details: http://forum.xda-developers.com/android/general/guide-workaround-running-xposed-t3338765
Viper4Android Sound Mod
Unfortunately, Viper4Android is a no go on EMUI 3.0 and EMUI 3.1. There is partial support i.e. the mod will only work when it is running in background and will not work on stock EMUI apps such as Music. Also be sure that after installing, DTS Sound Engine will be disabled (or won't work in most cases)!
L Speed Mod for Android Lollipop EMUI 3.1
This mod works flawlessly and I'm loving it! Visit the XDA thread for all information.
Changing Region
This is some really risky stuff. If anything goes wrong you'll end up with a bricked device. I have personally tested this and have successfully changed my region from Pakistan to Malaysia. Nothing will go wrong if you carefully follow the instructions!​Prerequisites
Your device must be rooted.
ES File Explorer installed (no other Root Explorer should be used).
Backup of your stock ROM.
OEM Info File Download Link
Instructions
Dial *#*#2846579#*#* from your device to pop up Engineering Menu. Go to Network Information > Country / Vendor Info. I have listed some of the vendors below:
1. hw/spcseas – Malaysia
2. unicomelectric/cn – China
3. hw/meafnaf – Pakistan
4. mts/by – Belarus
Open ES File Explorer, switch to Root Mode and navigate to /data/. Open custom.bin using ES Note Editor. Clear the Vendor Information text in it and enter the text corresponding to the region you want to switch to. In my case as I switched from Pakistan to Malaysia, I cleared hw/meafnaf and inserted hw/spcseas. Save the file and make sure it's permissions are set to rw-rw-rw
Extract the OEM File Info and copy the oeminfo file of the country you are switching to. Using ES File Explorer, navigate to /dev/block/platform/hi_mci.0/by-name/ and paste it there. Replace the file currently present. Don't delete it! Now set it's permissions to rwx-rwx-rwx.
Finally reboot your device and enter Engineering Mode to verify Country/Vendor.
Download the latest ROM of the Vendor you switched to and flash it using Forced Flash Method. See Stock and Custom ROM > Upgrading from Kitkat to Lollipop for details.
Extracting Update.APP
This is a simple and straightforward guide! Follow and follow...​
We'll start by downloading Huawei Update Extractor. Visit the XDA thread and scroll down for links.
Extract the downloaded file in a safe folder and launch HuaweiUpdateExtracter.exe
Make sure Profile is set to Unknown (worstenbrood).
Switch to Extract tab and locate the Update.APP. (Well you must have downloaded the Stock ROM. No! No problem! See Stock and Custom ROM > Download Links section for links).
Hold down Ctrl Button and select the partitions (such as System, Recovery, Boot, etc.) you wish to extract. Then right click on any one of the selections and click Extract Selected.
Browse for a location where you wish to extract the partitions (or images).
Tada! It's done!
Credits
Inshaal Mirza for providing Stock Recoveries and Root Zips.
CarbonTesla.com for providing ROMs versions list and Changing Region guide.
XDA for everything it has taught me.
If you encounter any issues in this guide or you believe I have made an error, please feel free to PM me or comment to notify. Thanks everyone!
Changelog:
25/01/2016 Streamlined Content
02/02/2016 Added another Downgrade Method

Great information. Thx

[email protected] said:
Great information. Thx
Click to expand...
Click to collapse
No problem! Just thought of giving back something to the community....:angel:

hi,
it is not possible to register witch Phone nummer i live in germany and i canty type +49
can me someone help? unlock Bootloader?

rysalf said:
hi,
it is not possible to register witch Phone nummer i live in germany and i canty type +49
can me someone help? unlock Bootloader?
Click to expand...
Click to collapse
Dont worry. PM me your mobile information (see thread for detail) and i'll provide you with the unlock code.

rysalf said:
hi,
it is not possible to register witch Phone nummer i live in germany and i canty type +49
can me someone help? unlock Bootloader?
Click to expand...
Click to collapse
You can register with email, and give your phone infos later.

morpheus133 said:
You can register with email, and give your phone infos later.
Click to expand...
Click to collapse
The problem is, Germany is not on the country list during sign up.. So you can't create a phone account using a Germany phone. Huawei has made it an obligation to use a phone account for unlocking.

mfbcool said:
The problem is, Germany is not on the country list during sign up.. So you can't create a phone account using a Germany phone. Huawei has made it an obligation to use a phone account for unlocking.
Click to expand...
Click to collapse
It is not a problem.
Use email to register!
I am from Hungary. Hungary is not on the list to but I can use the site.

i downloaded b360 lollipop. and theres no middle package for downgrade. help me. i want to downgrade my 4c.

ijameslargo said:
i downloaded b360 lollipop. and theres no middle package for downgrade. help me. i want to downgrade my 4c.
Click to expand...
Click to collapse
Try changing your region to Malaysia and then flash any Kitkat image you like!

mfbcool said:
Try changing your region to Malaysia and then flash any Kitkat image you like!
Click to expand...
Click to collapse
malaysia already

ijameslargo said:
malaysia already
Click to expand...
Click to collapse
Alright... Then try this method (it does the same thing as region change does). You must be ROOTED.
1. Open build.prop located in /system/.
2. Change ro.product.model value to Balong.
3. Restart your device.
4. Now flash away any Kitkat ROM of any region.

mfbcool said:
Alright... Then try this method (it does the same thing as region change does). You must be ROOTED.
1. Open build.prop located in /system/.
2. Change ro.product.model value to Balong.
3. Restart your device.
4. Now flash away any Kitkat ROM of any region.
Click to expand...
Click to collapse
sir my phone is not yet rooted. is there any other way? like flashing middle package?

ijameslargo said:
sir my phone is not yet rooted. is there any other way? like flashing middle package?
Click to expand...
Click to collapse
No manufacturer wants the end user to downgrade to a lower version. You have to be rooted and bootloader unlocked in the first place to downgrade. The middle package is in B330 Lollipop ROM. You may try flashing it but I doubt it will work on B360.

mfbcool said:
No manufacturer wants the end user to downgrade to a lower version. You have to be rooted and bootloader unlocked in the first place to downgrade. The middle package is in B330 Lollipop ROM. You may try flashing it but I doubt it will work on B360.
Click to expand...
Click to collapse
is it ok to flash the middle package in b330 even my phone is not rooted?

ijameslargo said:
is it ok to flash the middle package in b330 even my phone is not rooted?
Click to expand...
Click to collapse
No, you don't need to be rooted. Also this is completely safe. Huawei Recovery won't flash the file it is not compatible so feel completely safe to try it!
I was on B330 Lollipop ROM and I did downgraded mine to Kitkat just for Xposed!

im using b360 lollipop. now i will try to flash the middle package of b330 to downgrade mine to kitkat. im hoping it will work.

@mfbcool If you're challenging my info , Our Phone Support 4G LTE Network!! one thing and 2nd thing, we have Sources for chipset of Our devices but thats are for Arm only not Arm64, so they are less used for us,,, we only need a developer,,, and third and last one, we can never change region as mentioned above and in carbontesla.com, i already read it, but thats not the way!! we needed vendor files which are available only for Pakistani one Rom (B120) and Indian (B390) only,,, not present for chinese or any other region,,, so we cant change region!!
@inshaalmirza
---------- Post added at 02:06 PM ---------- Previous post was at 02:03 PM ----------
@ijameslargo you dont need to be rooted and unlocked bootloader for downgrading, you can downgrade to any version from any Rom,,, if you have done in any way then its ok, if not then tell me, i will guide you!!
@inshaalmirza

inshaalmirza said:
@mfbcool If you're challenging my info , Our Phone Support 4G LTE Network!! one thing and 2nd thing, we have Sources for chipset of Our devices but thats are for Arm only not Arm64, so they are less used for us,,, we only need a developer,,, and third and last one, we can never change region as mentioned above and in carbontesla.com, i already read it, but thats not the way!! we needed vendor files which are available only for Pakistani one Rom (B120) and Indian (B390) only,,, not present for chinese or any other region,,, so we cant change region!!
My turn!
1. So my desktop computer supports WiFi cards but it hasn't one installed so it neither can't search Hotspot networks nor can't create one. Same case here! The Kirin 620 SoC has SUPPORT for 4G networks but the radio module required to make it available is not installed ON THE HARDWARE on our 4C (it's installed on P8 lite though) or IS DISABLED ON THE HARDWARE SIDE.
2. There are more things required to build Custom ROM other than kernel sources (which you are of course mentioning about). You need open source drivers for CPU Management, GPU, WiFi, Bluetooth, Dual SIM card, Graphics Stack, Radio Bands support, NFC, etc. Unfortunately, those aren't included or open-sourced in the source. That's why the only custom ROM ever made for Kirin SoC, the Cyannogen Mod 11 for Honor 6 has no support for Bluetooth, NFC, USSD Execution, etc. The developer for that ROM made seriously tons of patches and spent countless weeks to make it happen. That's also the reason why there is no CM (or any AOSP) ROM for even high end Huawei devices such as Mate 7, etc. These devices however do have KangVIP ROM which is Stock Based Chinese mockoff.
3. I did changed my region from Pakistan to Malaysia successfully. If that didn't worked for you, I'll upload flashable zips probably in few days that will automatically change the region for you
I wish you ever had a Motorola phone which will hard brick on downgrade (yup a dead phone RIP). Unfortunately no manufacturer wants the end user to downgrade because of security patches, exploits, etc. You can always try flashing system.img of a lower version together with boot and recovery to see whether your phone has downgraded.
That 'balong' method I posted is actually an exploit or more preferably a cheat. The phone loses it's identity, model and version and thus any version either higher or lower can be flashed. However it does require root.
Click to expand...
Click to collapse

Great great!! You should know one thing too.... You didnot mention CM12.1 of 4X ?? You know, thats made from our Kernel Sources!! Nd dev made all drivers etc for it.... So just sources enough for it...right...
And i once also changed region to malysia/india, but it got balong build,,, then i flashed vendor file of specified rom,,, it changes to its real build!! Then my region was really changed!! And about 4G,,, our hardware support 4G but software didnot!! See in indian Rom, 3 options 2G,3G,4G available in preferred mode!!
@inshaalmirza

[Auto ToolKit][BL Unlock][Magisk&SuperSU][Xposed] Zenfone 2 ToolKit [Z00A/Z008/Z00X]

Last update: 14.10.2017
Fantastic news
No more waiting for manually signed magisk, supersu or twrp versions from now on. Just install any new version and use the image signature fix action in the troubleshoot menu of the toolkit. :good:
Next level reached
No more waiting for special zenfone 2 patched xposed for magisk. Got my own zip to do some hex patching. You can either use one of the (already patched) xposed versions from the toolkit or download xposed for magisk and use the xposed patcher in the troubleshoot menu.
z00x users please read this post https://forum.xda-developers.com/showpost.php?p=72298931&postcount=214
Introduction
This is a windows batch toolkit for automated actions like bl unlock, flash, root, xposed, sideload tasks, ... for your ze551ml/ze550ml/zx551ml.
I hope you find it useful. Check the tabs above for more screenshots, downloads, review ...
Note:
This tookit works well for a lot of situations, but I need feedback especially for the new supported devices ze550ml and zx551ml. Please go on and try the toolkit, then leave a message on this thread, do a review or just vote.
Before you try any action in the menu, check that the device informations are shown.
Features
​
Supports ZE551ML, ZE550ML, ZX551ML
​
Device status and connection information
​
Automated actions
​
Bootloader unlock
​
Flash boot/recovery images (twrp, stock)
​
Fix wrong or missing image signatures!!
​
Root / unroot Magisk & SuperSU
​
Xposed for Magisk (install / uninstall)
​
Patching xposed for magisk for zenfone 2 (if installed the unpatched xposed for magisk by mistake)
​
Compatible with most current MM firmware versions from devices ZE551ML, ZE550ML, ZX551ML
Currently integrated Tools
​
v14.0 (default) and v14.2
​
SuperSU 2.79SR3 / 2.82 (default) / 2.82SR5
​
TWRP 3.0.3-M4 / 3.1.1 (default)
​
Xposed for Magisk v87.3 / v88.0 (default)
​
Stock boot/recovery support of most current MM firmware versions from devices ZE551ML, ZE550ML, ZX551ML
​
adb/fastboot 1.0.32 (optional: 1.0.36)
Installation instructions
Do a clean start:
​
Download the latest base package
​
Extract to your desired location. It will extract a "ze551ml toolkit" directory with all files.
​
(Optional / If the automatic download of the device specific files fails) Download the device specific packages and extract it directly to the "ressources" directory
To run the toolkit just execute "ze551ml toolkit.bat" (no admin rights are needed).
Usage instructions
Prerequisite:
​
Ensure that you have installed device usb drivers (e. g. see: https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Download/ )
​
Ensure that you have one of the latest MM firmwares for your device installed.
​
Ensure that you have enabled USB Debugging in Developer Options
​
Even if only a few actions could be really harmful to your data: Get a backup!
Then:
​
Run ze551ml_toolkit.bat
​
Check device status information & see if toolkit really likes your device
​
If your bootloader is still locked: Unlock it first with menu B -> choice U
​
(Optional) Choose your desired versions of the integrated tools in menu O.
​
(Recommended) Flash twrp with menu F -> choice T. If you want to try a newer twrp version, change it first in menu O
​
Check all the other nice functions of the toolkit
Downloads
Main: xda devdb archive
Mirror 1: https://mega.nz/#F!u8JhhY7T!9PryiRdjVSFf-O4erijDWg
Mirror 2: https://drive.google.com/drive/folders/0B4r2bJ3AgndSRVl5djNPNV9Qbkk?resourcekey=0-i9dHUezdzckVemi93NlYLA&usp=sharing
File structure:
​
ze551ml-toolkit-<VERSION>-base.zip - contains the base toolkit package without any device specific files
​
z00a*.zip - contains all device specific files for Z00A (ZE551ML)
​
z008*.zip - contains all device specific files for Z008 (ZE550ML)
​
z00x*.zip - contains all device specific files for Z00X (ZX551ML)
Changelog
Code:
[B]v1.3[/B]
Current changelog: 14.10.2017
[added] xposed for magisk v88.0
[new] Patching xposed for magisk for zenfone 2 (if installed the unpatched version by mistake)
Code:
[B]v1.22[/B]
Current changelog: 08.10.2017
[added] magisk v14.2
[removed] magisk v13.3
[fixed] xposed for magisk v87.3
[new] Fix wrong or missing image signatures!!
[fixed] Better support for encrypted devices
Code:
[B]v1.1b9[/B]
Current changelog: 22.09.2017
[added] magisk v14.0
[removed] magisk <v13.3
[removed] twrp 3.0.2-M1
[updated] magisk uninstaller
Code:
[B]v1.1b8[/B]
Current changelog: 19.07.2017
[added] magisk v13.3
[updated] magisk uninstaller
[new] action to download latest mirror file which is used to get some stock files updates
Code:
[B]v1.1b6[/B]
Current changelog: 13.07.2017
[added] magisk v13.2
[removed] magisk v13.1
[fixed] twrp detection
[modified] magisk manager will now be extracted from zip and installation will be forced after sideload
Code:
[B]v1.1b5[/B]
Current changelog: 11.07.2017
[added] magisk v13.1
[removed] magisk v13 betas
[fixed] minor fixes in supersu actions
Code:
[B]v1.1b3[/B]
Current changelog: 02.07.2017
[added] 2 magisk v13 beta versions
[removed] magisk <v12
[updated] xposed installer
[added] 2 more twrp versions
[fixed] hardened detection of installed twrp version (still needs root or already booted twrp for that)
[fixed] changed the way the toolkit downloads files
Code:
[B]v1.0b10[/B]
Current changelog: 04.04.2017
[added] magisk v12.0
[updated] fixed some help messages
Code:
[B]v1.0b8[/B]
Current changelog: 21.03.2017
[added] support for more devices: z00a, z00d, z00x
[added] automatic download for device files if needed
[added] magisk v11.6
[added] twrp 3.0.3-M4 (for encrypted devices or android n installations
[added] backup efs function
[added] integrity check
[modified] menu structure
[updated] changed some help messages
Code:
[B]v1.0b2[/B]
Current changelog: 14.02.2017
[modified] menu order
[disabled] usage of system installed platform tools, internal are forced now
[fixed] boot2recovery could have been failed in some cases
[fixed] timing problems in wipe routine
[added] validations added to each boot states
[removed] twrp 3.0.3.2
[adjusted] code / function names
Code:
[B]v0.9[/B]
Current changelog: 07.02.2017
[added] new twrp 3.0.3.2
[added] new magisk v11.1
[disabled] second disclaimer
[disabled] bootloader status in device overview at the top as I haven't found a secure way to detect a locked/unlocked bootloader yet.
[removed] magisk v10.2
[removed] twrp 3.0.3-N
Code:
[B]v0.7[/B]
Current changelog: 02.02.2017
[added] boot to safe mode
[added] wipe menu
[added] new twrp 3.0.3-N and platform tools 1.0.3.6 (no default yet. versions can be switched in troubleshoot menu for testing)
Code:
[B]v0.5[/B]
Current changelog: 31.01.2017
[added] each action shows some information about what's going to happen now
[changed] each action must be confirmed to be executed. if you don't need that, enable auto-yes in troubleshoot menu
Code:
[B]v0.3p1[/B]
Changelog: 28.01.2017
[fixed] added missing magisk manager to installation procedure
Thanks to/Credits
Code:
:: > shakalaca
:: > chainfire
:: > topjohnwu
:: > twrp
:: > social-design-concepts
:: > phhusson
:: > say99
:: > Deathschythe33
:: > ggrandou
:: > gerasiov
You'll find more credits inside the source code.
I hope i didn't forget anyone. If so please report.
XDA:DevDB Information
Zenfone 2 ToolKit [Z00A/Z008/Z00X], Tool/Utility for the Asus ZenFone 2
Contributors
rummsbumms
Version Information
Status: Stable
Current Beta Version: 1.3
Beta Release Date: 2017-10-14
Created 2017-01-28
Last Updated 2018-07-31

Reserved

Reserved

What makes this different with @Giovix92's tool?

Yes, same question as above. What makes it different from ZE55xML_Modder by Giovix92

@krasCGQ @fred_gaou
i think that main difference is that this toolkit supports the last 3 MM firmware versions and works automatically for all tasks, so user interaction is reduced to wait & perhaps read

@rummsbumms
Question 1: would you suggest to run ze551ml_toolkit.bat as admin or not?
Question 2: did you personally test all root method provided by toolkit: SuperSU, Magisk+SuperSU, Magisk+phh superuser? Did you succeed to properly unroot all of them? Will you suggest one method rather than another?
Question 3: did you test custom ROM install via TWRP such as last LineageOS after unlock bootloader and install TWRP with your toolkit?
Question 4: What is "Auto Packages" supposed to mean? What does it do? According to script code, it seems to unroot and restore stock bootloader. That's why I don't understand the Auto Packages term.
====
To avoid having to get always the same questions like
How to root for the 1st time or safely upgrade firmware and root again…?
How to get back to a clean stock device?
What does this menu entry really do?
etc.
I would suggest some guide lines to help users in the 1st post as well as in a "how to.txt" file along the toolkit or in the batch itself as a menu entry named "Help" or "FAQ" or else.
====
FEATURES REQUEST
# Add FACTORY RESET DEVICE menu entry. This will imply:
Code:
fastboot erase userdata
fastboot erase cache
# Add Erase /system, /data and /cache menu entry, may be useful before installing a ROM. This will imply:
Code:
fastboot erase system (I guess it will work only if bootloader have been unlocked)
fastboot erase userdata
fastboot erase cache
or a complete wipe that will format the partitions too
Code:
fastboot -w
# Add a way to Back up and restore EFS, see this thread.
# And +1 to the post below about ifwi.
====
I would suggest also in the 1st post as well as in a "how to.txt" that the functions be more detailed. Example:
I see you chose to use adb/fastboot 1.0.32 version. Just to let you know that Minimal ADB and Fastboot v1.42 provide a more up to date adb and fastboot (the last 1.0.36). Why do you use this old 1.0.32 version?
====
I didn't test ZE55xML_Modder by Giovix92 or this toolkit yet, but just by reading the batch file, I can tell your code is way more elegant and skilled and should avoid the magisk root bug that ZE55xML_Modder users encounter.
====
And why checking if ADB is installed as system-wide since your toolkit already provides local adb/fasboot ? What's the point to add this "unnecessary" step ?
====
Great Work ! :good:
I will test your toolkit very soon and give feedback. I hope to get answers from you in the meantime.
Regards

What would be ideal , if possible to add
Is ..
An ifwi version detector
Because , there are a lot of people who flashed their phones who haven't a clue they have M version with LP bootloader.
They think they have M BL and brick their phones
If any help...
IFWI versions on 551 or Z00A
0094.0177 is locked LP bootloader
0094.0173 is unlocked.
0094.0183 is M BL
If your tool kit could detect these , it could flash back original stock recoveries and help many unaware people restore and upgrade stock LP to M
Then they could again use your tool to unlock once upgraded to stock M.
Where they then could make back ups of stock again before flashing custom ROMs

@fred_gaou
You gave some nice questions&suggestions!
About your questions:
You don't need the batch to run as admin as I don't use any function that needs admin rights.
Yes, I've tested all root functions and switched between single supersu, magisk with phh and magisk with supersu, but of course always with running the unroot task first. my personal favorite is magisk with phh b/c of the magisk hide. that's what i need for some banking apps :angel:
Not yet. I don't think i'm going to try that soon as I want to stay at stock rom atm. If you have any idea to implement that to this toolkit, i would be pleased to know.
The idea of the auto packages is to combine some single actions like unroot & root. So there is actually just one package, which I used the most time to get back to my favorite root solution.
The other points:
Giving more guidelines/hints in this thread&toolkit is a good point. I'll try to add this as soon as possible. :good:
Putting factory reset & backup on my todo list :good: Are there any installation procedure for roms that recommend to erase /system first? I've done that by mistake a few months ago and started to sweat. As this is a very dangerous command, I would only implement this if there is a need.
I know about the newer 1.0.36 version. That was the reason for the action "force internal platform toolkit" in the troubleshoot menu. But I had a LOT of problems running the new version on 2 different machines. The daemon didn't start with an error telling that the adb.log couldn't be opened. I'll put it on my todo list too, but with low priority.

timbernot said:
What would be ideal , if possible to add
Is ..
An ifwi version detector
Because , there are a lot of people who flashed their phones who haven't a clue they have M version with LP bootloader.
They think they have M BL and brick their phones
If any help...
IFWI versions on 551 or Z00A
0094.0177 is locked LP bootloader
0094.0173 is unlocked.
0094.0183 is M BL
If your tool kit could detect these , it could flash back original stock recoveries and help many unaware people restore and upgrade stock LP to M
Then they could again use your tool to unlock once upgraded to stock M.
Where they then could make back ups of stock again before flashing custom ROMs
Click to expand...
Click to collapse
Haven't thought about that scenario. Can you give me some more details? Users with bricked phones can only boot fastboot and nothing else?
I currently don't know a method to detect the ifwi version in fastboot state, so i would probably need twrp or a running system (almost certainly with root permission) to get ifwi information.

Hi,
I just want to verify. I have the ASUS Zenfone 2 Deluxe Special Edition that I have upgraded from the stock 5.0.0 Android Lollipop (I forgot the ASUS Firmware version number) to the the Official ASUS 6.0.1 Marshmallow (Version WW-4.21.40.223(andriod M)) I can use this?
I regret upgrading from the Official LP to the Official MM with all the bloatwares. I am looking for a way to get root just like with my Sony Xperia phones but I am learning that getting root on ASUS Zenfones on MM is difficult. Almost all solutions I am reading is advising to downgrade from MM to LP, root, then manually upgrade to MM

rummsbumms said:
Not yet. I don't think i'm going to try that soon as I want to stay at stock rom atm. If you have any idea to implement that to this toolkit, i would be pleased to know.
Click to expand...
Click to collapse
Well, I'm still on stock LP so I would not be a good adviser. I trust the experienced users that switch and update ROM weekly so they will give useful feedback soon. Since some guys on LineageOS used Giovix modder to unlock bootloader and install ROM via TWRP, I guess it's currently the way to go.
rummsbumms said:
The idea of the auto packages is to combine some single actions like unroot & root. So there is actually just one package, which I used the most time to get back to my favorite root solution.
Click to expand...
Click to collapse
I get it now. It could be a useful section in future to run sequential commands at once.
rummsbumms said:
Putting factory reset & backup on my todo list :good: Are there any installation procedure for roms that recommend to erase /system first? I've done that by mistake a few months ago and started to sweat. As this is a very dangerous command, I would only implement this if there is a need.
Click to expand...
Click to collapse
Yes it is wise. I just provided the command because it was implemented in Giovix Modder and often reported as a way to clean up before flash all stock in other device. Don't know for 551.
rummsbumms said:
I know about the newer 1.0.36 version. That was the reason for the action "force internal platform toolkit" in the troubleshoot menu. But I had a LOT of problems running the new version on 2 different machines. The daemon didn't start with an error telling that the adb.log couldn't be opened. I'll put it on my todo list too, but with low priority.
Click to expand...
Click to collapse
Detail is good to know. What OS do you use: 7, 8.1 or 10? If 1.0.32 works fine on every version, there is no point to risk to break anything using 1.0.36.
Thanks for your answers.

rummsbumms said:
Haven't thought about that scenario. Can you give me some more details? Users with bricked phones can only boot fastboot and nothing else?
I currently don't know a method to detect the ifwi version in fastboot state, so i would probably need twrp or a running system (almost certainly with root permission) to get ifwi information.
Click to expand...
Click to collapse
Thinking about it now a bit more , it maybe tail end for this problem .
The actual problem people were having was they thought they had cm13 with M BL , actually they had the LP bootloader cm13 . They would be in a working system then flash 14.1 / 7.1 builds then , brick their devices .
They forget they never upgraded bootloader and with having 6.0.1 M in build information in settings, presumed they had upgraded bootloader at some point but didn't .
Maybe , to prevent the tail enders from performing such tasks again , maybe a simple addition like a warning , like build date which in cm 13 , to check.. if before July 2016 and have IFWI version 0094.0173 unlocked . Then you could direct them to say a return to stock option , flashing back boot and recovery for say on 551 LP 2 20 40 .196 Version , then possibly install the full ROM from say a link or something like ...Then info to upgrade to stock M before returning back to tool to unlock updated to the latest M.
But like mentioned , we maybe at the tail end of this problem.
Probably related to 95% of the bricking threads here for zenfone.
Anyway thanks for taking interest

Deathschythe33 said:
Hi,
I just want to verify. I have the ASUS Zenfone 2 Deluxe Special Edition that I have upgraded from the stock 5.0.0 Android Lollipop (I forgot the ASUS Firmware version number) to the the Official ASUS 6.0.1 Marshmallow (Version WW-4.21.40.223(andriod M)) I can use this?
I regret upgrading from the Official LP to the Official MM with all the bloatwares. I am looking for a way to get root just like with my Sony Xperia phones but I am learning that getting root on ASUS Zenfones on MM is difficult. Almost all solutions I am reading is advising to downgrade from MM to LP, root, then manually upgrade to MM
Click to expand...
Click to collapse
As far as i can see from the asus page, the zf2 deluxe special edition uses the same firmware files and you already have the newest firmware (.223) installed, so i think it should work.
Is your bootloader still locked?

Thank you so much for your awesome ToolKit, works flawlessly !!
<3

v0.5 is out

rummsbumms said:
v0.5 is out
Click to expand...
Click to collapse
thanks, can you simply make 3 downloads complete for the 3 mm versions? now is a bit confusing with this updating/base files.
I don't think that 80mb would be a problem to download, everyone have at least a dsl line, we are not talking of gbs, thanks

v0.7 is out
@fred_gaou: I've tested with win10. 1.0.3.2 works fine and will be default, but I've added 1.0.3.6 too. perhaps someone could test on other machines as i still have problems using it and don't know whats the problem.
@holymoz: I've made a additional "full" package which contains all files. the "base" version still only contains the latest mm firmware files.
@timbernot: Still thinking about it. Maybe some kind of decision tree asking for the problem could lead the user to an action that could cure the problem. I'll keep it on my todo list.

V0.5 works okay on my device with win 10 . i will test later the new build thanks

rummsbumms said:
As far as i can see from the asus page, the zf2 deluxe special edition uses the same firmware files and you already have the newest firmware (.223) installed, so i think it should work.
Is your bootloader still locked?
Click to expand...
Click to collapse
Hello @rummsbumms,
Thank you for taking your time to respond. Yup, my phone's bootloader is still locked. Everything in this phone is "official" including the freaking official bloatwares. I love the HW specs of this phone, but the bloatwares are F***ing crazy!

Guide to flash Nougat if you face bootloops when upgrading

Hey guys!
This is just a simple post for you guys who want to make the jump to Nougat on the Snapdragon version of the Redmi Note 3, but face issues like bootloop or soft brick .
I tried many times to flash to Nougat and failed, so I thought I would document my experience for anyone who needs it.
The main problem I faced was an outdated bootloader.
Here, I have detailed the steps I took to flash Nougat successfully on my phone.
This does assume that you do have some experience and knowledge about the world of custom ROMs.
- disclaimer -
I am not responsible for any damage you may cause as a result of following this guide.
I am not affliated with any of the authors that wrote the guides that I will link in this guide.
The links are there purely for reference, and if you wrote one of the posts that I have linked in this guide, please message me to have your name at the bottom of this post.
- disclaimer end -
Here are a few things to note.
1) The version of MIUI you were on when you unlocked your bootloader.
2) Whether or not you have uploaded your bootloader
3) Whether you unlocked your bootloader officially
4) Whether you have permission to unlock the bootloader from XiaoMi.
5) Download and install the latest version of MiFlash
6) Download and install ADB and Fastboot on your PC
7) Boot into download mode to check if your PC recognises your phone. If not, reinstall the appropriate drivers.
A few websites you might want to refer to :
A MIUI forum page which teaches you how to flash/unbrick your Redmi Note 3.
http://en.miui.com/thread-235865-1-1.html
A MIUI forum page that teaches you how to repair your IMEI if it gets corrupted
http://en.miui.com/thread-245598-1-1.html
A guide to the XiaoMi deep flash cable as a kind of last resort(This is essentially Xiaomi's version of Samsung's USB jig; to force your device into download mode)
http://forum.xda-developers.com/redmi-note-3/how-to/guide-how-to-flash-hard-bricked-redmi-t3490055
First, you may want to do a few things.
1) Check and double check your device codename (Kenzo for Redmi note 3 Pro, Kate for Redmi Note 3 SE)
2) Download the latest Global Developer ROM (There are .zip and .tar versions, for this guide we will be using the latter. I get my ROMs from here : http://en.miui.com/a-234.html )
After downloading it, decompress it until you see the file extension .tgz, then unzip it once more. At the end you should have one folder which contains some files and a folder called images.
3) Research and download the ROM and custom kernel of your choice
4) Check up and research anything you are unfamiliar with ( This is a great place to start : http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708 )
So, to flash the ROM, you can follow these steps. Do note that these steps worked for me at the time of writing and may not necessarily work for you.
1) Backup your stuff (Pictures, chats, contacts, etc.)
2) Go to developer options and check enable OEM unlock and ADB.
3) Reboot into bootloader.(adb reboot bootloader / vol- + pwr from power off state)
4) Use MiFlash to flash the global developer ROM you downloaded.
5) Use the MiUnlock tool to unlock your device.
6) Reboot to MIUI. (If you don't, you might face problems with TWRP demanding for password)
7) Boot to download mode again.
8) Install TWRP recovery.
9) You can now make a nandroid backup. Also make a backup of your EFS partition and keep it somewhere safe.
This assumes that you flashed the latest global developer ROM.
10) You can now flash the ROM and GApps.
11) If you want to install a custom kernel, finish setting up the phone before flashing one.
12) You can install Viper4Arise now if you want.

Newb needs help rooting, unlocking Bootloader and getting a Custom ROM for ALE-L21

Hey there,
I need help, hope you have some for me . I want to use the 6.0.1. OpenKirin OmniROM on my phone and struggle even figuring out a way to get there.
I just bought a used ALE-L21 DualSIM phone with the B602 Build and EMUI 4.0.3 installed. The device is not rooted, nor has its bootloader been unlocked. The EMUI update service does not offer me any patches.
Could someone please line out to me which steps I have to take in order to root my ALE-L21 and get this ROM to work?
Disclaimer: No, I'm not just a lazy moron who does not want to read other topics on this forum - I'm a mere user with less-than-average knowledge of Android development or stuff like that. And I just can't make complete sense of the various posts I've found, since English is not my mother tongue and there seems to be a whole bunch of ways to do certain things with a phone. Well, since obviously I don't want to brick my new phone, I'm not too sure how to best puzzle together the pieces this Forum offers me. It would be insanely helpful if I could get a list that reads out something like:
1. Action - Source (for needed files, e.g.) - Result, on to step 2
2. Action - Source (for needed files, e.g.) - Result, on to step 3
3. ... and so on...
Okay, just so you see that I'm not entirely lost, I'm gonna show you the picture which is currently in my mind.
From what I understand so far, there's the following steps to get there (please rectify or rearrange steps as far as needed):
1. Update the device to Vanilla EMUI 4.1, Build B895 or B896 (I am currently downloading the B896 Build from this forum - which one is recommended? My phone is DualSIM)
2. Unlock Bootloader (What's the best way to do it? Huawei CS? Heard it's not even sure you get an answer. DCUnlocker? Wants money... Please help me clarify)
3. get TWRP 3.1.1.0 (I already have the IMG file, how do I get it to run on my phone?)
4. Root the device (I'd like to go with MAGISK, does anyone have a link for a MAGISK build confirmedly working on ALE-L21?)
5. Do some magic with TWRP (Which steps exactly?)
6. Flash the ROM Zip file via TWRP
7. Flash Gapps via TWRP
Is that about it?
As I said, please feel free to add to/adjust my list!
Thanks in advance,
Pako

If you haven't already install minimal adb tools on computer (windows) found here :
http://bit.ly/2jxX4ya
You then need to unlock bootloader using minimal adb tools and the unlock code
Unlock Code:
http://bit.ly/2z9EFhV
Unlock Bootloader Method in this thread here:
http://bit.ly/2oIASBs
After you are done unlocking the bootloader
Install twrp find that here :
http://bit.ly/2ok9BTi
There was a tool that was here somewhere to install twrp but I will link to my copy here
http://bit.ly/2ATBgRP
What you do is put the twrp image file in data folder
then change the name of the twrp file to TWRP_3.1.1-0_ALICE.img or
edit the install.bat file line data\fastboot.exe flash recovery data\TWRP_3.1.1-0_ALICE.img to the name of your twrp file
Once twrp is installed then you can pick which rom you want
The 6.0 roms arent going to be supported anymore so i suggest going for 7.0 ROM
I'm on AOSPA which is the cleanest and has good battery life
To install 7.0 rom you need B895 or B896 found here on the first post:
http://bit.ly/2jypIij
this is installed through twrp (which is accessed when Phone is off by holding volume up + power then let go once it vibrates or connect the phone to the computer and then type adb devices then adb reboot recovery in minimal adb tool)
once in twrp you need to install the B895.zip or B896.zip file then reboot your phone will boot into emui
you need to install twrp again as B895 or B896 wipes it
After installing twrp you can then install any custom rom of your choice
let the rom boot and then go back into twrp and install gapps found here: "http://bit.ly/1JOWjUqi recommend nano or even pico pick am64 7.1
I would also recommend installing Galactic forced deepsleep http://bit.ly/2ANVdbS

Hey there,
thank you very, very much for your comprehensive walkthrough! (Almost*) everything worked to perfection and I am now a happy user of OpenKirin's OmniROM 6.0.3. mod! Yeah, no 7.x... but I'd prefer to wait with that until the "issues" section of AOSPA does not contain any relevant things anymore. OmniROM seems to have no issues anymore, so I'm content with my choice. I will now follow your last advice and flash the Deep Sleep Mod to improve my device's battery life, and then I'm just happy.
* = The only issue I encountered was when having flashed TWRP, the device booted to the crappy EMUI eRecovery instead of TWRP. I solved this issue using this advice from another thread.
So, once again, thank you! All you xdaDevs, keep on developing ways to improve people's lives with their android devices!
Cheers,
Pako

ZTE Blade A2 Plus Rooting( SuperSU or Magisk),Recovery & Flashing Stock Rom

Hi there, good to see you.
After struggling to find any helpful information about rooting ZTE Blade A2 plus, I finally was able to root>soft brick>hard brick>stock flash>repeat this beautiful device. So thought to share it here so that it becomes helpful for someone in need.
Device Information: https://forum.xda-developers.com/ge...te-blade-a2-plus-5-5-fhd-mt6750t-3gb-t3480759
Prerequisite: Winrar Latest version, VCOM and device drivers (MT67xx), General intelligence to download the attachments and to arrange everything in order and you're good to go
Step 1: Install custom recovery (We'll install TWRP)
a} Download recovery and preloader
b} Download Scatter file
c} Download SP Flash tools
d} Only tick recovery and preloader and select the downloaded files and flash it
e} When the process finishes and SP flash tools displays done, remove the phone and press "Vol Up+Power" to boot into recovery. It may ask you to make /system writable if you want swipe as indicated
f} Done enjoy
Note: Take this opportuniy to first of all backup your stock rom using TWRP and save it elsewhere.
Step 2: Rooting (With Magisk Or Super SU)
a} Download Magisk or Super SU flashable zip as per your need
Note: Magisk gives most of the Super SU features and doesn't trips google security net so you are able to use banking apps while rooted with magisk
b} Place downloaded zip in your sd card
c} Boot into TWRP recovery and flash the said zip
d} Done enjoy
Step 3: Flashing stock rom (Only russian version as of now)-Language is english bloatwares are Russian
a} Download Stock Rom from https://yadi.sk/d/RZLBrKKv3LxejN
Note: It contains PC Flashable stock rom along with scatter files and NVRAM backups so it'll help if you lose IMEI during the process, it is advisable to keep this offline as backup in case links stops working.
b} Flash the downloaded stock rom with SP flash tools
Note: This stock rom doesn't support VOLTE so i advice you to first take a full backup of your initial rom after installing TWRP, also please share that backup here as well so as i could add it to this thread to make it helpful for someone who has already lost VOLTE inclusing me
Conclusion: I'll be very happy if this information proves useful to you in any manner and also request you to must share your backup for me to get VOLTE back.
Thank You

MIUI 9 For A610 Plus
Preview:
Many many thanks Alfonso for making this vary valuable post . I think A2 Plus and A610 Plus are almost same , so kindly check this ROM me and may solve your volte problem
ww.getdroidtips.com/miui-9-zte-blade-a610-plus/[/url]

Rajevpmavoor said:
Preview:
Many many thanks Alfonso for making this vary valuable post . I think A2 Plus and A610 Plus are almost same , so kindly check this ROM me and may solve your volte problem
ww.getdroidtips.com/miui-9-zte-blade-a610-plus/[/url]
Click to expand...
Click to collapse
Although the rom is bugless but, unfortunately VOLTE didn't work.

MIUI 9 For A610 Plus
Did you flash this new MIUI 9 ROM , I think it has volte and it is in Android M.

Alfonso Osnofla said:
Although the rom is bugless but, unfortunately VOLTE didn't work.
Click to expand...
Click to collapse
does it boot into meta mode on pressing volume down+power button??( bcoz my fone boots into meta mode on doing so)
and how to go into bootloader?
while using sp flash tool i power off the fone and then connect it to sp flash tool via usb cable ...fone gets detected and but download for twrp doesnt occur ..it says PMT changed for the rom, select format all+ download ....
but i didnt do format all coz i dont have flashable stock rom...

I lost my IMEI after flash ROM, not able to retrieve IMEI

Issue in camera & Finger Lock
Alfonso Osnofla said:
Although the rom is bugless but, unfortunately VOLTE didn't work.
Click to expand...
Click to collapse
I have checked both ROM, Miui ROM camera is look like .02MB, No VOLTE, Finger Print lock is not working

Thanks. I have messed up anyway...
Anybody have a complete Readback (Using SP-Flash Tools) copy of (volte) rom?
I lost Imei, From the given NVram.bin, Could not edit Imei using BPGL.... pull as Maui Meta and SN writer can not do this with present update.
I need to revert back. please help with ROM copy and NVRAM Edit.

Alfonso Osnofla said:
Hi there, good to see you.
After struggling to find any helpful information about rooting ZTE Blade A2 plus, I finally was able to root>soft brick>hard brick>stock flash>repeat this beautiful device. So thought to share it here so that it becomes helpful for someone in need.
Device Information: https://forum.xda-developers.com/ge...te-blade-a2-plus-5-5-fhd-mt6750t-3gb-t3480759
Prerequisite: Winrar Latest version, VCOM and device drivers (MT67xx), General intelligence to download the attachments and to arrange everything in order and you're good to go
Step 1: Install custom recovery (We'll install TWRP)
a} Download recovery and preloader
b} Download Scatter file
c} Download SP Flash tools
d} Only tick recovery and preloader and select the downloaded files and flash it
e} When the process finishes and SP flash tools displays done, remove the phone and press "Vol Up+Power" to boot into recovery. It may ask you to make /system writable if you want swipe as indicated
f} Done enjoy
Note: Take this opportuniy to first of all backup your stock rom using TWRP and save it elsewhere.
Step 2: Rooting (With Magisk Or Super SU)
a} Download Magisk or Super SU flashable zip as per your need
Note: Magisk gives most of the Super SU features and doesn't trips google security net so you are able to use banking apps while rooted with magisk
b} Place downloaded zip in your sd card
c} Boot into TWRP recovery and flash the said zip
d} Done enjoy
Step 3: Flashing stock rom (Only russian version as of now)-Language is english bloatwares are Russian
a} Download Stock Rom from https://yadi.sk/d/RZLBrKKv3LxejN
Note: It contains PC Flashable stock rom along with scatter files and NVRAM backups so it'll help if you lose IMEI during the process, it is advisable to keep this offline as backup in case links stops working.
b} Flash the downloaded stock rom with SP flash tools
Note: This stock rom doesn't support VOLTE so i advice you to first take a full backup of your initial rom after installing TWRP, also please share that backup here as well so as i could add it to this thread to make it helpful for someone who has already lost VOLTE inclusing me
Conclusion: I'll be very happy if this information proves useful to you in any manner and also request you to must share your backup for me to get VOLTE back.
Thank You
Click to expand...
Click to collapse
Just try http://www.ztedevice.com/support/detail?id=FE22BEF5C33D4A17BCDA20AAE2631951 ( http://download.ztedevice.com/support/product/569/201802111051594/sd/20180211105554767.zip )
sd card update using twrp.
But first remove the first line from update script file located inside the zip.
Just reply.

Need MIUI rom
Heyy plz gime me teh rom for zte blade A2 plus i really need a miui rom for zte blade A2 plus...

Help I'm confused.
Reading the comments i got to know that many people lost their IMEI and VOLTE , I want to root the device So can anyone tell me when does this problem occur (loosing volte and imei) during rooting or while flashing a custom rom?

kingksath said:
I lost my IMEI after flash ROM, not able to retrieve IMEI
Click to expand...
Click to collapse
Did you loose your IMEI on rooting or while flashing any custom Rom?

http://www.mediafire.com/file/6768c1x7dqyd818/update.zip
version 4 sd card update

vasilemk said:
http://www.mediafire.com/file/6768c1x7dqyd818/update.zip
version 4 sd card update
Click to expand...
Click to collapse
What is it for?
Is it for volte?

vasilemk said:
http://www.mediafire.com/file/6768c1x7dqyd818/update.zip
version 4 sd card update
Click to expand...
Click to collapse
Is this an update to the Stock Rom?

hi, can u help me please, iam tryin to update with twrp , i did remove first line from script but i have error.

Found a way to unlock bands on MTK based phones by flashing basebands from phones with the same chipset. Doing this by using SPFLASH and flashing md1 files. Still unable to connect to cell network on my Doogee bl12000. Flashed this phones MD1, was wondering if anybody could provide me with the nvdata and nvram from the ZTE blase a2 plus. Hoping by flashing those files can connect to a U.S. network.