Related
Hello all
Official CM 12.1 nightlies based on Android Lollipop 5.1.1 for Find 7A/S have been officially released effective 22nd April 2015. Its time to thank the entire CyanogenMod Team and @[U]jajb[/U] for their efforts in the development and encourage them to keep supporting us the same way in the future.
Let the flashing go on!!!!:highfive:
Nightly Downloads
CM12.1 Find 7A
http://download.cyanogenmod.org/?device=find7
CM12.1 Find 7S (QHD)
http://download.cyanogenmod.org/?device=find7s
5.1 Minimal Gapps (for a light and blazzing fast experience):highfive:
https://www.androidfilehost.com/?fid=95916177934550851
Installation Instructions
Coming from 5.0 or less ROMS
Download cm-12.1-xxxxxxxx-NIGHTLY-find7x.zip to your sdcard
Boot into Recovery
Wipe data, cache & dalvik cache
Flash cm-12.1-xxxxxxxx-NIGHTLY-find7x.zip from sdcard
Flash 5.1 Minimal GApps.zip from sdcard
Reboot:highfive:
Coming from previous CM 12.1 build
Wipe cache & dalvik cache
Flash cm-12.1-xxxxxxxx-NIGHTLY-find7x.zip from sdcard
Reboot:highfive:
Somebody successfully flashed it ? It works ?
raber111 said:
Somebody successfully flashed it ? It works ?
Click to expand...
Click to collapse
It doesn't work. http://forum.xda-developers.com/showpost.php?p=58255547&postcount=397
I tried to flash the last CM11 build and I'm still stucked there.
Anyone tried 20150119 build yet? is it working??
CyanPile said:
Anyone tried 20150119 build yet? is it working??
Click to expand...
Click to collapse
It seems so, but wifi is terribly slow.
It's going to be announced soon in CM's blog, but find7a and find7s are split now and get separate builds. You need to flash "find7" on find7a devices and "find7s" on find7s qhd devices. You should update the recovery too, but I think there are no recovery images available yet. I might provide some if nobody else does it.
I successfully flashed cm 12 1901 build . WiFi works normally. Fonts and icons too small
on 2.0.4
Can we flash this on color os 2.0.4 version without any issues or have to downgrade to 1.2.7
sheraz1015 said:
Can we flash this on color os 2.0.4 version without any issues or have to downgrade to 1.2.7
Click to expand...
Click to collapse
You will have to flash it over 1.2.x Color OS. I flashed 19 build over 1.2.7.
Installed without an issue.
For QHD use Find 7s version.
mikeioannina said:
It's going to be announced soon in CM's blog, but find7a and find7s are split now and get separate builds. You need to flash "find7" on find7a devices and "find7s" on find7s qhd devices. You should update the recovery too, but I think there are no recovery images available yet. I might provide some if nobody else does it.
Click to expand...
Click to collapse
Thank for your
help and shall flash it.
Its there any way to backup imei of oppo find 7
ganeshbiyer said:
You will have to flash it over 1.2.x Color OS. I flashed 19 build over 1.2.7.
Installed without an issue.
For QHD use Find 7s version.
Click to expand...
Click to collapse
Sent from my LG-D802 using XDA Premium 4 mobile app
You can always use tantrums recovery flasher...they recently updated to v10.....has all the latest recoveries
Anyone having problems when using unified partition layout? After I flashed the ROM the phone just tells me that there's an encryption error and I have to wipe data. I wiped data and still the same error. When I went back to previous ROM I'm using everything else is fine, except with the proximity sensor bug. Cheers
darthbadar said:
Anyone having problems when using unified partition layout? After I flashed the ROM the phone just tells me that there's an encryption error and I have to wipe data. I wiped data and still the same error. When I went back to previous ROM I'm using everything else is fine, except with the proximity sensor bug. Cheers
Click to expand...
Click to collapse
De-unify first, then flash. You need to have to revert back to 1.2.x.
Flash Open TWRP and then flash CM12 Nightlies. COs 1.2.x and CM12 do not support Unification.
ganeshbiyer said:
De-unify first, then flash. You need to have to revert back to 1.2.x.
Flash Open TWRP and then flash CM12 Nightlies. COs 1.2.x and CM12 do not support Unification.
Click to expand...
Click to collapse
Soo, there's no way I'm using CM12 Nightlies with unified storage? Thanks for answering man. :highfive:
Changelog ?
changelog here http://www.cmxlog.com/12/find7/
and here http://www.cmxlog.com/12/find7s/
Chrome
Is the only way to switch between tabs the recent apps thingy? I mean I don't habe a problem but still kinda awkward not knowing where the tab went. BTW I got twrp 2.8.4 and there's always this horizontal line where the display shifts. It's like these lines on old videos that walk through the picture. Trying my best on English (I'm German )
alex1.salge said:
Is the only way to switch between tabs the recent apps thingy? I mean I don't habe a problem but still kinda awkward not knowing where the tab went. BTW I got twrp 2.8.4 and there's always this horizontal line where the display shifts. It's like these lines on old videos that walk through the picture. Trying my best on English (I'm German )
Click to expand...
Click to collapse
Regarding the line in recovery, use Nameless TWRP recovery from HERE.
I have not tried the latest TWRP Open Recovery 2.8.4 for Find7, but with Nameless TWRP Recovery, I am able to use OTG in recovery. This allows me to take backups into 32gb usb drive and restore from there.
Custom Ringtones
Hello Just flashed to build 2015/01/21 and I noticed that I was unable to change my ringtone. This may seem like a trivial thing but I would just like to know if it's my device specific. Find 7a running CM12 stock kernels and all.
Edit: Turned off NuPlayer in developers options and set SELinux Kernel to Permissive.
Enyioha said:
Hello Just flashed to build 2015/01/21 and I noticed that I was unable to change my ringtone. This may seem like a trivial thing but I would just like to know if it's my device specific. Find 7a running CM12 stock kernels and all.
Edit: Turned off NuPlayer in developers options and set SELinux Kernel to Permissive.
Click to expand...
Click to collapse
sorry for noob question
how can I change SELinux Kernel to Permissive ?
Missing languages
In the 21/01 build, some languages are missing - texts simply do not appear and the language list is empty near the end.
EDIT:
23/01 build solves it.
EDIT2:
Gyro doesn't work, screen doesn't rotate.
screen flickering or glitches on custom Roms like OMNI,PIXEL, Resurrection remix etc have same issue.... any solution?
A logcat sent to the ROM dev might be an idea.
Kaleem_qadir said:
screen flickering or glitches on custom Roms like OMNI,PIXEL, Resurrection remix etc have same issue.... any solution?
Click to expand...
Click to collapse
Wrong firmware
XDRdaniel said:
Wrong firmware
Click to expand...
Click to collapse
thanks for reply
i have oneplus 3 (A3003) .... which rom you suggest?
Kaleem_qadir said:
thanks for reply
i have oneplus 3 (A3003) .... which rom you suggest?
Click to expand...
Click to collapse
You can have any ROM so long as you have the matching firmware. Check in the ROM's thread.
tnsmani said:
You can have any ROM so long as you have the matching firmware. Check in the ROM's thread.
Click to expand...
Click to collapse
flashed 3/3T lineage and AOSP Roms. any difference between and 3T roms?
Kaleem_qadir said:
flashed 3/3T lineage and AOSP Roms. any difference between and 3T roms?
Click to expand...
Click to collapse
Unless it says Unified or 3/3T, they are different and flashing the wrong one can brick your phone.
Still not solving
I am still having issues. My nav bar gets a mirror effect on the uperside of the screen
I have a Oneplus A3000
Hello i have the same issue have you got any solution ?
I replaced my crack screen last month and last night I tried flashing AOSIP rom (From latest Open Beta) and got screen flickering and glitches to the point it was unusable. Wiped my phone clean again and tried RR rom and got the same flickering and glitches. Now I'm back to latest Open Beta. I wonder wether my new screen is the problem that caused me unbale to flash aosp roms? Because before my screen cracked I tried almost every rom and it's fine. Any idea guys?
I have the same problem, and I do too had my screen replaced, but some folks on OnePlus forum said that never replaced the screen
I tried many diferent versions of the firmware, and nice looking none fix for me
I have the same problem too, I've tried many kernels and many ROMs, it seems that only Sultanxda's ROM and Official ROM can be used. I've tried to compile MoKee with Sultanxda's Kernel source, it worked perfectly too. So I think that there maybe something kernel related is broken, and only Sultanxda fixed that. Maybe you could try it.
Thanks for reply . Los 14.1 and miui 9 are also ok
I've the same issue, and I think for the same cause because I replaced my cracked screen also, maybe OnePlus 3 have something like knox on samsgung where it'll be broken when rooted, Waiting to see if there's some kind of a solution because if the OOS (or OOS Beta) works fine it could be a kernel or firmware issue.
So it looks like the problem is with the replacement screen. Funny, because this is the 2nd time I replaced the screen (dont ask) but I didn't have flickering problem with the first one. Hopefully any talented devs can figure out the issue and resolves it, will gladly help however I can.
The change was merged:
h t t p s://review.lineageos.org/#/c/208861/
Maybe you could try the next build of LineageOS to see if the issue was fixed.
Lukedyue said:
The change was merged:
h t t p s://review.lineageos.org/#/c/208861/
Maybe you could try the next build of LineageOS to see if the issue was fixed.
Click to expand...
Click to collapse
thanks a lot .. i wil try this weekend for sure
Lukedyue said:
The change was merged:
h t t p s://review.lineageos.org/#/c/208861/
Maybe you could try the next build of LineageOS to see if the issue was fixed.
Click to expand...
Click to collapse
I've just installed it and still the same issue (The 2018-03-05 version)
N.B :
You can activate "Show surface updates" from the Developer Options Menu and the screen will not have those glitches anymore, because I realized that the glitches will go away whenever you update the screen.
rsm23 said:
I've just installed it and still the same issue (The 2018-03-05 version)
N.B :
You can activate "Show surface updates" from the Developer Options Menu and the screen will not have those glitches anymore, because I realized that the glitches will go away whenever you update the screen.
Click to expand...
Click to collapse
Well, by "next" I mean builds from 20180309 onwards.
Tried the 12-03 release, it does fix the screen errors, touch stop working if the screen is turned off, I need to reboot to it work again
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.
I have redmi note 5 pro indian version with huaxing display panel so if i flash any custom rom other than miui based rom it just shows a black screen ie no display so can anyone fix this?
I don't think Xiaomi will provide updated source codes
In recovery?
htchd2sucks said:
In recovery?
Click to expand...
Click to collapse
Recovery had the same issue earlier but latest builds fixed the issue
Now the issue is with roms
rahulrulz said:
Recovery had the same issue earlier but latest builds fixed the issue
Now the issue is with roms
Click to expand...
Click to collapse
Yes, I informed the various recovery devs about that, I know it was fixed on latest versions.
I'm surprised it's not working for ROMS, I though the problem was fixed...
Have you tried telling that to the roms dev? I doubt anyone will read that here in this questions section...
The latest PE rom (https://forum.xda-developers.com/redmi-note-5-pro/development/rom-pixel-experience-t3830197) is almost perfect. Maybe it can be updated to include the relevant drivers.
Maybe it's a kernel thing also, so maybe it's something you should discuss with Derp Kern devs, for example?
https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996
I don't really know who deals with "missing driver" in current context, try get more information in the threads?
htchd2sucks said:
Yes, I informed the various recovery devs about that, I know it was fixed on latest versions.
I'm surprised it's not working for ROMS, I though the problem was fixed...
Have you tried telling that to the roms dev? I doubt anyone will read that here in this questions section...
The latest PE rom (https://forum.xda-developers.com/redmi-note-5-pro/development/rom-pixel-experience-t3830197) is almost perfect. Maybe it can be updated to include the relevant drivers.
Maybe it's a kernel thing also, so maybe it's something you should discuss with Derp Kern devs, for example?
https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996
I don't really know who deals with "missing driver" in current context, try get more information in the threads?
Click to expand...
Click to collapse
I informed the kernel Dev he said xiaomi has to update the sources that I think is less likely to happen
Same issue here. There's a RR build working for me though but I don't see fingerprint settings in security menu. I have goodix though. I tried a few pie ROMs and all of them just have a black screen.
NitinRanganath said:
Same issue here. There's a RR build working for me though but I don't see fingerprint settings in security menu. I have goodix though. I tried a few pie ROMs and all of them just have a black screen.
Click to expand...
Click to collapse
Can you give the link to the working rom
Anyone has a working aosp rom for hauxing display
rahulrulz said:
I have redmi note 5 pro indian version with huaxing display panel so if i flash any custom rom other than miui based rom it just shows a black screen ie no display so can anyone fix this?
I don't think Xiaomi will provide updated source codes
Click to expand...
Click to collapse
NitinRanganath said:
Same issue here. There's a RR build working for me though but I don't see fingerprint settings in security menu. I have goodix though. I tried a few pie ROMs and all of them just have a black screen.
Click to expand...
Click to collapse
The calibration file for this panel is missing on custom ROMs, here's a flashable zip with this file from MIUI which should fix this, mount system and vendor on recovery before flashing (mandatory)
rocker00 said:
The calibration file for this panel is missing on custom ROMs, here's a flashable zip with this file from MIUI which should fix this, mount system and vendor on recovery before flashing (mandatory)
Click to expand...
Click to collapse
Wow, can you confirm if this works on all ROMs ? Also, I'm using a custom modified kernel currently in order to use custom ROMs but it breaks WiFi. Does this break WiFi too ?
EDIT: I dirty flashed Bootleggers ROM which I was using with the modified kernel and flashed only the ROM and the fix zip. The black screen issue still persists. I had mounted both system and vendor before flashing the ZIP. Maybe I'm doing something wrong. I request the OP to confirm if the ZIP fixed his issue.
NitinRanganath said:
Wow, can you confirm if this works on all ROMs ? Also, I'm using a custom modified kernel currently in order to use custom ROMs but it breaks WiFi. Does this break WiFi too ?
EDIT: I dirty flashed Bootleggers ROM which I was using with the modified kernel and flashed only the ROM and the fix zip. The black screen issue still persists. I had mounted both system and vendor before flashing the ZIP. Maybe I'm doing something wrong. I request the OP to confirm if the ZIP fixed his issue.
Click to expand...
Click to collapse
I don't have this panel and also using MIUI, i just found this file while i was looking for something else, i thought it might do the trick, maybe Xiaomi should update the source code to support this panel for custom ROMs, but clearly this file is the calibration for this panel!
rahulrulz said:
anyone has a working aosp rom for hauxing display
Click to expand...
Click to collapse
deleted reply
NitinRanganath said:
Wow, can you confirm if this works on all ROMs ? Also, I'm using a custom modified kernel currently in order to use custom ROMs but it breaks WiFi. Does this break WiFi too ?
EDIT: I dirty flashed Bootleggers ROM which I was using with the modified kernel and flashed only the ROM and the fix zip. The black screen issue still persists. I had mounted both system and vendor before flashing the ZIP. Maybe I'm doing something wrong. I request the OP to confirm if the ZIP fixed his issue.
Click to expand...
Click to collapse
Can u send me the kernel
NitinRanganath said:
Same issue here. There's a RR build working for me though but I don't see fingerprint settings in security menu. I have goodix though. I tried a few pie ROMs and all of them just have a black screen.
Click to expand...
Click to collapse
About the FP Sensor I'm have a goodix too, but the dev of Pixel Experience is working on fix for it, maybe if you contact him, you problem with the Display can be solved.
MarcoD14 said:
About the FP Sensor I'm have a goodix too, but the dev of Pixel Experience is working on fix for it, maybe if you contact him, you problem with the Display can be solved.
Click to expand...
Click to collapse
The fingerprint issue was only with the old RR May build. After flashing the latest ROMs, the fingerprint option is available and works fine. Thanks though. As far as the display is concerned, custom ROMs don't boot without a specific kernel and that kernel breaks WiFi. I appreciate the efforts though. Also, on some ROMs, the maximum is quite dim but its fine on NOS and McAOSP.
---------- Post added at 07:03 PM ---------- Previous post was at 07:03 PM ----------
rahulrulz said:
Can u send me the kernel
Click to expand...
Click to collapse
Check PM.
rocker00 said:
The calibration file for this panel is missing on custom ROMs, here's a flashable zip with this file from MIUI which should fix this, mount system and vendor on recovery before flashing (mandatory)
Click to expand...
Click to collapse
It doesn't work still black screen
has anyone actually found a fix for this, or a non MIUI rom that works? I also have the black screen problem...
Thanks
https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-huaxing-displays-t3873266
Here is the fix
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