Rebrand-Update-Tool HWOTA7 for Huawei P9-EVA
German Thread (not updated yet): https://www.android-hilfe.de/forum/...-p9-eva-inoffizielles-oreo-update.884138.html
→ HWOTA7 Tool for P9 Plus VIE is different: https://forum.xda-developers.com/p9...rand-update-tool-hwota7-p9-plus-vie-t3843930/
In 2018, the P9 was still being used by many users. Many were annoyed because Huawei did not provide the Android 8 update for the European models. The Chinese models got Oreo and there was really no reason why European models didn't get it.
HWOTA7 offers the possibility to change the model of the P9. This allows, for example, a Chinese model to be converted into a European one - and a European model into a Chinese one. In order to update the P9 to Android 8, it is necessary to convert the respective European model (EVA-L09 or EVA-L19) to a Chinese model (EVA-AL10).
The instructions for this conversion and the Oreo update can be found in the next post #2:
https://forum.xda-developers.com/t/rebrand-update-tool-hwota7-p9-eva.3820849/post-77161313
Basic information:
→ HWOTA7 for EVA is programmed ONLY for to use on Android 7 (Nougat). It does not work on Android 8 Oreo (and it doesn't work on Android 6). Of course you can update from Android 7 to Android 8, but to go back to Nougat from Oreo this tool cannot be used. There is another solution for this purpose, you can find it in post #3:
https://forum.xda-developers.com/t/rebrand-update-tool-hwota7-p9-eva.3820849/post-77161314
→ The hardware and firmware of the different P9-EVA models is different. For example, if you convert an EVA-L09 (SINGLE-SIM) to an EVA-L19 (DUAL-SIM), you will not get a DUAL-SIM function. If you convert the European P9 to a Chinese P9 - which is necessary to update to Oreo - no mobile network will work at first because the chip is different and the Chinese firmware only addresses the real Chinese models. Therefore it is necessary to flash a network patch after updating to Oreo (see instructions Post #2).
→ With HWOTA7 you can just update your current Firmware with FullOTA-MF Firmware (3 zip files, two of them renamed), but the Firmware you use MUST match your device model and cust (for exampel, if your device ist EVA-L09C432 you cannot use C636 Firmware). For updating your Firmware with HWOTA7 you choose: Using the script /1. Change firmware
→ You can rebrand (convert your phone model) between L09/L19/L29 and all Chinese Brands (remember: your hardware does not change) by choosing in HWOTA7: Using the script /2. Change location. (14 oeminfo files are included for different locations and cust).
With this option you can debrand from Vodafone/Telekom to the open european cust C432 for example (which is not branded to a Cellular Provider) - or you can rebrand a chinese modell (for example EVA-AL00C00, EVA-AL10C00) to EVA-L19C432 (which has also Dual-Sim).
If you own a chinese modell and it is already on Oreo, you have to downgrade first with HiSuite to Android 7, then you can use HWOTA7 Tool to change location for example to EVA-L19C432. Immediately afterwards it is necessary to flash the appropriate firmware for EVA-L19.
→ If your Phone has SIM Lock, Debranding does not unlock mobile network - you can do that with HCU Client by DC Unlocker
→ Before you change anything, make a note of the build-number from the "About phone" settings. This is important to know if you want to go back to the original phone model.
To revert to the original model, the correct oeminfo is required (14 are included in HWOTA7 tool) - if your model is not there, backup the oeminfo with TWRP. If you send me these, I can integrate them into the tool. The oeminfo of the P9 models on Android 7 does not contain any security-related, device-specific information such as IMEI or serial number.
And you need the firmware files corresponding to the model.
Where can I get the model-specific firmwares?
The new HWOTA7 Tool Version 1.2 contains the folder "1.Firmwares" This contains already the starting firmware for EVA-L09C432 and EVA-L19C432, as well as the required Android 7 firmware for EVA-AL10 and the Android 8 update firmware for EVA -AL10. The firmwares are already renamed correctly to work with the HWOTA7 tool.
The "1.Firmwares" folder also contains the "2.Downgrade-EVA-AL10-Andr.8-to-Andr.7" subfolder. It contains a HWOTA.zip that allows you to downgrade from Android 8 to Android 7 by using the SD card + TWRP. After that, the HWOTA7 tool can be used again to return to the original model (Instruction for that see Post #3)
The most important firmwares are already included in the HWOTA7 tool to update from Nougat to Oreo and also to return to Android 7 and EVA-L09/EVA-L19(C432).
Of course I cannot include all firmwares that are available for the different models and locations.
In 2018 and for some time afterwards, it was pretty easy to find the right firmwares with the Firmwarefinder (by Developer MT). This option no longer exists!
If you need a different firmware (than included) for your original model, this is the only way: https://forum.xda-developers.com/t/...geos-16-0-for-huawei-p9.4078383/post-85016053
But for that you must use the new URL: https://professorjtj.github.io/
If you download firmwares from that source, the firmwares must always contain 3 zip files.
And you must rename two of the zip files, because the HWOTA7 is programmed to only work with those names:
update.zip = update.zip (do not rename)
update_full_EVA-XXX_XXX_cn.zip - rename to: update_all_hw.zip
update_data_full_public.zip - rename to: update_data_public.zip
→ You should disable "Hide extensions for known file types" in Windows Explorer's file options under the "View" tab. Because if you unintentionally rename the update_all_hw.zip to "update_all_hw.zip.zip", flashing the firmware will not work.
Requirements:
You need the Bootloader Unlock code for your phone → if you do not have it, it can be read out with HCU Client by DC Unlocker (4 credits = about 4 EUR).
Developer Options must be enabled and inside: → OEM Unlock + ADB Debugging in charging only mode + USB Debugging (in this order) enabled
HiSuite HDB in Settings on the phone should be disabled, HiSuite on PC should be closed in the background
You need a working USB Connection (drivers) between P9-EVA and PC (MTP, ADB and Fastboot → Allow access to the phone, accept RSA key fingerprint)
The battery should be charged.
Backup your important data (folders from internal storage such as WhatsApp, DCIM, Downloads, Music, etc. - as well as user apps with data, contacts, calendars, sms, etc.) → The internal storage is erased several times during this process. Follow the instructions.
HWOT7 is working on Windows 7, 8.1, 10 and 11 by using update_eng.bat (it does not have to be run with administrator rights). The instructions in the thread are formulated for Windows users.
For Linux computers read post from @leodp : https://forum.xda-developers.com/t/rebrand-update-tool-hwota7-p9-eva.3820849/post-83916865
or/and use the tipp by @MSe1969 - which is the contributor of the amazing → Treble ROM based on LinegeOS 16, MicroG and Bromite WebView always up-to-date for Huawei P9 (Update to Oreo-Firmware required):
"A hint for Linux users: The HWOTA tool is in fact a windows wrapper around Linux shell scripts, so there is no real need to use Windows, if you have a working Linux installation ( however, make sure to replace the 'mkdir' commands in hwota_eng.sh with 'mkdir -p' ).
For MacOS computers use: https://github.com/feedsbrain/hwota7
Download P9-EVA-HWOTA7-v1.2.zip:
11,9 GB, MD5: 5e93700221dfd8f2d5083d2cf22706f1
https://mega.nz/folder/XNRjBJAS#7Ne--slFgj0IsFbQwrlaLw
Changelog:
v1.2: Added required Firmwares + HWOTA-SD-Card/TWRP-Downgrade from Oreo Tool + oeminfo for EVA-L29C636
v1.1: Added "cmd-here-exe" in HWOTA7\tools\windows. Run the file as an administrator for general operations using ADB or Fastboot Mode. You can flash an Image (ramdisk, recovery_ramdisk, system.img...) out of this folder. → Same function as "Minimal ADB and Fastboot" . Removed: "archive-recoverys" - no longer necessary.
v1.0 Stable Initial release:
Note: The HWOTA Tool is/was available for many Huawei devices. I do not know which person or group has programmed originally. I just took an "empty one" and modified the existing script to work with Huawei EVA, provided the required images (oeminfos, Recoverys, frp-file for eva..) and tested everything on my own device.
Spoiler: How to use the Tool:
How to use the Tool:
Download P9-EVA-HWOTA7-v1.2.zip, unzipp/extract it on the computer with 7zip. The zip file contains the main folder "HWOTA7" Just place this folder (unzipped) as it is to storage C:\ (means: C:\HWOTA7).
The subfolder "1.Firmwares" is located in the HWOTA7 folder. This contains the most important 3-part firmwares, but each packed in just one zip file (to reduce the upload size).
The firmware that you need must therefore first be unpacked.
The zip files contained therein (= 3-part firmware) must be copied to the "update" subfolder without being unzipped. → C:\HWOTA7\update - this is the main working folder.
With a double click on the "update_eng.bat" the rebrand/update tool "HWOTA7" is executed and a terminal window opens.
If you are on custom ROM, first go back to Stock Firmware ("Using script" and "Change firmware" - use the Firmware that matches your device and cust)
HWOTA7 is self-explanatory. It detects what to do and prompts you to press certain key combinations or enter the unlock code.
→ The USB cable between the phone and PC remains connected throughout the process!
→ The phone is connected to the PC via USB and you start with the key combination: VOL- and Power Button key into Fastboot mode.
→ Only press "Enter" in the terminal if the described step, in the line before, was executed.
→ If you face an error like: "adb: error: connect failed: no devices/emulators found" - close Terminal, reboot phone into Fastboot mode and restart HWOTA7
→ When the Bootloader is locked, the tool will unlock the Bootloader with the code. Thereafter, a factory reset is performed by clearing the internal storage = Lowlevel Wipe.
When the Bootloader is open, the tool automatically flashes TWRP and prompts you to press (and hold) VOL+ and Power Button to start into TWRP.
After you click 2x in the terminal on "Enter"
→ Before you choose: 2. Using the script and 1. Change firmware or 2. Change location - make sure, the 3-part FullOTA-MF Firmware is already in the update folder: C:\HWOTA7\update - and two of the three zip files are correct renamed (included Firmwares are already renamed)
Important difference between four situations:
1) When the Bootloader is closed, HWOTA7 opens it with the code, a "lowlevel" factory reset is performed and the device must then boot into the system. In the setup everything can be skipped (which is possible) - but the developer options must be switched on (1.ADB Debugging + 2.USB Debugging enabled). And HiSuite HDB disabled.
2) If you select "Change firmware" to flash the firmware, the tool copies the ZIP files to the phone in the /data directory, flashes the Nocheck recovery, and installs the firmware. In this case, you also need to boot into the system and check if Developer options with the required settings are enabled.
3) But if you do the step: "Change location" - this step is different! The tool will flash the corresponding "oeminfo", close the Bootloader and request the Unlock code to unlock the device and force a "lowlevel" factory reset → In this case (only), you should NOT boot into the system after the reset. Wait until the EMUI recovery is 100% done with the reset. Then comes the message "Reset succesful, device will restart" Now press (only) the VOL+ button and keep it pressed so that the device starts into TWRP. Now click on "Enter" in the terminal. HWOTA7 now copies the firmware to the device, flashes the Nocheck recovery, reboots and flashes the firmware belonging to the "oeminfo". After this step, the device must be booted into the system.
4) If the device boots into the system and you have a black screen, with an input field in the middle and possibly the keyboard (do not get worried) - the Bootloader was locked by the firmware during rebranding. In this case, press the Power Button to restart and hold down the VOL- button during the restart to start the device into Fastboot mode. Close the Terminal Script and restart update_eng.bat. Click on "Enter" in the Terminal and HWOTA7 will ask you for the Unlock Code and unlock again the Bootloader. Confirm the unlock on the device with the keys, then there is a factory reset followed by a reboot into the system. Now everything is fine.
→ Hint: If you face any error during Firmware will be copied to: /data/update/HWOTA - like: "connect failed, no devices/emulators found" – do following:
Close HWOTA7 Terminal and use menu "Reboot" of TWRP to reboot into Bootloader, start again update_eng.bat - TWRP will be flashed again - boot into TWRP with VOL+ and Power Button - allow system modification - hit "Enter" in HWOTA7 Terminal - Firmware will now again be copied to: /data/update/HWOTA - "System update should start automatically" - Phone will make reboot and flash the Firmware correctly.
Have fun
Credits:
@Atarii EVA-NoCheck Recovery
@OldDroid Android 7 TWRP for P9-EVA, TWRPs for many Huawei devices, Lead Developer/Maintainer Open Kirin Team
@Pretoriano80 Android 8 TWRP for many Huawei devices
@arshilhonor6x Guide to EMUI 8 for Honor 6
@reynard1 @vampirian @dkionline Thank you for cooperation and exchange
@urbanmec Thanks for many hints and tweaks
@zgfg Thanks for great support and help for users of this Thread
XDA:DevDB Information
HWOTA7-P9-EVA, Tool/Utility for the Huawei P9
Contributors
Tecalote
Version Information
Status: Stable
Current Stable Version: 1.2
Stable Release Date: 2022-06-22
(Old Stable Version: 1.1 / 2018-07-24)
Created: 2018-07-25
Last Updated: 2022-06-22
2022-06-21: This Post is under construction - please wait until the update is ready
Old text:
Unofficial Update for European EVA-models to official OREO
Unofficial method to update European models of Huawei P9 EVA to official Android Oreo
- for EVA-L09 - EVA-L19 - EVA-L29
Originally, all models of the P9 EVA and P9 Plus VIE should receive the Android Oreo update. Unfortunately, Huawei has decided to only supply the Chinese models with Android 8.
For this reason, there is an unofficial way to update to the official Oreo → by rebranding the European models to EVA-AL10.
Note: This Guide is for P9 EVA → P9 VIE HWOTA7 with a separate guide to the Oreo update you can find here: https://forum.xda-developers.com/p9-plus/development/rebrand-update-tool-hwota7-p9-plus-vie-t3843930
Oreo runs smoothly and well on the P9, the battery last longer and with Android 8 there is Treble Support. Since it is possible to update P9 to Oreo -
Huawei P9 is officially supported by the OpenKirin Team:https://forum.xda-developers.com/p9/development/roms-openkirin-aosp-collection-t3828806
Here is a small Guide how to go back from OpenKirin to EMUI: https://forum.xda-developers.com/showpost.php?p=77905152&postcount=833
Preparation for the update to Oreo:
If you are on any Custom Rom - go back to Stock firmware first - before rebrand to another location!
You should be on the latest approved Firmware for your device - if you have not the latest approved Firmware, use HWOTA7 Tool to update your Firmware.
Do for every case a Backup (TitaniumBackup /Huawei Backup - without System-Apps/Settings) before. TWRP Backup makes no sence, because you can not restore it on Oreo! [/B]Make sure, the Update-Firmware is copied to the folder C:\HWOTA7\update - and two zip files are RENAMED as mentioned in OP → read OP Post#1. Update your Firmware by using the script (HWOTA7 Terminal: 2. Using the script + 1. Change firmware)
Instructions for updating to Oreo by rebranding your phone to EVA-AL10:
Requirements:
A) HWOTA7 Tool
B) Bootloader Unlock Code for your device
C) For rebranding from EVA-L09 or EVA-L19 or EVA-L29 to → EVA-AL10 you need to download the following 2 Firmwares:
EVA-AL10b399Sp17a /Android 7 (this Firmware is required for the Update to Oreo):
update.zip: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1864/g1755/v138329/f1/full/update.zip
update_data_full_public.zip: http://update.hicloud.com:8180/TDS/...29/f1/full/public/update_data_full_public.zip
update_full_EVA-AL10_all_cn.zip: http://update.hicloud.com:8180/TDS/...A-AL10_all_cn/update_full_EVA-AL10_all_cn.zip
EVA-AL10C00B540 (8.0.0.540) /Android 8 Oreo:
update.zip: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3115/g1699/v208318/f1/full/update.zip
update_data_full_public.zip: http://update.hicloud.com:8180/TDS/...18/f1/full/public/update_data_full_public.zip
update_full_EVA-AL10_all_cn.zip: http://update.hicloud.com:8180/TDS/...A-AL10_all_cn/update_full_EVA-AL10_all_cn.zip
Steps:
0) Check: Your original device is updated to the latest Firmware - you had downloaded the two EVA-AL10 Firmwares (Nougat, Oreo) - you made a Backup from personal folders of your internal storage (WhatsApp-DCIM-Download-etc. folders) and a Backup from your (User) apps, contacts, calendar etc. - HiSuite is closed on PC and disabled in settings on the phone - Developer Options are enabled with OEM Unlock and ADB Debugging + USB Debugging enabled - the 3 Firmware zip files for EVA-AL10b399Sp17a are in the C:\HWOTA7\update folder (two files renamed as descriped in OP Post #1)
1) Connect your device with USB to PC and start from HWOTA7 main folder: update_eng.bat - Accept possibly the RSA query on the display of the P9
2) Restart P9 into Fastboot mode (use restart/restart and press VOL- /or shutdown phone and press VOL- and Power Button)
→ Note: During all steps USB Cable stays connected between phone and PC and you hit "Enter" in Terminal only, if the step, which is written before, is already done!
3) HWOTA7-terminal detects if Bootloader is open or closed - if the Bootloader is closed go to 4) - if the Bootloaer is open go to 7)
4) Terminal ask you for the Unlock code - enter the Unlock code and confirm the Unlock on the phone
5) The P9 reboots and an automatic factory reset is done with internal storage wipe (lowlevel reset) - wait until the phone reboot to system. Skip everything during setup (except what can not be skipped) - Important: Enable Developer Options with ADB Debugging and USB Debugging
6) Restart your P9 into Fastboot mode - now hit "Enter" Button - HWOTA7 Terminal will flash automatically TWRP for Android 7 and gives you the order to boot into TWRP by pressing VOL+ and Power Button (dont hit "enter" before this step is done)
7) In TWRP swipe to allow system modification - now hit "enter" (2x) in the Terminal - after a short while you will see: Upgrade Options
8) 2. Using script: 2.Change location - you will see a list of available "oeminfo" - use: 2.EVA-AL10C00
→ Note: The Firmware for EVA-AL10/Nougat must be already in the update folder (and two zip files renamed)!
9) HWOTA7 flashes now oeminfo for AL10, Bootloader is getting closed, confirm the Unlock on device - automatic factory reset is executed, wait until 99% and 100% restarts the phone → NOW PRESS VOL+ to boot the phone into TWRP instead of system!
10) Allow system modification in TWRP and hit "enter" Button for Terminal - HWOTA7 copies now the firmware to the directory: /data/update/HWOTA - restart phone automatically and flashes the Firmware with EVA_RECOVERY_NoCheck.
→ After the P9 has started into the system - you may see a black screen with an input field and a keyboard - if yes, go to 11) - if no, go to 13)
11) Close HWOTA7 Terminal and press Power Button on P9 to restart your Phone, restart phone, in the moment of restart press VOL- Button to boot into Fastboot Mode → Bootloader is closed. BTW: Chinese Brands dont have FRP.
12) Open update_eng.bat, click enter, enter the Unlock code, confirm Unlock on phone, phone makes a Factory reset with lowlevel wipe. Then the P9 starts automatically into the system. Now you have already rebranded to EVA-AL10c00b399sp17a / Nougat. :good:
13) Accept the terms and conditions (Huawei + Google Services) and skip the rest, what can be skipped. Do not be nervous, the P9 has no IMEI at the moment and no mobile network. This is normal. In Settings/Advanced settings menu disable: "Trust Space" and "HiSuite HDB". In Settings/About phone/Build Number/7x click - enable Developer options - go into menu/Developer options and enable ADB-Debugging and USB-Debugging (in this order)
14) Click enter in Terminal, select 2. No, I would not and HWOTA7 will be closed. → Change now the Firmware in the update folder to EVA-AL10C00B540 (8.0.0.540) /Android 8 Oreo (remember: two zip files has to be renamed!)
15) Start again update_eng.bat. Reboot phone into Fastbood Mode. Hit "enter" for Terminal - TWRP will be flashed automatically - reboot with VOL+ and Power Button into TWRP - allow system modification - hit "enter" in HWOTA7 Terminal
16) Use Upgrade options: 2.Using the script - 1.Change firmware (Same brand update /but Oreo)
17) Click enter in Terminal, Firmware will be copied to: /data/update/HWOTA - "System update should start automatically" → if you receive any error like: "connect failed, no devices/emulators found" - go to 18) - if everything is okay go to 19)
18) Close HWOTA7 Terminal and use menu of TWRP to reboot into Bootloader, start again update_eng.bat - TWRP will be flashed again - boot into TWRP with VOL+ and Power Button - allow system modification - hit "enter" in HWOTA7 Terminal - Firmware will be copied to: /data/update/HWOTA - Phone will make reboot and flash the Firmware for Oreo automatically.
19) You have now successfully updated to Android 8. :good: Phone will reboot into EVA-AL10C00B540 (8.0.0.540) Oreo. → You should accept the terms and conditions (Huawei + Google Services) - otherwise Playstore will not work later! Do not enable WLAN and do not set up your phone (Fingerprint etc)right now! - skip, what can be skipped. → You will have "unknown IMEI" and no mobile network at the moment, that is normal.
Open Settings/System and enable again Developer Options/ADB+USB Debugging. In Settings /Security+Privacy you can find "Trust Space" - disable it - and in same menu you find in "More" "Allow HiSuite to use HDB" - disable it!
→ Now we must do some steps that the phone is able to recognize the IMEI and mobile network as well as NFC on L09 and Dual-SIM on L19/L29 and disable Chinese apps, which we do not need in Europe.
20) Downloads:
TWRP for Oreo P9-EVA-8.0.0-TWRP-v4.img: https://www.androidfilehost.com/?fid=1322778262903998750 - we need this to flash the important changes to system without the need of Root
This TWRP is made by @Pretoriano80 for Honor 9 Lite. I made just small changes for hi3650. You can backup and restore everything, except data! There is no access to /data - means: you can not do Factoryreset from TWRP - and decryption of the internal storage for the TWRP session is not working. → For Backkup and restore data you can use HiSuite or Huawei Backup or Titanium Backup. MTP ist working, when you just disable/enable it once.
Network-Patch zip files (new released 03.03.2019):
→ select the zip according to your original model (which you had before rebranding to EVA-AL10)
→ Copy the zip file to the external SD or to the USB Stick, which you connect to P9 after with OTG cable. Since TWRP can currently not access /data (internal storage) - you can not flash this Patches without → external SD or USB OTG
→ The Network Patch zip files can be used for b540. If you are already on Oreo and have an older Firmware (b528, b535), you must update first to b540.
→ Update from older Oreo Firmware to b540: https://forum.xda-developers.com/showpost.php?p=77161303&postcount=5
EVA-L09_b540-SingleSIM_NetworkPatch-v2.6.zip: https://www.androidfilehost.com/?fid=1395089523397910447
MD5: 8662c7129945f5bc2236e8f87031b793
EVA-L19_b540-DualSIM_NetworkPatch-v2.6.zip: https://www.androidfilehost.com/?fid=1395089523397910449
MD5: 46dc8f974cb345027746d88ac141f6e1
EVA-L29_b540-DualSIM_NetworkPatch-v2.6.zip: https://www.androidfilehost.com/?fid=1395089523397910453
MD5: afac13a9e6445b6d5a2beb8289abda6b
VIE-EVA-FaceUnlock-Oreo-v1.5.zip: https://www.androidfilehost.com/?fid=1395089523397898660
MD5: 973d006c55fa812d722b653a57c844c0
Installing NetworkPatch-v2.6 and optional VIE-EVA-FaceUnlock-Oreo-v1.5
→ You just need one Network patch. This must match your original model - which you had before rebranding!
21) Copy the downloaded TWRP into the folder C:\HWOTA7\tools\Windows - connect P9 with USB to PC - right click on cmd-here-exe (run as administrator) - type: adb reboot bootloader (enter, to restart your P9 Plus into Fastboot mode) Flash now TWRP in Fastboot Mode:
Code:
fastboot flash recovery_ramdisk P9-EVA-8.0.0-TWRP-v4.img
22) Disconnect the USB cable from P9 and press (with the left hand) VOL+ and Power Button (with the right hand) and keep pressing until the Phone is rebooted into TWRP.
23) On the first Screen click on "Cancle" (because decryption is not working) but swipe to confirm to "Allow System modification"
→ Go to: Install /select storage: Micro SD (or USB-OTG) and choose your downloaded NetworkPatch.zip file. If you like, you can use the function down left "Add zip file" and choose the VIE-EVA-FaceUnlock-Oreo-v1.5.zip
24) Swipe to confirm flashing the Network Patch (and the optional added VIE-EVA-FaceUnlock-Oreo-v1.5.zip file)
25) If you had used an older NetworkPatch before flashing the newest one - go back to the main menu of TWRP, go to wipe → advanced wipe and choose only "cache" (not Dalvik) → but if you are new on Oreo b540 you can skip this step
26) Reboot to the system
27) Finally, Playstore and any keyboard is needed. Download the apks from here (February 2019): https://www.androidfilehost.com/?w=files&flid=290476
28) Install it, enable keyboard, open Playstore and log into your account. After that reboot your phone. Now you can update apps, download and install your favorite apps and additional all other Google apps from Playstore → do not flash GApps instead!
29) After you have installed all required files, you have currently TWRP installed → this is good for Users, which like to have Root and disabled OTA.
Root Guide can be found here: https://forum.xda-developers.com/showpost.php?p=77161300&postcount=4
→ But if you like to enable OTA instead:
A) Download and flash: Enable-Hwota.zip from here: https://www.androidfilehost.com/?w=files&flid=290481
B) Go back to the main menu of TWRP and Reboot to Bootlader
C) flash in Fastboot mode the Stock EMUI Recovery
Code:
fastboot flash recovery_ramdisk EVA-b540-EMUI-RECOVERY_RAMDIS.img
Download from here: https://www.androidfilehost.com/?fid=1395089523397898706
Reboot Phone and enjoy
As Mirror for the Downloads you can use also the Mega folder by @zgfg
https://mega.nz/#F!JwkVyRya!Rb7OUE0z3PEpXBRxGOM-vQ
@zgfg is the official authorized supporter for this thread. He give you a lot of help and support and he do a lot of tests, before we release new Patches.
Many Thanks!
If you search for older files (Network Patches etc) for older Firmwares, you can also search my folder on Android Filehost:
https://www.androidfilehost.com/?w=files&flid=124276
Note: It is not possible to lock the Bootloader on to EVA-AL10 rebranded phone with Network Patch and FaceUnlock! This would revert all the required changes and in the worst case push your phone into a bricked state.
→ But what you can do with installed EMUI Recovery (instead of TWRP): You can do from settings /system /reset a Factoryreset with wipe of the internal storage (to clean up previous instalations) → in this case the Factoryreset lowlevel does not revert the changes! The only difference is: When you get Push notifications, the Badges over the app symbol on Homescreen will change from numbers to points (which is standard on Oreo) → which is currently not change able in settings without Factoryreset.
Known issues:
VoLTE and WiFi-Calling is is visible in the menu - but does not work for now!
If you want synchronisation between Google calendar and EMUI calendar - you need to install Google calendar from Playstore.
If you like to use Google Assistant and have problems to teach this app with your voice "Hello Google" - just open settings /apps & notifications /standard (default) apps - and choose Google Assistant as default app (then it will work).
→ Please read also the next few posts (Root, current firmware with eRecovery, Update Firmware on Oreo with HWOTA8, going back to EVA-AL10 Nougat and rebrand back to original model)
Restore current Firmware - or going back from Oreo to Nougat and rebrand back
2022-06-21: This Post is under construction - please wait until the update is ready
Old text:
Restore current firmware (if you are on EMUI or OpenKirin ROM) → check out following Post:
https://forum.xda-developers.com/showpost.php?p=77905152&postcount=833
How to go back from Oreo to Nougat → and rebrand back
A) Method by using HiSuite (on PC):
1) If you have Magisk Root - uninstall Magisk with Magisk Manager (Button Uninstall)
2) Make sure, you have EMUI-Stock-Recovery installed (it does not work with TWRP)
3) Download Huawei HiSuite: https://consumer.huawei.com/minisite/HiSuite_en/
4) Update HiSuite on PC to (minimum) version: 8.0.1.302_OVE and connect your Phone with PC and HiSuite.
5) Let HiSuite install HiSuite App on your Phone - accept the Permission requests. Once that is done:
6) Click on "Systemupdate" - a new window pop up and show you your current version, click on the Link "Change version" - then you can downgrade to the latest Android 7 AL10 firmware
7) → then it is possible to use HWOTA7 again for rebranding back...
B) Method by using HuRUpdater → requires external SD or USB OTG:
If you want to go back from unofficial Oreo to Nougat and rebrand back to your original brand, you can do it with simply steps.
→ Note: HuRUpdater can not only be used for Downgrade, it can also be used for Update Firmware - It depends only on which firmware you pack together with HuRUpdater in the folder (which you have created on external SD or USB OTG)
→ The Firmware must be FullOTA-MF (same renaming than with HWOTA7 Tool)
1) Bootloader must be open
2) Flash TWRP for Oreo Download TWRP by Pretoriano80: https://www.androidfilehost.com/?fid=1322778262903998750
3) Backup your data with Huawei Backup (because TWRP can not acces data for now, because it has no encryption/decryption support)
4) Make a folder on your external SD and name it: Downgrade or Update (or however)
5) Copy the 3 Firmware zip files into the folder and make sure, two zip files are renamed (same as you did for HWOTA7)
6) Download HuRUpdater_0.4.zip from here:http://www.mediafire.com/file/r14sor2g4cbugzw/HuRUpdater_0.4.zip
7) Copy HuRUpdater into the same folder together with the firmware zip files. If you have the Nougat AL10 zip files inside, you will downgrade.
The folder contains now 4 files:
HuRUpdater_04.zip
update.zip
update_all_hw.zip
update_data_public.zip
8) Boot into TWRP. It will ask you for password. Just cancle. In TWRP open "Wipe" - but dont wipe anything - you must use the Button on the right Format Data. Confirm with typing: yes. Soon data is formatted, go back to the main menu and open Reboot - but do not reboot System - you must Reboot Recovery
→ Note: Format data is only important until we have TWRP with working data decryption
9) After TWRP is rebooted go "Install".
10) Navigate to the folder which containes the files and flash ONLY HuRUpdater_04.zip In some seconds the Akku vibrates - in this moment press for one second the VOL- Button. Now HuRUpdater will flash automatically the FullOTA-MF Firmware.
11) Once it is done, use on the left: Wipe Cache Button. After go back to the main menu and Reboot RECOVERY.
12) Your device has rebooted now into EMUI Stock Recovery. From there perform Wipe Cache Partition and Factory reset and boot to system.
Once you are back to Nougat - you can use again the HWOTA7 Tool to rebrand back to your original brand. Just use Change location (for your original cust) and make sure, the Firmware is in the update folder..
Credits:
@zxz0O0 Many thanks for HuRUpdater
HuRUpdater Thread: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
2022-06-21: This Post is under construction - please wait until the update is ready
Enable Root Access
Instructions for root access
Root is not required, but if you still wish, here is the guide:
Due to the fact TWRP cannot access the encrypted data partition, you cannot JUST flash Magisk!!
→ A) But you can flash Magisk with TWRP using a workaround
→ B) Alternatively it is possible to flash a Magisk patched ramdisk.img in Fastboot mode
A) Workaround for flashing Magisk with TWRP – for Advanced Users:
1) Download the favorite Magisk version from here (all releases): https://github.com/topjohnwu/Magisk/releases
The actual and newest stable version you can get always from here too: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
2) Copy the flashable Magisk-vXX.zip and Magisk Manager apk to external SD – and make sure, you have Developer options with 1) ADB Debugging and 2) USB Debugging (in this order) enabled.
3) Reboot device to TWRP, cancle Password, allow system-modification (swipe to confirm)
4) On the main menu go first to "Mount" - down left click on "Select storage" and choose "Micro SD"
5) Go back to main menu and open "Advanced" and open "Terminal"
NOTE:
If you have got a OTA-Firmware Update with “Patch02” or “Patch01” before flashing the Network Patch (after Network Patch, you will not see this in "About phone"!) or if you don’t remember, then use following both Lines in Terminal, but if you are sure, you have only Firmware without Patch 01 or Patch02, then use just "Keep Force encrypt" Line. Write the Lines in TWRP/Terminal exactly.
6) Write following code with Terminal:
Code:
echo KEEPVERITY=true>>/cache/.magisk
echo KEEPFORCEENCRYPT=true>>/cache/.magisk
→ Confirm each Line with blue/white checkmark on keyboard, before writing the next Line and confirm also the second Line (if you use two)
7) Go back to the main menu to "Install" and flash Magisk - after that reboot phone without wipe of Dalvik/Cache!
8) Search for Magisk Manager on Homescreen - if it is not installed, just install the Magisk Manager apk
9) Open Magisk Manager → everything should be okay
10) Open normal settings /apps & notifications /Magisk Manager /permissions and make sure Magisk Manager has permission for storage.
11) From Magisk Manager menu above left, section “Downloads” – download and install directly “Busybox for Android NDK” by osmosis – save log and reboot phone.
→ If Magisk get a major update, uninstall first Magisk from Magisk Manager and use “uninstall” button. “Uninstall complete” The phone restarts automatically. After that you can flash the new Magisk and reflash the modules.
B) Flashing Magisk with patched ramdisk.img in Fastboot mode:
If you don’t want flash Magisk with the TWRP workaround – you can use a Magisk patched ramdisk.img instead.
1) You can patch ramdiks.img from update.app by yourself, with following method:
Extract the update.zip of the current installed Firmware, because we need the UPDATE.APP.
Download Huawei Extractor v0.9.9.5 from here: https://forum.xda-developers.com/showthread.php?t=2433454
In the settings of the Huawei Extractor disable "verify header checksum" - then put with drag and drop the UDPATE.APP into Huawei Extractor and extract by right click the RAMDISK.img (on earlier Android Versions it would be: BOOT.img)
2) Copy the original RAMDISK.img to your phone to the internal storage in the folder: Download
3) Install the latest Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
4) Open Magisk Manager, Magisk Manager ask you "Install Magisk-vx.zip?" - first click on: no thanks
5) Since internal storage is encrypted by default, you must first enable the checkbox: "Preserve force encryption"
5) If you have installed a OTA-Firmware Update with Patch01 or Patch02 – then enable additional the checkbox "Preserve AVB 2.0/dm-verity" in Magisk Manager.
6) Then click on "Install" - "You want to install Magisk-v1x.zip now?" - Install - Patch Boot Image File...
7) Navigate to Download folder, and choose RAMDISK.img
8) Magisk will now patch the RAMDISK.img and and once that's done, Magisk will save the patched ramdisk.img with the new name: patched_boot.img in the "Download" folder on internal storage.
→ Do not be confused - this is just named “patched_boot.img, but it is in fact the patched ramdisk.img !
9) Go to Settings /Apps & notifications/Apps and uninstall Magisk Manager
10) Now you must flash the “patched_boot.img” – Reboot your phone into Fastboot mode
Android 8:
Code:
fastboot flash ramdisk patched_boot.img
10) Reboot phone, install again newest Magisk Manager, open it and you will be asked: "Requires Additional setup - to you want to proceed now" Yes. → This step is required for to work properly.
2) Instead of doing yourself – you can use the already patched ramdisk.img:.
→ important: the right patched ramdisk img must be used for the right Firmware version (example: b540)
Magisk patched ramdisk.img you can download always from @zgfg MEGA folder:
https://mega.nz/#F!JwkVyRya!Rb7OUE0z3PEpXBRxGOM-vQ
And you can download also from my folder: https://www.androidfilehost.com/?w=files&flid=290471
Current version:
→ depending if you have b540 with OTA-Patch02 or b540 without Patch02 (you must know, because after flashing Network Patch you cannot see it in Settings /System /About phone !)
Magisk 18.1 patched ramdisk.img for b540 without OTA-Patch02:
https://www.androidfilehost.com/?fid=1395089523397898715
Magisk 18.1 patched ramdisk.img for b540 Firmware with OTA-Patch02:
https://www.androidfilehost.com/?fid=1395089523397898717
→ if you don’t remember, if you have OTA-Patch02 installed, then use the one for Patch02
Installing patched ramdisk.img:
Reboot your Phone into Fastboot mode and flash the patched ramdisk.img with following command → depending on which version you install:
Code:
fastboot flash ramdisk EVA-b540_Magisk_v18.1_Encrypt-Ramdisk.img
Code:
fastboot flash ramdisk EVA-b540_Patch02-Magisk_v18.1_Encrypt_AVB-Ramdisk.img
Google Playstore certification
You can try it with method by @zgfg:
https://forum.xda-developers.com/showpost.php?p=79070144&postcount=1574
→ If it does not work you can try advanced method:
1) Set your phone into Flight Mode (no network should be connected)
2) Open Settings/Apps & notification/Apps and down right in the dot menu click on: show systemprocessing
3) Go step by step into following Apps (if there): Google - Google Play Store - Google Play Services - Google-Service-Framework - each has the entry: storage - delete ONLY cache /not data
4) Open with Mixplorer the directory:
/data/data/com.android.vending/shared_prefs - search for the xml file: finsky.xml
5) Open finsky.xml with TEXT Mixplorer Text Editor
6) Search inside finsky.xml for: <boolean name="device-google-certified"value="false" - change it to:
Code:
<boolean name="device-google-certified"value="true"
- means, you change only "false" to: "true"
7) click on the save symbol to save the changes! - close Mixplorer and everything in the Background
8) Disable Flight Mode (so Phone search for network connections)
9) Reboot your Phone
10) Open Playstore menu /settings/ =certified
If you have problems with current version of Magisk and using Gpay (Google Pay), try following workaround:
https://forum.xda-developers.com/showpost.php?p=79028818&postcount=5
How to uninstall Magisk:
A) Before you doing an OTA Update, it is required to uninstall Magisk → and also make sure, to have Stock EMUI Recovery installed (instead of TWRP).
B) In case for a “major” Magisk update it is also sometimes necessary to uninstall Magisk before installing the new version, because with directly update the phone could get a Bootloop. (But normally Magisk updates can be done directly and without uninstalling Magisk before).
C) If your device can not boot into system due to an incompatible Magisk Module.
a + b) If you can boot normally to system, you can uninstall Magisk from Magisk Manager - just use the "Uninstall" button “Uninstall complete”. Magisk will be uninstalled and Magisk files deleted from /data directory. Thereafter, the P9 is restarted automatically.
c) If your device can not boot into system due to an incompatible Magisk Module, you can flash the original EMUI Stock ramdisk.img (which is not patched with Magisk)
→ ramdisk.img must match the Firmware version of your device
For the current Firmware EVA-AL10 b540 you can download the original ramdisk.img here:
EVA-b540-RAMDISK.img:
https://www.androidfilehost.com/?fid=1395089523397898709
You can flash it in Fastboot Mode:
Code:
fastboot flash ramdisk EVA-b540-RAMDISK.img
Alternatively, you can flash the image with TWRP.
In this case you flash the img with TWRP by using: "flash img" - but important is, you must flash it to: ramdisk (and NOT to recovery_ramdisk !!)
Soon you have installed the EMUI ramdisk.img, the device can boot to system again and Magisk is disabled.
Enjoy
Credits:
@osm0sis Busybox for Android NDK
@Didgeridoohan MagiskHidePropsConfig module
@topjohnwu Magisk root
2022-06-21: This Post is under construction - please wait until the update is ready
Manual Firmware-Update on OREO
Manual firmware update – if you are already on Oreo
You can manual update the Firmware - if you are already on Oreo → but you can not update with this method from Android 7 to Oreo!!
→ The manual update is based on a special EMUI Recovery for EMUI 8 which does not check if you have modified your system.
We will post the actual Links here and/or on the actual last pages.
→ you need an external memory card in the device for this method - it does not work with USB OTG
The current firmware is EVA-AL10C00B540 (8.0.0.540):
update.zip: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3115/g1699/v208318/f1/full/update.zip
update_data_full_public.zip: http://update.hicloud.com:8180/TDS/...18/f1/full/public/update_data_full_public.zip
update_full_EVA-AL10_all_cn.zip: http://update.hicloud.com:8180/TDS/...A-AL10_all_cn/update_full_EVA-AL10_all_cn.zip
1) Renames:
Enable in Windows Explorer “Show file extension” (to see the extension: zip, doc, docx etc. at the and of the filename) because if one file is named update.zip.zip → it will not work!
update_data_full_public.zip → rename to: update_data_public.zip
update_full_EVA-AL10_all_cn.zip → rename to: update_all_hw.zip
→ do not rename update.zip
2) Required: installed TWRP →see Post #2 how to flash
Download: https://www.androidfilehost.com/?fid=1322778262903998750
3) FirmwareUpdate_onOreo_from-externalSD.zip
Download this zip file and extract (unzip) it:
https://www.androidfilehost.com/?fid=1395089523397898768
The zip file contains the folder HWOTA and inside are two files. Do not rename that files.
4) Create a folder on your external SD with the Name HWOTA in the main directory (don’t use another name!) - or copy the HWOTA folder from unzipped Firmware-Update.zip instead to your external SD
5) You have now the folder HWOTA in the main directory of your external SD (without Subfolders between)
6) The folder HWOTA must contain:
eva_vie_recovery_nocheck.img
ExtSD-FirmwareUpdateScript.zip
update.zip
update_all_hw.zip
update_data_public.zip
7) Reboot phone to TWRP, cancle Password, allow system modification, go to Install, select storage: Micro SD - and flash ONLY the zip file with the name: ExtSD-FirmwareUpdateScript.zip
8) The phone restarts and takes a while to flash automatically the EMUI-NoCheck-Recovery and takes also a while until the Firmware will be flashed automatically as well as Phone reboots after. Just wait, until it boots up.
→ if you have Root, there is no need to Unroot before and you will lose no installed apps, except perhaps Playstore and Keyboard (but if it was updated, you will not lose Playstore and not Keyboard)
→ you have to flash again the Network Patch (for your device) from #2 with TWRP - and for the case you lost Playstore and Keyboard, just install your favorite apk and reboot phone.
Enjoy :good:
this tool can be used for eva-l19c636 asian to update to oreo right? same procedure?
iammitee said:
this tool can be used for eva-l19c636 asian to update to oreo right? same procedure?
Click to expand...
Click to collapse
Yes!
Do I need to be on the latest version of EMUI Nougat (I think it is B399SP01 or something)? It looks promising so far, I hope I can successfully be on Oreo so I can flash Treble ROMS. Thank you so much!
Gilgameshhhhhh said:
Do I need to be on the latest version of EMUI Nougat (I think it is B399SP01 or something)? It looks promising so far, I hope I can successfully be on Oreo so I can flash Treble ROMS. Thank you so much!
Click to expand...
Click to collapse
All information about these questions will be explained in Post # 2.
For new users / P9 terminals - Huawei is still providing Bootloader codes, or they have to be purchased from eg DCUnlocker?
There was also a rumour about alternative methods, bypassing Bootloader codes?
When it settles, are you also planning for MagicRainbow v5 based on Oreo?
zgfg said:
For new users / P9 terminals - Huawei is still providing Bootloader codes, or they have to be purchased from eg DCUnlocker?
There was also a rumour about alternative methods, bypassing Bootloader codes?
When it settles, are you also planning for MagicRainbow v5 based on Oreo?
Click to expand...
Click to collapse
The Huawei Unlock Site is down (since today): https://emui.huawei.com/en/plugin/unlock/detail
Reading the Unlock codes must be purchased for using DC Unlocker Software. https://www.dc-unlocker.com/read-unlock-codes-for-huawei-phones
At the moment there is no technique to bypass the bootloader unlock code.
Yes I am planning MagicRainbow v5 based on Oreo
Nice, waiting all information about rebrand to Chinese for Oreo Update
Necrodaemon said:
Nice, waiting all information about rebrand to Chinese for Oreo Update
Click to expand...
Click to collapse
I do it in the evening and tonight, so it should be ready tomorrow.
When we change from the European version to the Chinese version, would we lose the nfc?
Enviado desde mi EVA-L09 mediante Tapatalk
L09/L19 rebranded to Chinese Oreo - G2/G3/G4 baseband will work?
P9 eva-dl00
Tecalote said:
How to rebrand Huawei P9-EVA European Brand to Chinese Brand and update to Oreo
Under construction
Click to expand...
Click to collapse
Excuse me my friend... P9 EVA-DL00 also updated to Oreo oficially?
Thanks in advance!!
Regards!!
Hi!
Could this script be used to update firmware without loosing root and bootloader?
Thank you.
ironet said:
When we change from the European version to the Chinese version, would we lose the nfc?
Enviado desde mi EVA-L09 mediante Tapatalk
Click to expand...
Click to collapse
Yes, you loose NFC and don't win Dual SIM..
Same as if you rebrand from L09 to L19.
All Chinese Version have Dual SIM and no NFC.
zgfg said:
L09/L19 rebranded to Chinese Oreo - G2/G3/G4 baseband will work?
Click to expand...
Click to collapse
This and related questions will be answered in Post #2 (when it's ready)
Carlos6862 said:
Excuse me my friend... P9 EVA-DL00 also updated to Oreo oficially?
Thanks in advance!!
Regards!!
Click to expand...
Click to collapse
The final version for all Chinese versions is rolling out. To you have DL00?
Related
This thread is a continuation of existing threads, which started when Model 701 was not out yet.
Update 2017-04-22
Since we have verified that the "downgrade script" opens the door for multiple Mediapad X2 models we have much easier way:
Do a full backup with Huawei Backup Application ("Datensicherung") and copy all stuff from internal sd to external which you put manually on it.
For push applications like whatsapp do a backup of chat in whatsapp, manually on your google drive.
Unlock bootloader
https://emui.huawei.com/en/plugin/unlock/detail
create account, via selecting Honkong as localisation.
Then login on https://emui.huawei.com/én/plugin/unlock/detail
If it's redirected to a EMUI site, then simply call the link again https://emui.huawei.com/en/plugin/unlock/detail
check the agree box and fill the page with: "Before EMUI 5.0" and put model name in the field "GEM-701L" or "GEM-702L"
Then fill out the rest (you have to optain the productID via entering in Phone as if you will make a call: *#*#1357946*#* )
Then Huwaei will give you the bootloader code directly on this page.
install minimal adb and open cmd window
connect phone and start with VOL down key
type: fastboot devices
if you get no answer you'll have to update the windows driver to "ADB sooner single interface"
if you get answer type
fastboot oem unlock xxxx (wher xxxx is the bootloadercode you got from page above)
Do factory reset from EMUI (not from recovery, it will work, but you'l get problems later)
if you had replaced the original recovery with TWRP you must flash it back:
fastboot flash https://drive.google.com/file/d/0B5TWnuLR7ugZRmdVdEhzdjM3Tms/view?usp=drivesdkrecovery.img for B003 or B005 back if you already replaced it.
then download the "downgrade script" . Unpck the rar and put the dload folder to internal SD
Select Update in EMUI settings menu and select "local upate" and then "full update" from internal SD.
Then download the from the very slow huawei server B202 full package (DEMO) and put the dload folder to external SD (or internal)
Start system and select update and "local update" and install it.
Then boot in bootloader/fastboot mode again via VOL - key and flash TWRP for Android 6.0 via adb: fastboot flash recovery TWRP-ENG-6.0-BLACK-BLUE.img
If you install it via fastboot flash recovery2 TWRP-ENG-6.0-BLACK-BLUE.img , you will not overwrite the original recovery, which is need for factory reset or dload) If recovery is on recovery2 then you must keep a USB connection to PC to be able to start the TWRP. Otherwise remove USB cable before you boot into TWRP.
Start TWRP via holding VOL + Key via starting the phone and allow modifications and then press Install button and select external SD and then the kangVIP 212 V2
Or now newest version KangVIP V3 from thread https://forum.xda-developers.com/showthread.php?t=3215851
Wipe cache and dalvic and reboot to system.
Wait several minutes until first boot is finished. If you already have apps installed (dirty flash over existing KANGVIP) this may take up to 40 minutes)
If you need to do a factory reset from EMUI you will need the original Huawei recovery B202 wich you can install via fastboot
Restore your apps from Huawei Backup, besides Whatsapp.
Install whatsapp and then the question comes up to restore your backup.
THE REST BELOW THIS LINE HERE IS ONLY FOR HISTORICAL INTEREST or for people who have already updated to 5.11
################################################################################
Update 2016- 04 -05
See short way with B112 on http://forum.xda-developers.com/showpost.php?p=66156287&postcount=215
Hint: This seem not a 100% convesion to 5.1.1 because storage handling did not change.
Advantage: You may goback to B003 with a nandroid.
Unverified: If it can still charge on such a rollback
----------------
Meanwhile we have figured out how to flash a new ROM even on GEM 701 L.
Thanksgiving to all who have participated in this. Especially to ajsmsg78, eennap, ZeuseZ, and Ante666
I you have a 703 Model, you can simply upgrade via OTA and then go to one of the threads ajsmsg78 made and choose which ROM you like.
If you have Model 701 oder Model 702 you can use this thread, if you already have at least firmware B003 on your device.
Current situation in Jan 2016:
If you have a firmware B001, or B002, then zip your folder "/cust" and send it to ajsmsg78.
Then he would integrate it into the "universal cust". Please wait until he did this.
The "Universal Cust B112" hast the filename variant "UNIVERSAL-CUST-B112.zip"
Later if you install the SIMPLY_GOOGLE ROM Version a variation of this "cust" will be automatically installed then it is called "Simply Google B111 Cust".
If you install a B111KangVip or the NearStockB111 the "universal cust" also is integrated
Don't worry about the names, it is used to display the correct Roms name.
If you have 701 or 702 model, you may have heard, that Huawei published firmware only for the 703 model.
So we have to convert our device into a 703 model, by keeping it's hardware based additional LTE bands.
If you have converted by doing the following steps to B015,
you will be able to upgrade Android 5.0 to Android 5.1.1 on the follwing steps for D106
---------------------------
Update 2016-28-02
It seems possible directly install the B112. So much easier now. Just flash 4 B015 files, install the "universal cust B112" and then do "dload" procedure for B112.
Then you are on stock B112 can can flash the stabile "Near Stock B111". I have edited the new way in the post below
------------------------------------------------------------------------------
After that you will be able to install updated directly from Huawei via the OTA (Over the air) method, if you have a stabile WLAN connection.
This does not give you a direct jump from B106 to B111 (or B112) , so don't try this on the "dload" method.
My experience was that some components are not updated if you skip a version. Evidence see here
Alternatively you will also be able to do manual "dload" processes.
This both methods lead you up to version B112
After this you can install one on ajsmsg78 ROMS.
They differ in the composition of removing and adding components.
So look which version is the best for you and check, if it is up to date or maybe discontinued.
This are the steps to flash from 701L (B003) to custom firmware
Be aware: Don't try to return to B015 or B003 (Android 5.0), after you have once installed Andoid 5.1.
You will loose the ability to charge the phone in this case.
But it is possible temporary go back. For this you will find the guide in post 2 of this thread
If you have a lower version like B001 or B002 you MUST save your folder /cust to a zip fle and send it to ajsmsg78 and ask for advice!
Don't start flashing in this case!
If you already have a higher version than B003 you can skip the steps which lead to your version.
If you have B006, it seems that you can not upgrade. You must first downgrade to B003. Please report if you find a way.
Maybe you can do the dload for B112. Try this and report!
In case if you want to return to B003 there is a possibilty - > this is documented at post 2
----- To those who have already installed: Please check if there is missing something or wrong and leave a comment. ---
Steps are numbered to be compatible to then numbering of eennaps guide. (Some steps differ, because of newer cognitions.
- First of all: Be sure you have enabled USB debugging on your device. Otherwise you can not go into "manufacture mode" for DC - unlocker
To enable this you have to select "about phone" and tap 7 times on the "build number". After that you will find "developer options" in main menu.
- install ADB or got to ADB XDA Forum
- if you are on Win 10, then install Hisuite (for DC - unlocker manufactur mode drivers)
- Unlock Bootloader via DC-Unlockerr (see [https://drive.google.com/file/d/0By1mhgPLc1LqUzV0QVVRWmpBWlE/view?usp=sharing] reduced eennaps document just for the unlock chapture [/URL] for these steps )
If you get you code from Huawei, just open cmd window on PC and type
fastboot oem xxx
and replace xxx with the bootloader code you got from Huawei or DC-Unlocker software
If you have an unlocked phone you can start with these steps
Step 1
1.1 a - Download 2 TWRP versions
To download the files from Google drive klick on the little download icon. NOT ON THE FOLDER
5.0: https://drive.google.com/file/d/0By1mhgPLc1LqSlRTRVhmbjhTcjg/view?usp=sharing
5.1.1 https://drive.google.com/file/d/0B5I_q70mNuR4QkFzM2xOWVlvRkk/view
and put both files into your ADB folder on Windows PC.
1.1 b
- Download 4 Files from Firmware B015 which I have extracted via Huawei Update extactor
BOOT.img, https://drive.google.com/file/d/0By1mhgPLc1LqeGNLc0VKRVRNR2s/view?usp=sharing
RECOVERY.img, https://drive.google.com/file/d/0By1mhgPLc1LqTVd0c3FYVWJrVlU/view?usp=sharing
SYSTEM.img https://drive.google.com/file/d/0By1mhgPLc1LqZWY2SHJuaXB4YUk/view?usp=sharing
USERDATA.img. https://drive.google.com/file/d/0By1mhgPLc1LqeTJITEhGRk9ZNGs/view?usp=sharing
You can check the MD5.
1.1 c Copy these 4files into your ADB Folder on PC
1.1 d : insert a at least 32 GByte Class 10 SD Card. (better 64 GByte)
B: Copy all your content from the internal drive to the external SD card in a folder (for example name it "int_SD_Backup")
1.1 e: download ajsmsg78's "universal cust" and put it to the external SDCard.
1.1 d: Download at least the first 2 files (if you later want to go via OTA ) or all 4 Firmware versions, if you prefer the offline "dload" method for all files.
edit: It seems it is sufficient only download the B112 stockhttps://www.androidfilehost.com/?fid=24385226645962831
optional: B015
and also optional: B106,
optional: B109, and B111 if you prefer the dload method for these versions, too. For this download them from here
Step 1g-unzip these files to your PC and copy later step by step the unzipped folder "dload" of version B112 to your ext SD-Card (root directory not in subfolder)
I used a external USB SD Card Reader, this is faster than to copy via USB. But both works.
1.1 h: I recommend fist do download a near stock Variant NearStockB111 [/B] an put it on your external SD Card.
But you can also download B111KANGVIP or the much more dbloated "Google" ROM SimplyGoogle and put the zip file on the external SD-Card. Be aware: these 2 last variants do not include the Huawai Backup appliation to restore your saved configuraton. And the SimplyGoolge Variant is not stabile at this point of time.
After 4 weeks testing the Kangvip V2 and Simply Google (made in Feb 2016) I return today to "Near Stock", because KangVipV2 has white icons on white background on navigation bar when you hold in landscape mode. SimplyGoogle has not the full features of boot menu and a
advanced settings and you can not install XPOSED on it. So I recommend the "Near Stock". I saw no added features between 111 and 112.
I believe it is just to skip B109. This makes things easier. I update the guide for this today (2016-02-24)
1.1 i On Phone: Start the Huawei Backup App (Icon "Backup" or german: "Datensicherung")
and do 2 Backups on SD Card (one for account and settings and one for your apps)
1.1 j: Restart Phone in BootloaderMode (Vol - and Power Key while USB Cable is connected)
1.2.a On Windows PC: Do a Shift-Key-right-click on the ADB folder and select "open command here" .
Then type in the cmd window the following command to Flash X2_TWRP_CN_5.0 (not yet version 5.1 because it does not start on a 5.0 System)
fastboot flash recovery TWRP-ENG-5.0.img
(this takes 2-3 seconds)
1.2.b Remove USB cable and press Power Key until screen is dark
then press Vol + and PowerKey and hold until something comes on screen
then release PowerKey and hold Vol+ Key until TWRP starts.
1.2c Make a "NANDROID" of your current ROM
press "Backup" Button.
press the last line "storage:" and select external_sd
swype for backup and wait (about 4 -10 minutes until message [Backup Completed ....])
- press home key (bottom left)
1.2d WIPE CACHE and DALVIC
from main menu select "Wipe" and then "Advanced Wipe"
check "Dalvic Cache" and "Cache"
swipe to wipe
press home key (bottom left)
1.2e press Install and select UNIVERSAL-CUST-B112 (this is the universal cust) and swpe to install (maybe change "storage" to find it)
Step 2a) boot into fastboot (Vol - and power key)
- on windows in command window go to the ADB folder and type the following commands.
I highly recommend to copy the black lines from here an paste in the adb window to prevent typos.
Step 2b
If you come from B003 you can directly flash thes 4 files from the B015 version
fastboot flash boot BOOT.img
fastboot flash system SYSTEM.img
flashing system takes some minutes and does several actions. Wait until all are finished
fastboot flash userdata USERDATA.img
fastboot flash recovery RECOVERY.img
fastboot reboot
New: --> Try to skip step 3 and directly go to step 4a to "dload" the B112 stock
3a reboot system and do minimal setup and select "Settings" and scroll down for the "Backup and reset" menu.
3b select "Factory data reset" and check "format internal SD" (Remember : you had copied everything to SD Card and made a backup with the Huawai Backup Application. So you can do this risk free)
EDIT: (see post 3 and 4 normal recovery is necessary to do the factory reset)
3c after system reboots, shut down by pressing powerkey to be able to install the "universal cust"
- boot into fastboot mode and flash vom ADB window:
fastboot flash recovery TWRP-ENG-5.0.img
then and boot into TWRP and
3d press "Install" ,select KANGVIP-B111-CUST-MOD.zip and swype to flash. (you have to disable the MD5 verification checkbox.)
3f - boot into fastboot mode and flash the B015 recovery.img again which you had uploaded on step 1.1.b , because system needs it for the dload process in step 4.
fastboot flash recovery RECOVERY.img
Update 2016-28-02
4. a then reboot the machine and select from "options" -> "Update" and press menu icon for "manual firmware update" and select update from ext SD Card. This flashes all components of GEM-703L official stock ROM B112 via the dload folder.
--> Now go to Step 6
4. b If you come from B006 and and you run into error, you could try to dload the B106 update.app on this step. If this fails you have to install the B003 first and then flash the B015 and go on.
If you come form B006 and decide to stop the whole process you can restore your backup and then install B006 recovery
If you come from B006 the latest tests show that you first have to install the B003 and then start from the beginning of this thread
If you do the "dload" for B106 then it might might fail at 98%, because you have not installed a full B015. But don't worry, you can go on in the next steps without any errors. We have tested, if this can be prevented via dload B015 first. Some people reported it worked, but I seems not to be neccessary, so I removed this point in the guide
THIS is the point where you change from Android 5.0 to Android 5.1
5 g Reboot Phone, do a minimal configuration and select "Settings" and scroll down for the "Backup and reset" menu.
5 h select "Factory data reset" and check "format internal SD" This is important because now you are on Android 5.1.1 and the internal SC Card handling has changed.
5 i wait until reset is finished and the system starts again: Do again minimal configuration
5 j Then go to the firmware update menu and check if there is a OTA update available
5 k Select firmware update B106-> B112 (this comes via OTA)
6 If you have installed the B112 reboot the system and do a minimal configuration[/B]
7-9 dropped, because we don't need to install B109 and B111 stock anymore
Don't worry about the the info in "about phone" that internal Memory is only 1 GByte and you were on Android 4.1.1
This is, because the 703 firmware is running on a 701 or 702 model.
This is only a display issue. This will be fixed via the "universal cust", which will be automatically again installed later.
10 reboot into fastboot to flash the new TWRP
11 fastboot flash recovery TWRP-ENG-5.1.1.img[/B]
12 reboot into TWRP and make a backup of this clean stock B112, to be able to do a upgrade to Android 6.0 in future.
The next step will install the first custom ROM on your device wich will fix the problem with the wrong display of memory and Andriod Verision
13. Press "Wipe" and do a factory reset within TWRP
14 Press "Install" and install NearStockB111 from your external SD Card.
15. select Press Button "WIPE" and "Avanced" and check boxes to wipe cache and dalvic and Data and reboot into system.
16 go for coffee and after about 5 minutes later you are in B111 KangVip.
Now check in the "about phone info" if, Version = Android 5.1.1 and your Memory is correct.
This version is made from B111. I tested KangViPB112 and found no advantage in it. It was not stabile with KANGVIP V2. It has ab bug on the navigaton bar in landscape mode. On some apps you will have white icons on white background. So I advice to stay on B111 KangVipV1 near Stock. It is stabile and has the most feature. And you can install Xposted via the playstore Xposed installer, too.
17. do a full configuration. Maybe your 5 MHz WLAN will not be displayed. Then turn WLAN off an on or do a reboot to fix that.
18. Go into Advanced Settings in Settings and uncheck Lunar Calendar and Desktop Weather Lunar (if you see chinese letters somewhere)
19 Start Huawai Backup application and select your backupfiles to restore (first the accounts then apps)
If you can't find Huawei Backup look inside app folder of this link on phone and click on HWALLBackup and "install"
20 If you don't like gmail, install "myMail" app from playstore.
20 If you don't see SuperSu, you can alternatively use "Kingroot" and do start konfiguration inside to get the full control which apps will be allowed to have root access
You have alternatives which custom ROM you could flash via TWRP later:
NearStockB111: You have already installed this, if you followed this guide.
I advise to use this version. It is stabile.
It does not contain Supersu, but it uses KingRoot. (You can change to SuperSu)
This means you will be rooted and have control via the Purify app on the root authorization and autostart via this alternative
you will not have the whitescreen bug which has something to do with conflicts between SuperSu and KANGVIP Tools V2.
This version is almost like the stock B111, rooted but without chinese bloat ware: NearStock B111
You will find all Huawei system apps and the Backup.app where you can recover all your saved data
The other 2 versions do not include the Backup app. You can install them later.
KangVipSlim : Version with reduced system apps and "old" KangVipTools V1" very less Google staff go here
21. Goto http://forum.xda-developers.com/mediapad-x2/development/rom-kangvip-5-1-1-b108-t3215851
SimplyGoogle with KangVipTools V2 (And Supersu) and integrated Xposted SimplyGoogle
and read whats new on the release and don't forget to press thankyou button for asjmsg78
Be aware on SimplyGoogle: On the first boot, there may be a window form Superuser (SuperSu), which asks for permisson to "KangVipTools"
You must give permanent access, otherwise you will get a white sceen and you would not be able to use the Rom.
This is currently a known problem and might be solved later.
There are some unsolved problems with "Xposed" on this version.
If you ever want to start the whole process again from B106 then
download the 5.1.1 recovery from B106
--- reserved ----
01-15 installing the recovery is nevertheless necessary to do a factory reset on step 3 b
01-16 reduced the word document to just the steps for DC-unlocker
inserting installing universal cust on start
and wipe dalivic/cache
and skipping flashing normal cust (ajsmsg78 says this will work)
01-17 changing the link for the cust to the "universal cust", because of the includes ROM name. This may be confusing on this process.
01-18 inserting a format of internal SD card. Someone reported it was not correct after the whole process.
inserting wipe also data to prevent the while screen bug on the first start of SIMPLY GOOGLE
replacing SimplyGoogle with the NearCustB111 variant as first Custom Rom, because it includes the Backup.App from Huawei.
01-19 the error free dload on the B015 is confirmed. This is because we inserted to flash the universal cust before and skipped to install the cust.img
added reset and format internal sd directly after first android 5.1.1 installation
If you use the NearStock Rom you have to launch kingroot an do start konfiguration inside.
01-24 Moved the steps for returning back to Android 5 to this post 1, because it is a fact, that the phone will not continue charging, even if you have installed the "dload" of B003.
02-28 Seems that dload B112 stock on a patched B112 (via fasboot flash) gives you the full upgade (B016 and B0109 only were "delta" upgrades)
03-28 TheNearStock B111 link has been lost: I uploaded my copy from Jan18 here
Return to B003
If you have not updated to B105 and you are still on a Android 5.0 system you can install the B003 software again via "dload"
B003: Here you get the original B003 firmware which we could download directly from Huawei. Meanwhile it not available anymore, so we were lucky to save a copy.
It will work to do a manual firmware upgrade ( "dload") this, if you are still on a Android 5.0 version up to B015.
If you are on a Andriod 5.1.1, this may work also. But don't try this for fun.
You will loose the abilty to charge the battery.
This is because the method of charging the phone has changed in Android 5.1.
This specific charging method for Android 5.0 is not included in a Nandroid backup or any update.app (dload) files Huawei published.
So you could go back , but only do this with a full charged phone. Then you would be able to restore the NANDROID you have made as the first step before flashing the update. You will be able to look into some data, which you may forgot to save or for any reason else. But don't wait so long until your battery is empty. To return to Android 5.1.1 simply flash the boot.img, userdata.img and cust.img and system.img then do a "dload" to B105 (Andoid 5.1) Then you will be able to restore a 5.1.1. NANDROID of your last running system.
But in case of emergency and after you have tried everything else.
1 a install TWRP (if possible)
if not possible go to step f
b Wipe -> factory reset then
c boot into fastboot mode:
d to Step 2
f only if the above steps didn't work do this:
boot into fastboot and paste the follwing commands into your ADB windows (on PC) and press Return
fastboot erase userdata
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
2
Install on your PC the Huawei Update extractor
3 Extract the files boot.img , recovery.img, userdata.img, cust.img, system.img, cache.img
4 Flash boot, userdata and cust files: from your PC ADB window:
fastboot flash boot BOOT.img
fastboot flash userdata USERDATA.img
fastboot flash cust CUST.img
fastboot flash cache CACHE.img
then boot into TWRP and do a recovery of your last Andriod 5.0 NANDROID
5 Then you would be able start the system and do minimal configuration
6 then do a factory reset from the system.
7 a after reboot you can flash the rest via initiating update via running system
or via a manual "dload" :
- putting the folder "dload" with the B003 update.app into the root directory of a SD card.
- put the SD card into the phone and press Vol+ and Vol- and Power at the same time.
If something comes visible on screen, then release the power key and hold both knobs until the dload starts.
Maybe you have to connect the phone via USB to the PC, or flash the 5.0 recovery before you try this.
Please report if you came in this situation and tried this.
Please keep in mind: If you have came to this point, you will not be able to charge the battery anymore.
My 'old' GEM 701 converted to 703 got stolen. The only positive aspect of this event is I was able to repeat the conversion process again on a new 701 and verify the guide audioralf built so far.
My findings:
1. I was not able to do step 3.a (factory reset + internal SD format). The system didn't boot with TWRP 5.0 flashed no matter what I tried. Ii was rebooting back to TWRP in a loop. Then I did following:
1.a fastboot stock B15 recovery
1.b reboot,
1.c minimal setup (internal SD 3GB only).
1.d factory reset + internal SD card format. Completed with an error
1.e reboot
1.f minimal setup (internal SD size ok, >20GB)
1.g fastboot TWRP 5
1.h flash universal B111 cust
1.i fastboot stock B15 recovery
1j. dload B15 - no errors, wrong info
1.k fastboot TWRP 5
1.l flash universal B111 cust
1.m fastboot stock B15 recovery
1.n factory reset, no errors
1.o B15 intalled, info correct
2. dload B106 , no errors, wrong info
2.a fastboot TWRP 5.1
2.b flash universal B111 cust (info correct)
2.c fastboot stock B106 recovery
2.d factory reset, no errors
2.e B106 intalled, info correct
3. dload B109 , no errors, wrong info
3.a fastboot TWRP 5.1
3.b flash universal B111 cust (info correct)
3.c fastboot stock B109 recovery
3.d B109 intalled, info correct
4. OTA B111 , no errors, info correct
final note: it is important to flash universal B111 cust after each dload, otherwise the phone info is incorrect and following dloads/factory resets/OTAs will fail
Thank you for replying.
The steps you describe were steps to come out of the returning to TWRP.
I have updated the guide!
Reason:
I see that we have to install the original recovery to be able to do the factory reset from the running system (UI)
So I inserted the installing of recovery. It i circumstandly but it was a restrict advice from ajsmsg78 do run a factory reset from UI
I have inserted the universal cust like you have described everytime until step 5.
I was able do do the dload 106, 109 and 111 without any error and without installing the universal cust on each step.
If the "about info" is wrong it doesn't matter if you are already on B106.
The "universal cust" is integrated in the SimlpyGoogle Version, so everything is fine after you have installed that on the last step
I guess it is necessary to install the universal cust only on the step, where you are installing the B015 to make it a "703 device"
and on updating to B106 when it upgrades vom 5.0 to 5.1.1
So i keep the instructions in this way. I have a fully updated and good running system.
If anyone still gets problems, feel free to report here.
I edited my guide: First I thought it was because of flashing also the userdata.img. But this seems to be not the issue, but the missing recovery for the factory reset.
but I don't know if it is normal that you got this:
1.d factory reset + internal SD card format. Completed with an error
Click to expand...
Click to collapse
So let's hear what ajsmsg78 thinks about this.
audioralf said:
I edited my guide: First I thought it was because of flashing also the userdata.img. But this seems to be not the issue, but the missing recovery for the factory reset.
but I don't know if it is normal that you got this:
So let's hear what ajsmsg78 thinks about this.
Click to expand...
Click to collapse
Yes, it is normal, because phone info is wrong at this time, universal B111 cust were not flashed yet. But internal SD got formatted in the process.
Ok to prevent this error message we should install the universal cust additional before this step?
Some more step ...
I suggest the easiest way is to install the universal cust at the first step when doing the TWRP backup, and then skipping to fastboot the normal cust.
I edited the guide for this variant and inserted the wipe for cache and dalvic.
Ralf via Tapatalk. GEM701L, B111Kangvip Rom
Hi, is the B003 method also appy on my GEM-702l B005 version?
A while back, there's an ota and I've got my gem-702l updated to B005.
My current Android version is 5.0.1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Do a NANDROID this will bring you back.
I don't know if B003 would run on a 702. If if was delivered with b003 I would try it, if other solutions had failed. If you are still on 5.0 you will be able to restore the nandroid If it fails. I know from 1 person, who has successfully used this b003 package on a 701.
Please report if you had tried and what the result is.
Ralf via Tapatalk. GEM701L, B111Kangvip v2 SiGo
audioralf said:
Do a NANDROID this will bring you back.
I don't know if B003 would run on a 702. If if was delivered with b003 I would try it, if other solutions had failed. If you are still on 5.0 you will be able to restore the nandroid If it fails. I know from 1 person, who has successfully used this b003 package on a 701.
Please report if you had tried and what the result is.
Ralf via Tapatalk. GEM701L, B111Kangvip v2 SiGo
Click to expand...
Click to collapse
Yes, B003 runs on gem-702l. My device is a TW version. The default ROM when I bought it was B003, then there was an OTA to B005 about 1 or 2 weeks ago. I am still on stock rom of B005. I am gonna give it a try. Thanks.
By the way, I read it from the previous thread that a B005 version was found in Huawei's official website but everyone's not sure about it. I believe Huawei indeed has a B005 for gem-702l. At least for a TW version.
Here's the download link I copy from the Huawei TW official website:
GEM-702LV100R001C209B005CUSTC158D001
---------- Post added at 12:06 AM ---------- Previous post was at 12:04 AM ----------
Ok, I have a new question.
The step 4:
"4. b This flashes all components of GEM-703L official stock ROM B015 via the dload folder. "
But my TW version has different 4G LTE bands from China gem-703l. Does that mean my bandbase will be modified by this process?
Thanks.
We have never heard anyone loosing LTE bands. The hardware sets which LTE bands will be supported. The baseband drivers inside these packages seem to be designed for all variants.
A(alternative) for installing a Stock B111 with GApps and Root
As of B109 Google Apps are missing from the ROM.
In case you want stay Stock B111 but don't want to live without the Google Apps, most notably the Play Store, here's a guide how to add them to a ROM. The guide takes place after you installed B111. I wrote it because I want to stay Stock.
Oh - you can indeed uninstall all Chinese Apps and some Huawei apps without root.
A(alternative) for installing a Stock B111 with GApps and Root
A10 - restart in fastboot mode
A11 - flash the TWRP for 5.11 from ADB cmd window with the command
fastboot flash recovery TWRP-ENG-5.1.1.img
A12 - download OpenGAPPS micro package from opengapps.org . NOTE: select ARM64 and Android 5.1 . The Huawei X2 is equipped with a 64bit processor
A12b - copy the ZIP to your external microsd (either with a USB Stick, or while in TWRP recovery and connected via USB)
A13 - boot into TWRP recovery and flash "open_gapps-arm64-5.1-micro-20160119.zip"
(A13b - you could also flash SuperSU at this step while you are at it)
A14 - IMPORTANT: Go to 'WIPE' in TWRP and do a full factory reset! Otherwise, when booted youll be greeted with a black desktop and only the status bar visible!
A15 - reboot into the system, configure it, and that's it. NOTE: Most Chinese mobile phones with Google Services missing won't let you add more than 1 Google Account from the Settings -> Accounts options. So, if you want to use more than 1 Google Account on your X2 , just fire up Google Mail and add the second, third, etc Google account in GMail. It'll be fully synchronized with your mobile then.
NOTE: You edited the system that way. Even if you do a factory reset from within the Android System, GApps and SU will stay.
I have a problem, I can't run Huawei Update extactor on my win10 pc, it keeps saying " Huawei Update extactor stop working " and it terminates it self before the program even start. I've tried in al different compability mode, but none of them is working.
Anyone got an idea about whats wrong ?
Aznbull said:
I have a problem, I can't run Huawei Update extactor on my win10 pc, it keeps saying " Huawei Update extactor stop working " and it terminates it self before the program even start. I've tried in al different compability mode, but none of them is working.
Anyone got an idea about whats wrong ?
Click to expand...
Click to collapse
Try this. Click Start, click Run, type MSIEXEC /UNREGISTER, and then click OK. Even if you do this correctly, it may look like nothing occurs.
Then click Start, click Run, type MSIEXEC /REGSERVER, and then click OK. Even if you do this correctly, it may look like nothing occurs, or you may briefly see an hourglass. After you run this command, the operation is complete. Reboot your computer, then try running it.
I am an owner of Mediapad X2 701L on B001 and there is no OTA update for my device. I used to have Mediapad X1 501u which didn’t get update too. So I converted it to 503L and managed to get updates. But this conversion uncalibrated my device sensors like digital compass and I didn’t manage to fix that.
I am very tempted to convert my 701L to 703L, but I’m just worry about four things?
1- Are the sensors calibrated and exact after conversion of 701L to 703L?
2- Is my LTE bands still supported in 703L?
3- How can I zip my cust? I haven’t managed to root my device yet, so I can’t use root explorer / is there any other method like updating my 701L to B003 locally? Any download link would be appreciated
4- Is there any method to restore my current ROM if I didn’t get good feedback from the conversion?
Many thanks in advance
1 have no problems with Sensors
2 no problems with LTE
3You must unlock anb install TWRP for 5.0
Then install superuser.
Then install a filemanager to be able to copy your \cust folder to discard
Then copy it via usb to pc
Then zip this folder
Then send it to ajsmsg78 or upload it to dropbox and publish the link
It does not contain any personal data. You will see this on the filedate.
There are done people waiting for you, who have already flashed a new firmware and have problems because ajsmsg78 has to integrate some files from your cust to the universal cust.
4 you can make a nandroid Backup of your System to return. So after flashing B003 you would be able to restore you're backup, and you will be back on b001.
Ralf via Tapatalk. GEM701L, B111Kangvip v2 SiGo
ajsmsg78 said:
Try this. Click Start, click Run, type MSIEXEC /UNREGISTER, and then click OK. Even if you do this correctly, it may look like nothing occurs.
Then click Start, click Run, type MSIEXEC /REGSERVER, and then click OK. Even if you do this correctly, it may look like nothing occurs, or you may briefly see an hourglass. After you run this command, the operation is complete. Reboot your computer, then try running it.
Click to expand...
Click to collapse
It doesn't change anything, still can't run the software.
For what do you need the extraxtor? The files you need are already extracted and linked in my guide.
Ralf via Tapatalk. GEM701L, B111Kangvip v2 SiGo
I know that you already linked the files i needed, I just wanted to try everything out before I jump in all this flashing to another version. Just to make sure that if the link you provide all of a sudden is dead, I still can extract the files my self.
I have a gem-702 b006
They are blocked in step 4 b
when you restart hangs straight at 0% and does not install the dload b015
how to solve?
I also recharged 2 times "fastboot flash recovery RECOVERY.img"
HwOTA 7+8 for Huawei Mate 10 Lite1. On the phone, make a backup of all data (since during the upgrade all data will be erased). This is an obligatory condition.
2. Unlock your bootloader: (There´s no way around it (unfortnuately), but after the procedure your device will be locked again, so don´t worry!). The device will make a factory reset, so once again, BACKUP your files!!!!!!!!!!
3. Enable ‘USB debugging’ and ‘OEM Unlock’ option from setting>developer option>. To enable Developer Options, go to About phone and tap the Build Number 7 times.
4. You must download three zip-archives with a full "Full OTA" firmware on which you want to flash (If you look through in the FF (FirmwareFinder), you see there are 4 archives for China and 3 for other locations. You must to download for the version what model and location you will have after the firmware);
5. Add the downloaded files to the folder "HWOTA\Update" and run the .cmd file, it will rename them automatically according to the template:
- update_data_full_public.zip to update_data_public.zip
- update_full_....zip to update_all_hw.zip
- update.zip don't rename
6. After run the universal batch file update.bat in the "HWOTA" folder, which will provide an opportunity to choose the required work option (change firmware/rebranding (change location)). FOLLOWING INSTRUCTIONS ON THE SCREEN OF THE MONITOR - the entire process is accompanied by prompts.
At the end of the process, everything should work fine... Be prepared, the bootloader will be locked after changing the location or firmware as a FullOTA.
7. If suddenly it turned out "bootloop" - go into the stock Recovery and make wipe.
PS: To change the firmware using the SD card, you need to create a folder "HWOTA" on the SD card and copy three firmware archives with the changed names (see above). In the batch file select item 1 "SDCard HWOTA directory"
HwOTA 7+8
Short video tutorial for upgrade of any version authorized or unauthorized in phone P10 Lite Thanks @Alexxxx1
HwOTA8 method for rollback from EMUI 8 to Emui 5 - Huawei P10 lite Thanks @Alexxxx1
If you like my work, you can thank TeamMT PayPal
PPS: Sorry for my English!!!
vovan1982 said:
HwOTA for Huawei Mate 10 Lite1. On the phone, make a backup of all data (since during the upgrade all data will be erased). This is an obligatory condition.
2. Unlock your bootloader: (There´s no way around it (unfortnuately), but after the procedure your device will be locked again, so don´t worry!). The device will make a factory reset, so once again, BACKUP your files!!!!!!!!!!
3. Enable ‘USB debugging’ and ‘OEM Unlock’ option from setting>developer option>. To enable Developer Options, go to About phone and tap the Build Number 7 times.
4. You must download three zip-archives with a full "Full OTA" firmware on which you want to flash (If you look through in the FF (FirmwareFinder), you see there are 4 archives for China and 3 for other locations. You must to download for the version what model and location you will have after the firmware);
5. Add the downloaded files to the folder "HWOTA\Update" and run the .cmd file, it will rename them automatically according to the template:
- update_data_full_public.zip to update_data_public.zip
- update_full_....zip to update_all_hw.zip
- update.zip don't rename
6. After run the universal batch file update.bat in the "HWOTA" folder, which will provide an opportunity to choose the required work option (change firmware/rebranding (change location)). FOLLOWING INSTRUCTIONS ON THE SCREEN OF THE MONITOR - the entire process is accompanied by prompts.
At the end of the process, everything should work fine... Be prepared, the bootloader will be locked after changing the location or firmware as a FullOTA.
7. If suddenly it turned out "bootloop" - go into the stock Recovery and make wipe.
PS: To change the firmware using the SD card, you need to create a folder "HWOTA" on the SD card and copy three firmware archives with the changed names (see above). In the batch file select item 1 "SDCard HWOTA directory"
HwOTA.zip
If you like my work, you can thank TeamMT PayPal
PPS: Sorry for my English!!!
Click to expand...
Click to collapse
Hello
thank you, worked for me.
from rne-l21c432b133, i got to rne-c432b135, and the bootloader is locked.
thanks thanks.
thank you works
Exodusnick said:
thank you works
Click to expand...
Click to collapse
For Oreo beta?
No to RNE-L21C432B135 Nougat
I haven't tested it for oreo beta I'm back to MORFUZ V 1.0
Great looking, it works perfectly, I tried to install oreo but it does not work, it always returns to 7.0 and 5.1. At least I managed to redirect the cell. But for the oreo version I think I have to wait because I've tried many but no one works.
I used this on top of the MidgarD ROM I had, now I have a normal 4.5G AND a working face unlock. On Stock ROM, I didn't have the option for the face unlock, and when I installed Elemental ROM and later MidgarD ROM, it didn't work on both of those. This is interesting, isn't it?
I also didn't immediately lose my installed apps, by which I mean until I unlocked the bootloader again.
Bad news: Despite installing Magisk and enabling Magisk Hide after this, I fail the Safety Net check
Thanks man its working fine, my Mate 10 Lite was soft bricked or wont get proper hardware and face unlock, now it works
in start it was problematic for me, wifi would not turn on, phone will periodically show storage full (there was no SD Card in it)
then I restarted 2/3 times, and poof.
Now not only phone is back but it has oreo
Hi!
I tried this, downloaded the rne-l21c432b135 FullOTA from Firmware Finder and followed the instructions.
However, when it boots after finishing then my phone has turned into NEO-L21 and I am not able to get back to RNE-L21 without replacing the software with an older backup. It says also the unit is rooted (Huawei ID says so when I should enter my fingerprint) even though I have formatted the unit.
What am I doing wrong?
EDIT: Sorry, I had used the wrong file (there is one for the RNE-L01 and one for the RNE-L21) and that made all the difference, I am not back to stock!
Thank you so much for the help!
Hi,
Works for RNE-L01C432B135 perfect. I updated without any problem.
But because I don't want to stay with locked bootloader, I made all rooting procedure from the beginning.
That was easy too, because I have backups of every single details (important datas from internal storage, messages, programs and of course /data/hw_init folder, SuperSU-decyrpt)
Thanks again
vovan1982 said:
HwOTA for Huawei Mate 10 Lite1. On the phone, make a backup of all data (since during the upgrade all data will be erased). This is an obligatory condition.
2. Unlock your bootloader: (There´s no way around it (unfortnuately), but after the procedure your device will be locked again, so don´t worry!). The device will make a factory reset, so once again, BACKUP your files!!!!!!!!!!
3. Enable ‘USB debugging’ and ‘OEM Unlock’ option from setting>developer option>. To enable Developer Options, go to About phone and tap the Build Number 7 times.
4. You must download three zip-archives with a full "Full OTA" firmware on which you want to flash (If you look through in the FF (FirmwareFinder), you see there are 4 archives for China and 3 for other locations. You must to download for the version what model and location you will have after the firmware);
5. Add the downloaded files to the folder "HWOTA\Update" and run the .cmd file, it will rename them automatically according to the template:
- update_data_full_public.zip to update_data_public.zip
- update_full_....zip to update_all_hw.zip
- update.zip don't rename
6. After run the universal batch file update.bat in the "HWOTA" folder, which will provide an opportunity to choose the required work option (change firmware/rebranding (change location)). FOLLOWING INSTRUCTIONS ON THE SCREEN OF THE MONITOR - the entire process is accompanied by prompts.
At the end of the process, everything should work fine... Be prepared, the bootloader will be locked after changing the location or firmware as a FullOTA.
7. If suddenly it turned out "bootloop" - go into the stock Recovery and make wipe.
PS: To change the firmware using the SD card, you need to create a folder "HWOTA" on the SD card and copy three firmware archives with the changed names (see above). In the batch file select item 1 "SDCard HWOTA directory"
HwOTA.zip
If you like my work, you can thank TeamMT PayPal
PPS: Sorry for my English!!!
Click to expand...
Click to collapse
You should probably add credit to @mankindtw as this is his script
And switch places of step 2 and 3
ante0 said:
You should probably add credit to @mankindtw as this is his script
And switch places of step 2 and 3
Click to expand...
Click to collapse
He refused to support the lite model. I re-wrote his script and improved it. I will not add it. He need to be more flexible.
vovan1982 said:
He refused to support the lite model. I re-wrote his script and improved it. I will not add it. He need to be more flexible.
Click to expand...
Click to collapse
Oh. Sorry!
Good job then
Where can I find HwOTA for Huawei Honor View10?
HI Guys
my current firmware is RNE-L21C185B110 but i can't find any FULL OTA firmware but only OTA MF (RNE-L21C185B142CUSTC185D001 this is the last available update).
My bootloader is unlocked, unrooted and without TRWP
How can I do to update to last firmware with HwOTA?
ok
To install the update of the B142 you do not necessarily have to use the HWOTA, you simply have to copy the DLOAD folder from the extracted RAR file to your SD, if your SD says that the file is very large ... format the SD to another type of Format..
Formatting a unit SD in exFAT
1. Double-click on Equipment.
2. Right-click on the flash drive or memory card, then select Format.
3. In the File System list, click exFAT.
4. Click on Start.
5. Click OK to begin the format.
After saving the DLOAD folder to the SD.
- Turn off your smartphone
- Now press the volume button up + Volume down + Power button at the same time, so that the update process starts automatically.
- This procedure takes 5 to 10 minutes to complete
- Automatically it will restart ... and you will have installed the update.
giangi64 said:
HI Guys
my current firmware is RNE-L21C185B110 but i can't find any FULL OTA firmware but only OTA MF (RNE-L21C185B142CUSTC185D001 this is the last available update).
My bootloader is unlocked, unrooted and without TRWP
How can I do to update to last firmware with HwOTA?
Click to expand...
Click to collapse
Great,
updated without any problem.
Thank you very much
You're welcome
At all times when I can help I will. Greetings and a pleasure to have contributed ...
giangi64 said:
Great,
updated without any problem.
Thank you very much
Click to expand...
Click to collapse
Hi, I use version l21c432b135 rne-without root,has anyone tried to make update oreo , at bla-l09c432 with firmware fiinder?
dyller said:
Hi, I use version l21c432b135 rne-without root,has anyone tried to make update oreo , at bla-l09c432 with firmware fiinder?
Click to expand...
Click to collapse
I have the same model of L21, the firmware finder doesn't find the update yet. I'm located in Slovenia, if that helps anyhow. Although today I received the April security update B135.
HwOTA7 + HwOTA8 for Huawei Nova 21. On the phone, make a backup of all data (since during the upgrade all data will be erased). This is an obligatory condition.
2. Unlock your bootloader: (There´s no way around it (unfortnuately), but after the procedure your device will be locked again, so don´t worry!). The device will make a factory reset, so once again, BACKUP your files!!!!!!!!!!
3. Enable ‘USB debugging’ and ‘OEM Unlock’ option from setting>developer option>. To enable Developer Options, go to About phone and tap the Build Number 7 times.
4. You must download three zip-archives with a full "Full OTA" firmware on which you want to flash (If you look through in the FF (FirmwareFinder), you see there are 4 archives for China and 3 for other locations. You must to download for the version what model and location you will have after the firmware);
5. Add the downloaded files to the folder "HWOTA\Update" and run the .cmd file, it will rename them automatically according to the template:
- update_data_full_public.zip to update_data_public.zip
- update_full_....zip to update_all_hw.zip
- update.zip don't rename
and will be repack firmware (only HwOTA8)!!!
6. After run the universal batch file update.bat in the "HWOTA" folder, which will provide an opportunity to choose the required work option (change firmware/rebranding (change location)). FOLLOWING INSTRUCTIONS ON THE SCREEN OF THE MONITOR - the entire process is accompanied by prompts.
At the end of the process, everything should work fine... Be prepared, the bootloader will be locked after changing the location or firmware as a FullOTA.
7. If suddenly it turned out "bootloop" - go into the stock Recovery and make wipe.
PS: To change the firmware using the SD card, you need to create a folder "HWOTA" on the SD card and copy three firmware archives with the changed names (see above). In the batch file select item 1 "SDCard HWOTA directory"
HwOTA_PIC.zip
Short video tutorial for upgrade of any version authorized or unauthorized in phone P10 Lite Thanks @Alexxxx1
HwOTA8 method for rollback from EMUI 8 to Emui 5 - Huawei P10 lite Thanks @Alexxxx1
If you like my work, you can thank TeamMT PayPal
PPS: Sorry for my English!!!
Thanks :good:
Fixed
Heya,
This is a guide aimed on helping you to switch to a custom rom from the stock firmware.
For any questions, feel free to join our Telegram groups.
PREREQUISITES
1) Stock rom recommended by the maintainer of the rom that you want to flash. Typically for Q roms, 10.0.13.0, 10.0.18.0, 11.0.4.0 work well. (Link here).
2) The custom rom you want (Custom Rom list here).
3) Platform-Tools by Google for adb and fastboot (Link here).
4) TWRP Recovery Image and installer zip (Link here and here).
5) Force Encryption Disabler (Link here).
6) MiFlash by Xiaomi (Download the latest version from here).
7) An unlocked Bootloader
INTRODUCTION
Installing a custom ROM on an Android phone used to be a walk in the park. However, some newer phones, like Xiaomi Mi A2 Lite, have what's called an A/B partition layout. This facilitates an update process on stock ROMs, however it makes it harder to install and develop custom ROMs. You can read more about A/B partitions here.
The upshot is that Mi A2 Lite doesn't have a recovery partition. Instead, when you install TWRP, it gets installed to the boot partition. Which means that every time you install or update a ROM, you will need to re-flash the recovery ZIP. One more thing to keep in mind is that the ROM always gets installed to another slot. Meaning, if you're currently in the slot B, the ROM will be installed to slot A and vice versa.
INSTALLATION PROCESS
A) Installing Stock Rom as a Base
1) Extract the platform tools zip file and open the new extracted folder.
2) Open a command line / PowerShell window in that folder by holding the shift key and right clicking into the empty space of the folder. Press the "open PowerShell / Command line window here" option.
3) Plug the device into your PC with a Micro USB cable.
4) Hold down the power button and the volume down button for ~10-15 seconds. You should see the fastboot screen.
5) In the Command Line / PowerShell window type: "cmd" and hit Enter. Then, type "fastboot oem edl" and hit Enter again. If your device can't get detected (Stuck on "Waiting for any device") and nothing happens on your phone's screen, check the notes section of the guide below.
This will reboot your device into edl mode (Emergency Download Mode). The screen should turn off and the led indicator should be blinking indefinitely
5) Extract the MiFlash zip file and open the extracted folder
6) Launch the Mi Flash application by double clicking the XiaoMiFlash.exe file
7) Install the necessary drivers for MiFlash (Click ok in the dialogues).
8) Extract the downloaded stock rom.
9) Press the "select" button and point into the previously extracted folder. (There should be an images folder and some other sh and bat files in the same directory).
10) Click "Clean All" all in the bottom left.
11) Press "Refresh".
12) Your device should appear (COM port). (If not, check the notes section of the guide below)
13) Click "Flash". The process will take around 200-350 seconds.
14) After it is done, hold down the power button for ~10 seconds and verify that the stock rom boots.
DO NOT UPDATE OR MAKE ANY MODIFICATIONS IN THE BOOTED STOCK ROM IN ANY WAY.
B) Install the Custom Rom
(If you want to flash PixelExperience Official, continue with this guide by the PE team. If you face any issues, check the NOTES section of this guide)
1) Paste the downloaded custom rom (zip file) into your sd card and insert it into your phone.
2) Hold down the power button alongside with the volume down button. You should see the fastboot screen shortly.
3) Copy the TWRP IMG file to the platform-tools folder
4) Copy the TWRP Installer Zip file to your SD Card.
5) Open a cmd / PowerShell window in the platform-tools folder (like Step 2 of Section A)
6) Type: "fastboot boot twrp-3.4.0-3-unofficial-daisy.img".
7) You will see the recovery on your phone, prompting you to enter the password. Choose "Cancel"
8) Go into the main menu of TWRP. Press Wipe, then "Format Data". Type "yes" and press enter. (Keep in mind that all of your data will be wiped and there is no going-back).
9) Go back and press "Advanced Wipe". and select everything except "SD Card". Swipe to confirm the action.
10) Go into the main menu. Press "Install", "Select Storage" and select "Micro SD Card".
11) Flash the zips in this order (Click on them and swipe to confirm the action)
- Custom ROM
- TWRP Installer ZIP
- Force Encryption Disabler
DO NOT install Magisk, GApps or anything else yet, we will do that later!
(Some ROMs do not require Force Encryption Disabler as Force Encryption is disabled by default, although flashing that zip won't hurt anything)
After everything is done, DON'T TAP REBOOT YET. Instead, go back to the main menu, choose "Reboot", change the slot (e.g. if it says "Current Slot: A", tap "Slot B", vice versa.
12) Tap "Recovery" in the reboot menu.
13) Copy anything you would like to install on your phone (Magisk, Gapps, etc.) and flash it the usual way (optional)
(Some roms like EvolutionX and Pixel Experience have Gapps built-in so do not flash any gapps package in such roms.)
(Flashing Magisk isn't necessary but some roms may need it for CTS / SafetyNet to pass.)
14) Reboot to System and enjoy your Rom.
DIRTY FLASHING / MANUALLY INSTALLING A NEW BUILD
Manually Installing a new ROM build a.k.a Dirty Flashing is also somewhat complicated on A/B phones like Xiaomi Mi A2 Lite. However, if you follow these steps, you should be good to go:
1) Download the new build and copy it to your phone.
2) Reboot into the recovery mode (hold power + volume up) and flash the ROM ZIP.
3) Here's where the fun part begins: since we've just overwritten the boot partition, we don't have TWRP anymore, so we need to flash it again.
4) Once again, after you're done, don't tap on "Reboot" yet, instead, go back to the main menu, change the slot, and tap "Recovery".
5) Once the phone boots into recovery again, flash Magisk (optional) and Gapps if you had flashed them before.
6) Reboot the phone to system.
PSA: Dirty Flashing rom builds may cause unexpected problems and for this reason, it is recommended to perform a clean flash (Format Data) every time you want to flash a new build of your rom or switch to a different one.
SEAMLESS UPDATES
LOS Updater (which is used in Lineage OS and many other roms) downloads the ROM ZIP automatically and installs it to the inactive slot, which spares us the need to reboot into recovery. Thus, these updates look like OTA updates from the stock rom. However, there are a few gotchas here too:
After the OTA is installed, DON'T TAP ON "REBOOT". Instead, go to Magisk Manager and install a module called "TWRP A/B Retention Script" (you should be able to find it in the "Downloads" section)
Then, go to the Manager's main menu, tap on "Install" and choose "Install to inactive slot (After OTA)"
After the installation process is completed, you can reboot. You have to repeat the process every time you get an OTA if you want to keep Magisk and TWRP on your newly updated system.
- - - - NOTES - - - -
- Windows is the only supported operating system by this guide.
- If when you type a fastboot command (like fastboot oem edl) it just shows "Waiting for any device", it is probably due to missing drivers. See this page on how to install the Google USB driver that is required for fastboot to detect your phone.
- If you have an older version of Windows like 8, 8.1, 7 etc, your device might not get detected by MiFlash due to missing drivers. In this case, you will have to install the Qualcomm EDL driver on your own (Link here). Windows 10 finds and installs the driver automatically.
- If SafetyNet doesn't pass, ensure you have not modified anything in the system partition and that you have enabled Magisk Hide in Magisk Manager. If it still does not pass, try using the "MagiskHide Props Config" Magisk Module (More Info here). If it still doesn't work, try reinstalling your rom. If there are still issues regarding safetynet, it may be the rom's problem or google's new server-side changes might have affected your device (Learn more here)
- If some apps detect root and do not function properly (like banking apps), make sure SafetyNet passes. Also, you can try selecting the app in the MagiskHide section of Magisk Manager. The "Hide Magisk Manager" option in the Settings of Magisk Manager can be useful too.
- MIUI Roms / Ports have a special installation procedure (different from the one presented here) and thus, it is recommended that you take a look at their respective xda thread(s) and / or in the appropriate telegram group.
- If your download speed is slow when downloading the stock rom base, try using a download manager like IDM. If the speed is still slow, it is an issue with xiaomi's servers and there is nothing that can be done about it.
- 3.18 kernels such as butterfly, dragonheart etc, do NOT work and / or cause unexpected issues in updated custom roms because these roms use newer 4.9 kernels. The recommended custom 4.9 kernel is Sleepy and it can be found on Telegram (https://t.me/Laciakerneltg). Therefore, there will be no support offered if you are using a 3.18 kernel in a ROM that uses 4.9 kernels (all new UPDATED roms do)
- If your fingerprint doesn't work / partially works, flash this fix in twrp (This issue exists in the official version of pixel experience)
- Android 11 ROMs might require extra steps that are not mentioned here, please follow the respective maintainer's installation guide for now.
CREDITS
tkchn for some parts of the guide
@Offain for FED
@FDoop for some links and guides
Amazing ?
Detailed Guide
LinkBoi said:
Heya,
This is a guide aimed on helping you to switch to a custom rom from the stock firmware.
For any questions, feel free to join our Telegram groups.
PREREQUISITES
1) Stock rom recommended by the maintainer of the rom that you want to flash. Typically for Q roms, 10.0.13.0, 10.0.18.0, 11.0.4.0 work well. (Link here).
2) The custom rom you want (Custom Rom list here).
3) Platform-Tools by Google for adb and fastboot (Link here).
4) TWRP Recovery Image and installer zip (Link here and here).
5) Force Encryption Disabler (Link here).
6) MiFlash by Xiaomi (Download the latest version from here).
INTRODUCTION
Installing a custom ROM on an Android phone used to be a walk in the park. However, some newer phones, like Xiaomi Mi A2 Lite, have what's called an A/B partition layout. This facilitates an update process on stock ROMs, however it makes it harder to install and develop custom ROMs. You can read more about A/B partitions here.
The upshot is that Mi A2 Lite doesn't have a recovery partition. Instead, when you install TWRP, it gets installed to the boot partition. Which means that every time you install or update a ROM, you will need to re-flash the recovery ZIP. One more thing to keep in mind is that the ROM always gets installed to another slot. Meaning, if you're currently in the slot B, the ROM will be installed to slot A and vice versa.
INSTALLATION PROCESS
A) Installing Stock Rom as a Base
1) Extract the platform tools zip file and open the new extracted folder.
2) Open a command line / PowerShell window in that folder by holding the shift key and right clicking into the empty space of the folder. Press the "open PowerShell / Command line window here" option.
3) Plug the device into your PC with a Micro USB cable.
4) Hold down the power button and the volume down button for ~10-15 seconds. You should see the fastboot screen.
5) In the Command Line / PowerShell window type: "cmd" and hit Enter. Then, type "fastboot oem edl" and hit Enter again. If your device can't get detected (Stuck on "Waiting for any device") and nothing happens on your phone's screen, check the notes section of the guide below.
This will reboot your device into edl mode (Emergency Download Mode). The screen should turn off and the led indicator should be blinking indefinitely
5) Extract the MiFlash zip file and open the extracted folder
6) Launch the Mi Flash application by double clicking the XiaoMiFlash.exe file
7) Install the necessary drivers for MiFlash (Click ok in the dialogues).
8) Extract the downloaded stock rom.
9) Press the "select" button and point into the previously extracted folder. (There should be an images folder and some other sh and bat files in the same directory).
10) Click "Clean All" all in the bottom left.
11) Press "Refresh".
12) Your device should appear (COM port). (If not, check the notes section of the guide below)
13) Click "Flash". The process will take around 200-350 seconds.
14) After it is done, hold down the power button for ~10 seconds and verify that the stock rom boots.
DO NOT UPDATE OR MAKE ANY MODIFICATIONS IN THE BOOTED STOCK ROM IN ANY WAY.
B) Install the Custom Rom
1) Paste the downloaded custom rom (zip file) into your sd card and insert it into your phone.
2) Hold down the power button alongside with the volume down button. You should see the fastboot screen shortly.
3) Copy the TWRP IMG file to the platform-tools folder
4) Copy the TWRP Installer Zip file to your SD Card.
5) Open a cmd / PowerShell window in the platform-tools folder (like Step 2 of Section A)
6) Type: "fastboot boot twrp-daisy-3.3.1.0-offain.img".
7) You will see the recovery on your phone, prompting you to enter the password. Choose "Cancel"
8) Go into the main menu of TWRP. Press Wipe, then Advanced Wipe and select everything except "SD Card".
9) Go back and press "Format Data".
10) Go into the main menu. Press "Install", "Select Storage" and select "Micro SD Card".
11) Flash the zips in this order (Click on them and confirm the action) :
- Custom ROM
- TWRP Installer ZIP
- Force Encryption Disabler
DO NOT install Magisk, GApps or anything else yet, we will do that later!
PSA: Some ROMs do not require Force Encryption Disabler as Force Encryption is disabled by default.
After everything is done, DON'T TAP REBOOT YET. Instead, go back to the main menu, choose "Reboot", change the slot (e.g. if it says "Current Slot: A", tap "Slot B", vice versa.
12) Tap "Recovery" in the reboot menu.
13) Copy anything you would like to install on your phone (Magisk, Gapps, etc.) and flash it the usual way (optional)
PSA: Some roms like EvolutionX and Pixel Experience have Gapps built-in so do not flash any gapps package in such roms.
PSA2: Flashing Magisk isn't necessary but some roms may need it for CTS / SafetyNet to pass.
14) Reboot to System and enjoy your Rom.
DIRTY FLASHING / MANUALLY INSTALLING A NEW BUILD
Manually Installing a new ROM build a.k.a Dirty Flashing is also somewhat complicated on A/B phones like Xiaomi Mi A2 Lite. However, if you follow these steps, you should be good to go:
1) Download the new build and copy it to your phone.
2) Reboot into the recovery mode (hold power + volume up) and flash the ROM ZIP.
3) Here's where the fun part begins: since we've just overwritten the boot partition, we don't have TWRP anymore, so we need to flash it again.
4) Once again, after you're done, don't tap on "Reboot" yet, instead, go back to the main menu, change the slot, and tap "Recovery".
5) Once the phone boots into recovery again, flash Magisk (optional) and Gapps if you had flashed them before.
6) Reboot the phone to system.
PSA: Dirty Flashing rom builds may cause unexpected problems and for this reason, it is recommended to perform a clean flash (Format Data) every time you want to flash a new build of your rom or switch to a different one.
SEAMLESS UPDATES
LOS Updater (which is used in Lineage OS and many other roms) downloads the ROM ZIP automatically and installs it to the inactive slot, which spares us the need to reboot into recovery. Thus, these updates look like OTA updates from the stock rom. However, there are a few gotchas here too:
After the OTA is installed, DON'T TAP ON "REBOOT". Instead, go to Magisk Manager and install a module called "TWRP A/B Retention Script" (you should be able to find it in the "Downloads" section)
Then, go to the Manager's main menu, tap on "Install" and choose "Install to inactive slot (After OTA)"
After the installation process is completed, you can reboot. You have to repeat the process every time you get an OTA if you want to keep Magisk and TWRP on your newly updated system.
- - - - NOTES - - - -
- Windows is the only supported operating system by this guide.
- If when you type a fastboot command (like fastboot oem edl) it just shows "Waiting for any device", it is probably due to missing drivers. See this page on how to install the Google USB driver that is required for fastboot to detect your phone.
- If you have an older version of Windows like 8, 8.1, 7 etc, your device might not get detected by MiFlash due to missing drivers. In this case, you will have to install the Qualcomm EDL driver on your own (Link here). Windows 10 finds and installs the driver automatically.
- If SafetyNet doesn't pass, ensure you have not modified anything in the system partition and that you have enabled Magisk Hide in Magisk Manager. If it still does not pass, try using the "MagiskHide Props Config" Magisk Module (More Info here). If it still doesn't work, try reinstalling your rom. If there are still issues regarding safetynet, it may be the rom's problem or google's new server-side changes might have "hit" your device (Learn more here)
- If some apps detect root and do not function properly (like banking apps), make sure SafetyNet passes. Also, you can try selecting the app in the MagiskHide section of Magisk Manager. The "Hide Magisk Manager" option in the Settings of Magisk Manager can be useful too.
- MIUI Roms / Ports have a special installation procedure (different from the one presented here) and thus, it is recommended that you take a look at their respective xda thread(s) and / or in the appropriate telegram group.
- If your download speed is slow when downloading the stock rom base, try using a download manager like IDM. If the speed is still slow, it is an issue with xiaomi's servers and there is nothing that can be done about it.
- 3.18 kernels such as butterfly, dragonheart etc, do NOT work and / or cause unexpected issues in updated custom roms because these roms use newer 4.9 kernels. The recommended custom 4.9 kernels are: Sleepy (can be found in Telegram) and Loki (Link here). Therefore, there will be no support offered if you are using a 3.18 kernel in a rom that uses 4.9 kernels (all new UPDATED roms do)
CREDITS
tkchn for some parts of the guide
@offain for TWRP IMG and FED
@FDoop for some links and guides
@ScaryMen1325 for fixing MTP in @offain's twrp for 4.9 kernels
Everyone who builds Custom Roms
Click to expand...
Click to collapse
Hi LinkBoi,
Hope You're Doing Great.
Detailed Guide...
Really Appreciated For Your Hardwork.
Thanks,
MUHAMMAD Asif Qasim
Wow, so much information in one place. Thanks for spending your time on this.
Pat750 said:
Wow, so much information in one place. Thanks for spending your time on this.
Click to expand...
Click to collapse
Thanks for the positive feedback
Thanks for the great and detailed work..
I don't have windows, someone knows how can I do the steps that use the MI software? I just thinking on install Oreo again
mancarv said:
I don't have windows, someone knows how can I do the steps that use the MI software? I just thinking on install Oreo again
Click to expand...
Click to collapse
Not quite the same... But the stock rom .tgz can be flashed using fastboot. That's what I do, since my main system is a Mac.
I think EDL/miflash can fix some things fastboot can't (eg. partition table).
For "flash stock and erase data" it should be fine.
mancarv said:
I don't have windows, someone knows how can I do the steps that use the MI software? I just thinking on install Oreo again
Click to expand...
Click to collapse
Are you on mac or linux? For, mac, I know little about the process. Edl flashing is certainly not possible in mac os. Regarding linux, there is qdl if you wanna try it, but i do not recommend it. For fastboot flashing, you can try the .sh scripts in the stock rom's folder but no support will be given.
Guys thanks for your answers, sorry for being late I have been occupied. I'm on Linux, Ubuntu 18.04. I didn't remember that stock roms come with sh script. Has been a long time since I did this kind stuff and it was with a ZTE Open with Firefox OS :laugh: Maybe I'm gonna try downgrade, I'm testing the last stock version and it is working good so far .
Hi. Question about: "A) Installing Stock Rom as a Base". Can I skip this step if I'm already on a stock rom?
93starletgt said:
Hi. Question about: "A) Installing Stock Rom as a Base". Can I skip this step if I'm already on a stock rom?
Click to expand...
Click to collapse
Yes
93starletgt said:
Hi. Question about: "A) Installing Stock Rom as a Base". Can I skip this step if I'm already on a stock rom?
Click to expand...
Click to collapse
depends one which stock version you're on. The ones I have recommended have been tested and work well. Users have reported that latest stock q works well too. From my experience, anything over 10.0.13.0 is good but if you have weird bugs, try to flash any of the recommended stock roms first and see if those bugs persist.
TWRP Recovery Update
TWRP Recovery v3.4.0-0 - UNOFFICIAL
Updated: 4/9/2020
TWRP Bootable image
TWRP Installer ZIP
Changelog:
• Merged all TWRP 3.4.0-0 Changes
• Based on @TogoFire's OFRP device tree:
- Enabled System-as-Root
- Updated recovery.fstab
- Updated Rootdir & Blobs
- Added bootctrl from Stock Q
- Updated kernel, in the bootable image, to 4.9.233
- Fixed stability issues
- Fixed mounting issues
Note:
- The Tap-to-wake gesture was removed
- Decryption doesn't work (it never did)
Credits:
- @TogoFire for the device tree (Massive kudos to him for making a fully stable tree)
- @lslx_22S99176LF, @LmAo_device for testing
- @ScaryMen1325 for the MTP fix
LinkBoi said:
TWRP Recovery v3.4.0-0 - UNOFFICIAL
Updated: 4/9/2020
TWRP Bootable image
TWRP Installer ZIP
Changelog:
• Merged all TWRP 3.4.0-0 Changes
• Based on @TogoFire's OFRP device tree:
- Enabled System-as-Root
- Updated recovery.fstab
- Updated Rootdir & Blobs
- Added bootctrl from Stock Q
- Updated kernel, in the bootable image, to 4.9.233
- Fixed stability issues
- Fixed mounting issues
Note:
- The Tap-to-wake gesture was removed
- Decryption doesn't work (it never did)
Credits:
- @TogoFire for the device tree (Massive kudos to him for making a fully stable tree)
- @lslx_22S99176LF, @LmAo_device for testing
- @ScaryMen1325 for the MTP fix
Click to expand...
Click to collapse
Original post has been updated aswell
Twrp update 2
If you have the recovery loop issue (the device is always booting to recovery), go to advanced > fix recovery loop, confirm the action and it should be fixed )
Twrp update 2
TWRP Recovery v3.4.0-0 - UNOFFICIAL
Updated: 5/9/2020
TWRP Bootable image
TWRP Installer ZIP
Changelog:
• Based on @TogoFire's TWRP device tree:
- Updated kernel image in the bootable image to 4.9.234.
- Fixed USB, to be recognised better.
- Added the double-tap-to-wake (dt2w) gesture. (When the screen is off, you can press it twice to open it)
- Remove the reboot to EDL option as it didn't work
Note:
- Decryption doesn't work
- If you have any issues regarding double tap to wake, try to delete the .twrps file in the TWRP folder (can be found in the Internal Storage).
Credits:
- @TogoFire for the device tree (all of the work is his)
- @lslx_22S99176LF, @proxer05 for testing
Awesome guide, thanks a lot!
I have a question, if i want to install some patches and fixes throgth TWRP, is necessary to change the slot before reboot?
LinkBoi said:
TWRP Recovery v3.4.0-0 - UNOFFICIAL
Updated: 5/9/2020
Click to expand...
Click to collapse
Is this using some kind of Magisk based stuff to install or something because between this and the Force-enc disabler zip linked in this thread, something is causing my banking app to think my phone is rooted even though it isn't. I'd rather avoid having to install magisk purely for the sake of making my bank app work properly, so what's with this?
EDIT: well, I installed magisk anyway and got safetynet passing + magiskhide set up but the bank app still thinks im rooted so rip me i guess
EDIT 2: "Back in March of 2020, Google made some changes to SafetyNet that permanently trips when your bootloader is unlocked no matter what you do." welp,
Wher can I find "TWRP A/B Retention Script" in Magisk?
There is a new Design with no Download Selection.
How to Root Samsung Galaxy A7 2018 (a750fn) + Working Secure Folder & Samsung Health
Hello, this is a guide on how to root Samsung galaxy A7 2018 (a750fn). I've tried to simplify the guide as much as I can but I still suggest to root your phone only if you know what you are doing! Also if you have any questions or problems, just ask.
Note: Sorry for any grammatical or spelling mistakes. English is not my native language.
!Disclaimer!
- You do this at your own risk! I am NOT responsible for bricked devices, stuck on bootloop etc.!
- Backup your device before proceeding forward!
- This guide WILL trip Knox so your warranty will be void!
- The Knox-dependent applications like Secret Folder and Samsung Health will stop working but in this guide, there are two other miniguides that will explain how to enable them even after tripped Knox. - All of these steps have been tested on my phone - Samsung Galaxy A7 (2018) (a750fn) where they worked without problems.
Required Software/Resources:
- Odin (for flashing) - Download
- Samsung USB Drivers - Download
- 7zip (for archives) - Download
- Firmware with the last security patch from 2020 (for me, the patch was from November 2020) - Download
- TWRP Recovery - Download
- Magisk (for root) - Download
- DM-VERITY, FORCED ENCRYPTION, AND DISC QUOTA DISABLER (Disable_Dm-Verity_ForceEncrypt.zip) - Download
- A MicroSD card
Setup the Software/Resources:
1. Install 7zip
2. Install the Samsung USB Drivers
3. Extract Odin to a folder and put it on the Desktop
4. Extract the firmware to a folder and put it on the Desktop
In the firmware there'll be 5 files:
- BL_FIRMWAREVERSION
- AP_FIRMWAREVERSION
- CP_FIRMWAREVERSION
- CSC_OMC_OXM_FIRMWAREVERSION
- HOME_CSC_OMC_OXM_FIRMWAREVERSION (delete this one)
Delete the files starting with HOME_CSC.
5. Change the Magisk extension from .apk to .zip (Ex. Magisk_ver.apk --> Magisk_ver.zip)
6. Put the Magisk_ver.zip in the MicroSD card
7. Put the Disable_Dm-Verity_ForceEncrypt.zip in the MicroSD card as well
8. Insert the MicroSD card in the phone
Steps to Root:
NOTE: BEFORE PROCEEDING FORWARD, BACKUP YOUR DEVICE!
1. Enable Developer Options (by clicking 7 times the build number of your phone)
2. Open Developer Options and find the option OEM Unlock
3. Enable OEM Unlock (this will factory reset the phone)
- After the factory reset the OEM Unlock option will be enabled and this will allow
flashing custom recoveries and etc. to the phone.
4. After the factory reset, when the phone boots up, turn it off
5. Connect the phone to you PC/Laptop via USB cable
6. While the phone is completely turned off, hold the buttons Volume UP + Volume DOWN until Download mode shows up
7. Press Volume UP again to confirm that you'll be modifying your device
8. On your PC/Laptop open Odin
9. On the left side in Odin there are 3 tabs: Log, Options and Pit
10. Open Options and remove the checkmark on the Auto Reboot option, then go back to Log
11. In the middle of the program there are 5 slots:
- BL (Bootloader)
- AP (Application Processor)
- CP (Modem)
- CSC (Consumer Software Customization)
- USERDATA
12. Click the first slot and navigate to the location where you extracted the firmware
- The start of the names of each firmware file corresponds to the names of the slots in Odin
13. Place each firmware file in the correct Odin slot that corresponds to their names
(Ex. BL_FIRMWAREVERSION is inside the BL slot)
14. With your phone connected, press the Start button to flash the firmware
- After the firmware has been flashed successfully, your phone will be downgraded to the last security patch from 2020 which fixes possible bootloops or other issues when rooting/disabling forced encryption.
- The firmware is successfully flashed when the top left bar is green and above says PASS!
After flashing the firmware DON'T boot in Android yet!
15. After flashing, hold the Volume DOWN + Power button for around 7 seconds, immediately when the screen goes black switch to holding Volume UP + Volume DOWN
- You will enter back in Download mode
16. In Odin, press the Reset button and again uncheck Auto Restart in Options
17. In the AP slot, select the TWRP Recovery (which is in .tar archive)
18. With your phone connected to your PC/Laptop in Download mode, press Start on Odin
- This will flash the custom recovery to the phone
19. You can now disconnect the phone from your PC/Laptop
Again, after flashing the recovery, do NOT boot into Android yet!
20. After flashing the custom recovery, hold the Volume DOWN + Power button for around 7 seconds, immediately when the screen goes black switch to holding Volume UP + Power button
- This will boot the phone into the custom recovery (TWRP in this case)
22. Inside TWRP Recovery, go to Wipe, select Format Data and type 'yes' to confirm
23. After the format, go to Install, select the MicroSD card and find where you've put the Magisk_ver.zip file, select it and install it
- This will root to the device!
24. After you have installed Magisk, go back to Install, select the MicroSD card and find where you've put Disable_Dm-Verity_ForceEncrypt.zip and install it
- This will disable the forced encryption!
- If there's an error when installing the zip that says 'Failed to mount '/odm' (no such file or directory)", simply ignore it and proceed forward.
25. Go to Reboot, select System and wait around 5-10 minutes till Android fully loads
- After Android has loaded, proceed through the setup process.
26. Go to all apps and find the application called Magisk
- When you open it, it'll ask you to complete the installation of the Magisk app.
- It may also ask to reboot, to fully complete the installation.
27. After the application has been fully installed, your device will be Rooted and with disabled forced encryption!
Fix Secure Folder & Samsung Health
Note: TWRP Backup is recommended in case something fails
Samsung Health:
Required Software:
- A build.prop editor like this
Steps:
1. Install a build.prop editor from the play store
2. Give the build.prop editor root access
3. Open the editor and search for the line - ro.config.tima=1
4. Change the 1 to 0
(Ex. ro.config.tima=1 --> ro.config.tima=0)
5. Save and Reboot the device
6. After the reboot Samsung Health should work as expected
Secure Folder:
Required Software:
- Smali Patcher - Download
Steps:
2. Extract Smali Patcher.zip into a folder
3. Run as administrator
- Wait until it says 'idle..' at the bottom left of the program
4. Uncheck everything checked (like Mock locations, Mock providers, High volume warning etc.)
5. Check Samsung Knox
6. Enable USB Debugging on your phone
7. Connect your phone to your PC/Laptop
8. Press the ADB PATCH button
- A prompt will appear on your phone that asks if you allow your pc to do debugging mode operations on your phone.
9. Press allow on the prompt on your phone
- Wait until Smali Patcher is done.
- After Smali Patcher is done there should be a Magisk module inside it's folder.
10. Copy the Magisk module created by Smali Patcher to your phone
11. Open Magisk and go to Modules (the puzzle piece icon)
12. Tap on the button saying 'Install from storage'
13. Find the location where you've copied the module
14. Install the module
15. Restart your phone
16. If all done correctly, you should be able to set up and use Secure Folder
everything worked, thank you for the nice explanation and your help (A750F)
beytullahgol said:
everything worked, thank you for the nice explanation and your help (A750F)
Click to expand...
Click to collapse
Glad I could help
this one works! thx
Ive no idea which firmware link ot try
*EDIT* Im just waiting for first boot now. So far so good. IIRC first boot takes a while after all this so hopefully job done.
Thanks for guide
Ah ****e, magisk isnt working, says NO for ramdisk.
Root works though so I dunno what the craic is.
Works perfect, thanks!
Thanks, everything works perfectly.
Hello,
I have problem with:
26. Go to all apps and find the application called Magisk
Where I can find it, maybe I'm looking wrong, I can't find it. I didn't have error during install Magisk by TWRP, I don't have root device, what's going on, any can help me?
I installed the same firmware (the patch was from November 2020).
Tubeczka said:
Hello,
I have problem with:
26. Go to all apps and find the application called Magisk
Where I can find it, maybe I'm looking wrong, I can't find it. I didn't have error during install Magisk by TWRP, I don't have root device, what's going on, any can help me?
I installed the same firmware (the patch was from November 2020).
Click to expand...
Click to collapse
Did you flash Magisk v21.4 via TWRP?
Zanci19 said:
Did you flash Magisk v21.4 via TWRP?
Click to expand...
Click to collapse
Yes, I had to restart phone (or I have to longer waiting after configure and first start system)
Maybe someone will have a similar problem
5. Change the Magisk extension from .apk to .zip (Ex. Magisk_ver.apk --> Magisk_ver.zip)
Click to expand...
Click to collapse
I have to change on android (win10 I have a problem)
17. In the AP slot, select the TWRP Recovery (which is in .tar archive)
Click to expand...
Click to collapse
I selected ZIP file, not .tar
how to knw which firmware download its 2022
thanks for this guide! work well after 2 tried, also to answer the comment above me, you have to download the firmware from november 2020.
Спасибо!