Hello,
I recently got my new Mate 10 Lite and wanted to debrand it, update to Oreo, root and install useful Magisk plugins. Everything went fine and I got my phone debranded from C738 to C432, then I updated to Oreo B330 and tried to root. Couldn't succeed with dry Magisk 16.6 install, so I installed 16.0. Decided to give 16.6 a shot one more time but the story went the same, no 16.6 was installed and Magisk Manager had weird, arabic-like layout (inverted), so I wanted to patch boot image with 16.0 once again in order to clear all the "leftovers" 16.6 could leave. Unfortunately, after this operation my phone got softbricked, constantly entering ERROR MODE trying to boot both system and recovery, getting respectively Func NO 10 and 2 (boot image load failed!) and Func NO 11 and 2 (recovery image load failed!). I hoped that maybe I could just recover via TWRP installing it once again, but, unfortunately, it wasn't a thing and I couldn't boot anyway. I was, of course, installing Mate 10 Lite Oreo version of TWRP. HwOTA 8 doesn't help as well. dload update leaves me with crash at 5%. Any hopes for my baby, or only locking a bootloader and sending on warranty will do (if they even accept it)?
Thank you in advance,
Seven-
EDIT: Fixed. Just had to reflash kernel.img. As simple as that. Seems much more harder, doesn't it?
So here's a quick solution:
1. Go here: http://pro-teammt.ru/firmware-database/ Download Firmware Finder, search for Oreo ROM for your specific phone model and codename
2. Find update.zip. Unzip it and put UPDATE.APP to Huawei Update Extractor
3. Extract kernel.img and flash it via fastboot - "fastboot flash kernel kernel.img"
4. Reboot, should work from now.
This is solution for Oreo as I think it's a problem specific for Oreo because this partitioning system, but if you experience such problem with Nougat, download Nougat ROM and change all "kernel" words to "boot".
Hope you have a nice day, I'm glad that I might have helped a few of fellow Mate 10 Lite users
you can enter in recovery mode true?
try rebrand your device to stock and download the stock rom to flash via HwOTA or dload.
Can boot only to stock recovery, dload and fastboot. As I said, I rebranded to C432 and did it successfully and installed ROM for this version. I tried flashing both Nougat I used to rebrand and Oreo, both crash at 5% when flashing via dload, HwOTA doesn't work as it flashes TWRP you have to boot into, and I can't enter TWRP because I get Func NO 11 and 2 (recovery image load failed!). I tried 2 different TWRPs, this one from HwOTA and Azan Mughal's version. Neither of them works. Nougat versions don't even flash properly, which is normal because I "have" Oreo
Well, I might just say that this is the toughest phone I have ever been modding. I have just noticed that plugging the phone to charger also makes it enter ERROR MODE, which is also normal in this situation as boot image fails to load.
Just thinking... Might it be that recovery and boot partitions are somehow unformatted? I have no other idea why would recovery boot fail when installed. But on the other hand if it was unformatted it would either format it properly or not install at all, right?
EDIT: Tried to erase recovery but "Command not allowed".
I've got the exact same problem except dload because I don't know how to do that.
dload works with emui 4.x
It should always work. It's there for a reason, isn't it?
I might have discovered why am I getting boot and recovery failures. Obviously having Oreo there are no boot and recovery partitions but recovery_ramdisk and I think kernel (notsure) instead. I only have a question how do I repartition mobile device? There must be a way, right?
Like MTK-based devices have SP Flash Tool.
One click away from pushing all the files from UPDATE.APP from stock Oreo through Fastboot, is it safe enough? I mean, what if, for example, fastboot.iso fails to write or is corrupted, completely bricked phone?
Never been so scared modifying a phone, this one is so tough to mod and soft at once...
Can't boot to system, recovery, installing through dload crashes at 5%
i am in same problem plz developers do some work on these issues of this device to get back our devices thanks.
i have tried many mehods (dload, update. app, update. zip etc...... 1 different problem i got is when fladhing boot. img or recovery. img using cmd fastboot flash boot boot. img
failed remote; partition get size error.
---------- Post added at 09:17 PM ---------- Previous post was at 09:13 PM ----------
SevenUp9 said:
It should always work. It's there for a reason, isn't it?
I might have discovered why am I getting boot and recovery failures. Obviously having Oreo there are no boot and recovery partitions but recovery_ramdisk and I think kernel (notsure) instead. I only have a question how do I repartition mobile device? There must be a way, right?
Like MTK-based devices have SP Flash Tool.
Click to expand...
Click to collapse
keep searchig
@BaBa Yoga, you have Oreo, right? Try installing proper TWRP for 8.0 then and flash it as recovery_ramdisk instead, because it's how do partitions on Oreo look like. But I doubt it changes anything and makes your phone alive again.
FIXED IT, FIXED IT!!! Reflashed kernel and it works. Guys up here, you might want to try this out. As I thought, Magisk must have messed up with my boot file.
Adding solution to the main post.
SevenUp9 said:
@BaBa Yoga, you have Oreo, right? Try installing proper TWRP for 8.0 then and flash it as recovery_ramdisk instead, because it's how do partitions on Oreo look like. But I doubt it changes anything and makes your phone alive again.
Click to expand...
Click to collapse
yes oreo.... i am still trying twrps of azan mughal and other twrp for my device but now when i install custom recovery {fastboot flash recovery_ramdisk recovery. img}
it shows ok but when i reboot device in recovery mode there is no twrp recovery....... only stock recovery
---------- Post added at 10:02 PM ---------- Previous post was at 09:55 PM ----------
SevenUp9 said:
FIXED IT, FIXED IT!!! Reflashed kernel and it works. Guys up here, you might want to try this out. As I thought, Magisk must have messed up with my boot file.
Adding solution to the main post.
Click to expand...
Click to collapse
great bro....
plz share info here how to reflash kernal
@BaBa Yoga, I posted simple walkthrough in the first post, if you ever need explanation just ask here, I'll try to be more detailic then. Good luck unbricking your phone bro :victory:
SevenUp9 said:
Hello,
I recently got my new Mate 10 Lite and wanted to debrand it, update to Oreo, root and install useful Magisk plugins. Everything went fine and I got my phone debranded from C738 to C432, then I updated to Oreo B330 and tried to root. Couldn't succeed with dry Magisk 16.6 install, so I installed 16.0. Decided to give 16.6 a shot one more time but the story went the same, no 16.6 was installed and Magisk Manager had weird, arabic-like layout (inverted), so I wanted to patch boot image with 16.0 once again in order to clear all the "leftovers" 16.6 could leave. Unfortunately, after this operation my phone got softbricked, constantly entering ERROR MODE trying to boot both system and recovery, getting respectively Func NO 10 and 2 (boot image load failed!) and Func NO 11 and 2 (recovery image load failed!). I hoped that maybe I could just recover via TWRP installing it once again, but, unfortunately, it wasn't a thing and I couldn't boot anyway. I was, of course, installing Mate 10 Lite Oreo version of TWRP. HwOTA 8 doesn't help as well. dload update leaves me with crash at 5%. Any hopes for my baby, or only locking a bootloader and sending on warranty will do (if they even accept it)?
Thank you in advance,
Seven-
EDIT: Fixed. Just had to reflash kernel.img. As simple as that. Seems much more harder, doesn't it?
So here's a quick solution:
1. Go here: Download Firmware Finder, search for Oreo ROM for your specific phone model and codename
2. Find update.zip. Unzip it and put UPDATE.APP to Huawei Update Extractor
3. Extract kernel.img and flash it via fastboot - "fastboot flash kernel kernel.img"
4. Reboot, should work from now.
This is solution for Oreo as I think it's a problem specific for Oreo because this partitioning system, but if you experience such problem with Nougat, download Nougat ROM and change all "kernel" words to "boot".
Hope you have a nice day, I'm glad that I might have helped a few of fellow Mate 10 Lite users
Click to expand...
Click to collapse
bro i did not find firmware for my region i. e RNE L21 C185..... I FOUND DOME FIRMWARES on other sites one of thek i extract update. app using huawei updates extractor but there is no kernal.img file..... i found i. gs of boot, system, recovery, cust etc but no kernal. img what i do.....
You downloaded Nougat then, and you have to download Oreo that ends with B3xx, in your case then it will be RNE-L21C185B3xx There must be Oreo for C185, I know that because I was looking at C185 too when I was rebranding but then I noticed that C432 is what I should install for my region.
http://pro-teammt.ru/firmware-database/?firmware_model=rne-l21c185B3 - these are all the official Oreo builds for your specific region. I think all of them should do, I am certain that all the kernels in these packages are similar. Eventually you can just flash another one later
SevenUp9 said:
You downloaded Nougat then, and you have to download Oreo that ends with B3xx, in your case then it will be RNE-L21C185B3xx There must be Oreo for C185, I know that because I was looking at C185 too when I was rebranding but then I noticed that C432 is what I should install for my region.
[m/?firmware_model=rne-l21c185B3[/url] - these are all the official Oreo builds for your specific region. I think all of them should do, I am certain that all the kernels in these packages are similar. Eventually you can just flash another one later
Click to expand...
Click to collapse
should i download OTA-MF or FULLOTA-MF?
I Hope i could find kernal file now....
i am downloading FULLOTA-MF thanks to provide me firmware list of my region
thanks sevenup9 for getting back my device out of that problem i flash the kernel successfully wnd get back my twrp as well now what next..???????? thanks again
---------- Post added at 06:54 AM ---------- Previous post was at 06:01 AM ----------
i flashed kernel. img, cust. img, system. img and then reboot now i have twrp but still in bootloop what next
Yeah, good that you downloaded FullOTA, as it's a full system image. I assume there is no system.img or kernel.img in OTA package at all.
Since you have TWRP now but stuck in bootloop, try to wipe data and cache and try to boot again. If you don't succeed, then maybe try getting all of the 3 zips from FullOTA package on SD card (or USB stick if you have a USB OTG cable) and flash them via TWRP, starting from "update.zip". Should work just fine. Maybe your phone got more partitions messed up, but that should be recoverable as you have a good base being able to boot into TWRP
SevenUp9 said:
Yeah, good that you downloaded FullOTA, as it's a full system image. I assume there is no system.img or kernel.img in OTA package at all.
Since you have TWRP now but stuck in bootloop, try to wipe data and cache and try to boot again. If you don't succeed, then maybe try getting all of the 3 zips from FullOTA package on SD card (or USB stick if you have a USB OTG cable) and flash them via TWRP, starting from "update.zip". Should work just fine. Maybe your phone got more partitions messed up, but that should be recoverable as you have a good base being able to boot into TWRP
Click to expand...
Click to collapse
i did usb mathed as well but when flash update. zip via twrp error 9 shows
---------- Post added at 10:10 AM ---------- Previous post was at 10:06 AM ----------
then usi g fastboot i flash recovery_ramdisk kernel cust system ramdisk all these images..... now reboot and i lost twrp and it replaced with stock recovery.... in stock recovery i wiped cache... done... wipe data and factory reset..... stuck at 0% after 10 minutes... plz bro
---------- Post added at 10:12 AM ---------- Previous post was at 10:10 AM ----------
i didn't lock bootloader yet... i keep it still unlock
Related
Ive tried to install TWRP via adb about 3 times now and it just will not work. The install goes perfectly but when i try to enter recovery mode from the phone being turned off, it just infinitely says my phone is booting. Does not go into twrp at all. My Nougat installation is extremely buggy. I have no model number, i went through complete hell to even enter my google account info. Everything seems to work fine on nougat though but i just cannot stand the bugged installation. Could really use some help.....
EDIT: Flashed TWRP through adb sideload and the phone just sits there still even when i enabled usb debugging and all. Bluetooth doesnt work and NFC doesnt work. But everything else works perfectly fine. It would just be nice to get the full functionality of my phone back. Phone isnt rooted. Just need some quick assistance.... Thanks for whomever answers.
United States user
Huawei NXT-L29
Android 7.0
have you tried to flash through fastboot the twrp in this thread? http://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617 (do not worry if is for mate 9. it works anyway)
also please check if your bootloader is unlocked before doing it.
download srk huawei tool, is pretty easy to use: http://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
First you need to roll back to ur previous firmware.
You can try dload method using ur previous firmware or use rollback package.http://forum.xda-developers.com/mate-8/general/best-easiest-to-rollback-to-emui-4-0-t3507399/page1
When ur back with a working firmware,you have to unlock bootloader if its locked again,and flash twrp.
Once done u have to download nougat firmware with the data zip ment for ur region.
Go to twrp install the 2 zips( firmware and data) than reboot.
If the phone didn't boot after 10 minutes ,reboot into recovery( twrp will be replaced with stock recovery after installing the zips) and do factory reset.
Omg i forgot that the bootloader might be locked.. Ill try to find the comand to put my unlock code in and get back to this thread.. Thanks so much for suggestions.. Though ive had tkbdeal with it nougat is FANTASTIC
UPDATE: So far nothing is working. Tried the rollback packages and im still on nougat. I have an actual firmware version now. But its Russian firmware? Trying the dload method with L29185 firmwares like 200 and 320 and nothing works. Tried many things and now i cannot even install twrp. The install process would work it just wouldnt do anything when i tried to boot to twrp but now when i try to flash twrp over the recovery it just completely fails. no error code it just says it cannot find a file by that name or it cannot read it. adb says the bootloader is unlocked. Am i just completely stuck here on a buggy nougat installation? Is there any way to force a twrp backup to load outside of twrp?
gm007 said:
First you need to roll back to ur previous firmware.
You can try dload method using ur previous firmware or use rollback package.http://forum.xda-developers.com/mate-8/general/best-easiest-to-rollback-to-emui-4-0-t3507399/page1
When ur back with a working firmware,you have to unlock bootloader if its locked again,and flash twrp.
Once done u have to download nougat firmware with the data zip ment for ur region.
Go to twrp install the 2 zips( firmware and data) than reboot.
If the phone didn't boot after 10 minutes ,reboot into recovery( twrp will be replaced with stock recovery after installing the zips) and do factory reset.
Click to expand...
Click to collapse
ok so now most of this is done. Excuse me for pulling you aside I do hope you reply. Im having an issue getting twrp to work. Im on an official stock firmware. Bootloader unlocked, flashed twrp and im stuck at the screen that says my device cannot be trusted. Its on its way to booting to twrp but it completely wont. Its just stuck at that screen for about 5 minutes now. Ive let it ride and i think its just frozen there. Any ideas? im using the twrp posted by the commenter above you. The 3.0.2-1 and this is where im at.
Well now i cannot get my phone to stop wanting to factory reset itself. It keeps trying to boot into recovery and twrp is flashed over stock recovery and twrp still wont boot even though bootloader is unlocked. it freezes at the unsafe device booting screen every time it starts. I think this phone is bricked beyond repair now. Nougat update completely ruined my phone.
OcazPrime said:
ok so now most of this is done. Excuse me for pulling you aside I do hope you reply. Im having an issue getting twrp to work. Im on an official stock firmware. Bootloader unlocked, flashed twrp and im stuck at the screen that says my device cannot be trusted. Its on its way to booting to twrp but it completely wont. Its just stuck at that screen for about 5 minutes now. Ive let it ride and i think its just frozen there. Any ideas? im using the twrp posted by the commenter above you. The 3.0.2-1 and this is where im at.
Click to expand...
Click to collapse
That twrp is for mate 9 and will not work for mate 8 you need to fastboot another twrp. You need to flash another twrp you can try the twrp for the honor 8 which will work on mate 8
http://forum.xda-developers.com/honor-8/how-to/twrp-nougat-edition-t3504140
You will be to get into this twrp but not all functions are working.
---------- Post added at 02:03 AM ---------- Previous post was at 01:59 AM ----------
OcazPrime said:
Well now i cannot get my phone to stop wanting to factory reset itself. It keeps trying to boot into recovery and twrp is flashed over stock recovery and twrp still wont boot even though bootloader is unlocked. it freezes at the unsafe device booting screen every time it starts. I think this phone is bricked beyond repair now. Nougat update completely ruined my phone.
Click to expand...
Click to collapse
As long as you can get into fastboot mode, you can recover. Try to flash the nougat stock recovery then use the rollback package (try all three to see which one work) then you can dload back to your previous rom.
---------- Post added at 02:06 AM ---------- Previous post was at 02:03 AM ----------
Icchan said:
have you tried to flash through fastboot the twrp in this thread? http://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617 (do not worry if is for mate 9. it works anyway)
also please check if your bootloader is unlocked before doing it.
download srk huawei tool, is pretty easy to use: http://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
Click to expand...
Click to collapse
Did you try it and it works for you? I flashed this twrp and my phone just get stuck at the screen "your phone is booting" and I have to flash another twrp.
In total what ive done up to my current state:
Flashed nougat in. Installed wrong tried reverting and noticed twrp wouldnt boot. Downloaded rollback packages. Only the russian one worked and ended up on C636B180 firmware. Checked my other recovery thread for twrp and got twrp working finally. TWRP wont flash any roms for some reason. When it flashes roms it doesnt actually install anything. When i boot it just sits there on the screen you get with an unlocked bootloader i havent let it sit there for long because when i get back into twrp and check the file manager, there are no files in sdcard. So my rom straight up didnt install. When i check it on my pc the storage size hasnt decreased at all. Its just completely screwed right now and im so frustrated im probably getting a new phone.
OcazPrime said:
In total what ive done up to my current state:
Flashed nougat in. Installed wrong tried reverting and noticed twrp wouldnt boot. Downloaded rollback packages. Only the russian one worked and ended up on C636B180 firmware. Checked my other recovery thread for twrp and got twrp working finally. TWRP wont flash any roms for some reason. When it flashes roms it doesnt actually install anything. When i boot it just sits there on the screen you get with an unlocked bootloader i havent let it sit there for long because when i get back into twrp and check the file manager, there are no files in sdcard. So my rom straight up didnt install. When i check it on my pc the storage size hasnt decreased at all. Its just completely screwed right now and im so frustrated im probably getting a new phone.
Click to expand...
Click to collapse
If you are back to C636B180 firmware, you need to unlock the phone, flash twrp, which is fully working in emui 4, root the phone then use SRK to change to the software region you want:
http://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
Can i just download a superuser zip and flash it with twrp to root? Havemt rooted this phone in forever cuz i never did much with it since my first and only rooting
The reason why recovery doesn't work is due to kernel isn't supported on new bootloader
LastStandingDroid said:
The reason why recovery doesn't work is due to kernel isn't supported on new bootloader
Click to expand...
Click to collapse
What?
The previous twrp version doesn't work on nougat due to kernel.
I guess it's selected by bootloader or the new teecd
You can download twrp as mentioned here
http://forum.xda-developers.com/showthread.php?p=70126187
Also @tknguyencsu what works in that version for your mate 8?
Does MTP work and adb?
Data won't work unless you use encrypted version.
Sent from my FRD-L09 using Tapatalk
OcazPrime said:
Ive tried to install TWRP via adb about 3 times now and it just will not work. The install goes perfectly but when i try to enter recovery mode from the phone being turned off, it just infinitely says my phone is booting. Does not go into twrp at all. My Nougat installation is extremely buggy. I have no model number, i went through complete hell to even enter my google account info. Everything seems to work fine on nougat though but i just cannot stand the bugged installation. Could really use some help.....
EDIT: Flashed TWRP through adb sideload and the phone just sits there still even when i enabled usb debugging and all. Bluetooth doesnt work and NFC doesnt work. But everything else works perfectly fine. It would just be nice to get the full functionality of my phone back. Phone isnt rooted. Just need some quick assistance.... Thanks for whomever answers.
United States user
Huawei NXT-L29
Android 7.0
Click to expand...
Click to collapse
Budy I have same problem Pls note me when u find somethıng :=)) ıf I then ı will let u know.
TWRP Recovery 3.0.3
Download TWRP Recovery 3.0.3
http://sillanwali.com/downloads/twp-3.0.3.img
Build Number: FRD-L04C567B320 (USA)
Files for DOWNLOAD:
Download link:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1278/g104/v68366/f1/full/update.zip
Region Patch:
http://update.hicloud.com:8180/TDS/...66/f1/full/hw/usa/update_data_full_hw_usa.zip
How to install:
1. Requirements: Your device needs to have TWRP custom recovery installed and has to be rooted.
2. Before proceeding make sure that your device model is FRD-L04 from Settings > About phone.
3. Download the update.zip package from above links and copy it to your Sdcard /dload folder.
4. Turn your phone off and reboot into recovery mode by hold Vol up + Power for a few seconds.
5. Back up all the partitions into the external microSD card (recommended).
6. Now go to Install and select the update.zip package you copied to your Sdcard.
7. Upon installation wipe the cache and reboot your phone.
8. In case you encounter issues with Bluetooth, NFC, etc you can try flashing the region package provided above through TWRP.
Warning: As mentioned earlier, this is a beta update that contains many bugs and has several compatibility issues with hardware and 3rd party apps.
USE IT AT YOUR OWN RISK, I'M NOT RESPONSIBLE FOR ANY BROKEN RELATED TO IT
perzan07 said:
Build Number: FRD-L04C567B320 (USA)
Files for DOWNLOAD:
Download link:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1278/g104/v68366/f1/full/update.zip
Region Patch:
http://update.hicloud.com:8180/TDS/...66/f1/full/hw/usa/update_data_full_hw_usa.zip
How to install:
1. Requirements: Your device needs to have TWRP custom recovery installed and has to be rooted.
2. Before proceeding make sure that your device model is FRD-L04 from Settings > About phone.
3. Download the update.zip package from above links and copy it to your Sdcard /dload folder.
4. Turn your phone off and reboot into recovery mode by hold Vol up + Power for a few seconds.
5. Back up all the partitions into the external microSD card (recommended).
6. Now go to Install and select the update.zip package you copied to your Sdcard.
7. Upon installation wipe the cache and reboot your phone.
8. In case you encounter issues with Bluetooth, NFC, etc you can try flashing the region package provided above through TWRP.
Warning: As mentioned earlier, this is a beta update that contains many bugs and has several compatibility issues with hardware and 3rd party apps.
USE IT AT YOUR OWN RISK, I'M NOT RESPONSIBLE FOR ANY BROKEN RELATED TO IT
Click to expand...
Click to collapse
Thanks ..
I might as well post this here -> -> How to: Root and repair data on the FRD-L04 - B320
https://forum.xda-developers.com/showpost.php?p=70266853&postcount=262
Will android pay stop working even if I use the official beta 7.0?
Thanks man, but is there any successful way to flash B324 so far?
Is Wi-Fi calling enabled in this beta?
Managed to do the same using Charles app (see https://forum.xda-developers.com/ho...-to-nougat-t3510275/post69885525#post69885525) without any unlocking and flashing.
I have the FRD-L04B567 phone. I installed the TWRP for the Honor 8. I have installed a different ROM (CM13.1 ROM) successfully. I followed your instructions to the "T" in post #1 . The install of update.zip stopped at /cust with an error. I tried wiping and rebooting but am stuck in the "honor" bootup screen. Unable to force back into TWRP or fastboot or ADB at this time. Still picking up the pieces....
UPDATE: I forced phone into Huawei eRecovery screen and selected factory reset/wipe That got Nougat running but there is no keyboard and Google will only allow voice for any input. Since my wifi is encrypted, I cant give Nougat a password to get on the internet. I am creating a temporary unencrypted network to see if I can get further.
UPDATE: TWRP was wiped so I will reinstall. Then I will try update the regional update (second update mentioned)
UPDATE: Reflashed TWRP 3.0.2.0 for Honor 8, I can get into the bootloader but not recovery, eRecovery works but...(worthless). I cant flash the second update.zip because I cant get TWRP started. Obviously 3.0.2.0 is not compatible with Nougat, I may try 3.0.3.0? why not...
UPDATE - Flashing TWRP 3.0.3.0 was dumb. Now ADB sees the device (good) but I can not get to bootloader or recovery. TWRP flashes (displays) once a second and will not start (bad) . Hopefully someone can learn from my quest.
So, can someone help me proceed from a state where ADB sees the device? thanks Maybe extract update.zip?
thekubiaks said:
So, can someone help me proceed from a state where ADB sees the device? thanks Maybe extract update.zip?
Click to expand...
Click to collapse
This guy
https://forum.xda-developers.com/member.php?u=4210629
Could help you recover, but he will be back only after 15th Jan.
Have you tried Huawei's hisuite? It has a recovery option..
yalokiy said:
This guy
https://forum.xda-developers.com/member.php?u=4210629
Could help you recover, but he will be back only after 15th Jan.
Have you tried Huawei's hisuite? It has a recovery option..
Click to expand...
Click to collapse
Thanks for the reply, I finally got TWRP 3.0.2.0 for Honor 8 flashed (but now it won't work), I believe Nougat and TWRP aren't compatible. Huawei Hisuite said that phone was fine and recovery not necessary??? I disagree. I think I will have to wait for TWRP that is Nougat compatible with FRD-L04
thekubiaks said:
I have the FRD-L04B567 phone. I installed the TWRP for the Honor 8. I have installed a different ROM (CM13.1 ROM) successfully. I followed your instructions to the "T" in post #1 . The install of update.zip stopped at /cust with an error. I tried wiping and rebooting but am stuck in the "honor" bootup screen. Unable to force back into TWRP or fastboot or ADB at this time. Still picking up the pieces....
UPDATE: I forced phone into Huawei eRecovery screen and selected factory reset/wipe That got Nougat running but there is no keyboard and Google will only allow voice for any input. Since my wifi is encrypted, I cant give Nougat a password to get on the internet. I am creating a temporary unencrypted network to see if I can get further.
UPDATE: TWRP was wiped so I will reinstall. Then I will try update the regional update (second update mentioned)
UPDATE: Reflashed TWRP 3.0.2.0 for Honor 8, I can get into the bootloader but not recovery, eRecovery works but...(worthless). I cant flash the second update.zip because I cant get TWRP started. Obviously 3.0.2.0 is not compatible with Nougat, I may try 3.0.3.0? why not...
UPDATE - Flashing TWRP 3.0.3.0 was dumb. Now ADB sees the device (good) but I can not get to bootloader or recovery. TWRP flashes (displays) once a second and will not start (bad) . Hopefully someone can learn from my quest.
So, can someone help me proceed from a state where ADB sees the device? thanks Maybe extract update.zip?
Click to expand...
Click to collapse
If you want to get back to any working state, i recovered from 7.0 unbootable to vanilla 6.0 like so (for frd-l09, but probably still applies):
https://forum.xda-developers.com/honor-8/how-to/honor-8-bricked-t3521813/post70326674#post70326674
// edit, also for completeness, i then flashed twrp 3.0.2 (official) and installed the cm 7.1.1 from the other thread here. All working fine.
fuflo,
thank you for your reply, it helped me get my Honor 8 back up and running.... I am now running CM 14.1 and Nougat 7.1.1 on my FRD-L04
Cheers
---------- Post added at 05:32 AM ---------- Previous post was at 05:31 AM ----------
fuflo,
thank you for your reply, it helped me get my Honor 8 back up and running.... I am now running CM 14.1 and Nougat 7.1.1 on my FRD-L04
Cheers
B320? I used these update files and mine says B317. Am I missing something?
jim262 said:
B320? I used these update files and mine says B317. Am I missing something?
Click to expand...
Click to collapse
Look again in the thread closely, you'll find another script to go to B320
Same problem as above, I could flash the update.zip, but not the USA package, maybe I didn't have the right TWRP version?
I have European honor8 32gb b389
i install lineage os 7.1.2 but dont like it and wont do restore backup with twrp, but after restore the phone blocked on honor screen.
i tried everything, and now i have a lot of confusion, i tried dload, but nothing happened when i turn on with +-power. I try with huawai extractor to flash boot system cust and recovery but nothing device go in bootloop. if i flash recovery from b131 firmware i can go in dload but freeze at 5%
what i can do? sorry for my English, i speak Italian and Russian if somebody want to help me in pm.
crn4 said:
I have European honor8 32gb b389
i install lineage os 7.1.2 but dont like it and wont do restore backup with twrp, but after restore the phone blocked on honor screen.
i tried everything, and now i have a lot of confusion, i tried dload, but nothing happened when i turn on with +-power. I try with huawai extractor to flash boot system cust and recovery but nothing device go in bootloop. if i flash recovery from b131 firmware i can go in dload but freeze at 5%
what i can do? sorry for my English, i speak Italian and Russian if somebody want to help me in pm.
Click to expand...
Click to collapse
Are you sure you're using the rollback package before? You can download it from honor official website, then you move the firmware file in a dload folder on your sdcard. Boot up using both + and - buttons and the power button in the same time and the phone will force the flashing of the rollback ( package needed to go back from android 7 to android 6) file. Then you have to download the android 6 firmware for your device from the honor official website again and flash it with the same process of the rollback package. If you can't undestand i can try to explain it in italian
davide.melkior said:
Are you sure you're using the rollback package before? You can download it from honor official website, then you move the firmware file in a dload folder on your sdcard. Boot up using both + and - buttons and the power button in the same time and the phone will force the flashing of the rollback ( package needed to go back from android 7 to android 6) file. Then you have to download the android 6 firmware for your device from the honor official website again and flash it with the same process of the rollback package. If you can't undestand i can try to explain it in italian
Click to expand...
Click to collapse
thnx , i know this method, i tried it yesterday but don't worked, now i retry and reply to you the results
ok, i tried now the first update.app to rollback but device freeze (Your device is booting now)
i think i need to flash from fastboot stock recovery from b389 firmware before do this
crn4 said:
thnx , i know this method, i tried it yesterday but don't worked, now i retry and reply to you the results
Click to expand...
Click to collapse
Unless you flash the rollback package you can't flash older version. Not sure if rollback package for your model os released
---------- Post added at 03:50 PM ---------- Previous post was at 03:49 PM ----------
crn4 said:
thnx , i know this method, i tried it yesterday but don't worked, now i retry and reply to you the results
ok, i tried now the first update.app to rollback but device freeze (Your device is booting now)
i think i need to flash from fastboot stock recovery from b389 firmware before do this
Click to expand...
Click to collapse
Ofcourse you need to flash the stock recovery. Are you trying in twrp?
davide.melkior said:
Are you sure you're using the rollback package before? You can download it from honor official website, then you move the firmware file in a dload folder on your sdcard. Boot up using both + and - buttons and the power button in the same time and the phone will force the flashing of the rollback ( package needed to go back from android 7 to android 6) file. Then you have to download the android 6 firmware for your device from the honor official website again and flash it with the same process of the rollback package. If you can't undestand i can try to explain it in italian
Click to expand...
Click to collapse
shashank1320 said:
Unless you flash the rollback package you can't flash older version. Not sure if rollback package for your model os released
---------- Post added at 03:50 PM ---------- Previous post was at 03:49 PM ----------
Ofcourse you need to flash the stock recovery. Are you trying in twrp?
Click to expand...
Click to collapse
yes i tried to flash twrp with fastboot but cant reboot the phone in twrp recovery
crn4 said:
yes i tried to flash twrp with fastboot but cant reboot the phone in twrp recovery
Click to expand...
Click to collapse
Flash stock recovery and try
shashank1320 said:
Flash stock recovery and try
Click to expand...
Click to collapse
yes i tried a lot of times, i have huawei tool, i tried now another time, but with the tool can't reboot in twrp, and with power and+ also
crn4 said:
yes i tried a lot of times, i have huawei tool, i tried now another time, but with the tool can't reboot in twrp, and with power and+ also
Click to expand...
Click to collapse
Are you able to get into the bootloader?
shashank1320 said:
Are you able to get into the bootloader?
Click to expand...
Click to collapse
what do you mean?
in fastboot (- and pw) i have PHONE unlocked and FRP unlocked
crn4 said:
what do you mean?
in fastboot (- and pw) i have PHONE unlocked and FRP unlocked
Click to expand...
Click to collapse
Just flash the stock recovery there in fastboot. And reboot. Shutdown the phone and use dload method
Basically you missed one thing before restoring stock backup. You should have performed a full factory reset using the second recovery and then restored your TWRP backup.
Your device being stuck on Honor screen is because you forgot to enable encryption (that is done by performing a factory wipe through second recovery).
shashank1320 said:
Just flash the stock recovery there in fastboot. And reboot. Shutdown the phone and use dload method
Click to expand...
Click to collapse
I tried flash stock recovery from different firmwares and after try with dload, but dont work, the device freeze e dont wont boot dload, with recovery from b131 firmware (MM) the dload go on but freeze at 5%, now i try with b389 (Nougat) fw, within 15 minutes I tell you the result
hackslash said:
Basically you missed one thing before restoring stock backup. You should have performed a full factory reset using the second recovery and then restored your TWRP backup.
Your device being stuck on Honor screen is because you forgot to enable encryption (that is done by performing a factory wipe through second recovery).
Click to expand...
Click to collapse
Ahhh ok, and now for recover my phone what i need to do ?
now i flashed boot, cust , recovery and system from b389 firmware but nothing, the phone dont boot, dont want to dload, i dont know what to do....
crn4 said:
Ahhh ok, and now for recover my phone what i need to do ?
Click to expand...
Click to collapse
Follow my guide here https://forum.xda-developers.com/honor-8/how-to/guide-flashing-unapproved-firmwares-t3668306
Before you do it, flash stock Nougat recovery (if you were on EMUI 5) and perform a factory reset. Then flash TWRP again through Fastboot.
Use the TWRP method since you are unable to boot to EMUI. Chose any firmware you want, whether it be Marshmallow or Nougat.
hackslash said:
Follow my guide here https://forum.xda-developers.com/honor-8/how-to/guide-flashing-unapproved-firmwares-t3668306
Before you do it, flash stock Nougat recovery (if you were on EMUI 5) and perform a factory reset. Then flash TWRP again through Fastboot.
Use the TWRP method since you are unable to boot to EMUI. Chose any firmware you want, whether it be Marshmallow or Nougat.
Click to expand...
Click to collapse
i flashed stock recovery from you guide but i cant boot in recovery, i flashed different recoverys, from MM to Nougat but nothing i think this is bootloader problem
edit:
in fastboot i see this
ap_s_abnormal na
what is the signification?
crn4 said:
i flashed stock recovery from you guide but i cant boot in recovery, i flashed different recoverys, from MM to Nougat but nothing i think this is bootloader problem
edit:
in fastboot i see this
ap_s_abnormal na
what is the signification?
Click to expand...
Click to collapse
Are you following the steps exactly as mentioned?
You need to flash TWRP first then setup your device to install the firmware. Read the TWRP section again and follow it exactly as mentioned.
Nothing to worry about that Fastboot status. It is normal.
SOLVED!!!!!! thanks at all people, and very sorry for my English,
i relock end unlock boot loader many times and i flash every is flashable from firmware b131 (boot, system......) and whola!!!! the system dont boot but the dload after this has been restored to work, now i update to last fw and root and dont touch more nothing =D
crn4 said:
SOLVED!!!!!! thanks at all people, and very sorry for my English,
i relock end unlock boot loader many times and i flash every is flashable from firmware b131 (boot, system......) and whola!!!! the system dont boot but the dload after this has been restored to work, now i update to last fw and root and dont touch more nothing =D
Click to expand...
Click to collapse
Damn. I forgot you could simply flash files from Fastboot.
In the future only flash system, cust, vendor, boot and recovery. Do not attempt to flash any other file.
Still, if you want to update to the latest OTA, my guide is always there to help you out.
hackslash said:
Damn. I forgot you could simply flash files from Fastboot.
In the future only flash system, cust, vendor, boot and recovery. Do not attempt to flash any other file.
Still, if you want to update to the latest OTA, my guide is always there to help you out.
Click to expand...
Click to collapse
now i have another problem, i tried to update with stock updator, but from 6 to 7 go wrong, device boot but dont work right, the keyboard dont exist and other lags, try to factory reset but error. after this i flash twrp and format data but see this : failed to mount /cust /system /data; repair or change file system do the same.
if i flash with dload b131 the phone freeze on honor screen
Hello, I would like some help since I got this device just yesterday.
I got it with the EMUI 4 Android 6.0 stock installed on it. Since there was no update for it I unlocked the bootloader installed twrp rooted and manually flashed EMUI 5 7.0. Everything worked fine.
I created a backup through TWRP and restored it succefully multiple times.
Then I installed the Meticulus TWRP (since I was told it is a prerequisite for the AOSP). I Flashed the AOSP but it stuck during the boot animation (30 minutes afterwards I powered it off).
I reflashed my old TWRP and tried restoring my backup. IT fails with the explanation "Cannot wipe /vendor" while at the top it says "Cannot mount /vendor (invalid argument)" "Cannot mount /product (invalud argument)".
Anyone has a clue how to fix this? Fastboot adb all works so there should be a way to boot into an OS properly?
Since AOSP was not booting i guess you forgot formatting /data partition to ext4... And did u Used Stock vendor and not openkirin ones ?
Gesendet von meinem Honor 6X mit Tapatalk
As said I have replaced the custom TWRP with the default one so I think this should not apply anymore?
The "cannot mount vendor/product" messages came from the default TWRP after I reflashed it again.
At the top it says "cannot mount /vendor" either so I guess that is the actual problem?
It would be nice to get teh AOSP up but I really want to be able to boot into something first honestly.
And did u Used Stock vendor and not openkirin ones
Click to expand...
Click to collapse
Can you please explain? When I flashed your ROM i was on your TWRP. Does this even matter anymore?
At best I would be able to restore my backup.
To me it appears to be caused by the vendor partition.
Is there any way I can manually create that through TWRP?
algg said:
To me it appears to be caused by the vendor partition.
Is there any way I can manually create that through TWRP?
Click to expand...
Click to collapse
Yes you can but not creating it through twrp, but flashing it by fastboot mode: this is because
image (.img) files needs to be flashed by fastboot mode to avoid any kind of problem.
So, you should look for the last version of stock firmware on which you was before going custom, like BLN-L21CXXXB368 for example; tell me your build number and I'll find the package for you. Then, extract from the UPDATE.APP (a very big file that contains every partition in your phone like recovery, vendor, data, ecc. - you'll find this file inside the zip archive that contains the downloaded update) the vendor.img using Huawei Update Extractor, and then flash it through fastboot mode using the command "fastboot flash vendor vendor.img".
Otherwise, you could rely on dload method to reflash a full update package, and this should really fix everything since that it'll be like a new and clean installation of the OS. Then, unlocking the bootloader again and reflash TWRP to finally restore your previous backup made when it was working would be the final step.
Feel free to ask for further help
Thanks for the reply first really appreciate it.
I got the device on EMUI 4 Marshmallow rooted it and unlocked the bootloader then installed the BLN-L21C185B140 which worked smoothly.
I used that update.zip and extracted into dload root folder and started the huawei recovery installer but it said "package not found".
I tried flashing something to vendor before with fastboot but it said command not allowed.
Maybe I am doing something wrong?
algg said:
Thanks for the reply first really appreciate it.
I got the device on EMUI 4 Marshmallow rooted it and unlocked the bootloader then installed the BLN-L21C185B140 which worked smoothly.
I used that update.zip and extracted into dload root folder and started the huawei recovery installer but it said "package not found".
I tried flashing something to vendor before with fastboot but it said command not allowed.
Maybe I am doing something wrong?
Click to expand...
Click to collapse
Latest build on Nougat after the update was BLN-L22C185B140 so? If yes, the package that you need to download is that one. Unluckily i can't help about dload method, i never had fortune using dload because package verification always failed at 5%, i tried every combination but without success.
Command not allowed while flashing vendor image... but flashing others, like recovery or boot.img is allowed? If yes, i don't know what's causing this sorry... I'm sure that my friend @shashank1320 could surely help more than me about how using dload method correctly. Check his signature, it should contain a guide on how to use it
RedSkull23 said:
Latest build on Nougat after the update was BLN-L22C185B140 so? If yes, the package that you need to download is that one. Unluckily i can't help about dload method, i never had fortune using dload, i never be able to using it successfully because package verification always failed at 5%.
Command not allowed while flashing vendor image... but flashing others, like recovery or boot.img is allowed? If yes, i don't know what's causing this sorry... I'm sure that my friend @shashank1320 could surely help more than me about how using dload method correctly. Check his signature, it should contain a guide on how to use it
Click to expand...
Click to collapse
For fastboot yes flashing recovery or boot do work but vendor does not. Maybe the ISO is corrupted somehow I will try it again on a different machine now with the tool.
The link you posted the dload method from is the one where I initially found it as well so yea.
Also it shouldn't matter what I install since the only thing I need is the actual vendor (and product?) partition to work. I have a functional backup just TWRP cannot create/mount the partitions. So even a way to just create them without any data would actually fix my problem (at least I hope so?)
When trying to use Fastboot to flash the vendor/product img I get remote: Command not allowed (yes my bootloader is unlocked) although I can flash the recovery without any problem.
The dload method does not work as said. I placed the extracted content of the update.zip into the dload folder but the software "cannot find" the package.
algg said:
When trying to use Fastboot to flash the vendor/product img I get remote: Command not allowed (yes my bootloader is unlocked) although I can flash the recovery without any problem.
The dload method does not work as said. I placed the extracted content of the update.zip into the dload folder but the software "cannot find" the package.
Click to expand...
Click to collapse
@RedSkull23, thanks for the tag mate.
@algg, No need to flash the vendor image as you already had the stock vendor img.
Now what else you can try is to flash the stock recovery, boot to stock recovery, select factory reset and reboot. It should most probably fix the issue.
If not, reflash the TWRP, a regular TWRO available and not specific to elite or meticulous, but generic one given by OldDroid.
I hope you have downloaded the content for dload, if not, download these for B140.
Flash this via TWRP- http://update.hicloud.com:8180/TDS/...afnaf/update_data_full_BLN-L21_hw_meafnaf.zip
no further changes and Then use dload method for this file- http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1756/g1755/v105054/f1/full/update.zip
Try above and provide feedback. This is what I could think of best possible way to have everything with all system app working.
If not, let me know and I will try to help further.
Hi, I thought I need the vendor image since TWRP (all versions) tell me "Could not mount/wipe vendor" and "Could not mount/wipe product" "invalid argument" for both.
I tried the factory reset before but it does not work. It stops at 23% then shows a red exclamation mark and just goes to the original screen with the 3 buttons (restart, shutdown and wipe).
I am currently trying to get it to recognize my sd card. But somehow it does not work through TWRP it just does not recognize the 8GB SD Card. Also I am currently on the TWRP I was before all of this happened (3.1 openkirin). Without the SD Card recognized I can't put the dload files for it on it and in turn I can't use the dload.
I mean technically it should very well be possible to fix the device since it isn't a real brick and even TWRP and Fastboot load. It's just that all those little things are somehow ruining it.
Edit: I will get a new micro sd for some reason this one does nt work. I'll say then whether the flash then dload worked.
@shashank1320
Mind explaining why I should first use TWRP to flash something and then on top of it use dload?
And why those specific files?
algg said:
Edit: I will get a new micro sd for some reason this one does nt work. I'll say then whether the flash then dload worked.
@shashank1320
Mind explaining why I should first use TWRP to flash something and then on top of it use dload?
And why those specific files?
Click to expand...
Click to collapse
Sure, let me explain.
The first file is the data file which will install few systems apps like file manager, updater, themes, clock, fm radio etc. This will work via dload as well but the installation time is around 3-7 seconds so, over the course of time and flashing few times, i realised that these PV files cannbe flashed via TWRP and it works perfectly fine specific to PV files( twrp won't supoort other stock zips). We foash this first so that it updates your buld number and also does not replace the recovery with stock (as if you flash the main update zip first, it will replace with stock recovery so flashing the 2nd file will be quick but with unstable system apps, sometime).
Now we flash the main zip file with update.app via dload and it Install the main firmware for boot, vendor, recovery, system, usrdata etc.
Hope this explanation helps, if not let me know and I will rephrase myself.
It does help. I did all of this and now in the dload app I get "Software install failed Incompatibilty with current version please download the correct update package".
When I flashed the zip you linked me with TWRP it said "cannot mount /data /vendor /product". Appearently data cannot be mounted since it is encrypted.
Any clue as to what I am doing wrong? Or is this device now a real brick with functioning recovery but without OS?
Is there any way I can "debug" what is going on while the boot animation is playing?
What is confusing me is that the boot animation plays just normal but it simply does not continue to the actual OS.
algg said:
It does help. I did all of this and now in the dload app I get "Software install failed Incompatibilty with current version please download the correct update package".
When I flashed the zip you linked me with TWRP it said "cannot mount /data /vendor /product". Appearently data cannot be mounted since it is encrypted.
Any clue as to what I am doing wrong? Or is this device now a real brick with functioning recovery but without OS?
Click to expand...
Click to collapse
Not bricked..its just Data is not mounted or encryption. Should never encrypted it. NVM.
Do one thing, boot to twrp recovery. Try flashing and get error, then go to main TWRP page and click on reboot, select recovery out of 4 options( power off, system, bootloader and recovery). It will boot to recovery, now try flashing it again and see. Most if the time it helps.
Else, go to main page, select wipe, click on format rather than wipe here, it will prompt for typing Yes to confirm. Biit to recovery from main twrp page ( as mentioned above). And try this same thing of formatting data couple of times and then flash the zip and then dload.
I know these are tedious steps but inhave revived my device many a times with all these tricks after some efforts.
Good luck
YAY it works.
Just to recap what I did:
I flashed your thing first through TWRP tried to flash your other link with dload (which did NOT work)
Then I flashed the thing (emui5 Android 7 for Europe) through TWRP played in my old backup of exactly this through TWRP cleared dalvik & cache.
Then I waited 20 minutse and now it started.
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
algg said:
YAY it works.
Just to recap what I did:
I flashed your thing first through TWRP tried to flash your other link with dload (which did NOT work)
Then I flashed the thing (emui5 Android 7 for Europe) through TWRP played in my old backup of exactly this through TWRP cleared dalvik & cache.
Then I waited 20 minutse and now it started.
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
Click to expand...
Click to collapse
It is terrible indeed. Glad your phone working.
Thanks to @RedSkull23 for tagging, else I may have not responded as he was already involved and was helping as usual.:good:
algg said:
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
Click to expand...
Click to collapse
I'm happy for you man, indeed it would be so bad, especially because you got this device 3 or 4 days ago if i didn't read bad, anyway what matters is that now it works. Are you able to restore the previous backup through TWRP now? (But before trying... Make a backup of your actual OS )
shashank1320 said:
It is terrible indeed. Glad your phone working.
Thanks to @RedSkull23 for tagging, else I may have not responded as he was already involved and was helping as usual.:good:
Click to expand...
Click to collapse
Are you joking man? I just tagged you for more help, but practically you helped him in everything, not me; I'm sure that you would noticed the thread and helped as always even without my tag, i just speeded up things for being helpful to algg.
algg, I'd like to apologize myself; i didn't vanished after tagging shashank, today i just was at work and obviously i was busy for help, but as i saw with pleasure he already helped you to restore your OS and that was the objective. Nice one, guys!
I know, i know there's plenty of resources over the net already and I already spent 10+ hrs on this.
I bricked my phone when SuperSU prompts me to install su binary. And it got me into bootloop.
Tried https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108 but failed at 61%
Tried the backup oem file method but TWRP kept saying permission denied when trying to backup
Couldn't find a way to import dload+Update.app file into internal storage without actually booting up the phone first. I didn't knew the exact directory for internal storage so I couldn't copy it from OTG
Bootloader Unlocked, Rooted(before recovery), using TWRP.
I wanna go back to clean stock firmware
Any helps would be appreciated.
ADDED: ITS ORIGINALLY OREO
Any luck? I have the same problem here ..
Still have unlocked bootloader & know the firmware version you were on?
Right. Go to Firmware Finder. Download the FullOTA version of it.
Get one of the firmware extractor utilities. You're going to want SYSTEM, KERNEL, RAMDISK, and RECOVERY_RAMDISK (or RECOVERY_RAMDIS, depending on the extractor).
Get into fastboot mode.
Flash those 4 items to the partitions named the same.
Reboot into recovery - you're now in an EMUI recovery. Factory reset.
Reboot.
You should be back to stock with an unlocked bootloader. If you've gone poking around with root or whatnot and might have modified one of the other partitions, don't relock your device - it won't boot. Instead, hwota8 or a NoCheck stock recovery are probably the way you'd want to go. (To be honest, I haven't used either. If I want to get back to full stock knowing it's not modified, I usually do a downgrade flash to Nougat through HiSuite and then upgrade again.)
irony_delerium said:
Still have unlocked bootloader & know the firmware version you were on?
Right. Go to Firmware Finder. Download the FullOTA version of it.
Get one of the firmware extractor utilities. You're going to want SYSTEM, KERNEL, RAMDISK, and RECOVERY_RAMDISK (or RECOVERY_RAMDIS, depending on the extractor).
Get into fastboot mode.
Flash those 4 items to the partitions named the same.
Reboot into recovery - you're now in an EMUI recovery. Factory reset.
Reboot.
You should be back to stock with an unlocked bootloader. If you've gone poking around with root or whatnot and might have modified one of the other partitions, don't relock your device - it won't boot. Instead, hwota8 or a NoCheck stock recovery are probably the way you'd want to go. (To be honest, I haven't used either. If I want to get back to full stock knowing it's not modified, I usually do a downgrade flash to Nougat through HiSuite and then upgrade again.)
Click to expand...
Click to collapse
Data reset/factory reset not working !!
hussam_qashu said:
Data reset/factory reset not working !!
Click to expand...
Click to collapse
Try this one: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
And use this TWRP with it (won't work otherwise, most likely): https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3783353
(Also, that TWRP has decryption support so you can backup /data.)
Search and download your fw from http://pro-teammt.ru/firmware-database/
You'll want Update.zip, update_data_full_public.zip and the hw data zip. (Make sure it's actually for your phone, e.g. check region cust)
Rename update_data_full_public.zip to update_data_public.zip, rename hw data zip to update_all_hw.zip.
Put update zips and HuRupdater zip in the same folder on your sdcard/internal memory, flash HuRupdater with TWRP.
i have a question, im on mha l29 dual sim version with stock oreo magisk and twrp (368 update) how can i revert back to clean oreo? so i can get the updates normally. thanks !!
ante0 said:
Try this one: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
And use this TWRP with it (won't work otherwise, most likely): https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3783353
(Also, that TWRP has decryption support so you can backup /data.)
Search and download your fw from http://pro-teammt.ru/firmware-database/
You'll want Update.zip, update_data_full_public.zip and the hw data zip. (Make sure it's actually for your phone, e.g. check region cust)
Rename update_data_full_public.zip to update_data_public.zip, rename hw data zip to update_all_hw.zip.
Put update zips and HuRupdater zip in the same folder on your sdcard/internal memory, flash HuRupdater with TWRP.
Click to expand...
Click to collapse
that recovery wont work for me, only work twrp from pretoriano80 3.2.1-0, i got a mate 9 MHA-L29 dual sim...
edit:
well aparently theres 2, i dont get it, but when the recovery boot and show the logo of pretoriano, that version doesnt works, but when boot and show the classic twrp logo with pretoriano80 letters in red works...
so, if you flash recovery with fastboot and reboot recovery for the first time doesnt works, but if you reboot in recovery from twrp will show another version ...???? and works. sorry for my english
Colicablb said:
that recovery wont work for me, only work twrp from pretoriano80 3.2.1-0, i got a mate 9 MHA-L29 dual sim...
edit:
well aparently theres 2, i dont get it, but when the recovery boot and show the logo of pretoriano, that version doesnt works, but when boot and show the classic twrp logo with pretoriano80 letters in red works...
so, if you flash recovery with fastboot and reboot recovery for the first time doesnt works, but if you reboot in recovery from twrp will show another version ...???? and works. sorry for my english
Click to expand...
Click to collapse
That is weird, considering that he only made one TWRP for Mate 9