Hi,
I have a really annoying problem.
I updated my honor 8 to B399, and I can't activate bluetooth, the switch move, but stay gray.
I tried multiple factory reset, dload update... I also used the unbrick section of "huawey multitool".
I'm not really sure if I had performed a real complete system reset, this way.
But I still can't activate bluetooth...
Is someone having the same problem?
A way to fix it...
Thanks a lot.
Ok, I finally managed to downgrade to android 6 emui 4, B131, and the bluetooth is working again!!!
I followed this guide :
https://forum.xda-developers.com/honor-8/how-to/problem-frd-l09-t3596449
Now I will try to apply the OTA B394, automaticly proposed by the system, and maybe after that, the B399...
I'll update the thread...
B394 seems to work well, bluetooth still working...
Bluetooth is already active on startup...before that when I was on B394, I had to reactivate it after restart... Not really important, but I prefer.
Now I Have a OTA B398 available.... Maybe a B399 will be available after this one...
B398 OK, bluetooth ok, no more OTA B399 available...
Next step , unlock Bootloader, TWRP, Root, Magisk etc...
Hope everything will work well.
@Rommco05 Thanks for help
I have issues with Bluetooth also on 399 it works but doesn't auto connect once disconnect, think I'll downgrade and do the official update.
Sent from my FRD-L09 using Tapatalk
I unlocked my Bootloader, flashed TWRP, Root, Magisk...
Everything seems to work well, I'm restoring my apps, sms, calls etc with hisuite. I think I will stay with the B398...
Well I've reset mine done 3 updates this morning but no sign of 398 for mine, stopped on 394.
Sent from my FRD-L09 using Tapatalk
Related
Hi,
I did something stupid - I wanted to update my phone by creating a dload folder on internal memory and updating to EMUI 4.0 beta that's floating around on the internet (I got it from carbontesla). I knew it required a B326 version, I had B324 and still went through with it, because I mistakenly thought that B326 is only required for L10 (I have L09). Now the phone is stuck in bootloop.
I have tried the following:
1. Forced update - it was apparently successful, but still the phone kept resetting
2. I reset to factory settings and wiped cache - still keeps resetting
3. I tried to force update again, this time I get an 'update failed' info and asks me to reboot. Still the same.
4. Tried to reset to factory settings and wipe cache again - still no luck.
I can't even turn the phone off, so for now I keep it in recovery mode.
Any idea what can I do? Am I screwed for good?
I searched around on XDA and other forums but couldn't find anything - if anyone can help me, I will be very grateful. I just bought this phone 3 months ago and I can't afford a new one at the moment.
Khasim83 said:
Hi,
I did something stupid - I wanted to update my phone by creating a dload folder on internal memory and updating to EMUI 4.0 beta that's floating around on the internet (I got it from carbontesla). I knew it required a B326 version, I had B324 and still went through with it, because I mistakenly thought that B326 is only required for L10 (I have L09). Now the phone is stuck in bootloop.
I have tried the following:
1. Forced update - it was apparently successful, but still the phone kept resetting
2. I reset to factory settings and wiped cache - still keeps resetting
3. I tried to force update again, this time I get an 'update failed' info and asks me to reboot. Still the same.
4. Tried to reset to factory settings and wipe cache again - still no luck.
I can't even turn the phone off, so for now I keep it in recovery mode.
Any idea what can I do? Am I screwed for good?
I searched around on XDA and other forums but couldn't find anything - if anyone can help me, I will be very grateful. I just bought this phone 3 months ago and I can't afford a new one at the moment.
Click to expand...
Click to collapse
Experienced all. Tsk. Should have stayed away from the Marshmallow upgrade thread.
Khasim83 said:
Hi,
I did something stupid - I wanted to update my phone by creating a dload folder on internal memory and updating to EMUI 4.0 beta that's floating around on the internet (I got it from carbontesla). I knew it required a B326 version, I had B324 and still went through with it, because I mistakenly thought that B326 is only required for L10 (I have L09). Now the phone is stuck in bootloop.
I have tried the following:
1. Forced update - it was apparently successful, but still the phone kept resetting
2. I reset to factory settings and wiped cache - still keeps resetting
3. I tried to force update again, this time I get an 'update failed' info and asks me to reboot. Still the same.
4. Tried to reset to factory settings and wipe cache again - still no luck.
I can't even turn the phone off, so for now I keep it in recovery mode.
Any idea what can I do? Am I screwed for good?
I searched around on XDA and other forums but couldn't find anything - if anyone can help me, I will be very grateful. I just bought this phone 3 months ago and I can't afford a new one at the moment.
Click to expand...
Click to collapse
Uh-oh... Another Mate 7 phone bricked by the Marshmallow beta B511 update...
I guess you'll just have to wait for the full official marshmallow update (no longer beta) for your TL09 phone for your region, or at least, wait for the official TL09 marshmallow to lollipop downgrade package for your region. When Huawei releases one or both, then you can install one or both via forced update (power + volume up + volume down) and have a functioning phone again.
For now, there's nothing you can do but wait and wait... unless you know your way around rooting, unlocking bootloaders and custom ROMs. There are actually quite a lot of Mate 7 owners in the similar situation as you. If only you can BAND together with a common cause/objective, your 'bricked by Marshmallow B511' group could somehow be a FORCE to reckon with that Huawei cannot ignore. Your group can petition Huawei with emails to release at least the 'marshmallow to lollipop downgrade package' for other non-China regions NOW, or the EARLIEST humanly possible...
You may want to read other users similar experiences with their bricked mate 7 phone (by installing the beta marshmallow b511 update) here: http://forum.xda-developers.com/mat...-marshmallow-b511-t3304178/page2#post65176950
It will make you feel much better knowing you are not alone. Alternately, you can just vent out your frustrations to Huawei in another thread. Not sure if its allowed in XDA though.
Those with bricked mate 7 phones:
Can you try and see if this suggestion works?
=========== (quoted from http://www.carbontesla.com/2016/01/download-ascend-mate-7-b511-marshmallow-ota-zip/) by wissam marrash
wissam marrash • a day ago
Guys I have mt7-l09 and its working with marshmallow, yes it drains more battery and some lagging in some areas but this should happen because its a beta and incremental release. For people who got spoil their phone while installing, you should read the requirements very well before downloading this rom. Its clearly mentioned for B326 and for un-rooted phones. so before you install you should install the B326 (you can download using this link: http://m.huawei.com/pkmobile/c... make sure to choose mt7-l09 or mt7-l10 and after installing the B326 install marshmallow beta.
For people who wants to downgrade, yes you can but you have to choose a full release like the B326-B327-B328.
N.B. ONLY Marshmallow BETA rom, Don't unzip the after downloading, its not like the other updates. You should copy the zipped file as is to inside "dload" folder.
Just a tip, some releases are not supporting 4G lte especially when it marked Europe.
For people who keep rebooting, try to connect you phone to pc or take out the memory card and use card reader and access your files and then delete the files from the "dload" folder and then download using your pc any full release rom (b326 or b327 or b328) and extract it and then copy the "UPDATE" file to the dload folder and then turn off the phone and then boot your phone while holding Vol up + Vol down + Power buttons at same time to automatically trigger the update installation and should go smooth.
Hope my comments will help
==============
Here are the links to full ROMs:
TL10: B326 full ROM:
http://consumer.huawei.com/pk/support/downloads/detail/index.htm?id=62450&key4=MATE7
L09: B326 full ROM:
http://consumer.huawei.com/pk/support/downloads/detail/index.htm?id=62371&key4=MATE7
reboot
Hi Don
We tried to follow Wassim's nstructions unfortunately it didn't work. As you said there are so many mate 7 users' faced this problem.
Any way thanks a lot for your attention.
maksudbek said:
Hi Don
We tried to follow Wassim's nstructions unfortunately it didn't work. As you said there are so many mate 7 users' faced this problem.
Any way thanks a lot for your attention.
Click to expand...
Click to collapse
i had that problem when tray to update it to MM tray it all the way no LUUUUUUUUCK
last i went to the Huawei Services the joke is they also can noooooooooooot do anything ??
last they decide it to change the main board of the phone then .. phone start with KK after that no problem
but i will never ever buy this brand again !!!!!!
Hi guys,
for some reason after I did update to KangVIP I can't get rid off it. Besides I got no wifi and bt and I was going to start over with b023 as suggested but at this point I wont bother anymore.
I did wipe the system, I did advanced wipe using twrp but no matter what I do none of the stock firmwares are going through however the Kanga one always goes through.(KangaVIP goes through only in TWRP)
twrp 2.8.7.0
wipe
advanced wipe
I select all the partitions
mkdosfs process ended with error=1
unable to wipe /usb
unknown mtp message type: 1
unable to wipe /usb
I go back, restart to fastboot, (device is saying there is no OS installed), I restore the recovery, create dload folder on my sdcard, put there 028 (actually I tried all of them already), volume+ volume - power and I get error.
What am I missing ?
Anyone can help ?
Thanks in advance.
Eric
First you did a OTA from B029 to B209?
If so you are now on a Android 6 ROM you cant go back to Android 5 without a Rollback from Huawei.
Hirs_E_Fruit said:
First you did a OTA from B029 to B209?
If so you are now on a Android 6 ROM you cant go back to Android 5 without a Rollback from Huawei.
Click to expand...
Click to collapse
Yes I did then I wiped everything and started with b028 again.
Same thing, wifi didn't work same with BT.
Wipe again and this time I did local update and since the local update I can't go back not even b029.
77Eric77 said:
Yes I did then I wiped everything and started with b028 again.
Same thing, wifi didn't work same with BT.
Wipe again and this time I did local update and since the local update I can't go back not even b029.
Click to expand...
Click to collapse
Right now you are on a Android 5 or Android 6 ROM?
If you on a Android 5 ROM you can force update a Complete ROM to install a clean system and try if everything works.
Hirs_E_Fruit said:
Right now you are on a Android 5 or Android 6 ROM?
If you on a Android 5 ROM you can force update a Complete ROM to install a clean system and try if everything works.
Click to expand...
Click to collapse
I'm stuck on 6.0
I know I can do force update on 5.0 I said it above I just can't do it with 6.0 -> b029, only with your rom.
Anyone else is having this issue ?
The Kanga rom got a quite few problems no wifi and not BT, Google play services crashing (this can be fixed with gapps) my co worker just tried it with his own methods and same issue. After I went through the whole Kanga thread 60% of the posters got problems most of them are ignored.
I don't have any problems but I think the people with problems are people who have a DAV 701L.
Hirs_E_Fruit said:
Right now you are on a Android 5 or Android 6 ROM?
If you on a Android 5 ROM you can force update a Complete ROM to install a clean system and try if everything works.
Click to expand...
Click to collapse
Hirs_E_Fruit said:
I don't have any problems but I think the people with problems are people who have a DAV 701L.
Click to expand...
Click to collapse
I got DAV-703L, just simple question, why is the wifi and bt not working ?
When I get into Kanga I can remove the root or deny access to it is there a way to ditch it ?
Yeah I know it's working for you and it's not working for 10 other people including 703L owners. There is something wrong with the rom no doubt about it.
77Eric77 said:
I got DAV-703L, just simple question, why is the wifi and bt not working ?
When I get into Kanga I can remove the root or deny access to it is there a way to ditch it ?
Yeah I know it's working for you and it's not working for 10 other people including 703L owners. There is something wrong with the rom no doubt about it.
Click to expand...
Click to collapse
I think there was an error while flashing and without a full clean Rom flash i can't see a solution.
Before I got it to work I flashed it more than 3 times and everytime everything worked so I think don't think the ROM is that bugged.
Hirs_E_Fruit said:
I think there was an error while flashing and without a full clean Rom flash i can't see a solution.
Before I got it to work I flashed it more than 3 times and everytime everything worked so I think don't think the ROM is that bugged.
Click to expand...
Click to collapse
The first rom you introduced is working "fine" I get the wifi and bt no problem but once I switch into the latest build it's gone.
Any idea where can I get full clean Rom ?
This one is a no go http://www.needrom.com/download/p8max-dav-703l/
I managed to rollback to 5.1.1 but when I try to force flash it, it says it's not compatible.
If you don't update properly to B209, when you flash any B209 rom you are going to run into issues such as the wireless Bluetooth and sim card switching for some. If you properly updated the dload method should have completed successfully. Look at the kernel and radio version of B209 in About phone and compare it to others and see if they match.
ajsmsg78 said:
If you don't update properly to B209, when you flash any B209 rom you are going to run into issues such as the wireless Bluetooth and sim card switching for some. If you properly updated the dload method should have completed successfully. Look at the kernel and radio version of B209 in About phone and compare it to others and see if they match.
Click to expand...
Click to collapse
I don't want to use your rom even if you removed the Chinese it's still inside the system. Boot load times take much longer. Unexpected crashes. I did try it on 4 phones with OTA and local updates 2 are working but the Kang does crash twice a day minimum.
All what I'm asking is how to restore it to it's original settings, this was my worst mistake ever.
What I'm trying to say if I do something I do it properly just look at your thread 85% failure ratio that doesn't look like it was done properly does it ?
77Eric77 said:
I don't want to use your rom even if you removed the Chinese it's still inside the system. Boot load times take much longer. Unexpected crashes. I did try it on 4 phones with OTA and local updates 2 are working but the Kang does crash twice a day minimum.
All what I'm asking is how to restore it to it's original settings, this was my worst mistake ever.
What I'm trying to say if I do something I do it properly just look at your thread 85% failure ratio that doesn't look like it was done properly does it ?
Click to expand...
Click to collapse
Really dude?? No worries, it will be the last time I do anything for the P8Max. Maybe you should just sell the phone since you're having all sorts of issues with it....or maybe you should have left it totally stock then. Or maybe read through the Mediapad X2 forums because the two phones are very similar.
Huawei Honor 8 FRD-L09 problem with wifi and bluetooth, i was using it and then suddenly wifi went down,and now it's impossible to switch it on (wifi) same s**t goes with bluetooth.. i wasn't able to fix it by doing factory reset, someone please help me :') Any help is greatly appreciated.. Thanks
here
watch?v=dGCTZx44OVM
flash the same firmware via dload (force update)
VenuGopalu said:
flash the same firmware via dload (force update)
Click to expand...
Click to collapse
How can I force update it? I am having exactly the same mentioned issue
Same issue for me. I'm on FRD-L14C567B360 all stock. Listened to music via bluetooth all morning yesterday then got to work and noticed my wifi was cutting in and out. now wifi and bluetooth just keep flipping on and off randomly. Tried full reset and no luck. I can't find the full firmware for this version, do i need to go back to B162 then do an OTA to get back to B360?
I picked up two Honor 6X BLN-24 models, the serial numbers are within a couple hundred of each other, so I'm assuming they're from the same batch. Right now they're both on Nougat, but one looks like it has a partial install of Nougat and the other has a "normal" install. Here's what happened:
1) The partial install phone - I unboxed it, connected it to WiFi, did a check for updates; it found the Nougat update, so I let the system update itself, rebooted, had Nougat B360. Flashed TWRP, which is working fine on the phone.
2) The "normal" install phone - instead of updating straight to Nougat, I installed TWRP first and had a bunch of issues with the wrong TWRP .img file; that's a separate issue. Got Nougat installed eventually on the phone but ended up with the "Test Keys" build issue. Ended up doing the rollback to MM, then did the check for updates, it found the Nougat update and I let it install. Phone has Nougat, build shows as B360.
Thought everything was fine and didn't really take a good look at the phones since I had to do other stuff to do before migrating to the Honors.. Now I'm ready and I'm noticing that one phone - the one that went to Nougat straight out of the box - doesn't have a bunch of apps that the second phone has, like the FM radio, CNN, Lyft, News Republic. Outside of the FM radio, I don't care about the other apps, but something else is missing - the System Update option in Settings. There may be other stuff missing, but the System Update thing is problematic.
So I figure my options are:
1) Rollback the phone that's missing things to MM, then retry the update, or
2) Try a dirty flash of the Nougat B360 update and data files.
3) Flash the smaller update_data file for the B360 build that contains most of the apps (but doesn't look like it has the FM radio)
Or is there another option?
Go with option 2. If no success then I would suggest for option 1.
Need couple of favours as you did rollback. Do you have the rollback package file? If yes, please share.
If you are rooted, use Huawei mutli tool and backup the oeminfo file. I need both these files so that if anyone messed up with their phone we will be able to revive and also address the nrd test keys issue and the best we can do is to debrand from other variant to US variant.
Thanks beforehand.
I had similar issues my phone was showing as nrd test keys and the backup of twrp also indentify phone as nrd test keys. When I checked updated update it was showing no update. My phone wassoft bricks so i download and updated package for build no b 340 and in build no it was showing nrd test key
Later i flashed zip shared in volte fix thread on xda as I was not having volte.
After flashing all thing went good test key issues resolved also so u can try that zip also.
Thanks for the replies, I'm away from the phones for a few days but will report back.
For shashank1320, the intermediate rollback package (the one that's flashed first from Nougat before the actual MM ROM) is still available on the US Honor site at http://www.hihonor.com/us/support/details/?DOC_ID=94205
You can use it if it matches with your last build no
WetWilly said:
Thanks for the replies, I'm away from the phones for a few days but will report back.
For shashank1320, the intermediate rollback package (the one that's flashed first from Nougat before the actual MM ROM) is still available on the US Honor site at http://www.hihonor.com/us/support/details/?DOC_ID=94205
Click to expand...
Click to collapse
Thanks downloading now. Yes then you can use this file for rollback.
Here's the latest update. - I tried the dirty flash method and it wouldn't work. AT ALL. I'm getting the "software failed update" at 5% message that several others have received. I downloaded the BLN-24C567B360 FullOTA package from three different sources; all had the same hash and *none* of them would work using the dload method. I ended up flashing the MM rollback package (which worked perfectly via the dload method) then flashed the MM firmware (also worked perfectly using the dload method). The phone booted into MM, it found the 2.35GB Nougat update (which is the same size of the Nougat .zips I downloaded), and it installed the update. It also installed the FM Radio (a system app) and the US package of apps that for some reason it didn't install when it upgraded to Nougat fresh out of the box.
I actually did this rollback/roll-forward twice since something odd happened while playing with SafetyNet with Magisk and the FRP Lock tripped. The next thing I know I'm getting the "data partition is corrupted" message and, again the B360 update.app files wouldn't flash. Thankfully the rollback worked. FYI, rolling back to MM relocks the bootloader. At this point I'm just keeping both the rollback and MM packages saved together on an SD card; flash rollback, pop card, rename folders on PC, pop card back in 6X, flash MM, reboot, find update, OTA to Nougat. Easier done than said, actually.
I am curious about why none of the B360 Nougat update.app files will flash on either phone. I don't think it's coincidental because the e-Recovery via WiFi doesn't find a package, and if I try System Recovery in HiSuite it says "no recovery available; take device to a Service Center".
WetWilly said:
I actually did this rollback/roll-forward twice since something odd happened while playing with SafetyNet with Magisk and the FRP Lock tripped. The next thing I know I'm getting the "data partition is corrupted" message and, again the B360 update.app files wouldn't flash.
Click to expand...
Click to collapse
If you get this issue again, try to format data inside TWRP.
itisiryan said:
If you get this issue again, try to format data inside TWRP.
Click to expand...
Click to collapse
I actually tried that. I ran into this same issue previously when I had TWRP installed, and TWRP's wipe data didn't work. Ultimately had to do the rollback to MM/roll-forward to Nougat and re-unlock the bootloader.
I can't figure out why my two phones won't flash Nougat using the dload method. The only logical reason is the upload.app file signatures, but I haven't found any alternative Nougat files for BLN-24C567B660.
I updated my honor 6x/gr5 2017 ; bill l22. Two days ago. After I received b384 update. It said it supports Voice over LTE and also updated EMUI to 5.0.1. Yesterday the phone worked fine. But today since morning my power button doesn't work. And it often gets restarted automatically. There are some other issues like dictionary words missing.
Is anyone else experiencing this ? Is there a way I can roll back this update? Any help is greatly appreciated. Thank you.
You can not rollback however you can reflash the entire firmware via dload. Let me check if files are available. Probably flashing the data file should address everything.