Considering that lately there were quite a few hard-bricks, I invite the users that experienced such bricks to post more details here.
Please use this model when you post :
Similar discussion is done in Mate 10 forums ( https://forum.xda-developers.com/mate-10/how-to/discussion-hard-brick-infos-t3789044 ) too I request all to share their experience.
Please also read this thread made by @ante0 - > https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241 <- you will also find a tool that will help you check the xloader.img
Upload your xloader.img to any file hosting and share us the link so that we can together find a solution for the issues.
1) Device = device codename (COL-L29 C432, AL-10 C00, etc)
2) Firmware and Region before Brick = exact firmware and region (B134 C636, B141 C432)
3) Firmware that lead to brick = The firmware version that lead to bricking
4) You were trying to just update your device or you were also trying to rebrand
5) Your device was rebranded or used stock region?
6) Other infos of modifications, update procedures, etc that you did before bricking
7) xloader.img image
8) Result of Xloader.img check tool ( https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241 ) if possible screen shots.
Thank you and please stay on topic!
Credits for @Pretoriano80 for the idea and @ante0 for the xloader check tool.
1) Device = Honor 10 (COL-L29)
2) Firmware and Region before Brick = COL-L29 8.1.0.106 (SP6C900)
3) Firmware that lead to brick =COL-L29C432B120 (8.1.0.120)
4) Trying to just update the device and also trying to rebrand from SP6C900 to C432
5) Used stock region and not rebranded.
6) Used HuRUpdater to update from COL-L29 8.1.0.106 (SP6C900) to COL-L29C432B120 but gave wrong device info so tried to use no check recovery from Honor V10 but it failed so again tried HuRUpdater to flash COL-L29C432B104 and boom got a hard bricked device. Except black screen nothing happened.
DELETED
@flattervieh , @NekoMichi , @mrspeccy , @awells845 can you please share your experience while updating.
My device did not brick, and the update was applied successfully.
1. Device - Honor 10 (COL-L29)
2. FW before update - COL-L29C432B120 (8.1.0.120)
3. FW after update - COL-L29C432B145 (8.1.0.145)
4. Update only, did not attempt to rebrand.
5. Device had not been rebranded beforehand.
6. Device was originally rooted by flashing ramdisk image from here.
Magisk version 16.4
Magisk manager version 5.8.3 (129)
Xposed 3.1.4 was also installed
Custom recovery used: TWRP
HuRUpdater used: Version 0.3
Prior to updating, I had removed all passwords/fingerprints/face unlock data.
After the installation was complete in TWRP, I cleared cache and Dalvik cache before rebooting.
I haven't used Xloader.
miststudent2011 said:
1) Device = Honor 10 (COL-L29)
2) Firmware and Region before Brick = COL-L29 8.1.0.106 (SP6C900)
3) Firmware that lead to brick =COL-L29C432B120 (8.1.0.120)
4) Trying to just update the device and also trying to rebrand from SP6C900 to C432
5) Used stock region and not rebranded.
6) Used HuRUpdater to update from COL-L29 8.1.0.106 (SP6C900) to COL-L29C432B120 but gave wrong device info so tried to use no check recovery from Honor V10 but it failed so again tried HuRUpdater to flash COL-L29C432B104 and boom got a hard bricked device. Except black screen nothing happened.
Click to expand...
Click to collapse
Well, HuRUpdater is not intended for rebrand and that was your first mistake (even if it wasn't the real problem).
Second, you tried to downgrade instead of trying to rebrand with NoCheck Recovery (that would have fixed your initial issue).
Third, there's not much to do for your device now and only a fix/replacement from Huawei will revive it.
You should check the xloader.img for COL-L29C432B120 and COL-L29C432B104, at least you could understand if xloader was the culprit or just the downgrade (mixed-up operations you did previously).
Pretoriano80 said:
Well, HuRUpdater is not intended for rebrand and that was your first mistake (even if it wasn't the real problem).
Second, you tried to downgrade instead of trying to rebrand with NoCheck Recovery (that would have fixed your initial issue).
Third, there's not much to do for your device now and only a fix/replacement from Huawei will revive it.
You should check the xloader.img for COL-L29C432B120 and COL-L29C432B104, at least you could understand if xloader was the culprit or just the downgrade (mixed-up operations you did previously).
Click to expand...
Click to collapse
Well, HuRUpdater is not intended for rebrand and that was your first mistake -- >Mine shows region as EU only which is COL-L29 so I dont think I am trying to rebrand (may be wrong).
Second, you tried to downgrade instead of trying to rebrand with NoCheck Recovery --> Tried with the same build but it did not work just failed installation, so tried with lower build it too gave same error.
You should check the xloader.img for COL-L29C432B120 and COL-L29C432B104 --> Currently dont have the files will re download and check them.
BTW do you have any idea of how to check extract currently installed build Xloader from mobile ?
miststudent2011 said:
Well, HuRUpdater is not intended for rebrand and that was your first mistake -- >Mine shows region as EU only which is COL-L29 so I dont think I am trying to rebrand (may be wrong).
Second, you tried to downgrade instead of trying to rebrand with NoCheck Recovery --> Tried with the same build but it did not work just failed installation, so tried with lower build it too gave same error.
You should check the xloader.img for COL-L29C432B120 and COL-L29C432B104 --> Currently dont have the files will re download and check them.
BTW do you have any idea of how to check extract currently installed build Xloader from mobile ?
Click to expand...
Click to collapse
2) Firmware and Region before Brick = COL-L29 8.1.0.106 (SP6C900) <- this looks like demo unit or something,clearly not C432 (hw/eu).
So it seems that you tried to flash a firmware not intended for your region. Or maybe i'm missing something?
Pretoriano80 said:
2) Firmware and Region before Brick = COL-L29 8.1.0.106 (SP6C900) <- this looks like demo unit or something,clearly not C432 (hw/eu).
So it seems that you tried to flash a firmware not intended for your region. Or maybe i'm missing something?
Click to expand...
Click to collapse
Yes it is a Demo unit , In settings while I looked for device info it showed as International and hw/eu . So I am assuming its a EU variant(not sure).
miststudent2011 said:
Yes it is a Demo unit , In settings while I looked for device info it showed as International and hw/eu . So I am assuming its a EU variant(not sure).
Click to expand...
Click to collapse
The correct procedure would have been this:
1)Rebrand with NoCheck Recovery from demo to C432
2)Flash a FullOTA for C432,profit!
miststudent2011 said:
BTW do you have any idea of how to check extract currently installed build Xloader from mobile ?
Click to expand...
Click to collapse
From a terminal:
dd if=/dev/block/sda of=/sdcard/xloader.img
(This requires TWRP at least)
Then transfer to computer to check manually or:
You can then run the xxd command, though this requires busybox
xxd -s 0x1a8 -l 1 /sdcard/XLOADER.img | grep '000001a8: 01'> /dev/null && echo "01 XLOADER. Safe when going 01 to 01, 01 to 02. 02 to 01 WILL brick" || echo "02 XLOADER. Safe when going 02 to 02. 02 to 01 WILL brick
ante0 said:
From a terminal:
dd if=/dev/block/sda of=/sdcard/xloader.img
(This requires TWRP at least)
Then transfer to computer to check manually or:
You can then run the xxd command, though this requires busybox
xxd -s 0x1a8 -l 1 /sdcard/XLOADER.img | grep '000001a8: 01'> /dev/null && echo "01 XLOADER. Safe when going 01 to 01, 01 to 02. 02 to 01 WILL brick" || echo "02 XLOADER. Safe when going 02 to 02. 02 to 01 WILL brick
Click to expand...
Click to collapse
Thanks for the command I will try it, can you also give commands to backup stock recovery before flashing twrp , and similar command for all other partitions
miststudent2011 said:
Thanks for the command I will try it, can you also give commands to backup stock recovery before flashing twrp , and similar command for all other partitions
Click to expand...
Click to collapse
For recovery you can actually do
dd if=/dev/block/bootdevice/by-name/erecovery_ramdisk of=/dev/block/bootdevice/by-name/recovery_ramdisk
This will write erecovery ramdisk to recovery ramdisk, as they both use the same image.
For other partitions you can use dd too, but they become rather large as dd copies the whole partition rather than just occupied data.
Example: dd if=/dev/block/bootdevice/by-name/system of=/sdcard/system.img
If it complains about /dev/block/bootdevice you have to use the full platform path or figure out whats linked to what.
You can 'cd' to /dev/block/platform/xxxxxxx/by-name/
Xxxxxx= platform dependent, not sure what Honor 10 uses.
Then use 'ls -la' there to show where symlinks go, and you should then see that system is linked to /dev/block/sdd59
Then you can just dd if=/dev/block/sdd59 of=/sdcard/system.img
miststudent2011 said:
Thanks for the command I will try it, can you also give commands to backup stock recovery before flashing twrp , and similar command for all other partitions
Click to expand...
Click to collapse
If you don't have busybox installed, you can open the xloader.img from sdcard with this app - > https://play.google.com/store/apps/details?id=com.kos.binaryviewer <- go to "000001a8" offset and check if it has the 01 or 02 switch.
ante0 said:
For recovery you can actually do
dd if=/dev/block/bootdevice/by-name/erecovery_ramdisk of=/dev/block/bootdevice/by-name/recovery_ramdisk
This will write erecovery ramdisk to recovery ramdisk, as they both use the same image.
For other partitions you can use dd too, but they become rather large as dd copies the whole partition rather than just occupied data.
Example: dd if=/dev/block/bootdevice/by-name/system of=/sdcard/system.img
If it complains about /dev/block/bootdevice you have to use the full platform path or figure out whats linked to what.
You can 'cd' to /dev/block/platform/xxxxxxx/by-name/
Xxxxxx= platform dependent, not sure what Honor 10 uses.
Then use 'ls -la' there to show where symlinks go, and you should then see that system is linked to /dev/block/sdd59
Then you can just dd if=/dev/block/sdd59 of=/sdcard/system.img
Click to expand...
Click to collapse
Do I need root for this or just stock is enough ? or as suggested above do i need twrp ?
Firmware for my version is not available so wanted to make sure before proceeding. Doesnt want to hard brick one more device.
miststudent2011 said:
Do I need root for this or just stock is enough ? or as suggested above do i need twrp ?
Firmware for my version is not available so wanted to make sure before proceeding. Doesnt want to hard brick one more device.
Click to expand...
Click to collapse
Root is mandatory if TWRP is not installed.
Pretoriano80 said:
Root is mandatory if TWRP is not installed.
Click to expand...
Click to collapse
Image link from your previous post is broken ?
miststudent2011 said:
Do I need root for this or just stock is enough ? or as suggested above do i need twrp ?
Firmware for my version is not available so wanted to make sure before proceeding. Doesnt want to hard brick one more device.
Click to expand...
Click to collapse
Pretoriano80 said:
Root is mandatory if TWRP is not installed.
Click to expand...
Click to collapse
And TWRP is fine if no root
dd works even with the adb enabled mankindtw recovery, so you would just need that if you don't want to flash TWRP.
But you will need one if them... I guess TWRP would be better as you can backup ramdisk that way and keep it stock.
But if Honor 10 was released with 8.1 I'm pretty sure it has a 02 xloader already, P20 has had it since the first firmware and its most likely why dc/fh doesn't work for it.
ante0 said:
And TWRP is fine if no root [emoji14]
dd works even with the adb enabled mankindtw recovery, so you would just need that if you don't want to flash TWRP.
But you will need one if them... I guess TWRP would be better as you can backup ramdisk that way and keep it stock.
But if Honor 10 was released with 8.1 I'm pretty sure it has a 02 xloader already, P20 has had it since the first firmware and its most likely why dc/fh doesn't work for it.
Click to expand...
Click to collapse
That's why i'm curious if COL-L29C432B104 has 01 or 02 xloader. [emoji6]
Pretoriano80 said:
That's why i'm curious if COL-L29C432B104 has 01 or 02 xloader. [emoji6]
Click to expand...
Click to collapse
Oh, it's 01
http://imgur.com/a/qMCjPDi
Related
HWOTA won't work with OREO, so we need to rollback manually with ADB.
this guide (more like just code memo) is for people who didn't backuped before update,
or can't go back to B183 directly by any reason (like dead capacitive keys).
What You Need to Read
[STF-L09C432] How to install Oreo on your H9
https://forum.xda-developers.com/honor-9/how-to/stf-l09c432-how-to-install-oreo-h9-t3707729
[GUIDE][REBRAND] Honor 9 [ANY REGION]
https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719/post75439859#post75439859
What You Need to Download
HWOTA (Windows tool)
Firmware Finder (Windows tool)
ADB and Fastboot (Windows tool)
C432B120 Firmware File
Stock NoCheck Oreo Recovery
What You Need to Have
unlocked bootloader and superuser, ADB.
adb push won't work, so you will need microSD card.
exFAT may not work on some ROMs (like Treble AOSP 8.0), so format it to FAT32.
What You Need to Do
1.
download B432C120 from Windows Version Firmware Finder and rename it (check [REBRAND] Honor 9 Thread).
why B120? bcuz it's the only firmware that leave capacitive keys and flashlights alive.
put them into microSD card root, with NoCheck Oreo Recovery .img (check How to install Oreo Thread).
insert microSD card to your phone and connect the phone to your PC and open ADB.
first of all,
Code:
adb shell
su
let's change recovery with NoCheck one first.
Code:
dd if=/storage/sdcard1/STF_RECOVERY_OREO_NoCheck.img of=/dev/block/bootdevice/by-name/recovery_ramdisk
dd if=/storage/sdcard1/STF_RECOVERY_OREO_NoCheck.img of=/dev/block/bootdevice/by-name/erecovery_ramdisk
note that 'sdcard1' maybe different, like 'E1F2-A123', base on your ROM. It's your sdcard's name.
We'll put Firmware into recovery cache and make stock recovery to flash it.
Code:
echo --update_package=/sdcard/update.zip > /cache/recovery/command
echo --update_package=/sdcard/update_data_public.zip >> /cache/recovery/command
echo --update_package=/sdcard/update_all_hw.zip >> /cache/recovery/command
reboot recovery
note that 'sdcard' is not 'sdcard1', so you don't have to change it to sth like E6F3-A496.
your phone will reboot 2, 3 times and will suggest low level format and download new firmware.
now go to fastboot and unlock the bootloader.
this will do low level format.
2.
now your phone is something like EMUI 8.0 Android 7.0, with broken build number.
do HWOTA (no need to do rebrand, just do firmware flash with update option) with C432B120 we downloaded before.
This will make your phone Stock C432B120.
3.
Let's Go back to B183, the newest Nougat ROM.
download Firmware Finder for Huawei app at Play Store.
choose C432B183 and update it with proxy.
maybe you got 'yet approved' error,
but there are quite numerous C432B183 so check every single one of it.
There is one that is flash-able.
4.
TADA, now you rollbacked your phone.
I think you can also rollback with Hisuite on PC, I did a few times to rollback from beta.
I don't like your guide because :
-You're flashing a B120 firmware which is not to rollback from oreo when there is already a B183 oreo's rollback available for this on FF.
-You have to flash it 2 times to fix your build version issue (maybe because it's not a rollback firmware).
Please note that your step 1 & 2 are the same, you just did hwota manually on step 1.
-You then updated from B120 to B150 when you could have directly updated to B183 not for oreo's rollback on FF.
Sorry.
nednapalm said:
I think you can also rollback with Hisuite on PC, I did a few times to rollback from beta.
Click to expand...
Click to collapse
Never tried that, but it would be much more simple and clear. This Thread will become useless though lol.
oslo83 said:
I don't like your guide because :
-You're flashing a B120 firmware which is not to rollback from oreo when there is already a B183 oreo's rollback available for this on FF.
-You have to flash it 2 times to fix your build version issue (maybe because it's not a rollback firmware).
Please note that your step 1 & 2 are the same, you just did hwota manually on step 1.
-You then updated from B120 to B150 when you could have directly updated to B183 not for oreo's rollback on FF.
Sorry.
Click to expand...
Click to collapse
1. isn't that rollback for beta B321 and disables capacitive keys and Flash lights with B360a?
2. that's the point of this guide, since HWOTA is not properly working with oreo. you can just change the strings inside the hwota.sh if you want to.
3. no you can't jump to B183 directly from B120, shows approve error. any other firmware except B150 shows the error, same to B183 from B150.
Thx for the opinions though.
TASON42 said:
1. isn't that rollback for beta B321 and disables capacitive keys and Flash lights with B360a?
Click to expand...
Click to collapse
Nope, it's a rollback from oreo B3xx.
It's still has to be tested if rolling back from B3xx to B183 mess with capacitives keys.
TASON42 said:
2. that's the point of this guide, since HWOTA is not properly working with oreo. you can just change the strings inside the hwota.sh if you want to.
Click to expand...
Click to collapse
...
TASON42 said:
3. no you can't jump to B183 directly from B120, shows approve error. any other firmware except B150 shows the error, same to B183 from B150.
Click to expand...
Click to collapse
Sorry but you are wrong : by using FF on B120, I can guarantee you that YOU CAN update to approved B183 using the full ota update ( the B183 one that is not to rollback).
TASON42 said:
Thx for the opinions though.
Click to expand...
Click to collapse
You're welcome, I didn't want to let bad guides posted without telling so.
oslo83 said:
Nope, it's a rollback from oreo B3xx.
It's still has to be tested if rolling back from B3xx to B183 mess with capacitives keys.
...
Sorry but you are wrong : by using FF on B120, I can guarantee you that YOU CAN update to approved B183 using the full ota update ( the B183 one that is not to rollback).
You're welcome, I didn't want to let bad guides posted without telling so.
Click to expand...
Click to collapse
With this you can do whatever you think is the only problem that is in Russian. http://4pda.ru/forum/index.php?showt...ost&p=69940847
---------- Post added at 07:53 PM ---------- Previous post was at 07:49 PM ----------
letterio said:
With this you can do whatever you think is the only problem that is in Russian. http://4pda.ru/forum/index.php?showt...ost&p=69940847
Click to expand...
Click to collapse
https://4pda.ru/forum/index.php?showtopic=833645&st=2400#entry69940847
I found out that We do can OTA to B183 directly, so I changed the GUIDE + some minor change.
2. now your phone is something like EMUI 8.0 Android 7.0, with broken build number. d
I didn't get this point. i mean with hwota (link you put in) we have just 2 options. update and rebrand. we have no choice for just flashing. sorry for my bad understanding.
ImHonor said:
I didn't get this point. i mean with hwota (link you put in) we have just 2 options. update and rebrand. we have no choice for just flashing. sorry for my bad understanding.
Click to expand...
Click to collapse
do update.
which version of B183 are we supposed to take? I choose the last one: 116404
but I'm not sure it's the correct one. (changelog tell it's a rollback firmware)
seems the good one is the 111176 (changelog is not about rollback)
Don't follow this outdated OP and thread which were never right in the first place.
For rollback use HiSuite or HuRUpdater.
I am currently on Android Nougat stock.
The bootloader has been unlocked and TWRP recovery has been installed.
I would like to update to Oreo but have been unable to do so.
This guide was followed [urlhttp://www.droid views.com/install-android-8-0-oreo-based-emui-8-0-huawei-mate-9/][/url] (but was unable to get past option 4) (I left a space after droid as the link is getting blocked, just put ********** together.)
''Double-click on the Replace_Recovery.bat file in the extracted HWOTA8 folder. This will install TWRP recovery on your device.''
I keep getting a failed notification when trying to do so. The handset was in fastboot mode but refuses to update recovery.
Am I able to update to Oreo with the old TWRP recovery & update it after? I am running the old Nougat version.
Option 7 I also got stuck on. '' Create a folder named HWOTA8 on your device’s internal storage.'' whilst connected via USB to the computer.
I am unable to view internal or external storage when the USB is connected to the computer. When viewing internal/external memory normally I can see items as normal in external SD card but the internal memory files all appear jibberish even in recovery.
What am I doing wrong? I have been unable to find any clear guides of how to update from Nougat to Oreo including flashing the rom, flashing recovery and root.
Thanks for those able to help.
PS. I'm a new Huawei Mate 9 owner and have only just received the device several hours ago which is why I'm rusty. Compared to my previous Sony Xperia XZ Premium it is much more complicated. Sony was far easier to flash recovery and flash roms via recovery.
I am having the MHA-L29 international version.
Device now bootloops after following the guide of flashing SuperSU in recovery. I did what was said and received ''error 9'' after flashing the files.
Now bootloop.
Good news at least recovery is working but unable to boot. How to I update to Oreo with updated recovery & root?
Otherwise is THIS guide safe to follow:
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656
Could not even get past option 4. ''Do oeminfo backup in twrp,you should have a folder name twrp, inside this folder there is many subfolders.
In last folder there is 2-3 files,those files should be replaced with c636 oeminfo: http://www.mediafire.com/?szws87sk7rrkqr6''
Permission denied error.
kanej2006 said:
Could not even get past option 4. ''Do oeminfo backup in twrp,you should have a folder name twrp, inside this folder there is many subfolders.
In last folder there is 2-3 files,those files should be replaced with c636 oeminfo: http://www.mediafire.com/?szws87sk7rrkqr6''
Permission denied error.
Click to expand...
Click to collapse
The guide in OP is outdated, and it only has the oreo beta builds.
Do you know what your current firmware build is?
MHA-LxxCxxx
(It should be printed on the box of your Mate 9)
Next go here http://pro-teammt.ru/firmware-database/ and enter your model and cust in the search box (Example, MHA-L29C432)
Official Oreo builds begin at B360, if you happen to be at C432 the latest is B364 (Ok, it's B365 but it seems to be a test build and was released before B364 so January patches.)
Click the 'update' link in the FullOTA-MF row, download update.zip.
Click on the 'file list' link in the FullOTA-MF row, copy link of update_data_full_public.zip and paste into a new browser tab, this downloads the zip.
Do the same with L29 or L09 hw data, depending on your version.
Next rename update_data_full_public.zip to update_data_public.zip, rename the L29/L09 hw data zip to update_all_hw.zip.
Place update.zip, update_all_hw.zip and update_data_public.zip in the HWOTA folder on your sdcard.
Download this zip: https://mega.nz/#!RaAQDLqY!pgBcA5tcy4ewvROUxei3af59hns4YtkeFPC5_WCyV6g (Note, this is only for Nougat to Nougat or Nougat to Oreo, does not work in Oreo as partitions changed and it flashes the NoCheck recovery to the correct partitions in Nougat. It will not flash correctly in Oreo)
extract and put hwota7_update.zip, MHA_RECOVERY2_NoCheck.img and MHA_RECOVERY_NoCheck.img in the HWOTA folder on your micro sd.
Put back mSD in phone and boot to TWRP, flash hwota7_update.zip and wait.
Phone should now reboot and start updating.
This is basically the HWOTA8 zip for updating Oreo or downgrading to Nougat, all props to @mankindtw.
All I did was change the partitions to flash so they match Nougat's partitions.
ante0 said:
Unless you want to rebrand to a different cust, don't follow this.
Do you know what your current firmware build is?
MHA-LxxCxxxBxxx
Click to expand...
Click to collapse
Good thing I never went ahead with that!
I'm on international MHA-L29C185B182.
Thank goodness I was able to restore Nougat as I backed up with TWRP recovery.
However, what is the easiest way to upgrade to the latest Android Oreo 8? At the moment I'm on stock 7 Nougat but am rooted with TWRP recovery.
kanej2006 said:
Good thing I never went ahead with that!
I'm on international MHA-L29C185B182.
Thank goodness I was able to restore Nougat as I backed up with TWRP recovery.
However, what is the easiest way to upgrade to the latest Android Oreo 8? At the moment I'm on stock 7 Nougat but am rooted with TWRP recovery.
Click to expand...
Click to collapse
Check my post, I edited while you posted this.
Or you can use this one, it's basically the same anyway, only difference is that you use a .bat file: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Use the same steps as I wrote above for downloading the update files as this was not the way to do it when that guide was written.
^ It seems the model I have is not found? After several attempts it is not finding my model.
kanej2006 said:
^ It seems the model I have is not found? After several attempts it is not finding my model.
Click to expand...
Click to collapse
http://pro-teammt.ru/firmware-database/?firmware_model=MHA-L29C185&firmware_page=0
Here are links you need:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2307/g1699/v120294/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...94/f1/full/public/update_data_full_public.zip
http://update.hicloud.com:8180/TDS/...hw_meafnaf/update_full_MHA-L29_hw_meafnaf.zip
Rename update_data_full_public.zip to update_data_public.zip and update_full_MHA-L29_hw_meafnaf.zip to update_all_hw.zip
There is a B371 too, but it was released before b370 so probably a test build.
That guide in OP seems to be a mixup. It uses the HWOTA8 files, which are for Oreo, so that's probably why it gave you errors.
ante0 said:
http://pro-teammt.ru/firmware-database/?firmware_model=MHA-L29C185&firmware_page=0
Here are links you need:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2307/g1699/v120294/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...94/f1/full/public/update_data_full_public.zip
http://update.hicloud.com:8180/TDS/...hw_meafnaf/update_full_MHA-L29_hw_meafnaf.zip
Rename update_data_full_public.zip to update_data_public.zip and update_full_MHA-L29_hw_meafnaf.zip to update_all_hw.zip
There is a B371 too, but it was released before b370 so probably a test build.
That guide in OP seems to be a mixup. It uses the HWOTA8 files, which are for Oreo, so that's probably why it gave you errors.
Click to expand...
Click to collapse
Thank you so much ante0 for all the information, it was very helpful. I am now downloading the above three files. Once complete I will rename them as mentioned and flash hwota7_update.zip in TWRP recovery. Will let you know shortly the outcome!
Cheers ante0, finally got my phone fully updated to Android 8 Oreo following your guide. Thank you so much! If it was not for you this would not have been possible!
The other links I was looking at were outdated as you mentioned and the instructions you provided were better. I appreciate your time to help me.
Upon booting, my EMUI version is now 8.0 and Android Version 8.0.
I will now follow this link for getting root:
https://forum.xda-developers.com/mate-9/how-to/discussion-root-mate9-oreo-emui-8-0-how-t3712495
@ ante0, I was able to get recovery and root but had to once again unlock bootloader...
kanej2006 said:
@ ante0, I was able to get recovery and root but had to once again unlock bootloader...
Click to expand...
Click to collapse
Great. I would suggest Magisk but that's up to you to decide
Bootloader getting locked is normal when updating Nougat to Nougat and Nougat to Oreo. Oreo to Oreo is stays unlocked.
ante0 said:
Great. I would suggest Magisk but that's up to you to decide
Bootloader getting locked is normal when updating Nougat to Nougat and Nougat to Oreo. Oreo to Oreo is stays unlocked.
Click to expand...
Click to collapse
I did not see any guide for Magisk, guess I missed it.
Anyway there are pros and cons for both, though I also prefer Magisk. Either way they both do the job, root access.
All is good now. I am very happy with the phone. Still not even been 24 hours since I received it yet already the bootloader has been unlocked, TWRP recovery and root. Nice :good:
Great and very helpful thread. thanks for everyone who's contributed to it. I'm trying to do the exact same thing coming from ROM Aur. Do you think I can use the same exact process is yours coming from a custom ROM? Did you have to do the boot loader unlock in order to Root? If there are no custom roms then perhaps the boot loader unlock is unnecessary? In order to install Magisk to root, what are the prerequisits? Do I need to reinstall TWRP? If so , is there a link to the correct version? Are there any other pointers that you can give me that you found out while doing this whole process? Thank you so much
kanej2006 said:
I did not see any guide for Magisk, guess I missed it.
Anyway there are pros and cons for both, though I also prefer Magisk. Either way they both do the job, root access.
All is good now. I am very happy with the phone. Still not even been 24 hours since I received it yet already the bootloader has been unlocked, TWRP recovery and root. Nice :good:
Click to expand...
Click to collapse
---------- Post added at 01:33 AM ---------- Previous post was at 01:02 AM ----------
Thanks for the guide!! Very helpful. However, Before I can even start following it, I'm running into some issues. The challenge that I'm facing is that I'm currently on a custom ROM (ROM AUR) and I do not know what my firmware build is. The box only tells me what the model number is and it's the MHA-L29. how would I find my firmware build ? The phone was purchased at bestbuy in the US.
Thanks again
ante0 said:
The guide in OP is outdated, and it only has the oreo beta builds.
Do you know what your current firmware build is?
MHA-LxxCxxx
(It should be printed on the box of your Mate 9)
Next go here http://pro-teammt.ru/firmware-database/ and enter your model and cust in the search box (Example, MHA-L29C432)
Official Oreo builds begin at B360, if you happen to be at C432 the latest is B364 (Ok, it's B365 but it seems to be a test build and was released before B364 so January patches.)
Click the 'update' link in the FullOTA-MF row, download update.zip.
Click on the 'file list' link in the FullOTA-MF row, copy link of update_data_full_public.zip and paste into a new browser tab, this downloads the zip.
Do the same with L29 or L09 hw data, depending on your version.
Next rename update_data_full_public.zip to update_data_public.zip, rename the L29/L09 hw data zip to update_all_hw.zip.
Place update.zip, update_all_hw.zip and update_data_public.zip in the HWOTA folder on your sdcard.
Download this zip: https://mega.nz/#!RaAQDLqY!pgBcA5tcy4ewvROUxei3af59hns4YtkeFPC5_WCyV6g (Note, this is only for Nougat to Nougat or Nougat to Oreo, does not work in Oreo as partitions changed and it flashes the NoCheck recovery to the correct partitions in Nougat. It will not flash correctly in Oreo)
extract and put hwota7_update.zip, MHA_RECOVERY2_NoCheck.img and MHA_RECOVERY_NoCheck.img in the HWOTA folder on your micro sd.
Put back mSD in phone and boot to TWRP, flash hwota7_update.zip and wait.
Phone should now reboot and start updating.
This is basically the HWOTA8 zip for updating Oreo or downgrading to Nougat, all props to @mankindtw.
All I did was change the partitions to flash so they match Nougat's partitions.
Click to expand...
Click to collapse
seti007 said:
Great and very helpful thread. thanks for everyone who's contributed to it. I'm trying to do the exact same thing coming from ROM Aur. Do you think I can use the same exact process is yours coming from a custom ROM? Did you have to do the boot loader unlock in order to Root? If there are no custom roms then perhaps the boot loader unlock is unnecessary? In order to install Magisk to root, what are the prerequisits? Do I need to reinstall TWRP? If so , is there a link to the correct version? Are there any other pointers that you can give me that you found out while doing this whole process? Thank you so much
---------- Post added at 01:33 AM ---------- Previous post was at 01:02 AM ----------
Thanks for the guide!! Very helpful. However, Before I can even start following it, I'm running into some issues. The challenge that I'm facing is that I'm currently on a custom ROM (ROM AUR) and I do not know what my firmware build is. The box only tells me what the model number is and it's the MHA-L29. how would I find my firmware build ? The phone was purchased at bestbuy in the US.
Thanks again
Click to expand...
Click to collapse
You can do the exact same process, however, I strongly suggest you follow the above guide from ante0. His guides are clear and upto date. Other guides were unclear and old not being upto date.
And yes, you must have an unlocked bootloader to flash a rom, however it is very easy to do. There are many guides which tell you how to do so. Simple fastboot commands when your phone is set to fastboot mode. You only need the unlock code via Huawei's website.
With regards to Magisk/SuperSU, yes, you must have a working recovery in order to flash either one. Without recovery you cannot get root access. I suggest you flash SuperSU as it is far easier than Magisk, a simple two step procedure!
What Android version are you on? Nougat or Oreo? Beware that when flashing recovery and root, it must be for the correct Android version. And of course if updating to Oreo, once again you will need to flash recovery and root made to run on Oreo to prevent issues and boot loops.
Do you not have the box that came with your device? I am guessing you have the international MHA-L29 version as I do, but you must be sure.
ante0 said:
Bootloader getting locked is normal when updating Nougat to Nougat
Click to expand...
Click to collapse
The bootloader (i.e. fastboot) is always locked (btw, is there an easy way to unlock FB Lock ?), you probably mean the 'USER Lock'. And the 'USER UnLock' is damaged only if you flash some random oeminfo files (which is a very dumb decision anyway).
This mechanism is documented in the USENIX paper i have linked in the OEMINFO thread.
---------- Post added at 12:19 PM ---------- Previous post was at 12:00 PM ----------
kanej2006 said:
Sony was far easier to flash recovery and flash roms via recovery.
Click to expand...
Click to collapse
It may be "easier", but Mate 9 is probably one of the most unbrickable smartphones that i know, because it can be recovered even if you manage to destroy 'partition table+xloader+fastboot' (the really critical parts, other partitions can be recovered without opening the phone case).
kanej2006 said:
You can do the exact same process, however, I strongly suggest you follow the above guide from ante0. His guides are clear and upto date. Other guides were unclear and old not being upto date.
And yes, you must have an unlocked bootloader to flash a rom, however it is very easy to do. There are many guides which tell you how to do so. Simple fastboot commands when your phone is set to fastboot mode. You only need the unlock code via Huawei's website.
With regards to Magisk/SuperSU, yes, you must have a working recovery in order to flash either one. Without recovery you cannot get root access. I suggest you flash SuperSU as it is far easier than Magisk, a simple two step procedure!
What Android version are you on? Nougat or Oreo? Beware that when flashing recovery and root, it must be for the correct Android version. And of course if updating to Oreo, once again you will need to flash recovery and root made to run on Oreo to prevent issues and boot loops.
Do you not have the box that came with your device? I am guessing you have the international MHA-L29 version as I do, but you must be sure.
Click to expand...
Click to collapse
Yes I intend to follow the awesome guide from ante0 (thanks for that ante). I'm on Nougat currently. After following the above method, I guess I will have a fully factory locked phone? SO, I will have to first install recovery, then root. Correct? I do have the box but it only says the model number MHA-L29. Nothing on firmware but since its a US phone bought here, I'm fairly confident that its a MHA-L29C567B183. Although when i installed ROM AUR I used the version for L29C432 and it worked. Which one would you try if you were me? Will I brick the phone if the version is incorrect? If that happens, how do i return to oreo stock from there? Do you have any links for the right Recovery and root?
Thanks and sorry for so many questions.
UPDATE-- So have an update. I was able to install oreo using the method listed above. everything seems to be working fine. however I'm getting an error 255 message while creating a backup I'm using TWRP. Thinking that my data partition needed decrypting, I deleted it and rebooted the phone. Set it up and then went back into TWRP. I'm still getting the same backup error. any ideas? The route also installed and works fine . My concern now is that I would end up with I found that cannot be backed up with TWRP. BTW. I installed TWRP 3.2.1-0 from here https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-oreo-t3734967.
Thanks
^ 1 Thing hopefully you did not forget, before flashing the rom, you must ''wipe data'' from TWRP recovery otherwise you will get bootloop and the encryption issue. Did you wipe data from recovery prior to flashing? Encryption is removed/disabled when wiping data in recovery.
Glad you got somewhere at least. If it wasn't for the guide from Ante0, I'd still be bootlooping on Nougat.
ante0 said:
The guide in OP is outdated, and it only has the oreo beta builds.
Do you know what your current firmware build is?
MHA-LxxCxxx
(It should be printed on the box of your Mate 9)
Next go here http://pro-teammt.ru/firmware-database/ and enter your model and cust in the search box (Example, MHA-L29C432)
Official Oreo builds begin at B360, if you happen to be at C432 the latest is B364 (Ok, it's B365 but it seems to be a test build and was released before B364 so January patches.)
Click the 'update' link in the FullOTA-MF row, download update.zip.
Click on the 'file list' link in the FullOTA-MF row, copy link of update_data_full_public.zip and paste into a new browser tab, this downloads the zip.
Do the same with L29 or L09 hw data, depending on your version.
Next rename update_data_full_public.zip to update_data_public.zip, rename the L29/L09 hw data zip to update_all_hw.zip.
Place update.zip, update_all_hw.zip and update_data_public.zip in the HWOTA folder on your sdcard.
Download this zip: https://mega.nz/#!RaAQDLqY!pgBcA5tcy4ewvROUxei3af59hns4YtkeFPC5_WCyV6g (Note, this is only for Nougat to Nougat or Nougat to Oreo, does not work in Oreo as partitions changed and it flashes the NoCheck recovery to the correct partitions in Nougat. It will not flash correctly in Oreo)
extract and put hwota7_update.zip, MHA_RECOVERY2_NoCheck.img and MHA_RECOVERY_NoCheck.img in the HWOTA folder on your micro sd.
Put back mSD in phone and boot to TWRP, flash hwota7_update.zip and wait.
Phone should now reboot and start updating.
This is basically the HWOTA8 zip for updating Oreo or downgrading to Nougat, all props to @mankindtw.
All I did was change the partitions to flash so they match Nougat's partitions.
Click to expand...
Click to collapse
@ante0
can i use these commands to upgrade to O as well
the only difference in the folder should be the hwota8 and the update zips for O ?
L09C316
d if=/external_sd/HWOTA/MHA_RECOVERY_NoCheck.img of=/dev/block/sdd33
dd if=/external_sd/HWOTA/MHA_RECOVERY2_NoCheck.img of=/dev/block/sdd30
echo --update_package=/sdcard/HWOTA/update.zip > /cache/recovery/command
echo --update_package=/sdcard/HWOTA/update_data_public.zip >> /cache/recovery/command
echo --update_package=/sdcard/HWOTA/update_all_hw.zip >> /cache/recovery/command
Hi
I have a rooted phone, and received the ota update, but when phone reboots, it goes boots to twrp .
Since ff is approved, could someone pls advise how to update via hwota8
kind regards
the-light said:
Hi
I have a rooted phone, and received the ota update, but when phone reboots, it goes boots to twrp .
Since ff is approved, could someone pls advise how to update via hwota8
kind regards
Click to expand...
Click to collapse
Flash stock recovery.
For HWOTA8, follow the thread. You need to download FullOTA.
Also with HWOTA8, you will not need to flash stock recovery manually. Basically you flash the zip from TWRP with the provided stock recovery and the three FullOTA update files from Huawei located in a HWOTA8 folder on your external SD card. Once the update is completed, you can then flash TWRP and root again. Same process for every update. Bootloader stays unlocked.
Here's the thread: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522/
the-light said:
Hi
I have a rooted phone, and received the ota update, but when phone reboots, it goes boots to twrp .
Since ff is approved, could someone pls advise how to update via hwota8
kind regards
Click to expand...
Click to collapse
mp187263 said:
Also with HWOTA8, you will not need to flash stock recovery manually. Basically you flash the zip from TWRP with the provided stock recovery and the three FullOTA update files from Huawei located in a HWOTA8 folder on your external SD card. Once the update is completed, you can then flash TWRP and root again. Same process for every update. Bootloader stays unlocked.
Here's the thread: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522/
Click to expand...
Click to collapse
Hi mp187263
Thank you for your reply, I also think updating via hwota8 is better solution, having said that, there are 4 file downloaded from ff 3 of them are with l29 and one is l09.
could u pls advise if i should dl and flash the 3 files all together with hwota8?
many thanks
You should only have 3 files, that are specific to your model. FF gives you the exact download links you need as long as the correct model is selected.
If you can get into the OS, it will be under Settings > System > About phone (example: MHA-L29 with the build number showing the region - ie. C636). Or a better way is to get the FF app and it will show you the model as well as the region. If you cannot get into the OS and your phone has not been rebranded, it will be on a label on the original box. My phone is from China so it came as a MHA-AL00, but was rebranded to MHA-L29C636 (International version). There are also other versions such as C567 for USA and so forth. The files you download have to match exactly what you have, do not flash it if unsure.
the-light said:
Hi mp187263
Thank you for your reply, I also think updating via hwota8 is better solution, having said that, there are 4 file downloaded from ff 3 of them are with l29 and one is l09.
could u pls advise if i should dl and flash the 3 files all together with hwota8?
many thanks
Click to expand...
Click to collapse
mp187263 said:
You should only have 3 files, that are specific to your model. FF gives you the exact download links you need as long as the correct model is selected.
If you can get into the OS, it will be under Settings > System > About phone (example: MHA-L29 with the build number showing the region - ie. C636). Or a better way is to get the FF app and it will show you the model as well as the region. If you cannot get into the OS and your phone has not been rebranded, it will be on a label on the original box. My phone is from China so it came as a MHA-AL00, but was rebranded to MHA-L29C636 (International version). There are also other versions such as C567 for USA and so forth. The files you download have to match exactly what you have, do not flash it if unsure.
Click to expand...
Click to collapse
Thx again for clarifying. im on c567, I didnt know if i should flash all 3 files, now I do..btw, there is a new patch coming in soon, .369, guess ill wait for it to be approved and then make the flash
ante0 said:
Flash stock recovery.
For HWOTA8, follow the thread. You need to download FullOTA.
Click to expand...
Click to collapse
I flashed the EMUI stock recovery but OTA update still fail. Any idea? Thanks.
drift08 said:
I flashed the EMUI stock recovery but OTA update still fail. Any idea? Thanks.
Click to expand...
Click to collapse
Any modified partitions? That would most likely be why, and you'd have to flash FullOTA if that's the case.
ante0 said:
Any modified partitions? That would most likely be why, and you'd have to flash FullOTA if that's the case.
Click to expand...
Click to collapse
I think I reflash EMUI to ram disk recovery via adb but still have root via magisk. When you say FullOTA, will it erase all my apps and accts? Thanks.
drift08 said:
I think I reflash EMUI to ram disk recovery via adb but still have root via magisk. When you say FullOTA, will it erase all my apps and accts? Thanks.
Click to expand...
Click to collapse
Difference between OTA and FULLOTA is that OTA patches existing partitions while full flashes full images. Your data will stay untouched
Hi folks.
This is a solution for who get troubles when you flash my own ROMs, it is all about Emui 8 related firmware because they denies the permissions to flash custom roms / root in the latest firmware like AL00XB335, C432B360/B375 or newer, here is a small tutorial to solve this issue once for all by downgrade to the earlier firmware which xLoader.img still present.
Note: this tutorial is for Honor 8 Lite and P8 Lite 2017, for other devices make sure to downgrade to older versions.
Requirements:
Unlocked bootloader.
TWRP, use Honor 9 Lite 0.2 Test build, click here.
NoCheck Oreo Recovery, click here.
Your device should be updated to the latest Emui 8.x versions that generate E1001 Errors.
OEMInfo Dual Sim Devices Only (Since most of you are ds):
AL00X.
C432.
PRA-AL00XC00B310:
update.zip .
update_data_full_public.zip .
update_full_PRA-AL00X_all_cn.zip .
Installation Guide:
Reboot to the TWRP.
Flash the NoCheck Recovery.
Run in the terminal (from adb shell is better)
Note: please flash those package once per time I mean that once you flash update.zip and boot the rom (in case of bootloop just check bootloader status and run factory reset) then reboot to fastboot and flash TWRP again then re-install nocheck recovery via TWRP and do same steps for other 2 packages .
echo –update_package=/sdcard/update.zip > /cache/recovery/command
echo –update_package=/sdcard/update_data_full_public.zip > /cache/recovery/command
echo –update_package=/sdcard/update_full_PRA-AL00X_all_cn.zip > /cache/recovery/command
PRA-LX1C432B321:
update.zip .
update_data_full_public.zip
update_full_PRA-L11_hw_eu.zip .
reserved
Thank you mate.
Graveen said:
Thank you mate.
Click to expand...
Click to collapse
You welcome.
Not working for me. Same e1001 error
Wire1122 said:
Not working for me. Same e1001 error
Click to expand...
Click to collapse
I did same steps and it is work after I flash B310 AL00, as I said I use Kirin970 source and it's boot fine.
I flash the europen version that you posted
Wire1122 said:
I flash the europen version that you posted
Click to expand...
Click to collapse
want an advice? go for GSI by phhusson instead wasting time, they are boot from first time.
Credit-
@oslo83 for the big help.
@OldDroid for EMUI Flasher tool.
@ante0 his tricks worked when I ended up with incorrect build number
WARNING-
Do not try to debrand from cn/all to other variant as that may lead to FRP lock status.
Do not reboot after flashing the oeminfo or it may brick the phone.
i.e. once oeminfo is edited, phone may brick :
- if device is rebooted with its original region stock firmware
- if wrong region firmware is selected in EMUI FLASHER
- if downgrading
- if flashing wrong packages
Prerequisites-
Unlocked and Rooted Honor 8X (root from here)
Backup of your data via Hisuite or TB backup or other tools.
Files for the new model (JSN-L21/L42 variant)
Free Storage around 8 GB space.
Downloads-
EMUI Flasher from here or here
OEMINFO binary from here
For JSN-L42 Indian version
Main update zip here
Data zip here
(Optional) Public Zip here
For JSN-L21 EU version
Main zip here
Data zip here
(Optional) Public zip from here
Procedure-
Root your phone using this guide
Install EMUI flasher downloaded but do not run it. (just click on done once installed)
Copy the firmware to internal memory
copy oeminfo binary to internal memory
on PC, go to adb folder, shift+right click, open command prompt here and type -
Code:
adb shell
su (please grant root on your phone at this step)
mkdir /data/local/tmp
mv /sdcard/oeminfo /data/local/tmp
cd /data/local/tmp
chmod +x oeminfo
./oeminfo JSN-L21 C432 hw/eu (if you want to debrand to EU version)
./oeminfo JSN-L42 C675 hw/in (if you want to debrand to Indian version)
Run the EMUI flasher app you installed earlier, give root persmission.
It will prompt for download of a file around 26 MB (no-check recovery), install it.
Select the respective firmwares from you internal memory based on the region you want to debrand/rebrand to (Update.zip, update_full_JSN-L21_hw_eu.zip and update_data_full_public.zip or update.zip, update_full_JSN-L42_hw_in.zip and update_data_full_public.zip
Click on the arrow or download symbol and EMUI flasher will start flashing the firmwares. (may take 10 minutes)
It may take few minutes to complete the update procedure in recovery, device will reboot automatically and will perform the factory reset.
once booted, your phone should be on the new region.
Thanks, i will try
Thanks. Any oeminfo???
Mewwo said:
Thanks. Any oeminfo???
Click to expand...
Click to collapse
Yes any oeminfo as long as you are putting correct model number and device code
Hello, can I rebrand Honor 8X AL00a? If you know, tell me how, please.
It's working on JSN-L22C636???
natsusii said:
It's working on JSN-L22C636???
Click to expand...
Click to collapse
Yes
chermosh said:
Hello, can I rebrand Honor 8X AL00a? If you know, tell me how, please.
Click to expand...
Click to collapse
It should. Process will remain the same
chermosh said:
Hello, can I rebrand Honor 8X AL00a? If you know, tell me how, please.
Click to expand...
Click to collapse
I'm looking for the same
Can debranding JSN-L21 to JSN-L22C636 ???
Need oeminfo of JSN-L22C636????
shashank1320 said:
WARNING-
Do not try to debrand from cn/all to other variant as that may lead to FRP lock status.
Click to expand...
Click to collapse
So no JSN-AL00? I have a JSN-AL00 128/6 that needs a rebrand...
Yir said:
So no JSN-AL00? I have a JSN-AL00 128/6 that needs a rebrand...
Click to expand...
Click to collapse
You can try. should work fine if followed correctly. Which region you want to rebrand to?
natsusii said:
Can debranding JSN-L21 to JSN-L22C636 ???
Need oeminfo of JSN-L22C636????
Click to expand...
Click to collapse
You can..No need. it will just be a command change for this step to C636 and instead of EU the correct one followed by correct firmware flash.
./oeminfo JSN-L21 C432 hw/eu
natsusii said:
Can debranding JSN-L21 to JSN-L22C636 ???
Need oeminfo of JSN-L22C636????
Click to expand...
Click to collapse
Update- I dont see any Oreo firmware for this model yet on firmware finder. it may be on easy firmware or other site.
shashank1320 said:
You can try. should work fine if followed correctly. Which region you want to rebrand to?
Click to expand...
Click to collapse
to anything but chinese, probably. International should be fine. My only worries are that the different firmware wont work with the different hardware.
Yir said:
to anything but chinese, probably. International should be fine. My only worries are that the different firmware wont work with the different hardware.
Click to expand...
Click to collapse
We dont have firmware for global model. EU or Indian should work fine for you.
My 8x is stuck in honor logo and then resets itself.. I can access e Recover. Any way to fix this?
MiyuChandria said:
My 8x is stuck in honor logo and then resets itself.. I can access e Recover. Any way to fix this?
Click to expand...
Click to collapse
What did you do before this happened ?
miststudent2011 said:
What did you do before this happened ?
Click to expand...
Click to collapse
I did the steps and flashed the L42 files and it worked out fine, and the font was reverted to its original. Then I repeated the steps again and it no longer boots. It can only reach the honor logo and it restarts itself.
MiyuChandria said:
I did the steps and flashed the L42 files and it worked out fine, and the font was reverted to its original. Then I repeated the steps again and it no longer boots. It can only reach the honor logo and it restarts itself.
Click to expand...
Click to collapse
Why did you repeat those steps ? Any specific reason ?