Database Info

bricked from downgrade

I tried to downgrade from L29C185B320 to L29C185B200 however I'm now faced with the following:
(Prior to the downgrade I did flash the B320 recovery.img as I was on TWRP before)
On boot, Huawei logo displays then display goes black. Still powered on but not displaying anything
eRecovery is accessible, tried wiping cache but no change, also tried factory reset. The "download latest version and recovery" option isn't possible, "getting package info failed"
Can't access device over ADB as it doesn't detect in "adb devices"
Bootloader is now locked (was unlocked before)
I can "fastboot reboot" but no other command works due to bootloader locked
I can do Vol Up+Down reset but takes me right back to blank screen after installing. I've tried with various update versions (B162, B180, B200, even going back to B320) but its the same result every time.
Afraid I now have a brick, would appreciate any help I can get.

MuPp3t33r said:
I tried to downgrade from L29C185B320 to L29C185B200 however I'm now faced with the following:
(Prior to the downgrade I did flash the B320 recovery.img as I was on TWRP before)
On boot, Huawei logo displays then display goes black. Still powered on but not displaying anything
eRecovery is accessible, tried wiping cache but no change, also tried factory reset. The "download latest version and recovery" option isn't possible, "getting package info failed"
Can't access device over ADB as it doesn't detect in "adb devices"
Bootloader is now locked (was unlocked before)
I can "fastboot reboot" but no other command works due to bootloader locked
I can do Vol Up+Down reset but takes me right back to blank screen after installing. I've tried with various update versions (B162, B180, B200, even going back to B320) but its the same result every time.
Afraid I now have a brick, would appreciate any help I can get.
Click to expand...
Click to collapse
I have same problem...
And cant find any solution for adb commands work again. I don't know where is the problem.Tryed everythink. And nothing. Maybe problem is FRP lock, but in bootloader its nothing showing. Just phone unlocked. I saw many users have this problem.

delete

Same problem
Hi guys,
I'm new here and I have the same problem after my try to downgrade from EMUI5 to EMUI4.1 Mashmallow.
My Phone bootload twice and after my only choice is to use eRecovery taht don't work. I tried to use italian swiss knife nad the other from Asia to unlock the phone but it don't work at all, I got the same message Failed : remote command unaviable, or something like that.
Please can you help me to recover my phone?
Thank you in advance for all your suggestions

lecsolo said:
Hi guys,
I'm new here and I have the same problem after my try to downgrade from EMUI5 to EMUI4.1 Mashmallow.
My Phone bootload twice and after my only choice is to use eRecovery taht don't work. I tried to use italian swiss knife nad the other from Asia to unlock the phone but it don't work at all, I got the same message Failed : remote command unaviable, or something like that.
Please can you help me to recover my phone?
Thank you in advance for all your suggestions
Click to expand...
Click to collapse
Try by dloadl UPDATE.APP (C185B521) from Update.zip.
After re-try rollback

pescixx79 said:
Try by dloadl UPDATE.APP (C185B521) from Update.zip.
After re-try rollback
Click to expand...
Click to collapse
Thank you, is the right update for an EU phone the C185B521?

lecsolo said:
Thank you, is the right update for an EU phone the C185B521?
Click to expand...
Click to collapse
I was on C185B521, flashed Rollback and tryed to downgrade to C185B180. Had ISSUE.
I extracted Update.app from C185B521 zip and Flashed (dload) (had keyboard issue and other not working)
Try to rollback again and alla woked fine.

pescixx79 said:
I was on C185B521, flashed Rollback and tryed to downgrade to C185B180. Had ISSUE.
I extracted Update.app from C185B521 zip and Flashed (dload) (had keyboard issue and other not working)
Try to rollback again and alla woked fine.
Click to expand...
Click to collapse
Ok I will try this, hope it will work on my phone
Thanks for your help

Problem solved this morning I try to boot with vol up and start bouton pressed, when wipe/factory reset appears and selected, then press ok. After that my phone reboot on EMUI 4.1/mashmallow and work fine.
Thank you very much for your help, much appreciated.

r4ason said:
I have same problem...
And cant find any solution for adb commands work again. I don't know where is the problem.Tryed everythink. And nothing. Maybe problem is FRP lock, but in bootloader its nothing showing. Just phone unlocked. I saw many users have this problem.
Click to expand...
Click to collapse
Sigh, that's a pity. I don't think it would be an frp problem in my case as I have my Google account details to login, rather just that it's failing to boot the os partition. What I've gathered from this is that something went wrong with the firmware installation and now that its relocked the bootloader there's no way to push the files into place with adb/fastboot.
Nevertheless, my device is still fairly new so I've sent it back to the supplier, will wait for their response...

Another Honor 8 Bricked

Hello,
After the purchase of my phone i unlocked the bootloader, installed a custom rom of android M, everything went fine, twrp, root, etc.
Few days ago I wanted to give a shot at Nougat. I went through a couple roms but lacking certain functions i needed. I then tried one last stock nougat beta rom (from this link : https://forum.xda-developers.com/honor-8/development/beta-android-7-0-emui-5-l04c567b320-frd-t3529465
This was the worst rom i've encountered. Please don't use it.
Three reasons : No bluetooth, TWRP gone, and no keyboard pre-installed.
Yes. You can only first boot this rom with google voice typing. I'm not joking.
More than that i cannot finish the initial boot of the rom, i get stuck at the "enter your google account" (try to enter yours with google voice...)
I can't even ignore it, it says that "This device was reset. To continue, sign in with a Google Account that was previously synced on this device".
Anyway, now that I lost TWRP i wanted to flash it back. My bootloader being still unlocked (phone shows "your device has been unlocked and cannot be trusted" at each boot), i went to adb to flash twrp.
I got this message after trying to flash it :
...
FAILED (remote: Command not allowed)
...
I get this message after i try to flash TWRP, update, boot or anything.
I've read that i need to enable oem unlock in the developer settings. Thing is I'm stuck before i can access any parameters.
I even tried Huawei Multi-Tool, with boot, recovery, unbrick, but again, can't flash anything.
tl;dr :
- Nougat 7.0 EMUI 5.0
- Stuck in initial boot
- Only type with google voice
- No TWRP
- FAILED (remote: Command not allowed) error when trying to flash anything
What can I do ?
EDIT : I did manage to enter my google account, but it says that i need to log in with one of the owner's account. I never entered any other account on my phone... Definitely stuck.

This question was already answered a million times before! Just use the search button!
This Honor 8 forum is full of threads created by newly come member that just create a new thread without any use when they could just search for the already answered questions!

Plug in USB to computer, hold down power + volume down until you enter bootloader. Flash recovery system image again, then reboot into recovery and re flash another ROM.

Telperion said:
Plug in USB to computer, hold down power + volume down until you enter bootloader. Flash recovery system image again, then reboot into recovery and re flash another ROM.
Click to expand...
Click to collapse
Even when i'm in fastboot mode I can't flash anything, boot.img, recovery.img, system.img... nothing.
Fastboot mode shows "PHONE Unlocked" "FRP Lock", if that helps.
I tried using the rollback solution shown here https://forum.xda-developers.com/honor-8/help/totally-screwed-honor-8-t3556678/post71033483#post71033483. Intermediate package did apply but the full android 6.0 firmware failed to update.
And yes I've been searching around this forum before posting, but I can't find a post talking about my problem, being unable to access the rom in normal boot, unable to flash anything.
Is there a way to fix the "FAILED (remote: Command not allowed)" error message ? As it is the only think keeping me from doing anything on my phone
Or maybe trick the phone into flashing a rom through recovery (like a rollback but with a random custom rom instead) ?

Hi, did you ever find a fix for this?

Rommco05 said:
Are you missing some stuff from the system?
Click to expand...
Click to collapse
I don't believe so. Why?

Rommco05 said:
You need to install zip data. Which is your model and build number?
Click to expand...
Click to collapse
FRD-L04, and my Build Number is whatever the build number is for the first Nougat Beta from last year haha.
But how would I install zip data if flashing stuff via fastboot isn't working?

Are you referring to the Data Fix.zip? Also, I haven't been able to flash the 6.0 Stock ROM Via ercovery.
---------- Post added at 09:16 AM ---------- Previous post was at 09:14 AM ----------
Rommco05 said:
FRD-L04 US model, right? First beta was maybe B320..?? Via dload
Click to expand...
Click to collapse
Are you referring to the Data Fix.zip? Also, I haven't been able to flash the 6.0 Stock ROM Via ercovery.

Rommco05 said:
FRD-L04 US model, right? First beta was maybe B320..?? Via dload
Click to expand...
Click to collapse
Rommco05 said:
For flash to 6.0 u need rollback packages and full M rom. Is your phone US model? I try send u links if is
Click to expand...
Click to collapse
Yeah I have the US model

Rommco05 said:
First install biggest second small, over dload methodhttp://update.hicloud.com:8180/TDS/data/files/p3/s15/G1278/g104/v72309/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...09/f1/full/hw/usa/update_data_full_hw_usa.zip
Click to expand...
Click to collapse
Thanks, so what's the install method for this?

Flashing new TWRP 3.1.1 lead me to no recovery

Hi guys.
My issue: I had TWRP 3.0.2.1 on my honor and decided to update to latest version. Big error.
I have the TWRP app installed and I followed the procedure to flash recovery with that app. It seemed everything was fine, because it said ""recovery flashed".
Now when I try to enter recovery, my phone gets stuck at logo "your device is booting now".
I have to reboot in EMUI recovery to go out from that stuck page and to load normally the phone.
So I decided to flash recovery in the old ADB fashioned way: now when I get to "fastboot flash recovery twrp.img", the phone tells me "FAILED (remote: Command not allowed)"
Practically now I have no TWRP and I do not know how to proceed.
Some good Samaritan out there?
Thanks.

My firmware is latest Nougat (BLN-L21C432B360).
I tried to flash TRWP 3.1.1. Before this try, I had version 3.0.2-1 as written above. I flashed twrp when I still had Android 6 with EMUI 4.
Regarding the way to enter TWRP, yes, I know the method and I do it.
The problem is my phone don't enter twrp but remain stuck at logo.
It seems that the recovery is not present or has problems.
I've tried even to reflash the old recovery, just in case. Nothing.

Try this-
flash stock recovery for your model.
boot normally.
flash TWRP latest.

Now I try and post later.
What a mess. I should leave the old 3.0.2 which was working good...

I was already on nougat and the 3.0.2 was still working perfectly. I had flashed that twrp when I was still on 6.0 and after the update with firmware finder it was still working.
Moreover I used the official TWRP app to update and it failed miserably even if it said flash successful at the end of operation....

Then I used the classic way with ADB and still nothing.
I can see on the Windows shell "failed: command not allowed"

Rommco05 said:
Frp in fastboot is unlocked?
Click to expand...
Click to collapse
AFAIK, Factory Reset Protection is linked to account protection in case someone steals the phone. In this way it should be more difficult to wipe completely the phone and use it.
Anyway, just checked in fastboot and no, FRP is locked. I just had a look in developer options and I noticed that "Enable OEM unlocked" is greyed out. But it should not have nothing to do with flashing the recovery.
Or not?

Let's see

Diamantes said:
Hi guys.
My issue: I had TWRP 3.0.2.1 on my honor and decided to update to latest version. Big error.
I have the TWRP app installed and I followed the procedure to flash recovery with that app. It seemed everything was fine, because it said ""recovery flashed".
Now when I try to enter recovery, my phone gets stuck at logo "your device is booting now".
I have to reboot in EMUI recovery to go out from that stuck page and to load normally the phone.
So I decided to flash recovery in the old ADB fashioned way: now when I get to "fastboot flash recovery twrp.img", the phone tells me "FAILED (remote: Command not allowed)"
Practically now I have no TWRP and I do not know how to proceed.
Some good Samaritan out there?
Thanks.
Click to expand...
Click to collapse
Unlock your boot loader

Bootloader is unlocked.
For some reason, my "OEM unlocked" option turned greyed out, and FRP is locked again.
I will try this eve to lock bootloader again and restart the unlocking operation from scratch.
Will see

Diamantes said:
Bootloader is unlocked.
For some reason, my "OEM unlocked" option turned greyed out, and FRP is locked again.
I will try this eve to lock bootloader again and restart the unlocking operation from scratch.
Will see
Click to expand...
Click to collapse
In emui 5 OEM unlock option is not there and can only be found in MM or Emui 4.x

you mean that even if I can't access TWRP, this should be still there and I cannot lock bootloader?
And you advice to do a factory reset first.
If this doesn't work? Then?

shashank1320 said:
In emui 5 OEM unlock option is not there and can only be found in MM or Emui 4.x
Click to expand...
Click to collapse
You mean that I couldn't even see the option?
I have nougat and emui 5, the option is present but greyed out

Diamantes said:
You mean that I couldn't even see the option?
I have nougat and emui 5, the option is present but greyed out
Click to expand...
Click to collapse
Yeah exactly. See SS
This was there till emui 4

So how can I solve the problem?
Someone told me the only way is to lock bootloader in order to have again this option available to be turned on... And so start the process again.
At the moment I cannot access TWRP nor flash it through ADB. Practically even if bootloader is unlocked, I have a rooted phone with no possibility to do anything else... Regarding flashing of course.

Thank you for your replies.
Anyway I really know now that I cannot buy honor for flashing.
I just tried a factory reset from advanced options.
After all the pin request etc, the phone rebooted and get stuck on the initial window (your phone has been unlocked and cannot be trusted-your phone is booting now...).
So I had to press usual buttons to enter in emui recovery, the only way I can get the rebooting option from this state.
Of course the phone is not reset.
I give up. This crappy phone is taking too much time of my life.
I will keep it like this. And I'm not sure at all I will get future OTA update.
I never EVER had these issues with Samsung phones or HTC, and believe me that I was flashaholic... I flashed tens and tens of ROMs, I rooted and unlocked all my previous phones with no glitches or whatever..,
This time I tried honor for the price.
Never again for flashing or playing around.
Just for normal, classic phone use, hoping it will last some other month before I purchase another brand.
Thank you all.

Of course my thoughts about this ****ty phone were all right.
I received the ota update for version b365, downloaded and OF COURSE STUCK at boot logo after automatic restart...
I will never be able to install anything else because the recovery is corrupted.
I am condemned to stay with b360 until this cursed phone will die for natural causes...
No comment

Diamantes said:
Of course my thoughts about this ****ty phone were all right.
I received the ota update for version b365, downloaded and OF COURSE STUCK at boot logo after automatic restart...
I will never be able to install anything else because the recovery is corrupted.
I am condemned to stay with b360 until this cursed phone will die for natural causes...
No comment
Click to expand...
Click to collapse
But recovery can be changed mate. Try twrp with new thread in my signature and follow steps, it won't be a trouble. Try once in free time as i know you already are frustrated with trying all ways.

The TWRP on official TWRP site sadly won't work for our berlin devices, i neither know why it is still there sincerely. Personally i can't recommend the usage of TWRP official app for our phone as it downloads a wrong version... you have to get the OpenKirin edition from here https://forum.xda-developers.com/honor-6x/development/twrp-t3583413 and flash that via adb fastboot. Be sure to have "USB debug" on by developer options menu, and to have installed HiSuite (just to have all the functional drivers)

I thank you all for your patience and replies.
But as Shashank said, I'm really frustrated because I tried everything in the past.
Now I'm rooted (luckily) but with FRP locked. It seems the reason why I cannot flash nothing.
In any case I will try again the suggestion of redskull. The last hope!
Thanks.

BLN-L24 Bricked/Bootlooped after rollback

I was rooted with TWRP but I want to sell this phone so I was rolling back to stock. I was able update successfully both times (back to B300 and then initial B310 firmware) and after the 2nd update it did an automatic data reset just like the instructions said it would. Now my phone is bootlooped stuck on the honor screen and I need some help getting it back. I read that rolling back will relock your bootloader so I assumed (incorrectly obviously) that it would just return everything to stock.
I now have stock recovery and erecovery works as well. Tomorrow when I get into work I'll be able to get it into fastboot then what do I need to flash to get this thing working again? Thanks in advance

just flash the respective firmware via dload and it will lock both bootlaoder and FRP and should be good to go with full stock.
let me know in case need help, will try as much as can.

Which firmware? I already used the dload method in my attempt to rollback to emui 4.1 since I read that would relock my boot loader. Both parts of the 2 part rollback were successful according to the updater . After the first update my phone boot and I was able to check in settings that I was rolled back to B300 firmware. I then did the dload with the B110 firmware and upon completing sucessfully it automatically reset my phone and went straight to bootloop.
In the following post the person says unroot and relock boot loader first which I did not, does that have anything to do with it?
https://forum.xda-developers.com/honor-6x/help/how-to-rollback-package-huawei-gr5-2017-t3574399

Dazed No More said:
Which firmware? I already used the dload method in my attempt to rollback to emui 4.1 since I read that would relock my boot loader. Both parts of the 2 part rollback were successful according to the updater . After the first update my phone boot and I was able to check in settings that I was rolled back to B300 firmware. I then did the dload with the B110 firmware and upon completing sucessfully it automatically reset my phone and went straight to bootloop.
In the following post the person says unroot and relock boot loader first which I did not, does that have anything to do with it?
https://forum.xda-developers.com/honor-6x/help/how-to-rollback-package-huawei-gr5-2017-t3574399
Click to expand...
Click to collapse
Nope. Dload woll lock the bootloader. I tried today but seems some issue and we may need to flash the boot.img before proceeding. Tried 3-4 times today but no luck. Will try later now as this is primary phone with all official apps installed

shashank1320 said:
Nope. Dload woll lock the bootloader. I tried today but seems some issue and we may need to flash the boot.img before proceeding. Tried 3-4 times today but no luck. Will try later now as this is primary phone with all official apps installed
Click to expand...
Click to collapse
Are you saying I need to flash the boot image? I thought boot, recovery and all the necessary images were contained in the update.app and are flashed on a successful dload update. I do know my boot loader is relocked
Like a fool I forgot my SD card on the bedside table this morning so I won't be able to dload anything but I will be able to ABD/fastboot once I get to work. I.was thinking of extracting the boot.img from the update.app and flashing it via adb

Dazed No More said:
Are you saying I need to flash the boot image? I thought boot, recovery and all the necessary images were contained in the update.app and are flashed on a successful dload update. I do know my boot loader is relocked
Like a fool I forgot my SD card on the bedside table this morning so I won't be able to dload anything but I will be able to ABD/fastboot once I get to work. I.was thinking of extracting the boot.img from the update.app and flashing it via adb
Click to expand...
Click to collapse
I am not saying this exactly but yeah, after unroot via zip, i got the message on recovery that i may need to flash the boot.img to completely unroot it and then proceed but I never did that.
I used dload main zip content and was success but device went to bootloop. Then later I tried the 2nd file and same. Earlier I used to flash both fine but only 2nd would boot me fine and main zip will lead to bootloop.
yeah, update.app contains all, not sure why its not working and flashing the boot.img directly.

In fastboot phone is locked FRP unlocked. I cannot flash boot.img, says
FAILED (remote: command not allowed)

Dazed No More said:
In fastboot phone is locked FRP unlocked. I cannot flash boot.img, says
FAILED (remote: command not allowed)
Click to expand...
Click to collapse
Tried unlocking the BL? Once that is done, you may proceed further

Unlocked BL and flashed boot.img from B110 update.app and still no boot
edit: last night booting into recovery (vol + and power) gave me three options: Reboot/Wipe Date Reset/Wipe Cache. Since unlocking the bootloader and flashing the boot.img today the same button combo launches eRecovery with Wifi update option but it fails getting package info.
Is it normal for factory reset after lock/relock to go from 15% to 100% and say succesful?

I used the team mt huawei multi tool app and after using the unbrick option it flashed boot, cust, recovery, system and userdata.img and my phone now boots! Shashank thank you for taking the time to respond.

I messed up with Huawei Mate 9. Please Help.

Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?

Please someone help me i spend 2 days and still nothing! How can i open this phone? Stock rom, with/without root, custom rom whatever, just tell me how can i open this phone

up

You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition

shae23 said:
You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition
Click to expand...
Click to collapse
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.

cannurkars said:
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.
Click to expand...
Click to collapse
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware

ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse
I will try it. Thank you very much.

cannurkars said:
Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?
Click to expand...
Click to collapse
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.

ConnerZhao929 said:
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.
Click to expand...
Click to collapse
No it wasn't work for me. But thank for your attention. I'm glad to find a good person to help me and my problem solved about 1-2 hour ago.

Special Request
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse

AniMaL92 said:
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
Click to expand...
Click to collapse
What's your firmware now?
You can get that info in Fastboot using
Code:
fastboot oem get-product-model
fastboot oem get-build-number
Since your recovery and fastboot still functions you probably will only need to use HWOTA to get back to stock.
It can be found here: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
But post your cust/build before proceeding.
Also cust.img is found in UPDATE.APP in the hw data zip.

Problem Solved - Somewhat
Hey ante. Thanks for the promt reply. I got it solved by using CHIMERA tool.
Would like to suggest others also stuck with same issue to use CHIMERA.
Note - It is a paid tool and 100% legit and it can help with all problems related to FRP, Bootloader Lock / Unlock & also flashes back to factory firmware.
However what I am facing now I have flashed another version of firmware which isn't my region and some features of my phone like fingerprint scanner and other things are not working but phone is back to live. So Im glad and looking forward to searching for clean Oreo Firmware for my region to flash using CHIMERA Again.
Also, the sick and stupid part of it. I went to the service center and a person non-technical told me straight that you lost your device and it's of no use now. We cannot fix such issues 99% but I'll still ask my team and let you know after 3 days.
Thank God I didn give them and wasted my time and money.
As soon as I returned, I followed up to things and got it done myself. :good:
Anybody can possibly suggest a official firmware Oreo EMUI for Middle East Region!? If not which one can be flashed instead and where to download from?