This thread outlines the exact steps in installing a custom ROM on your Huawei Honor Note 10 device with either EMUI 8 or EMUI 9. You can install and run TWRP on both EMUI and or EMUI 9.
Make sure to follow this guide precisely, as order matters. At the end, I will post an explanation of why we need to execute these steps. I spent an entire weekend of trial and error on my Huawei Honor Note 10, and now I have figured out the ins and outs so you don't have to. You're welcome
Prerequisites
Huawei Honor Note 10 device, either on stock ROM or rooted (doesn't matter)
MicroSD card (formatted exFAT or FAT, doesn't matter)
Bootloader unlock code for Huawei Honor Note 10 (follows a format like my own HBP38K14DBK2RNB4)
Computer with admin privileges
Before You Flash Anything
Back up, back up, back up! I am not responsible if you lose valuable or sensitive data. Your Huawei Honor Note 10 will factory reset a number of times (probably more) before you can get back up and running again. Either use TWRP to do this, or use HiSuite (not recommended but will work on a locked bootloader).
Remove your SIM card! Your carrier may get charged ridiculous amounts of fees if you have a limited data plan, such as 256MB (Canada has notoriously expensive phone plans, so Canadians beware). When you reboot, expect Huawei's stock ROM to use copious amounts of data on retrieving the latest version of bloatware and spyware.
Ensure you have stock recovery installed. If you don't, download the stock recovery image, place it in your Minimal ADB and Fastboot folder, then boot to download mode by holding the VOLUME DOWN button and simultaneously plug in in your Huawei Honor Note 10 device, then open Minimal ADB and Fastboot on your computer and run this command:
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
Steps to Install Custom ROM on Huawei Honor Note 10
Download the EMUI 9 stock ROM and place the dload folder on your MicroSD card
Boot to (stock) recovery by holding down the VOLUME UP, VOLUME DOWN, and POWER buttons at the same time. The update should begin immediately. Wait patiently for your phone to reboot
Fill out the bloatware questionnaire by Huawei and download any and all updates under Settings. This will ensure you have the latest boot image. You will reboot at least once.
Once you have completed all the updates, reboot to download mode; press and hold the VOLUME DOWN button while you plug in your Huawei Honor Note 10 device to your computer
On your computer, download and open Minimal ADB and Fastboot
Run the following command:
Code:
fastboot oem unlock <code>
(where code corresponds to a format that looks like this: HBP38K14DBK2RNB4)
Confirm unlocking your bootloader by using the VOLUME keys, selecting yes, and pressing the POWER button. The Huawei Honor Note 10 device will now perform a factory reset
IMPORTANT step. DO NOT let the Huawei Honor Note 10 reboot. DO NOT. Impatiently wait for the low-level factory reset to complete and as soon as it does, enter download mode again by pressing the VOLUME DOWN key and plugging in the device again
Flash this TWRP recovery:
Code:
fastboot flash recovery_ramdisk HN10_Twrp.img
Reboot to recovery by holding the VOLUME UP and POWER buttons for over 5 seconds. You should see the TWRP logo, and it should boot up. It should boot up right away, so if TWRP hangs here on the TWRP logo, you need to skip back to step 2
IMPORTANT: wipe to factory reset. Wipe /system again via advanced wipe just to be safe
Install any custom ROM you wish via selecting a system image
IMPORTANT: disable_Dm-Verity_ForceEncrypt by installing this zip. If you don't do this, you won't be able to enter TWRP again
Optionally install magisk, titanium backup, and other magisk mods
Reboot system and profit
Update: 2021-04-06
Reboot to recovery by holding the VOLUME UP and POWER buttons for over 5 seconds. This should boot you to stock RECOVERY.
Wipe to factory reset. Confirm by typing "yes" (WARNING: this wipes your device)
Plug in your Huawei Honor Note 10 to your PC with ADB
Boot to DOWNLOAD mode by holding down the VOLUME DOWN button as soon as your Huawei Honor Note 10 reboots
Flash this TWRP recovery:
Code:
fastboot flash recovery_ramdisk HN10_Twrp.img
Reboot to recovery by holding the VOLUME UP and POWER buttons for over 5 seconds. You should see the TWRP logo, and it should boot up. It should boot up right away, so if TWRP hangs here on the TWRP logo, you need to skip back to step 2
Install any custom ROM you wish via selecting a system image (or zip file if you have EMUI 8)
Install magisk, titanium backup, and other magisk mods (note that you will NOT be able to boot to recovery after this; consider this you last chance to install any mods)
Reboot system and profit
Background and Explanation
When you first flash a ROM, even in EMUI 8, your Huawei Honor Note 10 encrypts /system to prevent third parties such as TWRP from mounting it. Hence, you may successfully boot to TWRP, but /system will be mounted as read-only. This is problematic, as it means you can't install any new ROMs (however, you can make a backup, which can be useful for backing up stock, encrypted /system partitions)
Because /system gets encrypted, it means you have to wipe /system completely. Doing a factory reset (low-level) does this, once you unlock your bootloader. However, if you were to let your Huawei Honor Note 10 boot, then the stock ROM would, by default, encrypt /system, forcing you to start this process all over again (as TWRP will, in most cases, not even boot with an encrypted /system). If your TWRP hangs on the TWRP logo, your /system partition is likely encrypted. You need to factory reset, install TWRP again, and then wipe /system, followed by installing the Disable_Dm-Verity_ForceEncrypt_01.15.2020.zip script.
ROMs I Tested That Work (well)
Resurrection Remix 7 (openKirin)
I hope this guide helps other fellow Huawei Honor Note 10 owners. If you have any questions, please also make sure to include your EMUI version and steps taken so that I can best help you. I hope that I have saved some of you trouble when updating to EMUI 9 and also helped to explain why updating can become so tedious.
Thank you for the instructions! I've got some questions...
ForgottenSolstace said:
IMPORTANT: wipe to factory reset. Wipe /system again via advanced wipe just to be safe
Install any custom ROM you wish via selecting a system image
Click to expand...
Click to collapse
During these steps, I saw the error messages like these:
Code:
Updater process ended with ERROR:7
Error installing zip file '/sdcard/RR-P-v7.0.2-20200202-ravel-Unoffical.zip'
and
Code:
Failed to mount '/cust' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/odm' (Invalid argument)
Failed to mount '/product' (Invalid argument)
I tried getting into fastboot mode and flash the CUST.img, VENDOR.img, ODM.img and PRODUCT.img but failed with the error message "FAILED (remote: Command not allowed)", what should I do?
null00005 said:
Thank you for the instructions! I've got some questions...
During these steps, I saw the error messages like these:
Code:
Updater process ended with ERROR:7
Error installing zip file '/sdcard/RR-P-v7.0.2-20200202-ravel-Unoffical.zip'
and
Code:
Failed to mount '/cust' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/odm' (Invalid argument)
Failed to mount '/product' (Invalid argument)
I tried getting into fastboot mode and flash the CUST.img, VENDOR.img, ODM.img and PRODUCT.img but failed with the error message "FAILED (remote: Command not allowed)", what should I do?
Click to expand...
Click to collapse
Yep, so it sounds like you have an encrypted /data.
Make sure you can safely wipe the entire device, then try the following in download mode:
Bash:
fastboot erase userdata
(Note: this will erase everything on /data)
Then boot to TWRP again. Check the logs and try again.
ForgottenSolstace said:
Yep, so it sounds like you have an encrypted /system.
Make sure you can safely wipe the entire device, then try the following in download mode:
Bash:
fastboot erase userdata
Then boot to TWRP again. Check the logs and try again.
Click to expand...
Click to collapse
How do I wipe the entire device? I have done step 8 properly (get into fastboot immediately after low-level factory reset completes) and wiped system in TWRP, but still get the error messages.
null00005 said:
How do I wipe the entire device? I have done step 8 properly (get into fastboot immediately after low-level factory reset completes) and wiped system in TWRP, but still get the error messages.
Click to expand...
Click to collapse
Bash:
fastboot erase userdata
That will wipe /data.
Since you can also boot to TWRP, then try wiping /system, cache, and dalvik (factory reset). If you can also wipe /data, then that might also work in TWRP, depending on which version you're using.
ForgottenSolstace said:
Bash:
fastboot erase userdata
That will wipe /data.
Since you can also boot to TWRP, then try wiping /system, cache, and dalvik (factory reset). If you can also wipe /data, then that might also work in TWRP, depending on which version you're using.
Click to expand...
Click to collapse
After reinstalling the stock ROM and unlock bootloader and flash TWRP again, I performed "fastboot erase system" and "fastboot erase userdata" in fastboot, then wiped Dalvik, cache, Cust, Data, system, Product and Version in TWRP. However, I am still getting the "Failed to mount '/odm' (Invalid argument)" error message
I can't wipe odm in TWRP since there is no such option, and I can't perform "fastboot erase odm" as it shows up an error message saying "FAILED (remote: Command not allowed)". What should I do now?
null00005 said:
After reinstalling the stock ROM and unlock bootloader and flash TWRP again, I performed "fastboot erase system" and "fastboot erase userdata" in fastboot, then wiped Dalvik, cache, Cust, Data, system, Product and Version in TWRP. However, I am still getting the "Failed to mount '/odm' (Invalid argument)" error message
I can't wipe odm in TWRP since there is no such option, and I can't perform "fastboot erase odm" as it shows up an error message saying "FAILED (remote: Command not allowed)". What should I do now?
Click to expand...
Click to collapse
If you roll back to stock and unlock your bootloader again, then you don't need to do fastboot erase userdata because "factory reset low-level" will perform that once you unlock your bootloader again. So you should be able to flash TWRP, boot fine (only that one time), install whatever ROM you want, flash magisk, and boot (note: on EMUI9, you must reboot to recovery, as boot_ramdisk only exists in EMUI8).
In the past, I have ignored the message "failed to mount '/odm'" and still had success; just pay attention to the status code at the end when you install /system. Don't bother wiping odm, as we really care about mounting /system. Perform a factory reset just to be safe, and feel free to wipe /data, but it won't matter if you already performed a factory-reset (low-level) from unlocking your bootloader again.
Try installing your ROM of choice from TWRP despite this error, flashing magisk, and confirm if that works.
ForgottenSolstace said:
This thread outlines the exact steps in installing a custom ROM on your Huawei Honor Note 10 device with either EMUI 8 or EMUI 9. You can install and run TWRP on both EMUI and or EMUI 9.
ROMs I Tested That Work (well)
Resurrection Remix 7 (openKirin)
Click to expand...
Click to collapse
Hi, how about root with magisk in this rom?!
TheFastGT said:
Hi, how about root with magisk in this rom?!
Click to expand...
Click to collapse
I second that. Magisk installed in boot.img but ROM doesn't recognize root, installing SuperSU says done but no result. Once I got SuperSU to get into stage where it said that boot might take longer and it was recognized but I can't replicate that anymore.
jazzzy said:
I second that. Magisk installed in boot.img but ROM doesn't recognize root, installing SuperSU says done but no result. Once I got SuperSU to get into stage where it said that boot might take longer and it was recognized but I can't replicate that anymore.
Click to expand...
Click to collapse
Just done....you need to install magisk in this:
RECOVERY_RAMDIS.img
then flash via fastboot and reboot...
TheFastGT said:
Just done....you need to install magisk in this:
RECOVERY_RAMDIS.img
then flash via fastboot and reboot...
Click to expand...
Click to collapse
so I open Magisk app and patch RECOVERY_RAMDIS.img, then flash RECOVERY_RAMDIS.img and after that flash TWRP ? TWRP won't overwrite RECOVERY_RAMDIS.img ?
jazzzy said:
so I open Magisk app and patch RECOVERY_RAMDIS.img, then flash RECOVERY_RAMDIS.img and after that flash TWRP ? TWRP won't overwrite RECOVERY_RAMDIS.img ?
Click to expand...
Click to collapse
I've a Honor Note 10 and i haven't TWRP installed, i use stock recovery and Openkirin rom...
How can I unlock my bootloader?
Darj said:
How can I unlock my bootloader?
Click to expand...
Click to collapse
HCU client
TheFastGT said:
HCU client
Click to expand...
Click to collapse
Thanks.. this is the only device I have so I wanted to ask what would happen if I mess it up
TheFastGT said:
HCU client
Click to expand...
Click to collapse
And once I unlock the bootloader using HCU client, do I have to follow the steps above or can I just install a custom recover how you'd do on any phone?
@Darj , did you manage to sort out rooting your Huawei Honor Note 10? I've updated the installation steps to reflect the shortened steps I last took to get Magisk running (downgraded to EMUI8 on my Huawei Honor Note 10 to try to preserve TWRP).
Hopefully, we'll see more ROMS from the OpenKirin project, as the latest security patch is almost a year old on EMUI8.
@ForgottenSolstace not yet. I want to make sure I have all the informations I need before spending money to unlock the bootloader
@Darj , it only costs 15USD to unlock your Huawei Honor Note 10. Why not go ahead and try?
I assure you that the effort is much worth it; Stock ROM is bloated with all kinds of spyware from the Chinese government. When you install AOSP, you can actually secure your phone following the updated instructions which encrypts /data.
Let me know if you have any questions. Happy to help
Hi ...got problem using twrp?
Related
Dear friends I need help!
I've tried to flash my tablet but I've got an error message while flashing Katkiss 6.0
What I did:
downloaded Rom.(md5sum is OK)
my bootloader is ww_epad-11.4.1.17-20140711
recovery CWM v6.0.5.0
previous rom zoombi pop
/format data
wipe data factory reset
install zip from sd card. (from internal storage or micro sd card)
And I have got the following error (in attachement)
Please help, my tablet boot only recovery now.
Thanks in advance for the help
trying to boot in fastboot mode when children let me try that...
Edit: fastboot ok.
I placed the the files
KatKiss-6.0_TF701T_033.zip
open_gapps-arm-6.0-pico-20170120.zip
UPDATE-SuperSU-v2.79-20161211114519.zip
In
C:\Program Files (x86)\Minimal ADB and Fastboot
ok I don't know how to proceed now.
Seems I cannot change the recovery from CMW to TWRP,
My bootloader is 11.4.1.17 and the tutorial to install TWRP says in capital red:
MUST BE ON A BOOTLOADER 11.4.1.27, 11.4.1.29 or 11.4.1.30
So how can I do?
I there a way to upgrade the bootloader to be able to install TWRP?
Or should I Flash the custom rom from fastboot?
My TF701 in not booting anymore.... only bootloader and recovery CMW
the positive thing is :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
15C3E10090400000011FA8580 fastboot
Please help
I have been able to flash CROMI X (unfortunately with strong battery drain) so CMW is able to flash but for some reasons not Katkiss 6.0.
I have been told that my problem is not ROM related... So it is recovery related?
What is the better option to get katkiss on my tablet? Flash the recovery to get TWRP even if my bootloader is 11.4.1.17 and the tutorial to install TWRP says in capital red:
MUST BE ON A BOOTLOADER 11.4.1.27, 11.4.1.29 or 11.4.1.30????
There is a technical reason about this warning?
Edit: I found this on an old post:
You can try this:
Download the stock recovery from here: http://droidbasement.com/db-blog/?p=3210
Copy the image to your fastboot folder.
Download the Asus firmware, unzip the file once and copy it to your internal SD.
Boot tablet into fastboot
Issue this command
Code:
fastboot boot recovery.img
Note: Do not flash the recovery, just boot it.
It should recognize the firmware file on your tablet and flash it.
Click to expand...
Click to collapse
Would this method work to get the latest stock rom from Asus?
Got your PM and will try to find some time at work today. Hang in there and don't do anything to make it worse
Ok, work was crazy busy so it took a bit longer.
If you flash a recovery that is incompatible with the bootloader nothing happens. Until you use the recovery... That could permanently brick the tablet. So heed the warnings, they are there for a reason.
Ok, let's try to get you on the latest bootloader. It's no suprise at all that nothing boots if you try to flash a Android 6 rom on an Android 4 bootloader....
Download either WW or US package from here: https://forum.xda-developers.com/showpost.php?p=61045480&postcount=2
That zip contains the latest bootloader and a compatible TWRP recovery. Flash the zip in your current recovery just like any rom, then reboot.
When you flash a bootloader or recovery you actually write those files to the staging partition. On the next boot the bootloader will unpack it and write everything to it's proper place.
So it's essential that you flash, then reboot. Does not matter that the boot does not go anywhere. The first part, flashing the contents of /staging to it's partition(s), will happen anyway.
You should see a brief blue bar filling up when that happens. It does not take long.
Boot back into fastboot and check your bootloader version.
Enter recovery through RCK and that should be TWRP now.
Then format /data. Do not wipe it, format it. Do not interrupt it. Wait for it to finish even if it takes an hour (a full battery is a must before you start this). The format command is under the Wipe menu.
Unfortunately the formatting in this kanged TWRP is pretty buggy, but I still like it better than CWM.... If you get lots of error messages after the format (cannot mount this, cannot mount that) go into Wipe > Advanced > select Data > Change or repair file system > Change file system > choose ext3 and execute
Note: The button you have to swipe is pretty "sticky". Swipe it slowly and fully
Reboot to recovery
Go back into Wipe > Advanced etc and change the file system back to ext4
Reboot to recovery
Now everything should be ok, try to mount/unmount data.
Finally you are ready to flash Katkiss
If the bootloader flash does not work, we can try to flash Asus firmware in fastboot, but try the above first.
berndblb said:
Ok, work was crazy busy so it took a bit longer.
If you flash a recovery that is incompatible with the bootloader nothing happens. Until you use the recovery... That could permanently brick the tablet. So heed the warnings, they are there for a reason.
Ok, let's try to get you on the latest bootloader. It's no suprise at all that nothing boots if you try to flash a Android 6 rom on an Android 4 bootloader....
Download either WW or US package from here: https://forum.xda-developers.com/showpost.php?p=61045480&postcount=2
That zip contains the latest bootloader and a compatible TWRP recovery. Flash the zip in your current recovery just like any rom, then reboot.
When you flash a bootloader or recovery you actually write those files to the staging partition. On the next boot the bootloader will unpack it and write everything to it's proper place.
So it's essential that you flash, then reboot. Does not matter that the boot does not go anywhere. The first part, flashing the contents of /staging to it's partition(s), will happen anyway.
You should see a brief blue bar filling up when that happens. It does not take long.
Boot back into fastboot and check your bootloader version.
Enter recovery through RCK and that should be TWRP now.
Then format /data. Do not wipe it, format it. Do not interrupt it. Wait for it to finish even if it takes an hour (a full battery is a must before you start this). The format command is under the Wipe menu.
Unfortunately the formatting in this kanged TWRP is pretty buggy, but I still like it better than CWM.... If you get lots of error messages after the format (cannot mount this, cannot mount that) go into Wipe > Advanced > select Data > Change or repair file system > Change file system > choose ext3 and execute
Note: The button you have to swipe is pretty "sticky". Swipe it slowly and fully
Reboot to recovery
Go back into Wipe > Advanced etc and change the file system back to ext4
Reboot to recovery
Now everything should be ok, try to mount/unmount data.
Finally you are ready to flash Katkiss
If the bootloader flash does not work, we can try to flash Asus firmware in fastboot, but try the above first.
Click to expand...
Click to collapse
Thanks a lot to take time to help me.
Will try that tonight and I'll let you know the result.
Thanks a lot!
It was just like you said.
I had to format to ext3 and ext4 because I had errors.
Battery seems to be very good. Just the screen display is very white, needs color saturation and contrast I guess...
Thanks again you save my tablet.
Now that's what I like to read! :cyclops:
Hi,
i thought I would make a new tread for that,because some have problems with it and it is clearer.
You need:
Firmware B533/B530/B528/B520/B511 or B510
HuRUpdater 0.3 for Edison AL10
IMG Files
Twrp for Oreo
This Twrp works only with Oreo and not with Nougat!
http://pro-teammt.ru/firmware-database/?firmware_model=edi&firmware_page=0
HuRUpdater 0.3 only for Edison AL10 Link here Thanks goes to zxzo0o for this Tool
Img Files Recovery,Kernel,Ramdisk https://www.androidfilehost.com/?fid=674106145207497141
Download all Files:Three Firmware Files,Img Files.zip and HuRUpdater0.3
Extract the IMG Files with Winzip,Rar...
Copy the three Firmware files,HuRUpdater0.3 and the Stockrecovery in a Folder on MicroSD on your Honor Note 8.Rename the RECOVERY_RAMDIS.img to recovery.img before copy in this Folder!
Copy KERNEL.img,RAMDISK.img and RECOVERY_RAMDIS.img in your ADB Folder for later.
Requirements:
You have to be on B359 Unlocked Bootloader and have Twrp installed!(Use Twrp for Nougat)
Instructions:
Boot into Twrp and wipe all:Format Data with "Yes"(Do you have a mistake while booting into the Erecovery and Format Data,you have the Option Format Data Partition,if an error occurs in Twrp)
Boot in Twrp and Format Data with "Yes" again.
Reboot after Format Data in Twrp again.
Format in advanced Wipe:System,Data,Cache,Dalvik Cache and Cache and reboot into Twrp.
Install the HuRUpdater0.3 in Trwp and follow the instructions.
After installing reboot into Bootloader,the Bootloader is locked.
Unlock the Bootloader with your Unlockcode.
In my case:My Phone boot not into System and it will display an error white background picture with red text and Notyfication Led flashes red.If not and your Phone boot into System skip this step.
Reboot into Bootloader and flash KERNEL.img,RAMDISK.img and RECOVERY_RAMDIS.img via ADB.
fastboot flash ramdisk RAMDISK.img
fastboot flash kernel KERNEL.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot reboot
The Phone boot not into System,make a Factory Reset with Volume up and Power Button.(shows Chinese Recovery)
After Reset Boot,if your sim card does not work make a Factory Reset(Low Level Reset)Into Settings Factory Reset with Internal Memory.
The Phone Boot and all works,i test it with B510,B511 and B520
I am on B533 with Security Patch August 2018
If you will go back to Android 7 B359,boot into Erecovery and restore via wifi to B359.
I hope you understand my Bad English!
I think there will be Twrp soon, for the Mate 8 with Emui 8 there is already one on the Chinese Page.
https://cn.club.vmall.com/thread-16048510-1-2.html
That should work on the HN8.
The Twrp HN8 for Android 7 is also from the Mate 8
Unfortunately, I can not log in.
Maybe someone has a Vmall account and can download it?
Then you can try it if it works
TWRP
letschky said:
I think there will be Twrp soon, for the Mate 8 with Emui 8 there is already one on the Chinese Page.
https://cn.club.vmall.com/thread-16048510-1-2.html
That should work on the HN8.
The Twrp HN8 for Android 7 is also from the Mate 8
Unfortunately, I can not log in.
Maybe someone has a Vmall account and can download it?
Then you can try it if it works
Click to expand...
Click to collapse
Here is the File that you requested from the link. I have not tested it myself. Good luck with your testing!
Download huawei-nxt-al10-em8_0-twrp3.2.1-8.5.21.img
letschky said:
Hi,
i thought I would make a new tread for that,because some have problems with it and it is clearer.
You need:
Firmware B520/B511 or B510
HuRUpdater 0.3
IMG Files
Downloads:
http://pro-teammt.ru/firmware-database/?firmware_model=edi&firmware_page=0
HuRUpdater 0.3 Link here Thanks goes to zxzo0o for this Tool
Img Files Recovery,Kernel,Ramdisk https://www.androidfilehost.com/?fid=674106145207497141
Download all Files:Three Firmware Files,Img Files.zip and HuRUpdater0.3
Extract the IMG Files with Winzip,Rar...
Copy the three Firmware files,HuRUpdater0.3 and the Stockrecovery in a Folder on MicroSD on your Honor Note 8.Rename the RECOVERY_RAMDIS.img to recovery.img before copy in this Folder!
Copy KERNEL.img,RAMDISK.img and RECOVERY_RAMDIS.img in your ADB Folder for later.
Requirements:
You have to be on B359 Unlocked Bootloader and have Twrp installed!(For Android 8 There is no Twrp available yet)
Instructions:
Boot into Twrp and wipe all:Format Data with "Yes"(Do you have a mistake while booting into the Erecovery and Format Data,you have the Option Format Data Partition,if an error occurs in Twrp)
Boot in Twrp and Format Data with "Yes" again.
Reboot after Format Data in Twrp again.
Format in advanced Wipe:System,Data,Cache,Dalvik Cache and Cache and reboot into Twrp.
Install the HuRUpdater0.3 in Trwp and follow the instructions.
After installing reboot into Bootloader,the Bootloader is locked.
Unlock the Bootloader with your Unlockcode.
In my case:My Phone boot not into System and it will display an error white background picture with red text and Notyfication Led flashes red.If not and your Phone boot into System skip this step.
Reboot into Bootloader and flash KERNEL.img,RAMDISK.img and RECOVERY_RAMDIS.img via ADB.
fastboot flash ramdisk RAMDISK.img
fastboot flash kernel KERNEL.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot reboot
The Phone boot not into System,make a Factory Reset with Volume up and Power Button.(shows Chinese Recovery)
After Reset Boot,if your sim card does not work make a Factory Reset(Low Level Reset)Into Settings Factory Reset with Internal Memory.
The Phone Boot and all works,i test it with B510,B511 and B520
I am on B520 with Security Patch June 2018
If you will go back to Android 7 B359,boot into Erecovery and restore via wifi to B359.
I hope you understand my Bad English!
Click to expand...
Click to collapse
Please wen will OTA release. Thanks
Sent from my EDI-AL10 using Tapatalk
TITAN-23 said:
Here is the File that you requested from the link. I have not tested it myself. Good luck with your testing!
Download huawei-nxt-al10-em8_0-twrp3.2.1-8.5.21.img
Click to expand...
Click to collapse
Uuhh,thanks Man!!!
ok,i install Twrp first failed.(remote: Command not allowed)The Problem isif the phonefinder is activated via the Huaweikonto you can not flash twrp.
I make a Factory Reset in Settings with Internal Memory and flash Twrp again and works,i can boot into Twrp.
Problem Data Partition not mounted.
Ok,i format Data with "yes" reboot again into Twrp and Data is mounted.
I flash 2 Files from the 3 Firmwarefiles in Twrp.update_data_full_public.zip and update_full_EDI-AL10_all_cn.zip and the Phone boot into System.
Short set up and boot again in Twrp and Data Partition is mounted.
Now all I have to do is try to root,i hope it works.
Twrp is only Chinese and English Language!
First i make a Backup,you can backup all Partitions,System,Data,Boot,Cust,Vendor,Version,Product,cool.
Next i test root if the Backup Finish
letschky said:
ok,i install Twrp first failed.(remote: Command not allowed)The Problem isif the phonefinder is activated via the Huaweikonto you can not flash twrp.
I make a Factory Reset in Settings with Internal Memory and flash Twrp again and works,i can boot into Twrp.
Problem Data Partition not mounted.
Ok,i format Data with "yes" reboot again into Twrp and Data is mounted.
I flash 2 Files from the 3 Firmwarefiles in Twrp.update_data_full_public.zip and update_full_EDI-AL10_all_cn.zip and the Phone boot into System.
Short set up and boot again in Twrp and Data Partition is mounted.
Now all I have to do is try to root,i hope it works.
Twrp is only Chinese and English Language!
Click to expand...
Click to collapse
this is what i get:
target reported max download size of 471859200 bytes
sending 'recovery' (12460 KB)...
OKAY [ 0.275s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.298s
Voyebanm said:
this is what i get:
target reported max download size of 471859200 bytes
sending 'recovery' (12460 KB)...
OKAY [ 0.275s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.298s
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=76861896&postcount=6
I successfully rooted it with Magisk,i delete unessersay Apps,smaler icon Mod works,disable online China services in Music and Viedeoplayer,yeah
We wait your full manual! As always!
2 pages long
letschky said:
https://forum.xda-developers.com/showpost.php?p=76861896&postcount=6
Click to expand...
Click to collapse
I did follow that.
phonefinder is not activated .
I tried again , still the same error
Voyebanm said:
I did follow that.
phonefinder is not activated .
I tried again , still the same error
Click to expand...
Click to collapse
I had the same issue,i go into Settings and make Factory Reset with internal Memory.(Low Level Reset)
After reboot short setup and boot into Bootloader.The Twrp img is in the ADB Folder?Remame the Twrp to a shorter Name (TWRP_HN8.img)and flash it.
fastboot flash recovery_ramdisk TWRP_HN8.img
ivanox1972 said:
We wait your full manual! As always!
2 pages long
Click to expand...
Click to collapse
I will update later Today
I have one issue,setting does not work,i think i delete wrong file,aahh
@letschky
Now, I am on B511.
How to update from B511 to B520? please advise.
Thank you
letschky said:
ok,i install Twrp first failed.(remote: Command not allowed)The Problem isif the phonefinder is activated via the Huaweikonto you can not flash twrp.
I make a Factory Reset in Settings with Internal Memory and flash Twrp again and works,i can boot into Twrp.
Problem Data Partition not mounted.
Ok,i format Data with "yes" reboot again into Twrp and Data is mounted.
I flash 2 Files from the 3 Firmwarefiles in Twrp.update_data_full_public.zip and update_full_EDI-AL10_all_cn.zip and the Phone boot into System.
Short set up and boot again in Twrp and Data Partition is mounted.
Now all I have to do is try to root,i hope it works.
Twrp is only Chinese and English Language!
Click to expand...
Click to collapse
Hi,
Now I am able to install TWRP and boot in it and mount data no problem
after I rep-flashed the 2 files, Just a boot loop now.
I can now re-install B520 and boot no problem with Network working right away, but I lose TWRP after the installation and restarted the process with the same problem.
Now, I am on B511, I try to flash new twrp (huawei-nxt-al10-em8_0-twrp3.2.1-8.5.21.img)
But I still found error "remote: partition length get error".
dekwat said:
Now, I am on B511, I try to flash new twrp (huawei-nxt-al10-em8_0-twrp3.2.1-8.5.21.img)
But I still found error "remote: partition length get error".
Click to expand...
Click to collapse
this the new command:
fastboot flash recovery_ramdisk huawei-nxt-al10-em8_0-twrp3.2.1-8.5.21.img
Voyebanm said:
this the new command:
fastboot flash recovery_ramdisk huawei-nxt-al10-em8_0-twrp3.2.1-8.5.21.img
Click to expand...
Click to collapse
Yes, I try this command but I still found same error.
P.S. I'm not sure, this twrp can use for B511 or not.
Hi guys,
I tried to root my P9 today but now I'stuck with a bricked P9.
I can fastboot and use TWRP
The main problem is that I get always failed to mount /data (Invalid argument)
I've tried to Change the file system with TWRP and Format Data but nothing
I've tried the unbrick procedure with Multi-Tool and an old firmware but nothing
Code:
19:21:37: Unbricking started. Your computer may freezes during the process.
19:21:37: flash boot "C:\Users\franc\Desktop\Nuova cartella\boot.img"
19:21:37: The Boot image is flashing successfully
19:21:37: flash system "C:\Users\franc\Desktop\Nuova cartella\system.img"
19:21:53: target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (449861 KB)...
OKAY [ 10.490s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 10.551s
19:21:53: Error#1
19:21:53: flash cust "C:\Users\franc\Desktop\Nuova cartella\cust.img"
19:21:58: Error! You are trying to flash the wrong image!
19:21:58: flash recovery "C:\Users\franc\Desktop\Nuova cartella\recovery.img"
19:22:00: The Recovery image is flashing successfully
19:22:00: Completed
19:22:00: Something went wrong (((
bomba697 said:
Hi guys,
I tried to root my P9 today but now I'stuck with a bricked P9.
I can fastboot and use TWRP
The main problem is that I get always failed to mount /data (Invalid argument)
I've tried to Change the file system with TWRP and Format Data but nothing
I've tried the unbrick procedure with Multi-Tool and an old firmware but nothing
Code:
19:21:37: Unbricking started. Your computer may freezes during the process.
19:21:37: flash boot "C:\Users\franc\Desktop\Nuova cartella\boot.img"
19:21:37: The Boot image is flashing successfully
19:21:37: flash system "C:\Users\franc\Desktop\Nuova cartella\system.img"
19:21:53: target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (449861 KB)...
OKAY [ 10.490s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 10.551s
19:21:53: Error#1
19:21:53: flash cust "C:\Users\franc\Desktop\Nuova cartella\cust.img"
19:21:58: Error! You are trying to flash the wrong image!
19:21:58: flash recovery "C:\Users\franc\Desktop\Nuova cartella\recovery.img"
19:22:00: The Recovery image is flashing successfully
19:22:00: Completed
19:22:00: Something went wrong (((
Click to expand...
Click to collapse
"P9" - EMUI 4 / Android MM, EMUI 5 / N or EMUI 8 / O
What was exacrly your full firmware name and number (like EVA-L09c532b505 or what)
"TWRP" - which/where from?
(diff TWRP installations must be used for MM, N or N), and if TWRP from TWRP site - that one is definitely not good for N and O
"root" - by SuperSU, Magisk or something else (hopefully not King.... tools or so)
So, from which Huawei firmware did you start, which steps did you perform and by which tools
Btw, rooting N by SuperSU or O by Magisk is pretty straightforward, but is important that proper, corresponding TWRPs are used.
And if anything goes wrong (brick or so) stock Boot partition (N) or stock Ramdisk partition (O) can be easily flashed over to go back
zgfg said:
"P9" - EMUI 4 / Android MM, EMUI 5 / N or EMUI 8 / O
What was exacrly your full firmware name and number (like EVA-L09c532b505 or what)
"TWRP" - which/where from?
(diff TWRP builds must be used for MM, N or N), and if TWRP from TWRP site - that one is definitely not good for N and O
"root" - by SuperSU, Magisk or something else (hopefully not King.... tools or so)
So, from which Huawei firmware did you start which steps did you perform and by which tools
Btw, rooting N by SuperSU or M by Magisk is pretty straightforward, but it is important that proper corresponding TWRPs are used.
And if anything goes wrong (brick or so) stock Boot partition (N) or stock Ramdisk partition (O) can be easily flashed over to go back
Click to expand...
Click to collapse
I'm sorry for the poor description but I was in panic.
Starting from EVA-L09C432B3xx, don't remember the exact version, N 5.0.1
TWRP 3.1.0.-1
SuperSU, https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258. I had big trouble trying to root because every time the phone rebooted before finishing the procedure.
I didn't use any tool at all for unlocking bootloader, flash recovery and root. Just adb and fastboot in cmd + TWRP.
BTW, I recovered the phone! Used DC-Phoenix to reset the phone from fastboot and then made a downgrade to b182.
PS: Why did you flash Cust?
For TWRP or to go back to stock Recovery, you only need to flash recovery (for N) or ramdisk_recovery (for O)
To flash root patch for SuperSU for N (or to restore back) you only need to flash boot partition, similarly for Magisk (O) ramdisk partution.
zgfg said:
PS: Why did you flash Cust?
For TWRP or to go back to stock Recovery, you only need to flash recovery (for N) or ramdisk_recovery (for O)
To flash root patch for SuperSU for N (or to restore back) you only need to flash boot partition, similarly for Magisk (O) ramdisk partution.
Click to expand...
Click to collapse
Because Multi-Tool 8 was asking to flash also CUST to apply unbrik procedure.
The problem was that I wasn't able to mount /data partition. Also from stock recovery I wasn't able to format /data, only wipe the cache
bomba697 said:
Because Multi-Tool 8 was asking to flash also CUST to apply unbrik procedure.
The problem was that I wasn't able to mount /data partition. Also from stock recovery I wasn't able to format /data, only wipe the cache
Click to expand...
Click to collapse
If you recovered and if you are on b182 now, you will hopefully receive OTA upgrades tp go back to N
Btw, working procedure for rooting N was described in thread
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
Again, if TWRP was not able to mount Data, was it really proper TWRP from XDA Huawei Nougat threads (adapred to support Huawei N and its encryption), like
https://forum.xda-developers.com/p9/development/twrp-t3565703
Some other TWRP 3.1.x.x, even declared for Huawei, maybe good for EMUI 4 / MM but not for EMUI 5 / N
EDIT: noticed that you fixed it through DC-Phoenix. Do you have a link where you found it and how to use? I don't mind downgrading coz I'm just gonna use the phone as a backup phone
I got the same issue. If you find an answer please tag me. I think i was using EVA-L19C636B180 Quite sure about the C636 part. TWRP 3.1.0.-3 and using SU but I can't recall the version
Quick background on mine:
I bricked my phone when I did a factory reset and deleted internal storage and accidentally deleted important files while doing so. I flashed a stock update from the warehouse and completely deleted the system instead. I then flashed Lineage ROM which reinstalled the system but now causes me to get stuck in bootup. When I installed Lineage ROM, I got the following error.
Attached photo
https://imgur.com/a/nx6U5bC
kazshizka said:
EDIT: ...DC-Phoenix. Do you have a link and how to use...
Click to expand...
Click to collapse
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
kazshizka said:
EDIT: noticed that you fixed it through DC-Phoenix. Do you have a link where you found it and how to use? I don't mind downgrading coz I'm just gonna use the phone as a backup phone
I got the same issue. If you find an answer please tag me. I think i was using EVA-L19C636B180 Quite sure about the C636 part. TWRP 3.1.0.-3 and using SU but I can't recall the version
Quick background on mine:
I bricked my phone when I did a factory reset and deleted internal storage and accidentally deleted important files while doing so. I flashed a stock update from the warehouse and completely deleted the system instead. I then flashed Lineage ROM which reinstalled the system but now causes me to get stuck in bootup. When I installed Lineage ROM, I got the following error.
Attached photo
https://imgur.com/a/nx6U5bC
Click to expand...
Click to collapse
I didn't use the method posted by @zgfg. What I did was: (this procedure is going to lock back your FRP setting and bootloader, so you can try it but at your own risk)
Use Multi-Tool 8 (https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923) to reinstall stock recovery and recovery2
Download https://www.dc-unlocker.com/downloads/get/jvObBBIo
Put the phone in fastboot
Use the FRP Erase option to recover/format /data (it cost you 15 credit, $15), it was successful
Take empty SD card formatted in NFTS
Put in dload folder the rollback UPDATE.APP file taken from http://download-c1.huawei.com/download/downloadCenter?downloadId=92765&siteCode=it and install it
Last, put in dload folder b182 UPDATE.APP file from http://download-c1.huawei.com/download/downloadCenter?downloadId=91783&siteCode=it
This functioned for me, you can try to skip step 5 and install directly b182.
zgfg said:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Click to expand...
Click to collapse
bomba697 said:
I didn't use the method posted by @zgfg. What I did was: (this procedure is going to lock back your FRP setting and bootloader, so you can try it but at your own risk)
Use Multi-Tool 8 (https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923) to reinstall stock recovery and recovery2
Download https://www.dc-unlocker.com/downloads/get/jvObBBIo
Put the phone in fastboot
Use the FRP Erase option to recover/format /data (it cost you 15 credit, $15), it was successful
Take empty SD card formatted in NFTS
Put in dload folder the rollback UPDATE.APP file taken from http://download-c1.huawei.com/download/downloadCenter?downloadId=92765&siteCode=it and install it
Last, put in dload folder b182 UPDATE.APP file from http://download-c1.huawei.com/download/downloadCenter?downloadId=91783&siteCode=it
This functioned for me, you can try to skip step 5 and install directly b182.
Click to expand...
Click to collapse
Will check out both methods. I'll try it through TWRP first since it should be easier to use an open bootloader rather than a locked one.
@bomba697 will reinstalling stock recovery fix my deleted system issue? coz I'm not sure if I flashed the custom ROM properly anymore
UPDATE:
Tried @bomba697 method and fixed my system but I skipped the FRP Erase portion. I just installed the stock recovery straight (thus not paying 15 credits) from the multi tool then rollback using dload then update to b182. Though it did change my system to C900 from C636.
Thank you very very much!!
kazshizka said:
UPDATE:
Tried @bomba697 method and fixed my system but I skipped the FRP Erase portion. I just installed the stock recovery straight (thus not paying 15 credits) from the multi tool then rollback using dload then update to b182. Though it did change my system to C900 from C636.
Thank you very very much!!
Click to expand...
Click to collapse
Happy that you found the solution! I tried directly flashing the rom but I wasn't able beacuse of the \data mount error.
I'm having trouble installing GSI on the Galaxy Tab A8 2021.
1.Dedicated TWRP Recovery in XDA data was released as Odin after bootloader.
2.I entered the TWRP recovery and there was a unable mount twrps error.
3.To solve the problem, I entered the Format Data of the Wipe section of the TWRP Recovery, entered yes, and initialized it. The problem has been solved since then.
4.To install GSI, I went to the Wipe item in TWRP Recovery and tried Swipe to factory Reset, then pressed Advanced Wipe, selected Dalbik/ART Cache,Metadata,Cache,Data,Internal Storage, and tried Swipe to Wipe.
5.Select Fastboot from the Reboot item in TWRP Recovery and enter Fastboot mode.
6.I ran Google Platform-tools_r33.0.3-windows on my computer and typed the command you see in the picture.
7.I ran Fastboot -w after flashing GSI, but I got an error and reboot my Galaxy Tab will boot indefinitely.
*The GSI ROM file used the 9/12 UNOFFICICAL arm64 bgs.img file of Lineage os19.1.
*The firmware version of the Galaxy Tab is the most recent version.
Please check if there is a problem with my installation method.
I'm a person who doesn't know how to use English, so I used a translator. Thank you for your understanding.
In the step #7, instead of run "fastboot -w" try to flash the system file with "fastboot flash system nameofthe.img". After that, reboot in recovery again and format data like you usually do with TWRP, finally try to reboot the system.
Dear guys,
I'm in a situation where I don't know what's best to do, honestly I was left with android 11 where everything was much simpler.
my xiaomi started from OEM miui 13 on which I installed twrp 3.7 with the " Onekey inject TWRP " method, I understood that the method was wrong with android 12 but the phone worked (in recovery mode it did not read the touch).
I loaded the same twrp from fastboot mode, I do a backup of everything (copied to the computer), and trying to install miui.eu, but the phone gave me the following "error "ERROR: 1 / can not mount system".
I tried with the twrp by skkk, launched from fastboot mode, I started the dirty installation of the miui.eu and when finish to install I pressed "Install Recovery Ramdisk".
I restart the phone but after two restarts it returns to recovery, i thought the problem was the dirty installation, so i went to "format data".
From this moment the phone restarts only in recovery, the phone memory is encrypted and cannot find any content (the phone has no password set), connecting it to the computer I cannot copy any content but it is read from fastboot mode.
The errors that appear on the phone are "Failed to mount '/system_ext' '/product' '/vendor' '/odm' (Invalid argument)"
How should you continue? I have no problem to losing any data.
do you recommend to flash a fastboot rom with Miflash?
Thanks a lot