Mate 9 OpenKirin LineageOS 15.1 WiFi and Bluetooth stopped working. - Huawei Mate 9 Questions & Answers

So everything was working great until two weeks ago when a few apps updated and my son installed some games on my phone. Now WiFi and Bluetooth won't toggle. Every now and then it works but not for long and I am hoping its corporate policies update that went wrong. I tried to reset the phone by reapplying my ROM but now my recovery sector won't toggle with volume up and power. When I tried to fastboot reflash over everything got all jacked up. I think my recovery backup is corrupt. Now I randomly can load the OS. Downloaded a full ota ROM for my phone but some stuff has changed since I did this last and I'm really turned around. Using a spare iPhone atm and I miss my android apps.
My phone is on an oreo treble ROM format but I can't seem to get it back to pre error status. I'm turned around about which tutorial to try and don't want to brick my phone using the wrong guide. I'd like to go back to openkirin lineageos 15.1 or better yet any stable pie 16 ROM. Alternatively back to emui works as well.
Could someone please direct me as how to proceed?

Its starting to come back to me a bit. I downloaded the right OTA_FULL region version of my product type.
MHA-L29C567 - US Firmware Download from the following link
https://pro-teammt.ru/en/online-firmware-database/?firmware_model=MHA-L29C567&firmware_page=0
This file MHA-L29C567B377 (8.0.0.377) MHA-L09C567B377 (8.0.0.377)
Used Huawei UpdateExtractor to pull the following img files from the Update.app link in the filelist.
System.img
Ramdisk.img
Recovery_ramdis.img
Kernel.img
Flashed the device from fastboot using the following commands
fastboot flash system
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash recovery recovery.img
fastboot flash kernel KERNEL.img
Now I can enter recovery Volume Up + Power and do a factory reset but the process never yield a working phone it gets to the boot screen and keeps looping.
Any advice from the forum from where to go from here would be greatly appreciated. I just want to return to stock to see if there is a hardware issue with the phone and the WiFi and Bluetooth. I've read guides for returning to stock but the process I believe is for a Nougat ROM and I have a Treble (OREO+) harware partition structure.
Can someone point me to the proper guide?

I'm back.
Edited: missing link and grammer
I figured out how to fix my phone after reading this article
https://************/unlock-root-brick-recover-huawei-mate-9/
I'm replying in the hope to help anyone else with a US C567 Mate 9 in the same predicament. I'm using Stock OREO 8.0.0.377 EMUI with the Pixel Launcher found here:
https://huaweiadvices.com/download-android-p-launcher-apk-for-huawei-emui-phones-pixel-3-launcher/
Section on Unbricking in particular but also adding Custom TWRP recovery and re-branding the phone is what I used. My bootloader was already unlocked which I believe anyone else in this predicament will need to have as well to add TWRP. Process I followed was as such;
1) Installed Custom Recovery TWRP
2) Re-Branded the Huawei Mate 9 to Firmware C636 up to step 8
3) Then I used the Huawei eRecovery to connect my phone to Huawei's Servers and it connected downloaded and installed the appropriate ROM.
4)Updateded to the latested patch and all is corrected with my WIFI and Bluetooth as well.

So my wifi and bluetooth issue came back and I'm all but convinced at the point that the issue is with thee hardware. Really a shame I reset the phone and I'm at the stock and OEM rom at this point for my use model but nothings aside from Mobile data works. I guess I'm in the market for a new phone.

Related

[BETA][OFFICIAL] Android 7.0 EMUI 5 (L04C567B320) for FRD-L04C567

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?

[HELP] Looking for Huawei Nexus 6P Bootloop Fix

My Huawei Nexus 6P is on bootloop for a week and a half now. I have made some fixes, but still no luck. Here's what happened and the things that I've done:
[1]
My 6P was pure stock, no unlocked bootloaders, roots, and such. No reset happened, all straight OTA update from Marshmallow to the lastest Oreo 8.0.0 update back then (Current situation of the phone before it all happened)
First occurrences of the bootloop is not a BLOD. The phone suddenly freezes and restarts to some limited bootloops, until finally, it did bootlooped indefinitely.
At that time I don't have an unlocked bootloader. I was about to follow this fix https://www.xda-developers.com/nexus-6p-bootloop-fix/ when suddenly my 6P booted while plugged into my computer (I assumed it's because of the heat). So immediately, I've backed up my files manually (not nandroid nor using Titanium backup).
My phone worked from then, but since I was afraid that the bootloop might occur again:
1. I unlocked my bootloader
2. Flashed TWRP
3. Flashed Magisk and rooted through TWRP
4. Flashed ElementalX kernel
After that it worked fine for a night and half of the day the other day.
[2]
Afternoon that day, the phone started to bootloop again. But this time it cannot boot to TWRP: Upon selecting recovery mode from Fastboot, my 6 just tends to bootloop again. So, again, I've tried some things:
1. Re-flahsed TWRP (no luck)
2. Booted TWRP from my computer through fastboot (no luck)
3. Flashed all stock images from Google (Angler's Oreo) but still no luck
All just resulted to bootloop upon rebooting from Fastboot. Haven't tried anything again since then, until today
[3]
Today I've tried to follow this https://www.xda-developers.com/nexus-6p-bootloop-fix/ fix, but unluckily, I flashed the boot image for Nougat (as mentioned, mine's Android version is Oreo 8.0.0 from Google's downloadable stock images). Now my 6P is stuck in the Google logo for long. I've tried forcing shut down the 6P in hopes that I can boot to Fastboot again (and flash Oreo4Cores instead), but I can't. Now questions linger as my hope since to slip off
1. What can I do next?
2. Does flashing the Nougat boot image to an Oreo device work?
3. How long does it really take for this boot image fix to boot (if ever it does work)
4. What should I NOT do?
5. Or any other tips in this situation if ever I've got the wrong questions.
I hope someone could help me. Thank you in advance.
HEY...Dont worry.Take deep breath and follow each and every steps very carefully post on this link...
https://forum.xda-developers.com/ne...loop-death-t3716330/post74774303#post74774303
Today itself my beloved nexus 6p run into bootloop. I tried every possible fix like factory reset, clearing data,cache and reflashing stock rom but no luck.so, from this thred i followed and fied my nexus 6p.
Just wanna add some basic check before you start fixing..
1. Make sure your pc is update to date officialy.Use windows pc.I am using windows 10 up-to-date.use Ccleaner latest version to clean pc.click analyse and then run.For registry cleaning,do analyse and run but don't take backup when asked just click on no and proceed to clean registry.
Then,right click C Drive >properties>disk cleanup.check all boxes and click on "clean up system files".Again check all boxes after calculating finished>ok>delete files.
Restart your pc and follow above mentioned thred for easy fix.
2. Needed good quality data cable,nexus 6p driver installed and all correct patched files for each version.
NO NEED TO FLASH OTHER FILES EXCEPT PATCHED 4 CORES BOOT IMG FILE IF YOU DON'T WANT TO ROOT OR FLASH CUSTOM KERNAL.

Oneplus one bricked twrp not loading and no rom installed

Hello everyone!
I am new here and really looking forward for some answers. I own oneplus one and had a good experience with it. I had upgraded to custom rom that is lineage os 14.1
I wanted to upgrade it to 15.1 through Twrp. I followed the same procedure as i did for last flashing. I wiped the old data and everything and started to flash new rom. But this time twrp was giving an error. When I did research on that i found that i needed to upgrade to newer version of twrp to install lineage os 15.1
I did the same. And then end of it I just unselected the Supersu root and it reboots. Now when I go to the twrp recovery. The oneplus icon shows but then nothing happens. My phone now doesn't have a rom and twrp recovery won't open. When I connect it to my laptop through fastboot, cmd doesn't recognizes the device. I don't have any knowledge about tech and stuff. And I might have done something wrong. Please help me with some solutions
First of all, try to reinstall TWRP trough fastboot (boot in bootloader mode with Volume UP + power), just google a guide if you don't know how fastboot works. also be sure to use the correct twrp for bacon
After that you should be able to boot back in recovery and flash your rom
if still it doesn't work, follow this guide
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Sometimes it happens we brick our phones but No worries as long as you can go to fastboot you can always restore back to how it was before.
Either use the Program the guy above provided or this guide:
https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
I want to know how to flash the twrp again through fastboot, because when I connect it, phone is not detected in cmd. It says no fastboot devices are there. But then I checked and it says some android thing is connected in device manager. I hope it is my Oneplus one. How to pass this step?
It's the android drivers. Make sure you have the drivers installed.
Thank you so much. I was able to download the twrp again and flashed the 14.1 lineage os. The latest twrp is not flashing in the phone i don't know why and because of that 15.1 lineage os is not flashing and shows error. But still it's a relief that my phone is working. Also, when i switch on the camera it's not working and the flashlight icon also is dim and doesn't gets clicked and not works.

My OP 7 PRO(GM21AA) is being completely stuck at Fastboot.

Hey,
It's been always a huge headache since when the Android 10 beta and stables updates are out to root and install twrp. I've tried almost every way possible but every-time, end up being stuck at TWRP or being half way rooted. This time I've tried doing that again :
* I was at OxygenOs Android 10 stable version,
* My bootloader was unlocked as well as OEM unlocking and usb debugging was on,
* I turned my phone into fastboot, and flash the twrp image as:
fastboot flash boot file.img
Then after my phone booted into TWRP since once or twice showing that 0mb internal storage, I flashed the Magisk.zip from adb command, and rebooted it.
Since then, my phone is completely stucked at fastboot, I've tried and followed almost every xda suggestion and everything, I've tried flashing flash.bat file, I've tried flashing stock recovery, In fact I've tried flashing complete fastboot Rom (with all in one app)and it everytime boots me into Fatboot.
Please, help me out guys. I'm stressed out of this problem since yesterday's night.
Let me know your suggestions.
Maybe THIS can help you?
Actually this thread helped me just now in the same situation:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
That thread Jonsat mentioned didn't help me either, at all. Its not very clear that thread, telling in the thread to unbrick a OP7 to look at the thread of the OP6, there send them to OP5 and so on, eventually having to use a short written manual for the OP3 which mentions different versions and so on, its not the best for inexperienced people like me, it just send me on a wild chase downloading drivers and other things that eventually didnt work at all. Maybe I will try to rewrite it, as soon as I have enough experience to do so, i own this device for just a week.
Next time, read before you peform the install steps. It's nowhere like the older devices due to the A/B Recovery.
1. Use MSM Downloader to put you back to stock.
2. Upgrade to Android 10
3. Factory Reset to Clean out your phone (don't forget to unlock bootloader)
4. Initialize phone
5. Boot twrp (specific to Android Q + OP7 Pro)
6. Install TWRP and Magisk from TWRP
7. reboot and enjoy your rooted phone
lloydlim996 said:
Next time, read before you peform the install steps. It's nowhere like the older devices due to the A/B Recovery.
1. Use MSM Downloader to put you back to stock.
2. Upgrade to Android 10
3. Factory Reset to Clean out your phone (don't forget to unlock bootloader)
4. Initialize phone
5. Boot twrp (specific to Android Q + OP7 Pro)
6. Install TWRP and Magisk from TWRP
7. reboot and enjoy your rooted phone
Click to expand...
Click to collapse
What is MSM download tool? I'm going to try using All in One.
On searching for MSM tool, I found https://www.techoxygen.com/msm-download-tool/ is that correct?
Scratch this, MSMdownload is part of zip, I'll read through https://forum.xda-developers.com/showpost.php?p=79972789&postcount=50 and see how it goes

Lenovo Tab 4 10 plus 30 second boot loop

How can in get out of this boot loop, any advice, answers, help appreciated?
As background my Lenovo Tab 4 10 plus (stock 7.1 rom) had a failed SD card so I replaced the card and factory reset and thought I would try TWRP, Linageos 17.1 with magisk and relevent gapps - this all worked fine other than a Skype issue. I then found an 18.1 rom and tried that and this is where it seems to have gone wrong I set it up in the same ways as the 17.1 rom but with Andriod 11 gapps to suit, did a factory reset and 30 seocnds in I got the boot loop.
To fix it I tried going back to the 17.1 rom set-up that had worked but this then boot looped even with a full recovery reset. I have gone back to the stock rom backup in TWRP again with a recovery reset same boot loop. I have even used the Lenovo recovery tool to EDL mode flash a newly downloaded stock rom and it's still boot looping. I can only think that the 18.1 andriod 11 rom changed something fundimental but I can't find what?
Further I have another problem, the EDL flash worked but it locked the bootloader, however as I can't get in to Andriod with the boot loops, I can't switch ADB mode on so I can't unlock the bootloader to get TWRP up again.
So is there a way to start ADB without access to develeoper settings maybe through fastboot or recovery which I can get in to? Unlock the bootloader without ADB? Does anyone know why after the 18.1 Andriod 11 based rom, I have this continous boot loop?
I have a tb-x704f wich was totally caught in a boot loop, but I manisched to get back to working stock.
I was running firmware s000056 when I flashed twrp without backing up anything. I thought I never would have to go back to nougat, but standby time on lineage os was just not good for me, as I only use my tablet maybe half an hour a day, and I had to charge several times a week nevertheless.
So I tried to get back to stock and awesome standby time.
It was not easy bootloop after bootloop.
Tried Lenovo rescue and smart assistant multiple times, factory reset before and after flash, without SD card inserted etc, but bootloop.
Tried flashing the rom downloaded from the rescue tool with qfil but same result.
I then tried flashing the files with miflash 2016.08.30.0 still the same rom as I thought it had to be s000056. Miflash stopped halfway with some kind of error.
I then downloaded a stock rom from lenovo-forums.ru http://lenovo-forums.ru/topic/24135-lenovo-tab4-a10-plus-proshivka-tb-x704f_s000037_170703_row_qfil/
from the link in the discussion in the bottom of the site.
I had twrp still so from there I got into terminal and wrote "reboot edl" to get into emergency download mode and then flashed away. I presume that I could just as well had gotten in to edl mode by pressing vol+ and vol- simultaneously and then connected to PC holding those to buttons pressed. When the tablet was finished it was off, so I started going to recovery and wipeed cache and did a factory reset. Then booted and instead of bootloop it showed the Lenovo screen with a progress bar underneath. I successfully booted and took a update and then i am back to stock s000056.
The rom I got from lenovo-forums.ru stated it was only for EU and wi-fi model only. I am in Denmark and my tablet is WiFi only.
I think chances for success is greater using miflash than other tools when recovering from bootloop, but then again I don't know. Maybe I could just have flashed the s000037 rom with qfil or maybe I was just lucky, who knows.
But this what worked for me.
I hope this can help someone as I could not with the help of god find any useful help regarding this problem.
pallep said:
I hope this can help someone as I could not with the help of god find any useful help regarding this problem.
Click to expand...
Click to collapse
Thanks kind man You helped finish my struggle!
The only thing I want to add is that the ROM from the original link is no longer available, so I found the correct ROM using Google from the original filename here https://firmware247.com/lenovo-tab4-a10-plus-tb-x704f-firmware/

Categories

Resources