Develop Bugs

Zenfone 2 roms & what should I go for?

Hello so I am still loving every bit of my zenfone 2 and all but the rom I am using is no longer being updated as the OP no longer has the device I was wondering what the users here suggest I like blisspop rom but I don't like that the camera just looks bad in stock gaps app and the zenfone 2 app by asus looks so good in comparison I know there is a sorta ported camera app for cyanogen based roms and all but every time I use that it seems to crash the app for some reason.
Thanks for the help also is there still a app compatibility issue on the cyanogen zenfone 2? Sorry again just returning after about 7 months with the same rom on my phone.
Currently on: Prism Barebone V12.5
Zenfone 2 4G version

I highly recommend Echoe Zen Rom. It's currently the best out there for me.

mastermarkofroms said:
Hello so I am still loving every bit of my zenfone 2 and all but the rom I am using is no longer being updated as the OP no longer has the device I was wondering what the users here suggest I like blisspop rom but I don't like that the camera just looks bad in stock gaps app and the zenfone 2 app by asus looks so good in comparison I know there is a sorta ported camera app for cyanogen based roms and all but every time I use that it seems to crash the app for some reason.
Thanks for the help also is there still a app compatibility issue on the cyanogen zenfone 2? Sorry again just returning after about 7 months with the same rom on my phone.
Currently on: Prism Barebone V12.5
Zenfone 2 4G version
Click to expand...
Click to collapse
Back up everything and move to either Stock CM 13 or CM 12.1, I prefer CM 13 as it is performing much better than CM 12.1. Yeah I agree Google Camera/ CM camera are not as good as Asus Camera or at least doesn't have too many options, but hey there is always play store where you can download other 3rd party camera apps. If you can cope with that, I think CM 13 is the best option.

Sayan44 said:
Back up everything and move to either Stock CM 13 or CM 12.1, I prefer CM 13 as it is performing much better than CM 12.1. Yeah I agree Google Camera/ CM camera are not as good as Asus Camera or at least doesn't have too many options, but hey there is always play store where you can download other 3rd party camera apps. If you can cope with that, I think CM 13 is the best option.
Click to expand...
Click to collapse
I have decided on blisspop 6.1 PS any ideas for camera? I find for some reason the google camera app has way to much static compared to stock asus camera app.

Why don't you stick with Barebone v 12.5 until official MM arrives? Do you experience any issues/bugs?
I am currently on V12.5 with xposed + amplify, removed few more apps and with BORETS24's kernel. The device runs smooth and I get around 5hrs SOT (battery lasting 2 full days). And I have everything enabled (data, wifi, location..).
I tried Echoe's rom but it just has too much bloatware for me. I installed it, wasted 2 hours setting it up and deleting useless stuff only to realise that it is not as responsive as Prism's Barebone v12.5. So I'm sticking with v12.5 even though it wont be updated anymore.
If it aint broke, don't fix it!

pecholino said:
Why don't you stick with Barebone v 12.5 until official MM arrives? Do you experience any issues/bugs?
I am currently on V12.5 with xposed + amplify, removed few more apps and with BORETS24's kernel. The device runs smooth and I get around 5hrs SOT (battery lasting 2 full days). And I have everything enabled (data, wifi, location..).
I tried Echoe's rom but it just has too much bloatware for me. I installed it, wasted 2 hours setting it up and deleting useless stuff only to realise that it is not as responsive as Prism's Barebone v12.5. So I'm sticking with v12.5 even though it wont be updated anymore.
If it aint broke, don't fix it!
Click to expand...
Click to collapse
I switched because well as much as I love a stock asus based rom my issue is I want more themeing options and Asus just dont have and I don't think will offer 3rd party again besides I do love some of the AOSP roms out there like blisspop but I am now expirenceing an issue with my phone This is before I even opted to install blisspop as I have not done it yet for some reason I am able to access TWRP through adb reboot recovery on windows but I can't access my bootloader using the power and volume down or adb reboot bootloader and I am not sure why at the moment. I like my phone like I like my linux pc with themeing options
Edit: Flashing blisspop 6.0.1 did not fix my bootloader issue and I also tried flashing the boot.img manually

mastermarkofroms said:
I switched because well as much as I love a stock asus based rom my issue is I want more themeing options and Asus just dont have and I don't think will offer 3rd party again besides I do love some of the AOSP roms out there like blisspop but I am now expirenceing an issue with my phone This is before I even opted to install blisspop as I have not done it yet for some reason I am able to access TWRP through adb reboot recovery on windows but I can't access my bootloader using the power and volume down or adb reboot bootloader and I am not sure why at the moment. I like my phone like I like my linux pc with themeing options
Edit: Flashing blisspop 6.0.1 did not fix my bootloader issue and I also tried flashing the boot.img manually
Click to expand...
Click to collapse
i guess you mean, that power + VOL-UP didn't work right? if you were pressing VOL-DOWN, try VOL-UP

pecholino said:
i guess you mean, that power + VOL-UP didn't work right? if you were pressing VOL-DOWN, try VOL-UP
Click to expand...
Click to collapse
Yeah sorry I meant up and it still dont work I can only access recovery but through adb if I try and load the bootloader the asus logo just sits there and after like a minute the phone reboots and sists on asus logo again if I turn off device manually and turn it on normal the phone turns on so I am not 100% sure what is going on its really weird

Black screen in TWRP after screen replacement

Hello to all,i have Redmi Note 5 Pro(whyred).I broke my screen and ordered new from Aliexpress.I arrived yesterday and i succesfully replaced it.Everything is working perfect except TWRP.I had installed RedWolf recovery and Masik 2.2 and i wanted to update it to 2.4.But when i restarted phone into recovery mode,screen was black(blank) and computer recognized it as mtp.My screen is huaxing nt36672 fhd video mode dsi panel.Is there any TWPR that supports this panel?

Me too!

Me too!

Me too!
---------- Post added at 04:53 AM ---------- Previous post was at 04:51 AM ----------
filipo96 said:
Hello to all,i have Redmi Note 5 Pro(whyred).I broke my screen and ordered new from Aliexpress.I arrived yesterday and i succesfully replaced it.Everything is working perfect except TWRP.I had installed RedWolf recovery and Masik 2.2 and i wanted to update it to 2.4.But when i restarted phone into recovery mode,screen was black(blank) and computer recognized it as mtp.My screen is huaxing nt36672 fhd video mode dsi panel.Is there any TWPR that supports this panel?
Click to expand...
Click to collapse
Me too

resolved
filipo96 said:
Hello to all,i have Redmi Note 5 Pro(whyred).I broke my screen and ordered new from Aliexpress.I arrived yesterday and i succesfully replaced it.Everything is working perfect except TWRP.I had installed RedWolf recovery and Masik 2.2 and i wanted to update it to 2.4.But when i restarted phone into recovery mode,screen was black(blank) and computer recognized it as mtp.My screen is huaxing nt36672 fhd video mode dsi panel.Is there any TWPR that supports this panel?
Click to expand...
Click to collapse
Twrp for multirom is good!

I have flashed it,but every custom non-Miui gives me black screen(Masik works fine).I can hear lock-unlock sounds,but everything else is black.Do you know any aosp-los based rom that works on this screen?

It is twrp multirom. You can flash any aosp/Los based in second partition

Yes,but it shows miui logo when booting starts and from there only black screen.I think that some drivers are missing in aosp/los based kernel from miui.And when developers port that drivers we will be able to use non-stock roms.

Did someone found solution for this problem??

same problem here

filipo96 said:
Did someone found solution for this problem??
Click to expand...
Click to collapse
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1314
They need to update vendor blobs in recovery, so they can recognise the new screens.

htchd2sucks said:
They need to update vendor blobs in recovery, so they can recognise the new screens.
Click to expand...
Click to collapse
Or they can try OrangeFox recovery for whyred.

DarthJabba9 said:
Or they can try OrangeFox recovery for whyred.
Click to expand...
Click to collapse
Which is based on...TWRP, so in theory it should get the same issue (unless they updated some components inside twrp).
Edit: @DarthJabba9 Oh I just notice you're the one doing the OrangeFOX recovery page on XDA.
It looks great!
Can you comment then on why they should use OrangeFox recovery instead of TWRP? Have you updated some "blobs" (im referring to the bug report on github saying that's why the users have black screen)? Just a quick explanation (unless it's a try-and-see).

htchd2sucks said:
Which is based on...TWRP, so in theory it should get the same issue (unless they updated some components inside twrp).
Edit: @DarthJabba9 Oh I just notice you're the one doing the OrangeFOX recovery page on XDA.
It looks great!
Can you comment then on why they should use OrangeFox recovery instead of TWRP? Have you updated some "blobs" (im referring to the bug report on github saying that's why the users have black screen)? Just a quick explanation (unless it's a try-and-see).
Click to expand...
Click to collapse
OrangeFox has no black screen issue, and has never had it, period. I cannot comment on why official TWRP has this problem (kernel? device tree? build system?).
As far as features are concerned, a list of extra features can be seen here: https://forum.xda-developers.com/re...ment/twrp-orangefox-recovery-project-t3837547

relax guys
official twrp maintainer is already working on issue and it will be ready soon in 2-3 days (probably)
and orangefox devs just started working on issue

DarthJabba9 said:
OrangeFox has no black screen issue, and has never had it, period. I cannot comment on why official TWRP has this problem (kernel? device tree? build system?).
As far as features are concerned, a list of extra features can be seen here: https://forum.xda-developers.com/re...ment/twrp-orangefox-recovery-project-t3837547
Click to expand...
Click to collapse
Yes, it's possible several things:
1) OrangeFOX did not had this issue because no one reported it yet
2) OrangeFox users did not have the new or different screen manufacturer
3) OrangeFox uses updated "Blobs" or whatever technical which would justify that the issue is not impacting (maybe root cause is unrelated).
That's the thing, it seems to be a few users who got a new HW, some it's because the screen had been broken and replaced. Others, maybe it's new versions of the device?
Yes, it's true, it's very simple, the user could simply flash OrangeFox and try. We read it was based on TWRP so I thought it was not going to change the missing "blobs" (unless twrp was modified in orangefox).
Anyway, we could also try for the TWRP person to comment on the bug and update, it's just everything long usually around here (I don't even have the black screen issue, I just want to know what was root cause).

htchd2sucks said:
Yes, it's possible several things:
1) OrangeFOX did not had this issue because no one reported it yet
2) OrangeFox users did not have the new or different screen manufacturer...
Click to expand...
Click to collapse
Both of these. It is a kernel driver issue. All that one needs is an updated kernel. I am sure that Ankit will release a fix soon. I will certainly be releasing one for OrangeFox.

DarthJabba9 said:
Both of these. It is a kernel driver issue. All that one needs is an updated kernel. I am sure that Ankit will release a fix soon. I will certainly be releasing one for OrangeFox.
Click to expand...
Click to collapse
Thanks for the information!
Just for my understanding, the kernel can come with the ROM, right? Because I have flashed the latest "PE" rom and it comes with some version of DERP kernerl 3.4 xyz.
So how come that would be impacting at recovery level?
I mean, if you flash the rom the first time, it should then update kernel... So how come that user got a black screen at that stage?
Unless there's something else at recovery level...I just don't see how come it can work and then not work with the same kernel (I assume his device worked in MIUI before custom rom)...

htchd2sucks said:
I mean, if you flash the rom the first time, it should then update kernel... So how come that user got a black screen at that stage?
Click to expand...
Click to collapse
Hey
Do you also have phone with huaxing screen panel ?
I've spoke to orange fox recovery dev and he said that there is barely any rom works with this screen, coz karnel sources isn't released by xiaomi yet. Pixel experience rom dev confirmed that.
Ankit said that any rom with GSI may probably work, but i doubt that
How can i test or prove it without actually getting "soft bricks" or without risk test roms with arb4 phone ?

htchd2sucks said:
Thanks for the information!
Just for my understanding, the kernel can come with the ROM, right? Because I have flashed the latest "PE" rom and it comes with some version of DERP kernerl 3.4 xyz.
So how come that would be impacting at recovery level?
I mean, if you flash the rom the first time, it should then update kernel... So how come that user got a black screen at that stage?
Unless there's something else at recovery level...I just don't see how come it can work and then not work with the same kernel (I assume his device worked in MIUI before custom rom)...
Click to expand...
Click to collapse
I think this is getting OT. LEt's just say that recoveries have their own kernel, and ROMs have their own kernel. Both do not mix. It can be easier to get a kernel working with a recovery than with a ROM, because a recovery is a self-contained OS in its own right.

Screen blacking out after custom rom installation on twrp

I recently unlocked my note 5 pro bootloader and flashed twrp. When i tried to install custom rom, the rom installs and every thing is fine until you reboot to system. The phone reebots and shows mi logo and then blacks out. It never turns off or do anything. I could hear the sound of phone locking and unlocking. I could even take screenshots, i can hear the sound and it even shows up when you connect the phone to computer. But nothing ever shows on screen.
Twrp versions: Tried all latest twrp as well as orange and redwolf recoveries.
Rom used: Pixel experience Pie
Hope someone have a fix for this issue.
Advanced thanks as well..

dennisthomas706 said:
I recently unlocked my note 5 pro bootloader and flashed twrp. When i tried to install custom rom, the rom installs and every thing is fine until you reboot to system. The phone reebots and shows mi logo and then blacks out. It never turns off or do anything. I could hear the sound of phone locking and unlocking. I could even take screenshots, i can hear the sound and it even shows up when you connect the phone to computer. But nothing ever shows on screen.
Twrp versions: Tried all latest twrp as well as orange and redwolf recoveries.
Rom used: Pixel experience Pie
Hope someone have a fix for this issue.
Advanced thanks as well..
Click to expand...
Click to collapse
I think u have huaxing display panel
Custom roms is not supported in huaxing displays as of now

rahulrulz said:
I think u have huaxing display panel
Custom roms is not supported in huaxing displays as of now
Click to expand...
Click to collapse
Is there a solution? And what is huaxing display panel?

dennisthomas706 said:
I recently unlocked my note 5 pro bootloader and flashed twrp. When i tried to install custom rom, the rom installs and every thing is fine until you reboot to system. The phone reebots and shows mi logo and then blacks out. It never turns off or do anything. I could hear the sound of phone locking and unlocking. I could even take screenshots, i can hear the sound and it even shows up when you connect the phone to computer. But nothing ever shows on screen.
Twrp versions: Tried all latest twrp as well as orange and redwolf recoveries.
Rom used: Pixel experience Pie
Hope someone have a fix for this issue.
Advanced thanks as well..
Click to expand...
Click to collapse
ORANGE FOX RECOVERY 8.3 , try using that !
1. try installing LOS , and see
2. if you flash miui back! is everything ok?

YasuHamed said:
ORANGE FOX RECOVERY 8.3 , try using that !
1. try installing LOS , and see
2. if you flash miui back! is everything ok?
Click to expand...
Click to collapse
I haven't tried LOS, But flashing miui makes everything back to normal.

dennisthomas706 said:
Is there a solution? And what is huaxing display panel?
Click to expand...
Click to collapse
Huaxing display panel is the new display panel used in note 5 pro
The current kernel sources doesn't work for huaxing panel

rahulrulz said:
Huaxing display panel is the new display panel used in note 5 pro
The current kernel sources doesn't work for huaxing panel
Click to expand...
Click to collapse
Someone might be working on it right? Official twrp?

dennisthomas706 said:
I haven't tried LOS, But flashing miui makes everything back to normal.
Click to expand...
Click to collapse
if you stay on miui 10 and change some other kernel! what happens?

YasuHamed said:
if you stay on miui 10 and change some other kernel! what happens?
Click to expand...
Click to collapse
Haven't tried that. But can you just swap kernels in miui just like other custom roms?

dennisthomas706 said:
Haven't tried that. But can you just swap kernels in miui just like other custom roms?
Click to expand...
Click to collapse
yes, customer kernels that supports miui , you can
try NONAME kernel
try Agni 3.2 with MIUI Support

In huaxing panel no custom kernel is supported
One dev is working for huaxing panel and he has made a kernel based on stock kernel and wifi fix module to use with custom roms

rahulrulz said:
In huaxing panel no custom kernel is supported
One dev is working for huaxing panel and he has made a kernel based on stock kernel and wifi fix module to use with custom roms
Click to expand...
Click to collapse
Can you please provide a link to this kernel and the wifi fix module? Thank you!

rahulrulz said:
In huaxing panel no custom kernel is supported
One dev is working for huaxing panel and he has made a kernel based on stock kernel and wifi fix module to use with custom roms
Click to expand...
Click to collapse
When to solve this problem Will it be integrated into all custom roms and kernels

Willow device - wake up display broken on AOSP images

Is there please someone who can help me?
I have an unlocked willow device.
But when I install any custom rom (AOSP like - Android 12 or 13) the display will not light on first power button press after going to deep sleep or display lock. It will take several button pressing, until the display will come alive/wake up.
Sometimes it seems, that the display is unlocked, but is at lowest brightness level. The hardware is okay. I changed the power button pcb already.
The latest MIUI firmware rom (from xiaomifirmwareupdater.com) runs without bug. Its a A11 image.
Is this a bug maybe in the vendor file? Is there any other solution than staying on stock rom MIUI A11?
Thx for your feedback in advance!

kerberos666 said:
Is there please someone who can help me?
I have an unlocked willow device.
But when I install any custom rom (AOSP like - Android 12 or 13) the display will not light on first power button press after going to deep sleep or display lock. It will take several button pressing, until the display will come alive/wake up.
Sometimes it seems, that the display is unlocked, but is at lowest brightness level. The hardware is okay. I changed the power button pcb already.
The latest MIUI firmware rom (from xiaomifirmwareupdater.com) runs without bug. Its a A11 image.
Is this a bug maybe in the vendor file? Is there any other solution than staying on stock rom MIUI A11?
Thx for your feedback in advance!
Click to expand...
Click to collapse
if it's not a hardware issue it's the firmware or you did a dirty flash ?

No dirty flash. Always clean install. I think that there could be a major bug in all custom images for Willow devices. I tested several custom rom. None worked correctly.
Is there noone else with a Willow and the same problem?
And is it the vendor Image part i should flash over custom rom's vendor part? Then the custom Image does not boot anymore...
Any help is appreciated. Thx!

This evening I mixed up dtbo, modem, efs partitions from MIUI official A11 rom with a current A13 custom rom. Now the display works as expected.
Maybe I messed something up myself some months ago. Now i have a backup of a working system. That is good!
Gonna try flashing some custom A13 rom(s) again and test If it will break the "display wake up" again.

Question Poco F3 and weird behaviour on A13

When I flash a custom A13 ROM, the adaptive brightness on my Poco F3 stays on 13% (only adjusts when I move the slider but then goes down later), and fingerprint sensor does not appear under the Security settings.
I have flashed full MIUI ROM both 14.0.7 and 14.0.4 and afterwards, followed the respective flashing instructions of each ROM (BananaDroid, GhostDroid, AlphaDroid, Evo-X) but each time these 2 issues occur.
On A12 custom ROM, I was not having these problems.
I hope someone can shed some light on what I can do to alleviate this.
FYI, I live in Canada and bought the phone on Ali Express which has Russian print on the box. I don't know if this makes a difference or not with the MIUI stock ROM I should flash.
Thanks for any help.

maybe install latest MIUI through fastboot and then try a13 custom ROMs?

Kusay_1 said:
maybe install latest MIUI through fastboot and then try a13 custom ROMs?
Click to expand...
Click to collapse
I tried that multiple times plus install using recovery MIUI ROM but same result.

nickelnine said:
I tried that multiple times plus install using recovery MIUI ROM but same result.
Click to expand...
Click to collapse
I heard about firmware causing trouble with fingerprint scanners, but not removing the option all together, perhaps try multiple firmwares and see if this fixes it?
About auto brightness, do you have anything covering your screen? Maybe that could be the problem
Is miui working well?
Surely if miui on a13 works, then this should be a custom Rom thing

Nothing covering the screen but I reflashed from scratch and now auto brightness works better but still not how it used to be on A12 but it's fine for now. Fingerprint scanner still not available although when I went back to MIUI 14.0.4 and 14.0.7 it was missing from there too so I'm not sure what the problem is. I do have face unlock though.