L04 Region Patch and Bluetooth (Nougat B360 Help) - Honor 8 Questions & Answers

I've installed twrp and rooted my phone. I flashed the region patch and NFC appears to be working, but bluetooth isn't. Anyone run into this issue? I can flash the B320 region patch and bluetooth works fine.
***Update*** I fixed the issue. If anyone runs into this issue. Install the b320 region patch, reboot into system. Once booted up, reboot into recovery, flash the b360 region patch, and wipe dalvic and cache. Once you reboot back into system, bluetooth should now work.

where is the b320 region patch?

And does the region patch let you install English language firmwares from other regions (Europe)? I understand B380 fixes the "OK Google" problem in the Camera app and short battery life issue some people were having?

Related

Problem with Magisk ver 15.O and new flashing B369

Hi !
I had a problem for a few days.
I rooted my phone ( BLN L 21 C432B360) with Magisk, and when i update Magisk to version 15, i had no "Audio Engine "anymore.
With luck, i flashed my phone and updat this to B369, and rooted with Magisk Version 14.0.
Audio engine work fine yet, but I am unable to enter in developper option and in sécurity option to allow unknow source..
Any idea what happening?
I made a factory reset, flash boot.img, made a factory reset via TWRP but nothing work..
check u'r model number- it would be most probably generic
come back to stock by dload method or restore working twrp backup if u have with u'r model number and recheck u'r model number - if it's back to stock
after cleaning everything
follow this procedure
https://forum.xda-developers.com/showpost.php?p=74968881&postcount=108
or
this
https://forum.xda-developers.com/honor-6x/help/calling-testers-stock-rom-t3725430
don't forget to report back
It's the same error that i encountered, only that i was on B368 before updating other than B360. At the beginning i thought that i made something wrong, but as suggested by @sreekantt, Magisk versions above V14.5 breaks up the vendor.img of our phone. I flashed through TWRP Magisk V14.6 and that's where all this is started. This means that now if you go on phone info, your model should be changed to "generic_a15" instead of BLN-L21. At the moment i solved this restoring a previous backup took on B368 just before updating to B369, but i had to fix some errors still present in the file that i exposed in this guide https://forum.xda-developers.com/honor-6x/how-to/guide-how-to-correct-wrong-shown-build-t3724439 to make my build name correct again, because even restoring a previously took backup, my build number remained B369 (and i was on a B368 build with October security patch, not the November one), so i've solved incompatibilities with some apps of my original build that was keeping crashing, like camera. I'll download the update again, update and root but this time staying on Magisk V14.5, until a fix will be ready.
RedSkull23 said:
It's the same error that i encountered, only that i was on B368 before updating other than B360. At the beginning i thought that i made something wrong, but as suggested by @sreekantt, Magisk versions above V14.5 breaks up the vendor.img of our phone. I flashed through TWRP Magisk V14.6 and that's where all this is started. This means that now if you go on phone info, your model should be changed to "generic_a15" instead of BLN-L21. At the moment i solved this restoring a previous backup took on B368 just before updating to B369, but i had to fix some errors still present in the file that i exposed in this guide https://forum.xda-developers.com/honor-6x/how-to/guide-how-to-correct-wrong-shown-build-t3724439 to make my build name correct again, because even restoring a previously took backup, my build number remained B369 (and i was on a B368 build with October security patch, not the November one), so i've solved incompatibilities with some apps of my original build that was keeping crashing, like camera. I'll download the update again, update and root but this time staying on Magisk V14.5, until a fix will be ready.
Click to expand...
Click to collapse
Thnaks you for your help.
I use Root Explorer but I am unable tu enter in root/version/special cust/BLN-L21/hw/eu/prop/local.prop because my phone , even if i installed Magisk Version 14 , is not rooted because I am unable to allow unknow source and developper option....
My build nummer is BLN-L21 but yesterday I saw in my Build.pro "Generic-a15...."
How can I downgrade or fresh install B369 or B365???
Or haow cann acces to the folder root/version/special cust/BLN-L21/hw/eu/prop/local.prop?
Thanks in advance.
ben75011 said:
Thnaks you for your help.
I use Root Explorer but I am unable tu enter in root/version/special cust/BLN-L21/hw/eu/prop/local.prop because my phone , even if i installed Magisk Version 14 , is not rooted because I am unable to allow unknow source and developper option....
My build nummer is BLN-L21 but yesterday I saw in my Build.pro "Generic-a15...."
How can I downgrade or fresh install B369 or B365???
Or haow cann acces to the folder root/version/special cust/BLN-L21/hw/eu/prop/local.prop?
Thanks in advance.
Click to expand...
Click to collapse
Try to get full firmware package and use dload method to flash the latest update. Go only with a number matching or superior your build number to make dload work fine (if you're on B369, actually you can dload only with B369 for example)
RedSkull23 said:
Try to get full firmware package and use dload method to flash the latest update. Go only with a number matching or superior your build number to make dload work fine (if you're on B369, actually you can dload only with B369 for example)
Click to expand...
Click to collapse
Hi,
I download the latest B69 firmware and try to install with DLOAD but updating work to 5% and said Update Failed.
I find a solution to endter in my system prop, My Buil nummer is BLN-L21C432B369 but in my build prop, it is notified generixc_a15....
And the problem is, i can not enter in the menu "Security" and not enter in the developper option, even if it is notified...
How to erase everithing and flash the B369 i have downloaded?
Sorry for my bad english
ben75011 said:
Hi,
I download the latest B69 firmware and try to install with DLOAD but updating work to 5% and said Update Failed.
I find a solution to endter in my system prop, My Buil nummer is BLN-L21C432B369 but in my build prop, it is notified generixc_a15....
And the problem is, i can not enter in the menu "Security" and not enter in the developper option, even if it is notified...
How to erase everithing and flash the B369 i have downloaded?
Sorry for my bad english
Click to expand...
Click to collapse
Never had luck using dload method so i can't help much, but try like this, it should work;
1 - in the local.prop file, modify every voice that ends with B369 with B368, save, reboot and check by phone info if the build number is still B369 or it is become B368. Because in this way, you'll be able to receive the OTA of B369 again.
2 - Remove root by Magisk Manager with the completely uninstall function (you're already without, but do it anyway). Reboot.
3 - Flash by fastboot the stock boot.img and recovery.img for BLN-L21C432B368 (i provided those two in the repository thread here on XDA, check this post of mine to get them https://forum.xda-developers.com/ho...ory-honor-6x-file-depot-t3534800/post74645608). After that you've flashed both of them, reboot.
4 - Go on system update. It will detect the partial OTA for B369, that weights 247MB or something like that. Don't do it, but instead click on the 3 dots in the upper right corner and tap on "download latest update". Then it'll detect the BLN-L21C432B369-FULL package. Once it'll be available for download, download it and when UI prompts if updating immediately or during night, let the update start.
If everything will works, you'll be on B369, with BLN-L21 as model number and with everything in its right place. Good luck
RedSkull23 said:
Never had luck using dload method so i can't help much, but try like this, it should work;
1 - in the local.prop file, modify every voice that ends with B369 with B368, save, reboot and check by phone info if the build number is still B369 or it is become B368. Because in this way, you'll be able to receive the OTA of B369 again.
2 - Remove root by Magisk Manager with the completely uninstall function (you're already without, but do it anyway). Reboot.
3 - Flash by fastboot the stock boot.img and recovery.img for BLN-L21C432B368 (i provided those two in the repository thread here on XDA, check this post of mine to get them https://forum.xda-developers.com/ho...ory-honor-6x-file-depot-t3534800/post74645608). After that you've flashed both of them, reboot.
4 - Go on system update. It will detect the partial OTA for B369, that weights 247MB or something like that. Don't do it, but instead click on the 3 dots in the upper right corner and tap on "download latest update". Then it'll detect the BLN-L21C432B369-FULL package. Once it'll be available for download, download it and when UI prompts if updating immediately or during night, let the update start.
If everything will works, you'll be on B369, with BLN-L21 as model number and with everything in its right place. Good luck
Click to expand...
Click to collapse
Thanks you for your help. I will try it and see feedback soon !!!
I hope it work yet
RedSkull23 said:
Never had luck using dload method so i can't help much, but try like this, it should work;
1 - in the local.prop file, modify every voice that ends with B369 with B368, save, reboot and check by phone info if the build number is still B369 or it is become B368. Because in this way, you'll be able to receive the OTA of B369 again.
2 - Remove root by Magisk Manager with the completely uninstall function (you're already without, but do it anyway). Reboot.
3 - Flash by fastboot the stock boot.img and recovery.img for BLN-L21C432B368 (i provided those two in the repository thread here on XDA, check this post of mine to get them https://forum.xda-developers.com/ho...ory-honor-6x-file-depot-t3534800/post74645608). After that you've flashed both of them, reboot.
4 - Go on system update. It will detect the partial OTA for B369, that weights 247MB or something like that. Don't do it, but instead click on the 3 dots in the upper right corner and tap on "download latest update". Then it'll detect the BLN-L21C432B369-FULL package. Once it'll be available for download, download it and when UI prompts if updating immediately or during night, let the update start.
If everything will works, you'll be on B369, with BLN-L21 as model number and with everything in its right place. Good luck
Click to expand...
Click to collapse
Also.
I made everything possible.
Flash B368, unroot...
But yet my build number is B368 and i cant received any notification of update.
And i am not allowed to enter in the Security option and in the developper option...
I dont know what I can do yet...
Thanks for the heads up. Didn't even realize the magisk update had completely borked my system.
Bro I Had The Same Problem Just Go To Recovery And Uninstall Magisk v15 And Flash Magisk V14.Everything Will Be Back To Normal.
I like how I found this thread AFTER I went through heck and back to fix my audio issue after flashing Magisk v15. Ultimately ended up flashing magiskuninstaller.zip then flashing with supersu.zip as I figured Magisk was the cause. Sure enough now Youtube and stock music app now works. I will be attempt reflashing magisk v14 and see if that makes a difference. Glad I wasn't the only one having this issue!!
I've been looking everywhere for a solution for the same problem. No sound and can not play any kinda video. I'm useing a BLN_-L24 567360. And I tried a twrp back up and now it say my phone is generic_a15. I was just rooted with magisk and twrp recovery.
McRoberts said:
I've been looking everywhere for a solution for the same problem. No sound and can not play any kinda video. I'm useing a BLN_-L24 567360. And I tried a twrp back up and now it say my phone is generic_a15. I was just rooted with magisk and twrp recovery.
Click to expand...
Click to collapse
I try since yesterday all possible. And I think the only solution is to revert to stock but I am im moment unable to revert to stock....
jyothis.shajiv said:
Bro I Had The Same Problem Just Go To Recovery And Uninstall Magisk v15 And Flash Magisk V14.Everything Will Be Back To Normal.
Click to expand...
Click to collapse
ieatgravity said:
I like how I found this thread AFTER I went through heck and back to fix my audio issue after flashing Magisk v15. Ultimately ended up flashing magiskuninstaller.zip then flashing with supersu.zip as I figured Magisk was the cause. Sure enough now Youtube and stock music app now works. I will be attempt reflashing magisk v14 and see if that makes a difference. Glad I wasn't the only one having this issue!!
Click to expand...
Click to collapse
McRoberts said:
I've been looking everywhere for a solution for the same problem. No sound and can not play any kinda video. I'm useing a BLN_-L24 567360. And I tried a twrp back up and now it say my phone is generic_a15. I was just rooted with magisk and twrp recovery.
Click to expand...
Click to collapse
ben75011 said:
I try since yesterday all possible. And I think the only solution is to revert to stock but I am im moment unable to revert to stock....
Click to expand...
Click to collapse
To use Magisk 15
Follow this
https://forum.xda-developers.com/showpost.php?p=74968881&postcount=108
Perfectly working
sreekantt said:
To use Magisk 15
Follow this
https://forum.xda-developers.com/showpost.php?p=74968881&postcount=108
Perfectly working
Click to expand...
Click to collapse
Thanks you, but my problem is for the moment to be able to revert to complete stock.....
ben75011 said:
I try since yesterday all possible. And I think the only solution is to revert to stock but I am im moment unable to revert to stock....
Click to expand...
Click to collapse
Do you still have a restore on twrp,? All I did to fix was went inti twrp and uninstalled magisk via magisk uninstaller then rebooted to recovery then flashed magisk v14 and now I think it's all sorted out for the min. I just got it done but I got sound and video again. The XDA labs app is picking my phone up anain as honor x6 non generic a_15.
McRoberts said:
Do you still have a restore on twrp,? All I did to fix was went inti twrp and uninstalled magisk via magisk uninstaller then rebooted to recovery then flashed magisk v14 and now I think it's all sorted out for the min. I just got it done but I got sound and video again. The XDA labs app is picking my phone up anain as honor x6 non generic a_15.
Click to expand...
Click to collapse
I found the solution with this amazing topic https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985
I flashed my phone with latest firmware B369 and yet all is fine !!!!!
thanks you for your help.

Semi bricked honor 6x bln - L24. Please read, weird problems

So I got an honor 6x that I can't do anything with. I can't flash any ROMs or firmware here's the weird part of it.
Its on some version of EMUI that I can't have the system update menu and it has a button for app twin. It says BLN-L24C567B366 as the model number. Speakers don't work. I can't play videos on it and I can't use the camera in any app.
Here's the really weird part:. If I wipe all partitions and try to flash a room it boots to the same EMUI firmware not the custom rom I can't do anything to change what the rom is. It's like it's stuck in that weird Frankenstein EMUI firmware that I don't even know how I got. I tried restoring anback up cause I formatted my data partition on accident causing it not to boot or something and the backup I restored was not the backup that I made . The backup I made was a stock backup onto an SD card. When I restore it it's rooted and has some downloaded apps on it. And a different launcher. Not what I backed up originally.
I'm at a loss here. What do I do? Ihave full access to adb to flash with fastboot and can get into twrp or stock recovery. No ROMs I flash will work. In twrp it says it was successful. Ut when I boot it doesn't boot to that room, it boots to the weird emui os I can't get rid of.
Has anyone run into this issue or know how to fix it?
The exact same thing has been happening to me. The only OS that will boot up completely is the EliteRom that I attempted on my first flash after bootloader unlocking. I'm almost at my wit's end on how to resolve the issue, as I have tried the guide to roll back to stock posted here at XDA to a tee, with three different update.app files, and each one fails on install package step at 5%.
Hopefully someone with more experience than I will come along and can help us, but I did want to let you know you are not alone with this issue. At this rate, I'll have to get a backup phone to use.
All my update.app files get stuck at 5% too. And I know honor/Huawei won't repair it cause the warranty is void or if they can they would charge you.
Honestly get the Moto G5s plus. Get the unlocked version at best buy if you're in the states. It's 239 for the 32gb/3gb. Ram model and 299 for 64gb and 4gb. Best budget phone you can get and dual cameras. The ROM support isn't as big as the honor but it is easy to unlock the bootloader and do things. My only ROM issue I've had with this was trying to update magisk the phone had to reboot to install and after that, I had a lock screen set up btw, when I went to enter the pin the screen would go black, the phone would buzz, and go back to the lock screen. And I tried restoring a backup I made but the phone wouldn't boot stuck at the boot logo before the animation.
But the stock firmware I acquired on XDA along with the steps to flash in adb every file in the stock firmware fixed it with no problems at all so at least there's an easy way to restore the stock firmware for my new phone. It's way better than the honor 6x
Seriously tho check out the Moto G5s plus. Out of the box it has Android 7.1.1 mostly stock without all of Google's bloatware. Front mounted fingerprint sensor that you can you for the home, recent apps and back button, and can lock the screen with it if you have fingerprint set up and activate the Google assistant. It also has a notification light that you need root to use. But it has this cool "always on display" type thing that shows a clock and notifications when you move the phone or get a notification. It isn't an AMOLED display tho. It's. 1920x1080p one. Ips good viewing angles. Honestly this is the best phone I've ever used. And it has a Motorola turbocharger in the box. It's really worth it
TurtlePwr82 said:
The exact same thing has been happening to me. The only OS that will boot up completely is the EliteRom that I attempted on my first flash after bootloader unlocking. I'm almost at my wit's end on how to resolve the issue, as I have tried the guide to roll back to stock posted here at XDA to a tee, with three different update.app files, and each one fails on install package step at 5%.
Hopefully someone with more experience than I will come along and can help us, but I did want to let you know you are not alone with this issue. At this rate, I'll have to get a backup phone to use.
Click to expand...
Click to collapse
i think it could be an issue with the kernel cause the eliteRom has a custom kernel in it.. i have the update.app file for the BLN-L24C567B366 ad B365 files that i can extract and give you all the images that they have and maybe try to get the stock kernel somehow that might help?
TurtlePwr82 said:
The exact same thing has been happening to me. The only OS that will boot up completely is the EliteRom that I attempted on my first flash after bootloader unlocking. I'm almost at my wit's end on how to resolve the issue, as I have tried the guide to roll back to stock posted here at XDA to a tee, with three different update.app files, and each one fails on install package step at 5%.
Hopefully someone with more experience than I will come along and can help us, but I did want to let you know you are not alone with this issue. At this rate, I'll have to get a backup phone to use.
Click to expand...
Click to collapse
Try flashing every single update version until one of them works. Once youve found one that works follow this guide: https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985
I had somewhat the same issue, I dload always had an error in 5%, try to flash B360 with dload, that did the job for me.
As for the apps that dont show like the updater(yes, its a system app and is stored in /data) flash the other zips that come with the update.zip
My procedure was:
-Wipe /system and /data
-TWRP flash alternative zips that come with update.zip
-dload B360
That should bring you back to factory stock, In case you still dont have updater and other system apps:
-unlock bootloader(again)
-install TWRP
-DO NOT WIPE ANYTHING
-TWRP flash alternative zips that come with update.zip
-dload B360
xinoxkai said:
I had somewhat the same issue, I dload always had an error in 5%, try to flash B360 with dload, that did the job for me.
As for the apps that dont show like the updater(yes, its a system app and is stored in /data) flash the other zips that come with the update.zip
My procedure was:
-Wipe /system and /data
-TWRP flash alternative zips that come with update.zip
-dload B360
That should bring you back to factory stock, In case you still dont have updater and other system apps:
-unlock bootloader(again)
-install TWRP
-DO NOT WIPE ANYTHING
-TWRP flash alternative zips that come with update.zip
-dload B360
Click to expand...
Click to collapse
I'll give that a try. When you say flash alternative zips that have update.zip do you mean "stock" firmwares off firmware finder?
xSpartacusx said:
I'll give that a try. When you say flash alternative zips that have update.zip do you mean "stock" firmwares off firmware finder?
Click to expand...
Click to collapse
Yes, firmware finder showed me 3 zips, update.zip, update_data_full_public.zip and update_full_BLN-L24_hw_usa.zip, the later 2 are the "alternative zips". Just TWRP flash them.
Also, update_full_BLN-L24_hw_usa.zip might throw an error when flashing it, don't worry, by the stage it fails in its script it already did what it was expected to do and you will not have further problems.
do i need the stock recovery flashed in order to do dload?
well i followed the first half of your guide and it successfully "updated" but my storage is encrypted
xSpartacusx said:
do i need the stock recovery flashed in order to do dload?
Click to expand...
Click to collapse
Not really, I did it when I had TWRP installed
well so far so good now to do the other part also my build number is stil B366 camera and everything works now no updater or anything like that
xSpartacusx said:
well so far so good now to do the other part also my build number is stil B366 camera and everything works now no updater or anything like that
Click to expand...
Click to collapse
Yeah, my build number never changed from B366, the only thing is that when I finished everything even though I'm in B366, EMUI stays in 5.0 and not 5.0.1 as it should be... But that is the only difference and I didn't notice any difference really
okay got the stock apps back updater is back everything is fine!! one thing i noticed.. before i started flashing roms, i had an update to EMUI 5.0.1 and i dont have an update for it anymore...?
xinoxkai said:
Yeah, my build number never changed from B366, the only thing is that when I finished everything even though I'm in B366, EMUI stays in 5.0 and not 5.0.1 as it should be... But that is the only difference and I didn't notice any difference really
Click to expand...
Click to collapse
xSpartacusx said:
okay got the stock apps back updater is back everything is fine!! one thing i noticed.. before i started flashing roms, i had an update to EMUI 5.0.1 and i dont have an update for it anymore...?
Click to expand...
Click to collapse
Maybe at this point to fix the build number that remains another even if you're in a previous build, it could be sufficient to flash through TWRP a version.img extracted from your ACTUAL build. You can extract it from the update.zip of your actual firmware with Huawei Update Extractor and then flash it as image through TWRP
RedSkull23 said:
Maybe at this point to fix the build number that remains another even if you're in a previous build, it could be sufficient to flash through TWRP a version.img extracted from your ACTUAL build. You can extract it from the update.zip of your actual firmware with Huawei Update Extractor and then flash it as image through TWRP
Click to expand...
Click to collapse
xSpartacusx said:
okay got the stock apps back updater is back everything is fine!! one thing i noticed.. before i started flashing roms, i had an update to EMUI 5.0.1 and i dont have an update for it anymore...?
Click to expand...
Click to collapse
Today I fixed that issue, it showed me that I had B366 but the security patch was on march 2017 and EMUI 5.0 instead of 5.0.1.
What I did was install B366 with the proxy method with Firmware Finder, I made it download the full package from the Huawei Updater (it was around 2.4gb) after it finished the update I had B366, EMUI 5.0.1 and november security patch so all is fine now! :victory:
xinoxkai said:
Today I fixed that issue, it showed me that I had B366 but the security patch was on march 2017 and EMUI 5.0 instead of 5.0.1.
What I did was install B366 with the proxy method with Firmware Finder, I made it download the full package from the Huawei Updater (it was around 2.4gb) after it finished the update I had B366, EMUI 5.0.1 and november security patch so all is fine now! :victory:
Click to expand...
Click to collapse
Good one dude, maybe FF proxy method could help xSpartacusx to solve his issue too!

signal problem in nokia 6 TA-1021

Hello after updating to Oreo 8.0.0 my Nokia drop network signals. I have to restart it many times to get back network. Is it only me getting this issue or is there anyother.
Also stock camera app not working.
Whenever i open it it says couldn't connect to camera. On other hand all other application working fine.
Did you install it manually or via updater? Did you install the homebrew Oreo from hikari_calyx? Do you have a custom recovery installed? @sargodian2
1st i installed original Nougat with OST LA. Then notification pop up for oreo 8.0.0 i just i stalled it. Then i unlocked bootloader and i stall chinese twrp.
I just checked today there's another update. V8.1.
How i can install it ?
Just let the device to download it and install.
Or install it manullay.
I have unlocked bootloader.
And chinese twrp installed.
sargodian2 said:
I just checked today there's another update. V8.1.
How i can install it ?
Just let the device to download it and install.
Or install it manullay.
I have unlocked bootloader.
And chinese twrp installed.
Click to expand...
Click to collapse
DON'T! It will brick your device, you cannot install this update. To your signal problem: try clearing cache + dalvik

Downgrade Honor 6x to Nougat

Most of us didn't liked the oreo... As there is no audio mods, full theme support, no xposed etc...so I decided to downgrade to nougat.. As dloading b340 works for BLN L22 version.. But for me it didn't work... Any build was not working on dload method.. So i tried HWOTA method.. HW OTA works fine but at the end emui fails to install the system...
So I got a way from various senior members...
Using Hu Ru Updater..
Just download latest version Hu Ru Updater and full firmware of Nougat(donot download rollback package) .. Like b362 build.. Download all the three zips and hu ru updater and place it in a single folder of SD card..
Then go to twrp, format data... Reboot twrp... Then wipe data and system from twrp and start the hu ru updater..
After the process, just boot to stock recovery and format your device... That's it... You're on Nougat ?
Jugabrat said:
Most of us didn't liked the oreo... As there is no audio mods, full theme support, no xposed etc...so I decided to downgrade to nougat.. As dloading b340 works for BLN L22 version.. But for me it didn't work... Any build was not working on dload method.. So i tried HWOTA method.. HW OTA works fine but at the end emui fails to install the system...
So I got a way from various senior members...
Using Hu Ru Updater..
Just download latest version Hu Ru Updater and full firmware of Nougat(donot download rollback package) .. Like b362 build.. Download all the three zips and hu ru updater and place it in a single folder of SD card..
Then go to twrp, format data... Reboot twrp... Then wipe data and system from twrp and start the hu ru updater..
After the process, just boot to stock recovery and format your device... That's it... You're on Nougat ?
Click to expand...
Click to collapse
Nice guide. I know a couple of people will benefit from this. Now, I agree that Oreo or EMUI 8 sucks. However if you're up for it, flash a custom ROM. There are a couple of (now discontinued) good Pie ROMs available. You can try those. Sound Mod and Xposed still won't work (Xposed isn't available yet for Pie) and substratum works but requires root. Or an Oreo custom ROM. Sound Mod also won't work but the other two will. The only requirement is an unlocked Bootloader.
Mannan Qamar said:
Nice guide. I know a couple of people will benefit from this. Now, I agree that Oreo or EMUI 8 sucks. However if you're up for it, flash a custom ROM. There are a couple of (now discontinued) good Pie ROMs available. You can try those. Sound Mod and Xposed still won't work (Xposed isn't available yet for Pie) and substratum works but requires root. Or an Oreo custom ROM. Sound Mod also won't work but the other two will. The only requirement is an unlocked Bootloader.
Click to expand...
Click to collapse
Yes... You are right.. But i saw along with me, some people were struggling to rollback to nougat .. Cuz volte is one important thing that missing in custom roms...by the way,I have tried pixysos and aospa extended...
Jugabrat said:
Most of us didn't liked the oreo... As there is no audio mods, full theme support, no xposed etc...so I decided to downgrade to nougat.. As dloading b340 works for BLN L22 version.. But for me it didn't work... Any build was not working on dload method.. So i tried HWOTA method.. HW OTA works fine but at the end emui fails to install the system...
So I got a way from various senior members...
Using Hu Ru Updater..
Just download latest version Hu Ru Updater and full firmware of Nougat(donot download rollback package) .. Like b362 build.. Download all the three zips and hu ru updater and place it in a single folder of SD card..
Then go to twrp, format data... Reboot twrp... Then wipe data and system from twrp and start the hu ru updater..
After the process, just boot to stock recovery and format your device... That's it... You're on Nougat ?
Click to expand...
Click to collapse
Could you please post the links for the B340 files? I am confused which ones to download. Thanks a ton. Need to wake my device soon. Nothing seems to work for me too.
casperskie said:
Could you please post the links for the B340 files? I am confused which ones to download. Thanks a ton. Need to wake my device soon. Nothing seems to work for me too.
Click to expand...
Click to collapse
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1190/g79/v105727/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...el_in/update_data_full_BLN-L22_channel_in.zip
I'm not sure if it works for u or not...
But if u are able to use twrp then use hu ru updater and flash b362

[Troubleshooting] Stuck at "your device is booting"... after Magisk and DM-Verify update

Greetings Everyone.
Am facing a problem with my 6X .. yesterday (and I don't know why) updated Magisk to the latest version and am not sure why I checked the DM-Verify option.
the phone rebooted and stuck with "your device is booting..".
I think it's something related to userdata and system encryption.
I can enter eRecovery and Fastboot,
am unable to flash anything due to FRP lock.
Am running debranded GR5 2017 to BLN 6x
OS is Oreo 8.0.0.510 (C675)
The bootloader is Unlocked.
am in thankful to everyone who will help.
Edit :
I can enter TWRP recovery (I think it still exists since debranding to BLN 6X).
Edit 15/02/2022:
I was able to fix my device by doing Board Factory Method Link, Then I did FRP by test points, after that flash using SDCard the EMUI 4.1 and EMUI 5 Firmware reaching official Nought firmware, last but not least, I did rebranding using this method Link and updated to Oreo 8.0.0.510.
now am facing a bit of lagging or slowness in the firmware while doing stuff. I think am going to update to firmware version 520 to see if the problem exists.

Categories

Resources