Database Info

Droid Turbo XT1254 5.1 Rooted Images (+Xposed, other extras) UPDATED 10/10

This is only for devices currently on 4.4 or rooted 5.1 w/ moforoot. This upgrade path allows moforoot to continue to work, and retains the ability to downgrade to 4.4.
Note 12/2/2015:
Development on this has been discontinued with the release of the SunShine bootloader unlock.
To use SunShine without having to deal with KingRoot, you can flash the Rooted v3 system img and then use SunShine to unlock. This is the most stable method if you can use mofo.
After unlocking using SunShine, please flash the latest bootloader/radio images from here. This will bring your phone completely up to date and provide a more stable experience with custom ROMs.
These images are still flashable after unlocking your bootloader if you'd like a stable, closest-to-stock ROM possible.
Instead of using mofo to flash the system image, you can just use
Code:
fastboot flash system filename-goes-here.img
You can then flash your own tweaks like Xposed.
I'd recommend making a back up of the stock ROM in TWRP so you have a stable base to go back to if anything goes wrong.
Note 10/10/2015:
Updated all images to the latest OTA update (SU4TL-44) and included the latest official Xposed version (v75) in extras v5.
Follow the instructions with 5.1_images_v4.zip to flash the updated firmware images.
Note 9/5/2015:
Updated extras (v4) to include the latest official Xposed version (v73). Read the previous note for more information.
Note 8/31/2015:
Updated extras to the latest official Xposed version (v72). Reflashing all of the images is not required, only the extras system.img using mofo.
You can download the full extras image (1.5gb), or if you already have the rooted v2 image, use the extras v3 patch (8mb) with the instructions below.
Using the rooted v2 image + patch will allow you to update in the future without redownloading the entire image (as long as you keep the original after patching).
Note 7/23/2015:
Updated to the latest OTA (23.11.39). Make sure to follow instructions and reflash all images from the latest zip.
Unfortunately, I couldn't provide a patch to go from rooted image v1->v2, so a redownload is needed.
When applying the latest extras, make sure you're applying it to the rooted image v2.
Files (updated 10/10/2015 w/ latest OTA & extras v5)
5.1 firmware images (v4)
SHA1: 8be8a19664e6ba5aa556838bb3f744cdbf41f2ef
Stock 5.1 system image (v3)
SHA1: 1e67fc22331f035e9f3bd6c28d81fb173dd86a3e
Rooted 5.1 system image (v3)
SHA1: b8ff04d7f6ad9de31292cf62da94a3d80d3e373c
Extras 5.1 system image (rooted v3 + extras v5) (see below for details)
SHA1: 126744919f86132c05d15e79373ea759f74e37cf
Instructions
A data wipe is not required, but please back up any important data beforehand in case something goes wrong.
After extracting 5.1_images_v4.zip, reboot into bootloader and run the following commands to prepare your phone for the latest 5.1 system image:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem modem.img
fastboot flash mdm1m9kefs3 fsg.mbn
fastboot erase mdm1m9kefs1
fastboot erase mdm1m9kefs2
fastboot flash recovery recovery.img
fastboot erase ddr
fastboot reboot-bootloader
Then use mofo to flash the system image of your choice and reboot.
After flashing a system image, the first boot will stay on the Motorola logo for an extra 30 seconds to 1 minute. This is rebuilding the cache partition (erased by moforoot after every flash).
If your phone doesn't boot after 5 minutes (and isn't showing the "Upgrading apps" dialog), try formatting the cache in recovery by doing the following:
While phone is off, hold the volume down button and turn it on to boot into bootloader. Use the volume keys to find the recovery option and press power to confirm.
Once you see the dead Android (it may also say "No Command", this is normal), pull up the recovery menu by holding power and pressing volume up (5.1 recovery is different than 4.4) and use the wipe cache option.
If the screen is blank in recovery with a periodically flashing Android icon, try booting the phone normally and trying again. This happened to me a few times, and I theorize it's because of the cache partition not being formatted after erased.
Extras (updated 10/10/2015 w/ latest OTA & Xposed official v75)
Download patch (v5)
SHA1: 451be2eef3df509facf16b807c6fc665c8fac090
If you don't want to deal with patching the image using xdelta3, you can download the full extras image in the Files section above.
This will prevent you from updating without redownloading the whole image in the future, but is easier for less experienced users.
Current extras:
Xposed official v75 (download APK from here)
(optional) ad blocking
busybox/sqlite3
tethering enabled
To apply the patch, use the rooted v3 image (not an already patched image) as a base, and follow the patching instructions (using xdelta3) in this post.
After patching the system.img with the extras, you'll use mofo to flash the patched image.
To use ad blocking, download AdAway (available in F-Droid) and enable it. Make sure the "Target hosts file" is set to "/data/hosts" in settings.

shouldnt we also be updating the radio?

diabl0w said:
shouldnt we also be updating the radio?
Click to expand...
Click to collapse
I haven't personally tested upgrading the radio, and whether that affects downgrading at all. If someone confirms it's without risk, I'll add the radio.img to the zip and instructions.

firstEncounter said:
I haven't personally tested upgrading the radio, and whether that affects downgrading at all. If someone confirms it's without risk, I'll add the radio.img to the zip and instructions.
Click to expand...
Click to collapse
ive downgraded radio from 4.4 to 4.2 in the past, but it messed up wifi somehow... isnt wifi part of the modem image? anyways, nothing else bad happened so idk if this is useful info
edit: when i did the downgrade (4.4.4 to 4.4.2 radio) it disabled the ability to turn on wifi and log messages gave the error wifistatemachine: failed to load wifi driver

diabl0w said:
ive downgraded radio from 4.4 to 4.2 in the past, but it messed up wifi somehow... isnt wifi part of the modem image? anyways, nothing else bad happened so idk if this is useful info
Click to expand...
Click to collapse
It looks like radio is just a collection of the modem images, so that should eliminate some of the commands. I'll update the OP.

firstEncounter said:
It looks like radio is just a collection of the modem images, so that should eliminate some of the commands. I'll update the OP.
Click to expand...
Click to collapse
check my edit

diabl0w said:
check my edit
Click to expand...
Click to collapse
Radios won't be compatible across ROM versions. You would flash the 4.4.4 radio if downgrading to a 4.4.4 image, not while running 5.1.

Ummmmm. Is this a dream? Someone pinch me...... There's no one around....... Can this really be true!? I'm afraid to try it and bork everything.

firstEncounter said:
This is only for devices currently on 4.4, requires moforoot. This upgrade path allows moforoot to continue to work, and retains the ability to downgrade to 4.4.
Files:
5.1 upgrade images
Stock 5.1 system image
Rooted 5.1 system image
After extracting the 5.1_images_v2.zip, run the following commands to prepare your phone for a 5.1 system image:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot erase ddr
(Commands based on this post. Thanks @mikeoswego and @JulesJam!)
Then use mofo to flash the system image of your choice.
Xposed and Adblock images coming soon.
Click to expand...
Click to collapse
Why aren't you flashing 5.1 recovery?

JulesJam said:
Why aren't you flashing 5.1 recovery?
Click to expand...
Click to collapse
Missed that command in the OP. Thanks!

Is the rooted image debloated
Sent from my XT1254 using Tapatalk

JulesJam said:
Why aren't you flashing 5.1 recovery?
Click to expand...
Click to collapse
So we should do that command as well?

janitorjohnson said:
So we should do that command as well?
Click to expand...
Click to collapse
I had trouble when I tried to stay on 5.0 recovery after I flashed 5.1 system image on my MX14.

JulesJam said:
I has trouble when I tried to stay on 5.0 recovery after I flashed 5.1 system image on my MX14.
Click to expand...
Click to collapse
Is that the final command?

trikotret said:
Is the rooted image debloated
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
No, it's completely stock with SuperSU installed.

janitorjohnson said:
Is that the final command?
Click to expand...
Click to collapse
I do
logo
boot
recovery
radios
But I do that b/c that is the way they are usually written in the scripts that come with the images. I think the only 2 where the order really matters is the bootloader and partition table and you aren't flashing those.
---------- Post added at 05:18 AM ---------- Previous post was at 05:16 AM ----------
firstEncounter said:
No, it's completely stock with SuperSU installed.
Click to expand...
Click to collapse
I went ahead and made one too just in case there were any issues with FirstEncounter's since I already have a device set up to do this anyhow.
https://www.dropbox.com/s/rmuev8agm5wl2lh/XT1254_5.1_root_system_ext4.zip?dl=0
PLMK if there are any issues with my image. I will take it down once people have started to modify the images, test them and are sure there are no issues.
It should be easy for someone to modify the buildprop so you can have free tether.

works like a charm
firstEncounter said:
This is only for devices currently on 4.4, requires moforoot. This upgrade path allows moforoot to continue to work, and retains the ability to downgrade to 4.4.
Files:
5.1 upgrade images
Stock 5.1 system image
Rooted 5.1 system image
After extracting the 5.1_images_v2.zip, run the following commands to prepare your phone for a 5.1 system image:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot erase ddr
Then use mofo to flash the system image of your choice.
Xposed and Adblock images coming soon.
Click to expand...
Click to collapse
Followed instructions to a T and used OP's files... Everything works like a charm and is buttery smooth: http://imgur.com/ZwIRB8X
Bootloader acted a little weird, got a couple screen flickers... not sure if related or not. It worked itself out after one or two reboots. Thanks for the awesome instructions!

Just updated the OP with a patch for Xposed, ad blocking, busybox and tethering. Let me know if it works for everyone.

firstEncounter said:
Just updated the OP with a patch for Xposed, ad blocking, busybox and tethering. Let me know if it works for everyone.
Click to expand...
Click to collapse
Thank you! You are working mighty quickly I must say. We all really appreciate it!

I can not seem to boot it to recovery after doing the steps in OP. Little man blinks and says "no command" under him. Wanted to do a factory reset after the steps in OP. Any ideas? I am letting it boot into LP for the first time and then will try to get into recovery to do the reset.
After I let LP boot up, I could enter into recovery and factory reset without a problem.

[Dec-25-2016] H850 20B DeOdexed

Your warranty is now void, don't blame me if your phone blows up blahblahblah.
Only system and kernel are being flashed, no Modem, BL, etc. You should already have updated to 20B before using.
Have not tested this myself, due to not owning the H850. edit: flashed it on T-Mobile 830 for fun with 20A 830 boot, no surprise, didn't work.
Decided to post anyway. If your going to use it, BACKUP, BACKUP, BACKUP
Based off of H85020b_00_TIM_IT_OP_1123.kdz
Only things touched are bootanimation (pixel black) and renamed recovery-from-boot.bak. It's also been zip-aligned.
Flash in recovery, profit??
SuperSu and Busybox included. Only /system is wiped, data left alone.
Should be able to dirty flash over current 20B if you like.
Any errors, etc, would most likely be related to deodexing as all files are stock.-Again, haven't tested this one myself
Link: H850_20B_DeOdexed
MD5: 99c9667294d1227de91605b8958233e0
If anyone would like to use this as a base, Great! Would appreciate some credit. [emoji13]
Enjoy.
Optional: Adjust Screen Color
Credits: @Chainfire for supersu. @SuperR. for the kitchen. @PlayerZ_ZawZaw for bootanimation. @jcadduono for TWRP. @bullghost for Firmware Extractor
It's people like them that make Android great!
Finally, thanks to Google/LG & XDA.
...whew.

Reserved

Great work Bro, nice. :good:

A couple questions 1. Isn't 20B just a security patch update? 2. Does this ROM zip upgrade firmware (bootloader , radio, recovery) or just update software. 3. Since it's based off of the Italian H850 variant this won't cause troubles for EU variant?

xlxcrossing said:
A couple questions 1. Isn't 20B just a security patch update? 2. Does this ROM zip upgrade firmware (bootloader , radio, recovery) or just update software. 3. Since it's based off of the Italian H850 variant this won't cause troubles for EU variant?
Click to expand...
Click to collapse
1. Not 100% sure. 2. Just system and kernel are flashed. No M/BL, etc. 3. No idea really.

Received error while flashing, code 7, seems it couldn't locate a certain filesystem and aborts installation - same here with the 20B version

Mr. Schnabel said:
Received error while flashing, code 7, seems it couldn't locate a certain filesystem and aborts installation - same here with the 20B version
Click to expand...
Click to collapse
Hmmm flashed ok on my h830(swapped kernel), wouldnt boot (of course, this is for 850), but still flashed. Not sure why your getting that error, already removed the assert.

lordodin912 said:
Hmmm flashed ok on my h830(swapped kernel), wouldnt boot (of course, this is for 850), but still flashed. Not sure why your getting that error, already removed the assert.
Click to expand...
Click to collapse
Same error... Keep at it tho, something like this could be really useful

If anyone wants to try this themselves here's a quick guide.
You can take the system.img and boot.img from either the kdz with LG Firmware Extractor or from autoprime complete zip.
Then Google "superR kitchen xda", if your using windows there is a VM iso in the thread you can use with VirtualBox etc.
Once you have the kitchen working just remember, set_metadata for perm, use smali/baksmali for deodexing and don't sign the zip or let it remove the meta-inf folders from apps.

In my h850 doesn't finish to install, it remains on initial boot animation.

failax said:
In my h850 doesn't finish to install, it remains on initial boot animation.
Click to expand...
Click to collapse
Flashed ok but stuck on LG logo? May need to flash no verify or "format data" in TWRP. BACKUP everything if formatting.

Ok so I just clean flashed my 20a for h830 and got that error code 7, doesn't happen on dirty. Just restarted TWRP after wiping and then it flashed ok. Might be the same problem over here.

[ROM][v521] LG Stock Nougat ROMs for LG G Pad X 8.0 (2018-06-18)

Disclaimer:
I am not responsible for anything that may happen to your phone as a result of installing this rom. You do so at your own risk and take responsibility upon yourself.
About:
The Stock ROMs posted here are extracted from official LG KDZ files for the T-Mobile LG G Pad X 8.0 | v521 | b3.
Only change made on ROM was to prevent stock recovery from restoring itself
ROM includes modem/radio, however you can also manually flash the modem/radio from here
root is NOT included. However feel free to flash your choice of root with Magisk, SuperSU, or any others at anytime to get root.
Info:
Android version: 7.0
Kernel version: 3.10.84
Build number: NRD90U
init.d support
forceencrypt disabled
Requirements:
Your device must be or have been on 20f or newer at one point or another. If your device has always been on Marshmallow and has never been updated to Nougat by kdz or OTA, you'll need to upgrade to Nougat and re-root first. (Thank to monkeyass408 for verifying)
You can follow this guide to do so: Guide to Update V521 LG GPAD X 8.0 to 7.0 and Root
You must have TWRP or another custom recovery already installed in order to flash this rom.
Instructions:
Download the version of your choice from below.
Boot into TWRP and make a backup. You may want to remove any lock screen security before doing this as restoring with lock screen may cause unexpected issues.
Optional: Wipe data and/or system. As of TWRP 3.1.1.0, you will want to reboot recovery after wiping data/system before flashing as TWRP may get stuck on a black screen during the flashing process without a reboot.
Flash ROM.
Optional: Flash the disable OTA zip to prevent and disable official LG OTA updates & notifications
Reboot and you should be all set.
Downloads: (Listed by Sofware version / Android security patch level)
Note: As of 2017-02-21, TWRP 3.0.2-0, will sometimes give the error "Failed to map file" when attempting to flash this rom. Rebooting TWRP will resolve it and allow you to flash the zip.
v52120n >> Apr 1, 2018
v52120m >> Feb 1, 2018
v52120l >> Dec 1, 2017
v52120k >> Oct 1, 2017
v52120j >> Aug 1, 2017
v52120i >> Jun 1, 2017
v52120h >> Apr 1, 2017
v52120g >> Feb 1, 2017
v52120f >> Dec 1, 2016
All Stock ROMs Folder
Disable Stock OTA
Note: This should prevent you from verifying and updating via OTA. The OTA notification may still pop up but it should go away when you attempt to update after flashing this. I haven't fully tested this so backup first and don't be surprised if it returns you to full stock.
Credits/Thanks:
tungkick for the initial root method
shabbypenguin for TWRP on the LG G Pad X
All other devs who make rom building possible

Reserved - Unlikely I'll need it but who knows?

Can this be flashed over marshmallow 10c? If so, what should be wiped? Thanks.

channeledbymodem said:
Can this be flashed over marshmallow 10c? If so, what should be wiped? Thanks.
Click to expand...
Click to collapse
Yes you can flash this over Marshmallow v52110c. Technically a dirty flash (no wipe) would work fine but you never know so don't be surprised if issues spring up. After you flash the rom, since you're upgrading from Marshmallow, you'll want to update the radios too. The flashable zips for it can be found @ https://forum.xda-developers.com/lg...irmware-modem-flashable-modem-zips-t-t3564590. I'd recommend flashing the respective radio of the Nougat version you end up using.

so after I flash the 20g my 5ghz wifi keeps on disconnecting, same thing after flashing the 20g modem. wiped data as well. coming from official 20f rooted with dirtycow.
my 10 other devices are fine so it's not my router. not sure if it's an issue with the 20g, never had any issue with 20f

supaet said:
so after I flash the 20g my 5ghz wifi keeps on disconnecting, same thing after flashing the 20g modem. wiped data as well. coming from official 20f rooted with dirtycow.
my 10 other devices are fine so it's not my router. not sure if it's an issue with the 20g, never had any issue with 20f
Click to expand...
Click to collapse
Hmmm I haven't had any issues with my 5ghz on my tablet. The roms are ripped straight out of the kdz files so any changes between 20g and 20f are strictly from LG/T-Mobile. Although I do recommend keeping the modem version and the rom version the same, I am curious, would you be able to test and see if it still happens if you downgrade the modem version to 20f while you're on the 20g rom?

Long overdue but added 20h, 20i, and 20j.
Decided to get rid of AROMA and root selection so any root method can be manually flashed afterwards.
Stock recovery shouldn't restore itself now. init.d support and forceencrypt is set to disabled by default since TWRP doesn't play along nicely with encrypt anyways.

.fenrir said:
Long overdue but added 20h, 20i, and 20j.
Decided to get rid of AROMA and root selection so any root method can be manually flashed afterwards.
Stock recovery shouldn't restore itself now. init.d support and forceencrypt is set to disabled by default since TWRP doesn't play along nicely with encrypt anyways.
Click to expand...
Click to collapse
Appreciate the update Thanks!!!

A bit quicker this time around. 20k has been added.
Amd4life said:
Appreciate the update Thanks!!!
Click to expand...
Click to collapse
No problem.

.fenrir said:
Yes you can flash this over Marshmallow v52110c. Technically a dirty flash (no wipe) would work fine but you never know so don't be surprised if issues spring up. After you flash the rom, since you're upgrading from Marshmallow, you'll want to update the radios too. The flashable zips for it can be found @ https://forum.xda-developers.com/lg...irmware-modem-flashable-modem-zips-t-t3564590. I'd recommend flashing the respective radio of the Nougat version you end up using.
Click to expand...
Click to collapse
i flashed from 10c marshmallow to nougat 20k. i am having problems getting lte data to even show up. Would u happen to know how to get it working?
i did wipe and started fresh install. I also flashed the k modem and it didnt work.

monkeyass408 said:
i flashed from 10c marshmallow to nougat 20k. i am having problems getting lte data to even show up. Would u happen to know how to get it working?
i did wipe and started fresh install. I also flashed the k modem and it didnt work.
Click to expand...
Click to collapse
Shouldn't need to do anything for LTE to work. Does it get signal at least? I would confirm the APN settings just to make sure they aren't missing for whatever reason.
Otherwise, try another version and see if it does the same thing. Although it shouldn't be the case, it's possible that the device may need to be kdz'd to Nougat first before a Nougat ROM works without any problems. That being said, I do remember being able to manually flash Nougat on my tablet from 10c with no issues back when I was on it.

.fenrir said:
Shouldn't need to do anything for LTE to work. Does it get signal at least? I would confirm the APN settings just to make sure they aren't missing for whatever reason.
Otherwise, try another version and see if it does the same thing. Although it shouldn't be the case, it's possible that the device may need to be kdz'd to Nougat first before a Nougat ROM works without any problems. That being said, I do remember being able to manually flash Nougat on my tablet from 10c with no issues back when I was on it.
Click to expand...
Click to collapse
I figured it out. I had to take 10c marsh to 20f nougat stock and rerooted +twrp in order for it to work. No longee had grayed out lte and apn and missing imei. Thanks for the reply.
Flashing straight 10c marsh to a nougat rom will always give me those errors. Same when tried with resurection remix.

monkeyass408 said:
I figured it out. I had to take 10c marsh to 20f nougat stock and rerooted +twrp in order for it to work. No longee had grayed out lte and apn and missing imei. Thanks for the reply.
Flashing straight 10c marsh to a nougat rom will always give me those errors. Same when tried with resurection remix.
Click to expand...
Click to collapse
Glad to hear it worked out for you. I stand corrected on it being flashed over Marshmallow so I've updated the first post to reflect that. Thanks for trying and verifying it.

Hello,
The V52120l_00_1201.kdz is OTA, so could you please make the lastest ROM base on V52120l_00_1201.kdz
thanks in advance

@ .fenrir: I appreciate all the work you've done on this and don't really need the monthly patches. Is there a way to disable ota download and notification on a rooted tablet?
Thanks.

20l has been added. I also realized on the older files I accidentally called the device 8.3 instead of 8.0 in the zip so that's been corrected now.
Char_Liu said:
Hello,
The V52120l_00_1201.kdz is OTA, so could you please make the lastest ROM base on V52120l_00_1201.kdz
thanks in advance
Click to expand...
Click to collapse
Thanks for the heads up. Been busy with the holidays so didn't have a chance to do anything.
channeledbymodem said:
@ .fenrir: I appreciate all the work you've done on this and don't really need the monthly patches. Is there a way to disable ota download and notification on a rooted tablet?
Thanks.
Click to expand...
Click to collapse
When rooted, you should be able to delete /system/etc/security/otacerts.zip which should prevent the device from verifying for the OTA. Afterwards if the OTA was already downloaded on the device, you can delete the OTA update file at /cache/update.zip . That SHOULD be enough to do it but I won't make any guarantees until I get a chance to test it as you would probably need to delete the other LGFOTA as well. I'll make a flashable zip for it later on if necessary/when I get a chance.

.fenrir said:
20l has been added. I also realized on the older files I accidentally called the device 8.3 instead of 8.0 in the zip so that's been corrected now.
Thanks for the heads up. Been busy with the holidays so didn't have a chance to do anything.
When rooted, you should be able to delete /system/etc/security/otacerts.zip which should prevent the device from verifying for the OTA. Afterwards if the OTA was already downloaded on the device, you can delete the OTA update file at /cache/update.zip . That SHOULD be enough to do it but I won't make any guarantees until I get a chance to test it as you would probably need to delete the other LGFOTA as well. I'll make a flashable zip for it later on if necessary/when I get a chance.
Click to expand...
Click to collapse
Thank you for the update.!

Appreciate the update

Thx a lot
.fenrir said:
20l has been added. I also realized on the older files I accidentally called the device 8.3 instead of 8.0 in the zip so that's been corrected now.
Thanks for the heads up. Been busy with the holidays so didn't have a chance to do anything.
When rooted, you should be able to delete /system/etc/security/otacerts.zip which should prevent the device from verifying for the OTA. Afterwards if the OTA was already downloaded on the device, you can delete the OTA update file at /cache/update.zip . That SHOULD be enough to do it but I won't make any guarantees until I get a chance to test it as you would probably need to delete the other LGFOTA as well. I'll make a flashable zip for it later on if necessary/when I get a chance.
Click to expand...
Click to collapse

I have always had excellent battery life but after a dirty flash of v.l it is terrible. I am losing 30% overnight. Can I roll back to v.k? I am reluctant to clean flash v.l; it's a lot of work getting back to normal.

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!