hello guys,
my stock mate 9 smartphone did an official ota update on tuesday evening (11.10.2018)
due to the reason that everything is gone well with the updates before i didnt safed my files/data.
so, it downloaded and rebooted but at the end it said verifying fail. since that its in an bootloop.
erecovery said to me i should do an factory resett, but i cant because of my data.
Therefore i bought an lifetime pass of funkyhuawei and tried the method A with the DNS method. My smartphone downloaded the funkyhuawei latest firmware and tried to install, same as before it said "fail".
So i tried the next method with fhunbrickflashtool, to force install the firmware. it sucessfully worked, it said the firmware was sucessfully installed. after that i rebooted and its still in bootloop.
I think ok, i try again the method A with the DNS method with erecovery, this method works as well, it said the firmware was sucessfully installed. so i reboot and its still in bootloop.
wipe partition cache i also tried in several times after sucessfully installs of firmwares.
what can i do now to solve the bootloop? because i think the firmware i really sucessfully installed.
i have no clue
If have twrp can use hwota
Related
So after more or less randomly trying different things, and fearing that I might only have made matters worse, I hope someone can help:
I have got a Huawei Honor 6 H60-L04 (bootloader unlocked and rooted) and was, until two days ago, running KitKat with the B114 build and cwm recovery. Since Marshmallow has officially benn available for the Honor 6 for a while now, I decided to finally update.
I flashed stock recovery and updated to Marshmallow build B820 via update.app on sdcard. Booting worked fine, however I was unrooted (ofc) so I decided to flash SuperSU (2.76 [latest stable]).
So I flashed twrp 3.0.2.0. and so far all good. Still no problems booting. Then I flashed SuperSU (according to twrp successfully) and rebooted, just to find myself stuck on bootscreen. That is not the first one you get in bootloop but the animated honor logo. Well ****.
Since then I tried many things, wiped multiple times (data is unimportant, but unfortunately I don't have a working twrp backup, please don't lecture me on this, i know -.-), flashed almost any stock ROM I could get my hands on. In twrp I get this Error:
Could not find 'META-INF/com/google/android/update-binary' in the zip file". >"Error installing zip file". "Failed"Somewhere on the way I got
error! Func NO : 9 (FUNC_BOOT_KERNEL) Error NO : 2while booting, that's gone though.
I'm at the point now where I can install B820 via update.app on sdcard, see the installation progress succeed to 100%, reboot, and again, find myself stuck on animated honor logo.
I honestly have no idea what I can do, I hope someone here does. I'll happily provide any further information you might need.
Try and wipe everything, then reflash TWRP. Good luck ?
Sent from my Samsung Galaxy S7 Red using XDA-Developers mobile app
I did that, I lost count how many times. I wiped everything, clean twrp flash, still get the "meta-inf" error message. Maybe someone can provide me with a clean twrp backup for B820? that might actually work.
Ok, after making a fool of myself, I finally found the culprit. Turns out I have to wait a couple of minutes after a new installation for my phone to boot. And all the time I thought it was soft bricked -.-
However, I does get soft bricked whenever I try to flash SuperSU. Root = bricked. Unroot = unbricked. Anyone got an idea how to get SuperSU to work? I really don't want to go back to unrooted...
I used supersu 2.62 with MM.
After install i update supersu with Google play.
Supersu update itself the binary to 2.76.
It works with B820 ans now with B860.
hagehagen said:
Ok, after making a fool of myself, I finally found the culprit. Turns out I have to wait a couple of minutes after a new installation for my phone to boot. And all the time I thought it was soft bricked -.-
However, I does get soft bricked whenever I try to flash SuperSU. Root = bricked. Unroot = unbricked. Anyone got an idea how to get SuperSU to work? I really don't want to go back to unrooted...
Click to expand...
Click to collapse
Haha, next time give the phone a couple minutes.
Sent from my Samsung Galaxy S7 Red using XDA-Developers mobile app
After doing a factory reset with TWRP (including /data), I flashed the custom ROM, as it got stucked in a bootloop, I tried to install stock firmware. I tried so using the dload method on external SD and internal storage as well. But both get to 5% and fail. I restored my backup but without /data because TWRP did not allowed me to back it up. Now it's running but without many apps. I would like to go back to stock. Any ideas?
My version is MHA-L29C636B158
For the mate 9 there actually are 2 Offline Firmwares available. a Chinese for the MHA-L00 and the other one is the international version, C636. Offline says they don't need the verification which for you fails at 5 percent. They will go through for sure using the dload method. Just ask Google for " Mate 9 offline firmware C636"
another solution for your problem is to download the specas data for your specific firmware using Firmware Finder ( Google play ) and flash it via TWRP.
Once done your phone should run regular.
You will get an error within TWRP but you may ignore it, the flash process will success, even it it shows something else.
Last step Wipe cache and dalvik cache, then reboot
WieserZ1C said:
For the mate 9 there actually are 2 Offline Firmwares available. a Chinese for the MHA-L00 and the other one is the international version, C636. Offline says they don't need the verification which for you fails at 5 percent. They will go through for sure using the dload method. Just ask Google for " Mate 9 offline firmware C636"
another solution for your problem is to download the specas data for your specific firmware using Firmware Finder ( Google play ) and flash it via TWRP.
Once done your phone should run regular.
You will get an error within TWRP but you may ignore it, the flash process will success, even it it shows something else.
Last step Wipe cache and dalvik cache, then reboot
Click to expand...
Click to collapse
Thanks! I tried downloading public/update_data_full_public.zip from Firmware Finder, i flashed it with TWRP but everything looks the same. So now I´m downloading this ffirmware https://drive.google.com/file/d/0B9GG_Oe0gQDyUWlCS3lTRm5IOUE/view , that i found on this https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656 thread, so i will try updating it with that. Should I flash hw_data for c636b136 (my actual version is c636b158),after flashing the previus step, as said on that thread?
for the international c636 you need the update_full_hw_spcseas.zip and the update_vendor.app
linorallo1 said:
Thanks! I tried downloading public/update_data_full_public.zip from Firmware Finder, i flashed it with TWRP but everything looks the same. So now I´m downloading this ffirmware https://drive.google.com/file/d/0B9GG_Oe0gQDyUWlCS3lTRm5IOUE/view , that i found on this https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656 thread, so i will try updating it with that. Should I flash hw_data for c636b136 (my actual version is c636b158),after flashing the previus step, as said on that thread?
Click to expand...
Click to collapse
Use this instead https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
It will let you update to the latest C636 build.
You'll have to unlock bootloader again after it's finished, and reflash twrp.
Though if you just want to use AurRom the one you downloaded will be enough.
And yes you will need too flash B136 hw and Public.
WieserZ1C said:
for the international c636 you need the update_full_hw_spcseas.zip and the update_vendor.app
Click to expand...
Click to collapse
Great, so i should download the update_full_hw_spcseas.zip for C636B158 from FF, and the update_vendor.app from the offlline C636 firmware. But i don´t quite understand the steps.
should i do like this?:
1- Flash offline C636, using dloader´s method .
2-Flashing TWRP
3-Flash update_full_hw_spcseas.zip from C636B158.
4-Done?
Sorry for so many questions but never had a Huawei before, and this is more complex than I expected.
Thanks all, the flashing via dloader´s method succeded, but now i have the b110 its not a problem.
you may update it through systemupdate if your system is untouched.
Any huawei apps now working?
WieserZ1C said:
you may update it through systemupdate if your system is untouched.
Any huawei apps now working?
Click to expand...
Click to collapse
I tried but, it doesn't detect any update. I think I will have to update manually, so far anything has worked
Hi,
I am having troubles with my Honor since I bought it. When I got the mobile and update the first time, 2 minutes out of the box, it got briked, bootloop.
I read a lot this forum. First I tried to put the B380. It worked but NTDKeys in compilation number, so I did the MM Rollback. Everything OK. I wait some days but I did not receive any ota. So, I installed FF and updated via Proxy, everything well until I upgraded to B389. I got another bootloop.
Well, I tried another time. I download from the Huawei UK the rollback now. I downgraded to MM. When I connected the Wi-Fi, I received the OTA to B360. Then B380, then B389 but **** the mobile again, another bootloop. I read more the forum, some people say they update the FRD from Hisuite and did not have any problem. I tried too, but another time bootloop beyond the B380.
The last thing I read about people with similar problems was that they update with the Service Full Repair B398, with dload method or flashing cust, system boot and recovery. But do you know what I get? Another bootloop.
The last thing I tried today is the last FULLOTA-PV I found on FF (b398), it was released 3 days ago. Flashed the firm and the regional update but bootloop. I don't know what to do. I want update my Honor but I don't know how. If anybody has any idea, it will be appreciate.
Thanks.
PD: The mobile phone was AL10 but the seller rebrand to European, L19C432. If I check right now the firmware from Fastboot, it is L19C432B398.
with that FullOTA-PV rom, i highly recommend you just install TWRP and flash the two zips this way. the PV versions of OTAs are flashable with TWRP, so no need for using stock recovery or redlotus.
TomTheGeek3 said:
with that FullOTA-PV rom, i highly recommend you just install TWRP and flash the two zips this way. the PV versions of OTAs are flashable with TWRP, so no need for using stock recovery or redlotus.
Click to expand...
Click to collapse
I already did this but there is no change, (with TWRP and dload, first dload and when I saw it was not workirg with TWRP). I have MM another time because it is the only way I found to have a mobile and not a brick,
RataDP said:
The last thing I tried today is the last FULLOTA-PV I found on FF (b398), it was released 3 days ago. Flashed the firm and the regional update but bootloop. I don't know what to do. I want update my Honor but I don't know how. If anybody has any idea, it will be appreciate.
Click to expand...
Click to collapse
Thanks!
try the latest FullOTA-MF and redlotus.
https://forum.xda-developers.com/honor-8/how-to/guide-flashing-unapproved-firmwares-t3668306
i've had success with this after being stuck on b360 on my FRD-L09 (i swapped from the L04 to the L09 via rebrand)
TomTheGeek3 said:
try the latest FullOTA-MF and redlotus.
https://forum.xda-developers.com/honor-8/how-to/guide-flashing-unapproved-firmwares-t3668306
i've had success with this after being stuck on b360 on my FRD-L09 (i swapped from the L04 to the L09 via rebrand)
Click to expand...
Click to collapse
I'm doing something wrong or my mobile likes to **** me...
I flashed the last FullOTA-MF with the custom recovery and redlotus but it had the same behaviour. Just after upgrade from hisuite, the mobile takes one long boot (blue honor screen for ~5 minuts) then it rebooted and started the bootloop until it enters to eRecovery.
Any more ideas? My last backup is with B380 and I'm be able to work with this but I cannot upgrade :S
Hi guys,
I am currently trying to figure out how to reinstall a clean version of the B385 for my FRD-L04. I have downloaded these two files from the Nougat Update for FRD-L04 Honor 8 (USA):
Full ROM – http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1585/g104/v83098/f1/full/update.zip
Data File – http://update.hicloud.com:8180/TDS/...FRD-L04_hw_usa/update_full_FRD-L04_hw_usa.zip
I have tried to flash them both from TWRP, but I always get the error: Updater process ended error 7
Can anyone please guide me through the process and let me know what I'm doing wrong?
I have look for a guide or post where this is detailed, but without luck. Can anyone link me to a guide on how to reinstall the stock firmware in my Honor 8 FRD-L04?
Thanks! :good:
The best way (if you don't want to unlock bootloader) is to flash a downgrade package first, then dload the Marshmallow update and finally your preferred Nougat update though Firmware Finder.
hackslash said:
The best way (if you don't want to unlock bootloader) is to flash a downgrade package first, then dload the Marshmallow update and finally your preferred Nougat update though Firmware Finder.
Click to expand...
Click to collapse
Thanks for the response. In my case, my phone is rooted, so I don't mind unlocking the bootloader. Would you please elaborate on how to do it that way?
Sent from my FRD-L04 using Tapatalk
juanboja said:
Thanks for the response. In my case, my phone is rooted, so I don't mind unlocking the bootloader. Would you please elaborate on how to do it that way?
Click to expand...
Click to collapse
Unlock your bootloader and follow this guide:https://forum.xda-developers.com/honor-8/how-to/guide-flashing-unapproved-firmwares-t3668306/
Choose the B385 firmware or any newer firmware available for your region.
So I decided to finally reinstall the stock firmware in my Honor 8 FRD-L04 in B389, and this is where the nightmare began.
- I made a full backup with TWRP just in case and I decided I wanted to start from the earliest firmware possible available.
- I started unrooting my phone using the UnSU zip by Osmosis.
- Then I flash via bootloader the recovery and boot image of the firmware B360.
- I flashed the rollback package from the Huawei official site with the B122 firmware also available at the same place. I saved the rollback package in my root directory in the dload folder, and loaded it with the 3-button method. After this I wasn't able to boot my phone normally, I was stuck in a boot loop. I still continue with the next firmware, the B122, and it was successfully loaded (this also relocked my bootloader).
- It is important to say I clear many times the cache and wipe/erase data through stock recovery options, and also tried to erecover but I wans't able to connect to the WiFi. I guess something was missing (at this point I was already going crazy).
- I was still stucked at a boot loop after loading the B122, so I decided to unlock my bootloader and flash the twrp 3.1.1-1-frd.img
- From there I tried to wipe data and cache and system and everything, but I wasn't able because an error saying unable to mount always appeared.
- After rebooting, since I already had unlocked the bootloader, the initial message prompting: "press power to continue, press for 3 seconds for erecovery, etc..." appeared.
- I enter the erecovery options with the hope it will do something... and it did!!! I could connect this time through WiFi and the system asked to update the firmware and many other things it said at that moment. This was the first time I felt relieved through the night.
- The phone updated perfectly, it started at the firmware B122 and I kept updating it until I reached the B389.
- I unlocked the bootloader again and rooted the phone. And everything is running smooth as silk!
I know this is a very long story, but I just want to get it out there in case anyone is facing the same problem I just passed. Hope this helps someone and brings peace to them! =) Good luck!
I believe B385 is not functional with TWRP. Flash B360 and reboot to recovery. This should go to stock recovery, where you will have to do a factory reset. I got EMUI working, but it refuses to update to any newer version (it does show B380 but doesn't update). Also there should be updates after making that update. The updates did work for other people, so you may be able to have it working.
juanboja said:
Hi guys,
I am currently trying to figure out how to reinstall a clean version of the B385 for my FRD-L04. I have downloaded these two files from the Nougat Update for FRD-L04 Honor 8 (USA):
Full ROM – http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1585/g104/v83098/f1/full/update.zip
Data File – http://update.hicloud.com:8180/TDS/...FRD-L04_hw_usa/update_full_FRD-L04_hw_usa.zip
I have tried to flash them both from TWRP, but I always get the error: Updater process ended error 7
Can anyone please guide me through the process and let me know what I'm doing wrong?
I have look for a guide or post where this is detailed, but without luck. Can anyone link me to a guide on how to reinstall the stock firmware in my Honor 8 FRD-L04?
Thanks! :good:
Click to expand...
Click to collapse
Try flash B360 then OTA to 388 or 391 (If 391 singed).
blackbuffalo said:
Try flash B360 then OTA to 388 or 391 (If 391 singed).
Click to expand...
Click to collapse
Thanks for the replies, any link to where I can find the B360?
Sent from my FRD-L04 using Tapatalk
juanboja said:
Thanks for the replies, any link to where I can find the B360?
Sent from my FRD-L04 using Tapatalk
Click to expand...
Click to collapse
http://pro-teammt.ru/firmware-database/?firmware_model=FRD-L04&firmware_page=0
blackbuffalo said:
http://pro-teammt.ru/firmware-database/?firmware_model=FRD-L04&firmware_page=0
Click to expand...
Click to collapse
Thank you very much for this info!
Sent from my FRD-L04 using Tapatalk
Hello guys,
long story short, I had the notification that a new update was released for my honor 8 FRD-L09C432 (B403, I was on B402), so, since I was rooted and with TWRP installed, I decided to unroot and install the original eRecovery.
Something went wrong and the system was damaged, so I flashed the B360 version first and after the B394. Now the phone is working really good but I can't install the new versions (B402 or 403). I tried:
flash the update from TWRP, not working
search the update from the dedicated option in the settings, no update found
tried to have it from the original eRecovery, error to find the info from the server.
tried also to update from the version B394 before unlock the bootloader, but it failed.
Am I missing something?
Use the get update through DNS thing in FF. It worked for me at least. Make sure the firmware is approved.
Days Tech said:
Use the get update through DNS thing in FF. It worked for me at least. Make sure the firmware is approved.
Click to expand...
Click to collapse
Hi Days Tech, could you please explain better what do you mean? Is there a link of some tut that I can follow?
Thanks!
Ok now I have the point, thanks for this tip!:good:
Flash TWRP.
use data.zip file and flash it via TWRP. (only download from FullOTA-MF PV file)
reboot and you are done. you will have updater in settings.
now you can flash the update.zip file via dload.
dlaod guide in my signature.