Database Info

Has Anyone Gotten a Custom ROM onto a BLN-L24 (US Variant)?

I have tried quite a few ROMs, and all ended up going back to stock firmware because they wouldn't boot. I know I have to format data, and some ROMs ask you to change the data partition as f2fs.
Still, I think that there may be no ROMs that currently work for the US variant. One guy said LOS 13 worked, but when I flashed it, it failed. If someone has gotten it to work, can you please post as many steps as you remember on how to get it work?

Debrand to BLN-L21 following this guide and you're ready to flash cooked ROMs https://forum.xda-developers.com/honor-6x/how-to/guide-successful-debranding-to-bln-t3701050

RedSkull23 said:
Debrand to BLN-L21 following this guide and you're ready to flash cooked ROMs https://forum.xda-developers.com/honor-6x/how-to/guide-successful-debranding-to-bln-t3701050
Click to expand...
Click to collapse
Thanks, but wouldn't there be more issues down the line with a debranded phone? What if I soft-bricked my phone, it seems like it'd be really hard to restore? Has anyone actually ever done this on a BLN-L24?

Hello all,
I too am having issues with flashing roms to this device, US variant (BLN-L24). In my particular case, the rom boots up (EliteRom v7.1) and will actually function. However, wifi does not work, as well as I have no sound whatsoever. Youtube also will not play, nor will any videos, which I'm guessing is tied to whatever issue is with the sound. I have flashed multiple times per the step by step instructions, as well as following the Youtube video, all with the same result over the last few days. At this point, my phone is effectively useless to me, though cellular data does still work, just no calls can be answered. Anyone have any suggestions I might be able to follow? Also, even my TWRP backup that I made before installing the rom will not restore at this point. Any help is appreciated, thanks.

Jessooca said:
You must be missing a step or something, because [Elite ROM][EMUI 5.1] Elite ROM v7.1 for Honor 6X by HassanMirza01 works on the L24 us variant without issues, I have none.
Perhaps go back to stock and start over. I haven't had any issues with his rom and I didn't do anything more than what's needed to root/install twrp and flash the rom per his instructions.
Click to expand...
Click to collapse
I just followed the instructions; I believe to the best I could, and I'm stuck in a bootloop now. Which version of EMUI were you on before flashing? I was on EMUI 5.0 which may be my issue.
I started from EMUI 5.0
Unlocked my bootloader
Let it factory reset
Installed the Elite TWRP on the page
Booted to Elite TWRP
Formatted all partitions excpet for external sd card
Reformatted Data to f2fs
Re-wiped data
Checked that it was f2fs
Installed Elite ROM zip
Installed open gapps 7.0 ARM64
Installed the patch
Rebooted
Bootloop

i4ybrid said:
I just followed the instructions; I believe to the best I could, and I'm stuck in a bootloop now. Which version of EMUI were you on before flashing? I was on EMUI 5.0 which may be my issue.
I started from EMUI 5.0
Unlocked my bootloader
Let it factory reset
Installed the Elite TWRP on the page
Booted to Elite TWRP
Formatted all partitions excpet for external sd card
Reformatted Data to f2fs
Re-wiped data
Checked that it was f2fs
Installed Elite ROM zip
Installed open gapps 7.0 ARM64
Installed the patch
Rebooted
Bootloop
Click to expand...
Click to collapse
On one of the attempts that I did for installing, I installed the patch and it put me in a boot loop. Maybe not installing the patch can help you?

I cant get anything to work for the US version. Sure stuff boots but some of it is just broken. On octOS i am unable to use root unless i switch supersu to automatically grant root to apps. I cant get root access by using prompt because nothing pops up. On crdroid i have the same exact issue. Id rather have the prompt than allow any app root access without my knowledge. With ELITE ROM my first boot brings up a home screen with no keyboard. It completely skips any kind of setup screen. I can get the setup screen by flashing a keyboard from an aroma gapps installer but then i lose google services. The US version also seems to be forgotten as for most roms you wont see it anywhere under supported lists.

I've never been able to get a custom rom to work on my BLN-L24. Everything just ends in a never-ending bootloop of frustration.
Though, I have only ever tried with EMUI 5.0+. Maybe an earlier version of EMUI gets better results...?

code_name_duchess said:
I've never been able to get a custom rom to work on my BLN-L24. Everything just ends in a never-ending bootloop of frustration.
Though, I have only ever tried with EMUI 5.0+. Maybe an earlier version of EMUI gets better results...?
Click to expand...
Click to collapse
It really sucks that nothing seems to work. Ive tried flashing using multiple recoveries and ive tried all kinds of flashing to fix issues with the ROMS. Nothing helps. If anyone has successfully gotten a ROM fully working on BLN-L24 they need to tell people exactly what they did step by step.

It seems that for the roms located here, they seem to all assume that the phone has been debranded to bln-l21 variant. I don't know if it has any bearing on the current issues we're all experiencing, but I did notice that all twrps available for this device on the forums state they are the "Open Kirin Edition". It's been a while since I've rooted or rom'd a phone besides this one, but I've never encountered a twrp with a custom name like that.
I know that the developer of the EliteRom had his custom twrp, but is there a different twrp besides that one that does not state it is an "Open Kirin Edition"? Like I said, not sure if it has any bearing on things here, but I've been very confused about that.

TurtlePwr82 said:
It seems that for the roms located here, they seem to all assume that the phone has been debranded to bln-l21 variant. I don't know if it has any bearing on the current issues we're all experiencing, but I did notice that all twrps available for this device on the forums state they are the "Open Kirin Edition". It's been a while since I've rooted or rom'd a phone besides this one, but I've never encountered a twrp with a custom name like that.
I know that the developer of the EliteRom had his custom twrp, but is there a different twrp besides that one that does not state it is an "Open Kirin Edition"? Like I said, not sure if it has any bearing on things here, but I've been very confused about that.
Click to expand...
Click to collapse
For most phone i've ever owned you never had to change the recovery for each ROM. Its confusing. Most recoverys say Open Kirin Edition when booting. What confuses me is why we need to debrand to get the ROMS to work. If the phone pretty much run on the same hardware then why is L24 having so many issues? Why are the devs not testing on these devices?

BakedOnSomeSour said:
For most phone i've ever owned you never had to change the recovery for each ROM. Its confusing
Click to expand...
Click to collapse
Right, that's what I was thinking. For any phone I've ever rom'd, there was always just one twrp that everyone worked from.
Edit: found this while looking through the roll back to stock forum. I don't know if it will help anyone else, but figured I'd put it here as well if it might. All credit for this goes to the original poster johnnyrichter:
johnnyrichter said:
Tried this method after being on LineageOS for a week or two and having poor LTE signal, no MMS, and voicemail issues so I'm trying to go back to stock so I can have a fully functional phone since I rely on it heavily for work. Followed all steps using BLN-L24 B360 firmware. On step 10 I rebooted to update and it went right to "5% Installing Update" and stuck there for 5 mins, then rebooted itself, has been sitting at "honor" boot screen for 14 minutes so I made it reboot to EMUI recovery, wiped/factory reset, rebooted, loaded EMUI afte 2 more minutes. Appears to have worked and hopefully my issues are fixed!
Edit: Signal, mms, and voicemail issues fixed.
Click to expand...
Click to collapse
Hopefully will benefit someone here as well.

When debranding the BLN-L24, and branding it to BLN-L21, are there any issues with the ROMs once they're installed? I imagine the radios, and such are different for the two models??

BakedOnSomeSour said:
Why are the devs not testing on these devices?
Click to expand...
Click to collapse
Devs can only test devices they have in possession. If they don't have your phone model, how are they going to test it?

galapagos said:
Devs can only test devices they have in possession. If they don't have your phone model, how are they going to test it?
Click to expand...
Click to collapse
well, many don't want to give them a phone because most developers here tend to stop work on a ROM and leave people hanging.

I have gotten several ROMs working on L24 variant...
Yes it seems to me any Elite kernel based ROM works or should work on the L24. But /data must be ext4 format. Then even that the ROM works, the fingerprint scanner never allows a complete successful scan. I think because it must be f2fs format for that encryption to work or something. This is the link to those ROMS https://hassanmirza01.blogspot.com/p/custom-roms.html?m=1
On the other hand the LOS based ROMs never work or at least they reboot and the screen is always black or the ROM branding just stays there flashing. This sucks cause I want to run the newest Resurrection ROM but I ask the developer about why I have that problem or how long that ROM takes to boot and I never get an answer. He also just put a new beta AOKP ROM up and it does the same black screen thing too.
I am also suspicious it has to do with the version of TWRP. I think some are capable of formatting f2fs correctly or the encryption or whatever. Point is some of the devs need to be a little more consistent answering questions at a minimum. I know it takes time to fix bugs but give us a little heads up.

Flash both A/B slots on stock recovery

Sorry if the question sounds weird, it's probably because I don't fully understand this. I know that the OnePlus 6 has two software slots, an A slot and a B slot, and I also have a vague idea about what those slots are doing during an update.
Looking around, I found a thread that recommends flashing software on both slots, saying that it could fix some issues. I'm currently on Oreo, and I'm planning to get back to 9.0.4., but I remember that during 9.0.2. I think, when I was upgrading from Oreo again, I locally installed the same update file twice. I installed it once, everything went well, I went back to the local upgrade menu after the restart, and installed it again. And the phone seemed to be faster for some reason, that's what I'm trying to achieve again.
The thread that I found mentioned how to flash the software on both slots while on TWRP, would locally installing it twice achieve the same effect? Or is there something else that I can do?
Thank you very much in advance

TheMadKing said:
Sorry if the question sounds weird, it's probably because I don't fully understand this. I know that the OnePlus 6 has two software slots, an A slot and a B slot, and I also have a vague idea about what those slots are doing during an update.
Looking around, I found a thread that recommends flashing software on both slots, saying that it could fix some issues. I'm currently on Oreo, and I'm planning to get back to 9.0.4., but I remember that during 9.0.2. I think, when I was upgrading from Oreo again, I locally installed the same update file twice. I installed it once, everything went well, I went back to the local upgrade menu after the restart, and installed it again. And the phone seemed to be faster for some reason, that's what I'm trying to achieve again.
The thread that I found mentioned how to flash the software on both slots while on TWRP, would locally installing it twice achieve the same effect? Or is there something else that I can do?
Thank you very much in advance
Click to expand...
Click to collapse
Yupp. Same effect ??

whizeguy said:
Yupp. Same effect ??
Click to expand...
Click to collapse
Thank you!

Problems with my Xiaomi Redmi 8A

Hello people of XDA Forum,
Since a couple of years I own a Xiaomi Redmi 8A, which I ordered brand new on AliExpress.
After a couple of failed attempts to install a Custom Rom on the device, I still have an unlocked bootloader
and a "offical" stock firmware on the smartphone installed. Sadly now occurs an other problem,
frequently the screen "freezes" when I want to use the touchscreen. Sometimes when I put the power-button
and pressing it another time the screen responsed to it. But not always, it's getting very frustating when
for example I play "Call of Duty Mobile". My question is that I want to know of the problem is software-
or hardware based? Hopefully you can help me out, thnx

Have you modified anything in your device recently? No? Then it's probably hardware issue.
Do you have any damage to your phone? Then it's even more likely to be hardware issue.

XDHx86 said:
Have you modified anything in your device recently? No? Then it's probably hardware issue.
Do you have any damage to your phone? Then it's even more likely to be hardware issue.
Click to expand...
Click to collapse
Thanks for the reply. Now I have this problem for a couple of weeks sadly... There is no visible damage on the
device, but I have dropped the smartphone a couple of times out my hand... So I have this problem and I thought
that a firmware upgrade might help me out, but the problem still remains.

TrippyBlade said:
Thanks for the reply. Now I have this problem for a couple of weeks sadly... There is no visible damage on the
device, but I have dropped the smartphone a couple of times out my hand... So I have this problem and I thought
that a firmware upgrade might help me out, but the problem still remains.
Click to expand...
Click to collapse
If you think the damage to your phone is significant enough for it to affect your screen then maybe you should send it for a checkup.
Although you can try using different ROM to test if it works since it's probably much cheaper to do so than fixing the screen.
But don't flash an OTA update, flash latest stock ROM manually or flash a custom ROM. That way the settings are reset, you can backup your data with TWRP.

XDHx86 said:
If you think the damage to your phone is significant enough for it to affect your screen then maybe you should send it for a checkup.
Although you can try using different ROM to test if it works since it's probably much cheaper to do so than fixing the screen.
But don't flash an OTA update, flash latest stock ROM manually or flash a custom ROM. That way the settings are reset, you can backup your data with TWRP.
Click to expand...
Click to collapse
Allright, thank you very much for the suggestion. Finally I managed to flash an older Fastboot ROM through
the "MI Flash Tool", which solved my touchscreen problems.

Nord (India) stuck in crashdump

Gentlemens, I ask for your help because it's 30 hours that i'm fighting for this
Last morning I woke up and I looked at my Nord, and I saw it sluggishly slow, a bit like it has been in recent times and I was really tired of it, so I decided to clean the Nord by restoring everything in the most pristine way possible to try to make it more like it's Out-Of-The-Box, so i chose to downgrade with msm and luckily i had the wit to back up the persist.img
Making a summary, after I reset everything I reviewed how many bloatware there were in the Nord Indian version (I have that) and I wondered if you could put the global or eu rom on top of the ac2001
Reading on xda, reddit and oneplus I saw that many have done it and everything is semi all right, at most the 5g, the footprint or similar gave them a bit of problems, then I said to myself FINALLY I can get out of this Indian hell as an european (I have not a damn way to use amazon on the nord, because it does not accept that I am in Italy, so it refuses to connect, I breathed fire to make it work by removing the bloatware version, fighting with the router, adb, and the list goes on) and then I immediately threw myself into it
The global / eu version worked, but they crashdumped as soon as I updated them
I thought "Oh well" and I go back to edl and try to put the Indian back
Everything is fine with oos10, but as soon as I ******* go back to updating to oos11 it crashdumps, and i and go back to msm with edl to flash
I feel idiotic, oh well
fact that says something with sensor_process rc
device_restart_work_hdlr
and various other little things
Anyone have any idea how I could upgrade to oos11, global/eu (maybe god) or india?
Thank you in advance and forgive me for the papyrus: /
PS: relatively relevant detail, at more or less the second hour and a half at 12 o'clock in hell the pc while flashing went to bsod for unreleated issues (how lucky am i) and there it gave the first crashdump, but as soon as I reflashed in edl it it booted and then the continuous is over
I've flashed various combinations various versions and several times with edm today, so I don't really know what I can do anymore

crashdump is
err_qdi.c:1045:EF:sensor process:0x1:SNS_REG_INIT:0x9e:sns_registry
_sensor.c:94:SNS_RC_SUCCESS == rc
subsys_err_fatal_intr_handlersubsys-restart: Resetting the SoC - ad
sp crashed.
device_restart_work_hdlr

GiuseppeT03 said:
crashdump is
err_qdi.c:1045:EF:sensor process:0x1:SNS_REG_INIT:0x9e:sns_registry
_sensor.c:94:SNS_RC_SUCCESS == rc
subsys_err_fatal_intr_handlersubsys-restart: Resetting the SoC - ad
sp crashed.
device_restart_work_hdlr
Click to expand...
Click to collapse
The same issue for me bro. Did you solve it?

GiuseppeT03 said:
Gentlemens, I ask for your help because it's 30 hours that i'm fighting for this
Last morning I woke up and I looked at my Nord, and I saw it sluggishly slow, a bit like it has been in recent times and I was really tired of it, so I decided to clean the Nord by restoring everything in the most pristine way possible to try to make it more like it's Out-Of-The-Box, so i chose to downgrade with msm and luckily i had the wit to back up the persist.img
Making a summary, after I reset everything I reviewed how many bloatware there were in the Nord Indian version (I have that) and I wondered if you could put the global or eu rom on top of the ac2001
Reading on xda, reddit and oneplus I saw that many have done it and everything is semi all right, at most the 5g, the footprint or similar gave them a bit of problems, then I said to myself FINALLY I can get out of this Indian hell as an european (I have not a damn way to use amazon on the nord, because it does not accept that I am in Italy, so it refuses to connect, I breathed fire to make it work by removing the bloatware version, fighting with the router, adb, and the list goes on) and then I immediately threw myself into it
The global / eu version worked, but they crashdumped as soon as I updated them
I thought "Oh well" and I go back to edl and try to put the Indian back
Everything is fine with oos10, but as soon as I ******* go back to updating to oos11 it crashdumps, and i and go back to msm with edl to flash
I feel idiotic, oh well
fact that says something with sensor_process rc
device_restart_work_hdlr
and various other little things
Anyone have any idea how I could upgrade to oos11, global/eu (maybe god) or india?
Thank you in advance and forgive me for the papyrus: /
PS: relatively relevant detail, at more or less the second hour and a half at 12 o'clock in hell the pc while flashing went to bsod for unreleated issues (how lucky am i) and there it gave the first crashdump, but as soon as I reflashed in edl it it booted and then the continuous is over
I've flashed various combinations various versions and several times with edm today, so I don't really know what I can do anymore
Click to expand...
Click to collapse
Bro, please help me. How did you solve the issue?

ajaygrylls said:
Bro, please help me. How did you solve the issue?
Click to expand...
Click to collapse
Hello, I was wondering, do you have the solution to the problem ?

Question Occasionally crash to "waiting to flash full ramdump"

Hi, sorry if this question was asked before by another user but my phone occasionally crashes to the waiting to flash full ramdump (or something of that sort) out of nowhere. After crashing, I could just force shut down the device using the volume keys and boot up normally again.
This only happens once or twice a week - my phone is unlocked and is sporting the latest kirasakura kernel.
Do you guys have any ideas on how to fix it?
Thanks in advance

Hello, I had same issue, it is caused by custom kernel, on .176 firmware both kernels listed on XDA are quite unstable. Just restore stock kernel by using payload dumper on firmware file and flashing boot.img, dtbo.img and vendor_boot.img using fastboot.
To keep root, patch boot.img with magisk before flashing.

vinotux said:
Hi, sorry if this question was asked before by another user but my phone occasionally crashes to the waiting to flash full ramdump (or something of that sort) out of nowhere. After crashing, I could just force shut down the device using the volume keys and boot up normally again.
This only happens once or twice a week - my phone is unlocked and is sporting the latest kirasakura kernel.
Do you guys have any ideas on how to fix it?
Thanks in advance
Click to expand...
Click to collapse
Did you flash the DLKM module?

MarekPietrzak said:
Hello, I had same issue, it is caused by custom kernel, on .176 firmware both kernels listed on XDA are quite unstable. Just restore stock kernel by using payload dumper on firmware file and flashing boot.img, dtbo.img and vendor_boot.img using fastboot.
To keep root, patch boot.img with magisk before flashing.
Click to expand...
Click to collapse
You probably shouldn't be starting rumors like that, especially without any legitimate proof. The reports are few and far between, but also addressed promptly. Neither of the kernels is "quite unstable" and the issue has happened on stock.

twistedumbrella said:
You probably shouldn't be starting rumors like that, especially without any legitimate proof. The reports are few and far between, but also addressed promptly. Neither of the kernels is "quite unstable" and the issue has happened on stock.
Click to expand...
Click to collapse
I don't intend to insult anyone, I just shared my personal experience, on previous firmware version both kernels worked fine and stable, but on .176 I had constant crashes with "waiting for flashing full ramdump" message. When I restored stock kernel, this issue no longer persisted. I will for sure try again custom kernel, but in two weeks or longer, as ROG phone 5 is my primary device and I need to stay in contact. I will try to reproduce this issue and grab logs. Now I can share my observation, that those crashes occurred when device was idle, and usually on charger.

JazonX said:
Did you flash the DLKM module?
Click to expand...
Click to collapse
Thanks for your response, do I need to? I flashed using FKM and not TWRP

vinotux said:
Thanks for your response, do I need to? I flashed using FKM and not TWRP
Click to expand...
Click to collapse
You honestly shouldn't need it at all anymore. I believe AnyKernel took the lead and fixed the issue, but it was only TWRP that needed it.
MarekPietrzak said:
I don't intend to insult anyone, I just shared my personal experience, on previous firmware version both kernels worked fine and stable, but on .176 I had constant crashes with "waiting for flashing full ramdump" message.
Click to expand...
Click to collapse
No worries. I was only making sure it was clear this was a recent issue and not an ongoing problem. Kirisakura spans a lot of devices and got the reports much later, so a slight delay in the fix should be expected.

twistedumbrella said:
You honestly shouldn't need it at all anymore. I believe AnyKernel took the lead and fixed the issue, but it was only TWRP that needed it.
No worries. I was only making sure it was clear this was a recent issue and not an ongoing problem. Kirisakura spans a lot of devices and got the reports much later, so a slight delay in the fix should be expected.
Click to expand...
Click to collapse
Great, I'll just reevaluate when the new update rolls out, thank you .

vinotux said:
Great, I'll just reevaluate when the new update rolls out, thank you .
Click to expand...
Click to collapse
Make sure to perform a backup of anything important, even if you are staying with stock. It appears the issue may go beyond something as simple as installing a custom kernel, assuming the issues reported on both are related.
Finding the common denominator, as they say, might find the root cause, but that is a pretty big task. It would also require more than one report and I only have the one.

twistedumbrella said:
Make sure to perform a backup of anything important, even if you are staying with stock. It appears the issue may go beyond something as simple as installing a custom kernel, assuming the issues reported on both are related.
Finding the common denominator, as they say, might find the root cause, but that is a pretty big task. It would also require more than one report and I only have the one.
Click to expand...
Click to collapse
Actually I flashed your kernel and it's been smooth sailing since then. I'm a little too busy to diagnose the root cause of the problem .

vinotux said:
Actually I flashed your kernel and it's been smooth sailing since then. I'm a little too busy to diagnose the root cause of the problem .
Click to expand...
Click to collapse
Fair enough. It shouldn't be on you to do it anyway. With any luck, i'll have debugging sorted out before the end of the weekend with proper instructions to avoid all the guesswork.
Asus Proprietary Logs
In trying to debug kernels, I realized that Asus has rerouted the location of some of the more important logs to make them "easily" accessible. Disclaimer: This is not a complete list of every file included, but lists the more "useful"...
forum.xda-developers.com

An error happens, the kernel logs the issue, the device reboots. This is how things are supposed to work. When disabling debugging, an error happens and the device reboots. The logging step is skipped, but life continues.
The problem is when debugging is partially disabled, but still attempting to write. This is basically why there is a "waiting for ramdump" message. It is waiting for the logging to complete to proceed to the next step.
Asus Power Debug: guard debugging so it can be disabled · freak07/[email protected]
Contribute to freak07/Kirisakura_ANAKIN_ROG5 development by creating an account on GitHub.
github.com
This commit set the stage for a future break, which happened in the .176 update when printk_buffer_rebase replaced get_last_shutdown_log.

Hi, just a quick update.
I had been experiencing major issues and the waiting to flash full ramdump debacle had gotten extremely frightening. The phone wouldn't recognize the IMEI of the device, wifi wouldn't work, etc. The error happened multiple times a day. I took it to ASUS and they basically told me to f off due to my phone being unlocked.
As a last resort, I flashed the .151 RAW firmware and I swear all of the problems vanished. If I was a betting man, I'd say that the .176 update caused all of the problems since I've used the device for a week now without any problems thus far.
Major thanks to @twistedumbrella and others for replying to this thread.

I don't doubt you are right about that. 188 improves things a bit, but they definitely broke something significant in 176. I have never crashed as much as on that build.