Hi guys,
Today i come to ask your help because i update my honor 8 (FRD-L19) to stock rom B389, but i have a problem, when i flash TWRP (by using fastboot flash recovery twrp.img) it tell me everything is ok, so i just reboot phone (fastboot reboot) and after that reboot to recovery (adb reboot recovery), but i'm stuck at the page who tell me my phone can't be trust but don't do anything more, i waited about 15 minutes but it don't do anything more.
I tried with 4 differents version of TWRP :
(twrp-3.2.1-0-frd.img
twrp-3.2.0-0-frd.img
twrp-3.1.1-0-frd.img
twrp-3.1.0-0-frd.img)
After that i tried to reset my developper option and activate usb debugging and OEM,
but now i can't have any action on the OEM "switch".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello,
i tried to factory reset this honor 8 but i'm still blocked on the "your device is booting now..." page.
Anyone know how i can get OEM enabled again please ?
Thanks.
Try flashing the very last TWRP, by OpenKirin team. I thing this is 3.1-1
Hi, i installed B131 and i get again access to my phone, and installed 3.1.1.1 TWRP it's Awesome, it's working ! But now, when i install Magisk, it let my phone into bootloop, their is any Honor 8 EMUI 5.0 android 7.0 version ?
Thanks for your answer you helped me
skyflo355 said:
Hi, i installed B131 and i get again access to my phone, and installed 3.1.1.1 TWRP it's Awesome, it's working ! But now, when i install Magisk, it let my phone into bootloop, their is any Honor 8 EMUI 5.0 android 7.0 version ?
Thanks for your answer you helped me
Click to expand...
Click to collapse
Which version of magisk you are trying??
skyflo355 said:
Hi, i installed B131 and i get again access to my phone, and installed 3.1.1.1 TWRP it's Awesome, it's working ! But now, when i install Magisk, it let my phone into bootloop, their is any Honor 8 EMUI 5.0 android 7.0 version ?
Thanks for your answer you helped me
Click to expand...
Click to collapse
Try this https://forum.xda-developers.com/attachment.php?attachmentid=4340290&d=1511453617 if it's the same you tried before, go for v14.0, the latest stable build of Magisk
Related
Hi there
I tried flashing the "[ROM] [NXT-L29] B320 International Rooted **UPDATE 6/14/16** " on my NXT-AL10 after that, it won't get further as to the screen where it says "Your device is booting now" (Picture attached).
Installed is TWRP 2.8.7.0. I'm able to enter TWRP and Fastboot.
I also tried flashing different ROMs but I'm still stuck at this screens.
I also tried the Italian Knife tool Unbrick option.
Do you guys have any tipps?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
which firmware did u have installed before? 2.8.7.0 is not compatible with B3xx roms, u need to flash 3.0.2 for EMUI 4.1 firmwares. there is also a 3.0.2 version for EMUI 4.0 (B1xx roms), so watch out not to use the wrong one.
best thing to do now is flash a B1xx rom via fastboot and then upgrade from there...
Sent from my Huawei Mate 8 NXT-AL10
jbmc83 said:
which firmware did u have installed before? 2.8.7.0 is not compatible with B3xx roms, u need to flash 3.0.2 for EMUI 4.1 firmwares. there is also a 3.0.2 version for EMUI 4.0 (B1xx roms), so watch out not to use the wrong one.
best thing to do now is flash a B1xx rom via fastboot and then upgrade from there...
Sent from my Huawei Mate 8 NXT-AL10
Click to expand...
Click to collapse
Thank you, you were totaly right.
i just got it up and working with the guid from Germaniac:
http://forum.xda-developers.com/mate-8/general/unbrick-updating-to-b321-t3375934
good, a bricked device is never fun....
post removed by creator
Hi, I need help;
I have a GR3 2017 "PRA-LX1" latest twrp installed. I tried to install many ROMS, none worked except haky's lineage:
https://forum.xda-developers.com/p8lite/development/rom-lineageos-14-1-huawei-p8-lite-2017-t3649292
But it had many problems in the early stages so I tried his other rom, SLIM:
https://forum.xda-developers.com/p8lite/development/rom-slimroms-ng-7-1-huawei-p8-lite-2017-t3714239
It also had problems like fingerprint and cam not working "phone acted like it had no fingerprint sensor". Now problem is, since installing this ROM, every other ROM I install gives error 7 on twrp which I bypassed by editing the script file. However none of them boots, all PRA-LX1 ROMS that I have installed gets stuck at "your phone is booting now" like the OP's screen. Yet the above SLIM ROM gets installed with no error and boots just fine.
I have no one to turn to, even the ROM maker is not responding, please any help would be appreciated
hi friends I have exact this problem
my first rom was c900b180 android 6 nnd twrp 2.8 and unlocked bootloader
because dint get android 7 I try to flash it manually
1- I try to install from twrp not success
2-try dload not success
3-try fastboot use this commands
astboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
============================NOW
PHONE stay on above screen booting now.......
and twrp not installed and try to install more version
oorginal recovery not installe install in fastboot say success bot really not install
please help friends
I wanted to try the android n beta out. so i unlocked my bootloader, installed twrp and flashed this beta through twrp.
but there i made the mistake not to decrypt my storage. but it worked. i used this beta for around a week and then a new version came out. i just wanted to boot to twrp and flash it, but i couldnt.
so i thought i just roll back to emui 4.1 which i used before, install twrp again, deecrypt the storage and everything works well.
but something didnt work as i wanted. so now i cant boot into twrp or in any rom, just into erecovery, fastboot and into the warning screen where it wants, after some minutes to install a update, which i cant dload, bcs i cant enter my sdcard..
bootloader is unlocked, frp too
K4Y3R said:
I wanted to try the android n beta out. so i unlocked my bootloader, installed twrp and flashed this beta through twrp.
but there i made the mistake not to decrypt my storage. but it worked. i used this beta for around a week and then a new version came out. i just wanted to boot to twrp and flash it, but i couldnt.
so i thought i just roll back to emui 4.1 which i used before, install twrp again, deecrypt the storage and everything works well.
but something didnt work as i wanted. so now i cant boot into twrp or in any rom, just into erecovery, fastboot and into the warning screen where it wants, after some minutes to install a update, which i cant dload, bcs i cant enter my sdcard..
bootloader is unlocked, frp too
Click to expand...
Click to collapse
What about your phone model?
NXT-L09, NXT-L29, NXT-AL10, NXT-CL00, NXT-DL00 or NXT-TL00
Mentioned on back of your phone like this image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Its already fixed ^^ ,but thanks for the response
Hi guys.
Trying to install TWRP 3.1 for Nougat.
Everything goes fine (flashing, etc..) till the moment I "fastboot reboot".
Instead of prompting TWRP, I enter the "Huawei eRecovery"...
Is the stock rom replacing recovery at boot?
Does anyone know how to fix it?
I need it of course to install SuperSU and get rooted.
Thanks.
Just shut down device, and then press power+volume up button until a message is shown. Then you're in TWRP. You don't need fastboot for that.
Engineer91 said:
Just shut down device, and then press power+volume up button until a message is shown. Then you're in TWRP. You don't need fastboot for that.
Click to expand...
Click to collapse
Thank you for replying, but you do get my point.
after flashing TWRP 3.1, I enter recovery as you wrote.
The problem is that I see this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Not TWRP.
I don't understand why the recovery changes to stock one.
I wrote "fastboot mode" because it is part of the procedure to install recovery through ADB.
And everything seems to be fine UNTIL I write the last command to enter recovery (of course I need an ADB command to exit and reboot in recovery).
Probably TWRP isn't being installed properly. What command did you use?
(already installed on my pc drivers and ADB tools)
from the beginning:
adb reboot bootloader
fastboot flash recovery twrp.img
(Once TWRP is successfully flashed) fastboot reboot
Then volume+ and power button
Well, that worked for me always. I don't know what is happening. Maybe a dev could help you.
I hope someone of them is reading this thread...
Engineer91 said:
Well, that worked for me always. I don't know what is happening. Maybe a dev could help you.
Click to expand...
Click to collapse
Are you on Nougat and EMUI 5?
Which TWRP image recovery did u install? Berlin 3.1?
Yes, EMUI 5, TWRP berlin 3.1. It worked with versions B342 and B360. I succesfully used Revolution recovery from P9 lite too, before TWRP 3.1 was released for our device.
Engineer91 said:
Yes, EMUI 5, TWRP berlin 3.1. It worked with versions B342 and B360. I succesfully used Revolution recovery from P9 lite too, before TWRP 3.1 was released for our device.
Click to expand...
Click to collapse
Boh... I don't know then...
I succeded in rooting when I was on android 6 and emui 4.1. After updating to nougat (b360), no way.
You need TWRP 3.1.0-2 and unplug the usb cable...
TWRP_3.1.0-2\EMUI5
YOU ARE THE MAN, bro!
Succeded with new TWRP.
Thanks thanks thanks
power off completely. Hold down : Power + Volume Up. You will see the magic.
Been stuck for two days!! Thanks for the advice on changing to TWRP 3.1.0-2 and unplug the usb cable...That worked.
Hi!
I've got a problem with my Mate. I wanted to update my smartphone to Nougat (My Mate is C636 B170) and I updated to B180 using Firmware Finder from Google Play without any problems. Then, I choosed B193 (I think) and something went wrong. Now i can only enter recovery, eRecovery or fastboot. My phone isn't rooted and bootloader is locked. I've tried to use rayglobe knife and SRKTool. Nothing helped. I can't flash via dload, update just doesn't start. In DC Unlocker I see, that my firmware is C900B172 (!) I don't know what to do know? Any ideas? (sorry for my English)
Unlock your bootloader and then unpack with Huawei Firmware Extractor from UPDATE.APP of B172 the following files: boot.img, recovery.img, recovery2.img, system.img, userdata.img and fastboot every single one into your device with the commands «fastboot flash boot boot.img, fastboot flash recovery recovery.img» and so on. It should be back on track.
How can I do that? I can't run my phone, so I'm not able to get Product ID and my Huawei ID that I made to get this code has only a few days. When I connect my phone in fastboot mode to PC and run DC Unlocker, there is only FRP erase and Network unlock whick is inactive.
EDIT: BTW, any B172 link? I can't find any active. My Mate is L29 of course.
Ok, I think I'm one step closer. Earlier I didn't see that there is a Mate 8 in "Select model" in DC Unlocker. Now, the problem is that when I click "Read bootloader code" response is:
Reading bootloader code...
unknown error (359)
What can I do with that?
Hello!
I'm still trying to fix my Mate. I know that flashing B320 via DC Phoenix but B320 is impossible to find :/ Can I flash any other firmware?
Now, when I reboot my device this is how it looks like :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can enter into fastboot mode, so I believe that there is still a chance for my phone
Any ideas?
up
Can I flash any other firmware like C636B170 or any which is posiible to download? Please help, because I don't know if I can use my bricked Mate as a hammer or still trying to bring him back to life.
up
Anyone? Anything?
I don't know why. I used erecovery with FirmwareFinder many time and it work all times.
But 1 day before, I unlocked bootloader, flash patched ramdisk.img (Magisk), and then reboot again. But then it meet bootloop, bootloader relocked, FRP lock. But this time, when I use Firmware Finder to recover, it cannot work, erecovery failed when getting package. I checked all step.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My mate 9 is briked in i install the last firmware oreo b369... Firmware finder
Please help me! 41$ for 5 credits FunkeyHuawei is too much for me. Could I buy 1 credit to flash firmware?
Are you still having issues, if so, have you been able to unlock your bootloader and flash a custom recovery? If you have I think I may be able to help you
@shae23: Thanks. If I have been able to unlock bootloader, I don't need to creat this thread. I had to bring it to a service shop (Viet Nam), it cost about 6.5$ US to reflash firmware.
someone know what to do ?!!
I unlocked the bootloader and flashed the recovery, the system booted successfully.
I tried to flash a ROM after that, it showed errors and didn't complete the flashing. since that time the phone has bootloop.
Unlocked bootloader and FRP
fastboot oem get-build-number : MHA-L29 8.0.0.374(C185)
I can access the TWRP recovery and erecovery and bootloader&fastboot
what I have already tried :
1-Fastboot flash ramdisk and kernel .
2-Tried to flash the stock firmware via TWRP.
3-Tried HurUpdater0.3
4- Extract update.app & HOWTA
5-Flash ramdisk and kernel from inside TWRP
Update: I can not access the recovery anymore. its just stuck at stock recovery with EMUI 0%
Tried to flash stock and custom recovery, but no luck
Update 2: I somehow managed to get into recovery. recovery is good now.
BUT still no luck with booting, I feel it's something stupid that I missed
Did you try this way?
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
didn't work