UPDATE:
temblor55 has made a Magisk patch for this problem, which he posted on 18 september::
https://drive.google.com/file/d/1-3y1CR6nfVhFYf9VpE11FXOmDEQl5VMt/view
Pat57 has confirmed that it works for him.
________________________________________________________________________________________________________
I have a RN8 from 11-2020 board ID 3.29
Instead of the usual Omnivision OV13855 frontcam, there is a new version OV13B10 inside.
This camera sensor is also installed in later Redmi phones
This new version works OK with Miui 11.0.11 -A9, and higher
Custom A11 rom's will problably work also all with this frontcam (I tried CrDroid 7.4 -A11 with succes)
But I can't find a custom A10 rom that can connect to this frontcam.
Always get the message "can not connect to camera"
Because of speed, stability and more development, I prefer a A10 custom rom (Resurrection Remix)
I think it isn't the Xiaomi FW, so maybe it could be the kernel.
I have tried the updated 2021 -A10 roms and A10 kernels without succes.
So problably it is about missing libs inside rom.
Is there a way to find these libs in a A11 custom rom or Miui rom and add them inside A10 rom?
I don't want to deep dig in it, because A11 will be the future solution.
But development on A11 rom's is fast ongoing, so there are bugs which some are irritating.
So if someone could give a direction, I will be thankfull
Elinx said:
I have a RN8 from 11-2020 board ID 3.29
Instead of the usual Omnivision OV13855 frontcam, there is a new version OV13B10 inside.
This camera sensor is also installed in later Redmi phones
This new version works OK with Miui 11.0.11 -A9, and higher
Custom A11 rom's will problably work also all with this frontcam (I tried CrDroid 7.4 -A11 with succes)
But I can't find a custom A10 rom that can connect to this frontcam.
Always get the message "can not connect to camera"
Because of speed, stability and more development, I prefer a A10 custom rom (Resurrection Remix)
I think it isn't the Xiaomi FW, so maybe it could be the kernel.
I have tried the updated 2021 -A10 roms and A10 kernels without succes.
So problably it is about missing libs inside rom.
Is there a way to find these libs in a A11 custom rom or Miui rom and add them inside A10 rom?
I don't want to deep dig in it, because A11 will be the future solution.
But development on A11 rom's is fast ongoing, so there are bugs which some are irritating.
So if someone could give a direction, I will be thankfull
Click to expand...
Click to collapse
I had similar problem, but i don't think it's not from the libs, it's a "persist" thing
restore "persistbak" and flash it (or if you already have a recovery backup of persist just restore it)
loopypalm said:
.... i don't think it's not from the libs, it's a "persist" thing
restore "persistbak" and flash it .....
Click to expand...
Click to collapse
No, I think it has nothing to do with the persist partition.
Because I have flashed several different rom's and kernels and found that only Miui and A11 custom does recognize the selfiecam
If the persist partition was corrupted, this wasn't possible.
Because FW is from Miui, it could be the kernel or rom.
A lot of A10 custom roms are EOL, they are build with the original early hardware drivers/libs
From 11-2020 PCB-ID 3.29 the camsensor is changed and the RN8 was also almost EOL.
In september 2020 the first A11 build came out and at the end of 2020 more and more builds.
So I assume most developers don't even think about updating the kernel or libs on their "old" A10 versions.
Inside the screenshots of the app "Device info HW" you see the 19 supported cams of CrDroid 7.4 and only 17 on RR 8.6.7
Elinx said:
No, I think it has nothing to do with the persist partition.
Because I have flashed several different rom's and kernels and found that only Miui and A11 custom does recognize the selfiecam
If the persist partition was corrupted, this wasn't possible.
Because FW is from Miui, it could be the kernel or rom.
A lot of A10 custom roms are EOL, they are build with the original early hardware drivers/libs
From 11-2020 PCB-ID 3.29 the camsensor is changed and the RN8 was also almost EOL.
In september 2020 the first A11 build came out and at the end of 2020 more and more builds.
So I assume most developers don't even think about updating the kernel or libs on their "old" A10 versions.
Inside the screenshots of the app "Device info HW" you see the 19 supported cams of CrDroid 7.4 and only 17 on RR 8.6.7
Click to expand...
Click to collapse
yes, on paper the problem sounds like it has nothing to do with persist
but as stupid as it sound ,it just worked ! (restoring persist) + latest stable A10 fw
devs didn't update the port because it just worked, and i heard it's a hard thing to mess with ...
loopypalm said:
...... as stupid as it sound ,it just worked ! (restoring persist) + latest stable A10 fw
devs didn't update the port because it just worked, and i heard it's a hard thing to mess with ...
Click to expand...
Click to collapse
For who has worked this? Have you one or more links to it?
I had read already the guides for restoring, but because all sensors does work I'm a bit holding back.
I like to read first some experiences with this, before I touch the persist partition.
Elinx said:
For who has worked this? Have you one or more links to it?
I had read already the guides for restoring, but because all sensors does work I'm a bit holding back.
I like to read first some experiences with this, before I touch the persist partition.
Click to expand...
Click to collapse
link to what ?
i had similar problem on my 128 variant and asked help in RR TG group (group is deleted by rodrigo) rr official dev is always offline, so rr users moved to milestone by zhan (which is miles better)
"all sensor work fine except camera"
nobody have idea and no dev support, so i try lot of things
and flashing latest A10 fw and restore persistbak + clean flash of RRos + 16 kernel are the last things i did and it worked
if you have orangfox do a backup of persist ,so if anything goes wrong you can just restore it
loopypalm said:
link to what ?
i had similar problem on my 128 variant and asked help in RR TG group (group is deleted by rodrigo) rr official dev is always offline, so rr users moved to milestone by zhan (which is miles better)
"all sensor work fine except camera"
nobody have idea and no dev support, so i try lot of things
and flashing latest A10 fw and restore persistbak + clean flash of RRos + 16 kernel are the last things i did and it worked
if you have orangfox do a backup of persist ,so if anything goes wrong you can just restore it
Click to expand...
Click to collapse
Ok I will try after backup
Which RN8 batch have you? Which camera didn't work?
Elinx said:
Which RN8 batch have you? Which camera didn't work?
Click to expand...
Click to collapse
what do you mean by batch ? i have ginkgo 6/128
the error was "can't connect to camera" (i guess,both front and back since i can't do anything while that error is apearing)
loopypalm said:
... batch ? i have ginkgo 6/128
the error was "can't connect to camera" (i guess,both front and back since i can't do anything while that error is apearing)
Click to expand...
Click to collapse
The batch date 11-2020 is the phone with problems.
First the problem with FW 12.01. This is the only phone that can't be flashed with that version. If you did with twrp, you had a brick.
Second the HW change of the selficam. I have seen I'm not the only one with Andoid Q "not connecting" to this specific cam.
On LOS 17 topic a saw there is a formel bug report published about this issue
I can use all other cams without problems. The error is only with selfiecam and A10. Not with Miui and not with A11.
That is why I think of a missing driver.
I read something about adding missing drivers, but think it isn't easy.
Also I understand that the vendor image contains the hardware drivers.
So trying kernels only hasn't influence on HW changes
I can imagine that A11 custom uses also later vendor images, that's why these roms work with selficam.
Next question would be.
Are vendor images for Ginkgo intechangable?
Elinx said:
That is why I think of a missing driver.
Click to expand...
Click to collapse
have you tried A10 latest stable FW ? (it has updated drivers in it)
Elinx said:
Are vendor images for Ginkgo intechangable?
Click to expand...
Click to collapse
as far as i tested(A10), they are all almost the same, except for some roms have some carrier overlays and BT in it and other have them in system
also audio mods and enhancement, some roms have it and other don't
loopypalm said:
have you tried A10 latest stable FW ?....
...
as far as i tested(A10), they are all almost the same, except for some roms ...
Click to expand...
Click to collapse
Yes I have the latest stable FW. First I thought that these contains the HW drivers.
But reading, I learned that with latest Android versions all drivers are inside vendor image.
That is why updating FW and kernel doesn't make any difference for RR.
Because of all brick/EDL troubles I'm being carefull what I flash.
I have made for now a twrp backup of vendor and efs partition.
The persist parttion must be backup with adb or terminal
My phone is still an empty phone so I can format data and so on.
I saw that Miui vendor files are downloadable.
The latest Global is 11.0.11
Elinx said:
The persist parttion must be backup with adb or terminal
Click to expand...
Click to collapse
use also recovery (you never know) ...
Elinx said:
I saw that Miui vendor files are downloadable.
Click to expand...
Click to collapse
before changing system try RR with A11 vendor just to make sure
(i did that between 2 A10 roms and it worked,but A11 = not tested)
you can wipe everything and flash rr since your data is not important
loopypalm said:
.....
before changing system try RR with A11 vendor just to make sure
(i did that between 2 A10 roms and it worked,but A11 = not tested)
...
Click to expand...
Click to collapse
Dit you flash the complete vendor.img from another A10 rom?
or replaced the 3 vendor files inside the rom's?
Elinx said:
Dit you flash the complete vendor.img from another A10 rom?
or replaced the 3 vendor files inside the rom's?
Click to expand...
Click to collapse
i flashed a rom (Don't remember the name) and i did a mess in vendor ,so instead of reflashing, i restored a recovery backup of vendor of an older rom (AEX) that was on my SD
of course error like app x stopped working popped off,so this is not a fix
this is just a crazy suggestion to test the compatibility of the drivers
also test this cam :
ɬɧɛ Ɩųŋąɬıƈ in Dtuxed Roms Public Group
t.me
it has updated libs
maybe it will work
loopypalm said:
...., i restored a recovery backup of vendor of an older rom (AEX) that was on my SD
.....
maybe it will work
Click to expand...
Click to collapse
Ok you flashed vendor.img with twrp
The download link is Miui camera.
There where no HW drivers inside
I already found also such a zip with libs, but without result
It is for improving camera results
Elinx said:
There where no HW drivers inside
Click to expand...
Click to collapse
i made a mistake in the zip
the cam that i wanted to give you is in the same group
i will see if i can find it
Try this bro
Thank you, I surely want to try this Magisk mod file, but the file isn't accessible without requist.
Maybe you have your reasons for that, but in that case it isn't possible to download.
I have tried to comment this with the video too, but you have disabled comments there.
temblor55 said:
Try this bro
Click to expand...
Click to collapse
temblor55 you forgot to make the file public
Sorry guy's made it public now
https://drive.google.com/file/d/1-3y1CR6nfVhFYf9VpE11FXOmDEQl5VMt/view
Related
Android 8.x
https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/cheeseburger/recovery/
Changes:
- TWRP 3.2.3 from android-8.1
- added vendor partition
Sources
https://github.com/TeamWin/android_device_oneplus_cheeseburger/tree/android-8.1
https://github.com/lineageos/android_kernel_oneplus_msm8998/tree/lineage-15.1
################################################################################################
Android 9.x (requires Pie firmware)
https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/recovery/
Changes:
twrp-3.3.1-0-20190713-codeworkx-cheeseburger.img
- fix bug in default device properties
twrp-3.3.1-1-20190623-codeworkx-cheeseburger.img
- add support for synthetic password version 3 (may update)
twrp-3.3.1-0-20190427-codeworkx-cheeseburger.img
- updated twrp to 3.3.1
- removed compatibility check
- removed twrp app check
- modified version string
Sources
https://github.com/TeamWin/android_device_oneplus_cheeseburger/tree/android-9.0
https://github.com/lineageos/android_kernel_oneplus_msm8998/tree/lineage-16.0
Tested/ working fine Running Oero Public Beta 2 with encrytion enabled,
thanks
Data decryption seems to be working fine on oos5 with encryption enabled
Not working with omnirom encrypted........will try with others when got time...
canteo said:
Not working with omnirom encrypted........will try with others when got time...
Click to expand...
Click to collapse
Which version of omni?
File based or full disk encryption?
Ext4 or F2FS?
Which oneplus firmware version 4.5.15?
codeworkx said:
Which version of omni?
File based or full disk encryption?
Ext4 or F2FS?
Which oneplus firmware version 4.5.15?
Click to expand...
Click to collapse
Upps... it is true, i am sorry, last omnirom it's 8.1 and all of us know that none twrp is working decrypting data
omni 8.1, ext4, flashed over second last oreo oss test rom( second open beta) before 5.0 oss with full disk encryption( i think..)
canteo said:
Upps... it is true, i am sorry, last omnirom it's 8.1 and all of us know that none twrp is working decrypting data
omni 8.1, ext4, flashed over second last oreo oss test rom( second open beta) before 5.0 oss with full disk encryption( i think..)
Click to expand...
Click to collapse
We'll get that fixed during next few days.
So this TWRP is to decrypt a encrypted rom?
obol2 said:
So this TWRP is to decrypt a encrypted rom?
Click to expand...
Click to collapse
Decrypt and access userdata when running OxygenOS 5.0 (Oreo). Probably mainly for doing backups and restores.
Amazing! It's working for both FBE and FDE?
codeworkx said:
Please test data decryption.
Click to expand...
Click to collapse
Working perfectly on my OP5 with Oreo (non-beta) encrypted.
Can confirm that it can see encrypted data, backup and restore perfectly!
Great job!!
Sent from my OnePlus5, OOS Oreo, Flash Kernel
Big Thanks, @codeworkx Testing features now and usb-otg is not working. I see the commit but I dont know if it's a oreo thing but you could add this line in init.recovery.qcom.rc
write /sys/class/power_supply/usb/otg_switch 1
Testing on official oreo release on Christmas release, on FBE encryption- only made a backup so far, will report more later.
Thanks also for posting additional commits also.
Works perfectly. Encrypted OP5 (Oreo FBE);and tested with several Rom upgrades with no issues.
morgoth6 said:
Works perfectly. Encrypted OP5 (Oreo FBE);and tested with several Rom upgrades with no issues.
Click to expand...
Click to collapse
Did you try xxx 9.2 on your encrypted device?
mcduffie2010 said:
Did you try xxx 9.2 on your encrypted device?
Click to expand...
Click to collapse
Yes. I installed 9.2 over 9.1a +Flash kernel and it works just fine. To be honest I read all the comments about xxx upgrade on encrypted OP5 after that ... Sic. Glad it worked for me.
morgoth6 said:
Yes. I installed 9.2 over 9.1a +Flash kernel and it works just fine. To be honest I read all the comments about xxx upgrade on encrypted OP5 after that ... Sic. Glad it worked for me.
Click to expand...
Click to collapse
I posted your findings on the xxx thread. Hope it helps people.
mcduffie2010 said:
I posted your findings on the xxx thread. Hope it helps people.
Click to expand...
Click to collapse
I wonder what can produce this problems. I personally like to have encrypted device, but makes me think twice before update to new ROM now.
Is there a way to check what kind of encryption is used ? I mean FDE or FBE (or both) ? Maybe the problem is there. I buy this phone quite recently and started with clean Oreo (with format data) so I probably ended with ext4/FBE. Maybe problematic cases used FDE+FBE ?
I would like to see someone find what can be the cause for this problems as clean install or reinstalling Rom ten times is not a solution :/
morgoth6 said:
I wonder what can produce this problems. I personally like to have encrypted device, but makes me think twice before update to new ROM now.
Is there a way to check what kind of encryption is used ? I mean FDE or FBE (or both) ? Maybe the problem is there. I buy this phone quite recently and started with clean Oreo (with format data) so I probably ended with ext4/FBE. Maybe problematic cases used FDE+FBE ?
I would like to see someone find what can be the cause for this problems as clean install or reinstalling Rom ten times is not a solution :/
Click to expand...
Click to collapse
I agree but like I said in xxx thread I can't test because I'm decrypted and planning to stay that way. Hopefully people are gonna test it and than we know or get feedback.
morgoth6 said:
I wonder what can produce this problems. I personally like to have encrypted device, but makes me think twice before update to new ROM now.
Is there a way to check what kind of encryption is used ? I mean FDE or FBE (or both) ? Maybe the problem is there. I buy this phone quite recently and started with clean Oreo (with format data) so I probably ended with ext4/FBE. Maybe problematic cases used FDE+FBE ?
I would like to see someone find what can be the cause for this problems as clean install or reinstalling Rom ten times is not a solution :/
Click to expand...
Click to collapse
Afaik oxygen is using keymaster1 and lineage/omni/aosp are using keymaster3. That seems to be a problem.
The upgraded firmware is also a problem for old twrp builds using N libs.
Sent from my OnePlus5T using XDA Labs
mcduffie2010 said:
I posted your findings on the xxx thread. Hope it helps people.
Click to expand...
Click to collapse
Thanks for your help, I tried to flash this TWRP via fastboot but same issue as before, can't seem to ask for a password in order to decrypt storage. I'm trying to sideload 9.2 to see if it can work by flashing on it again, we never know... In either case I'm screwed lol.
Any way to decrypt storage using a flashable zip in TWRP? Like no_verity, etc ? I feel like the answer is no since it will say that it is decrypted, but it won't decrypt the data that is already encrypted (would be too easy right?).
Welcome to the first WORKING Oreo based Custom ROM for the H930
THEORY OF EVERYTHING
INTRODUCTION
Welcome to my first FULLY working ROM, this time its a stock based Oreo ROM based off of the V300L21b firmware.
This ROM is a bit debloated, meaning mainly all the korean apps are gone (a full list of debloated apps is in post #2).
The name of the ROM is from @einhuman197 (Tobs) from the V30 Telegram group
I think thats a good name (as I am myself a physics student, and a real admirer of Stephen Hawkins work).
FEATURES
debloated (some google apps like sheets, slides... and korean ones)
removed automatic encryption (even "normal" encryptable forced an encryption for me, so removed that alltogether)
1. March security patch
ThinQ update (AI Camera and all that)
WORKING
everything
NOT WORKING
tell me
FLASH INSTRUCTIONS
Make sure your /data isnt encrypted though. I dont know how it will react if the ROM finds an encrypted /data partition, as I disabled it alltogether (****ed it up for me, even though forcencryption was off)
Download ROM + (potential) hotfix
Copy it on your sdcard/internal memory
Boot into TWRP
Make a Backup of Boot/System/Data/Cache
Wipe /system, /data, /cache, /dalvik/cache in TWRP
Flash .zip file(s)
SCREENSHOTS
see attachment
DOWNLOAD
V1: https://www.androidfilehost.com/?fid=746010030569964396
V1.01 Hotfix: https://www.androidfilehost.com/?fid=890129502657593599
XDA:DevDB Information
V300L21b Stock debloated for H930, ROM for the LG V30
Contributors
SGCMarkus
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Kernel Source: https://github.com/SGCMarkus/android_kernel_lge_msm8998/tree/lge-oreo
Based On: V300L21b
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2018-03-24
Created 2018-03-24
Last Updated 2018-03-24
CHANGELOG
V1. Initial Release
Debloated
Custom exfat driver (stock sources dont provide one)
V1.01 Fingerprint Hotfix update
Fixed fingerprint (using fingerprint.msm8998.so from nougat to match firmware version)
FAQ
Does this also work on the US998?
Seems to work fine, but some bands seem to be not working (for Verizon, maybe missing APNs? needs more testing)
Is the ROM already rooted?
No, but Im using Magisk 16.2 myself, so you can flash that afterwards
How do i restore to my previous ROM or go to another ROM?
Reboot into TWRP, wipe system, data, cache (do not format data if you wanna keep your internal memory), and restore your backup, or flash another ROM.
Warning: DO NOT USE LG UP TO RESTORE NOUGAT WITHOUT PERFORMING A FACTORY RESET BEFORE, YOU MIGHT END UP IN A BOOTLOOP
List of debloated Apps
Code:
[LIST]
[*]system/app/Drive*
[*]system/app/Duo*
[*]system/app/EditorsDocs*
[*]system/app/EditorsSheets*
[*]system/app/EditorsSlides*
[*]system/app/Facebook_AppManager*
[*]system/app/FidoASM*
[*]system/app/FidoAuthenticator*
[*]system/app/FidoClient*
[*]system/app/FidoCryptoService*
[*]system/app/FidoService*
[*]system/app/Gmail2*
[*]system/app/LGAccount*
[*]system/app/LGAirDrive*
[*]system/app/LGFOTA*
[*]system/app/lguplus-permission*
[*]system/app/lguplusp_mcc
[*]system/app/Maps*
[*]system/app/UBox*
[*]system/app/UplusTVonPhone*
[*]system/app/USIM_Agent*
[*]system/app/UsimOTAKR*
[*]system/app/UVSService*
[*]system/app/CNasTermsApp*
[*]system/app/CNasManagerService*
[*]system/app/CNasMainApp*
[*]system/priv-app/Facebook_Installer*
[*]system/priv-app/LGAirDriveSetting*
[*]system/priv-app/LGBackup*
[*]system/priv-app/LGBackupLauncher*
[*]system/priv-app/LGPay*
[*]system/priv-app/LGPay_QLauncher*
[*]system/priv-app/LGQHelpService*
[*]system/priv-app/ONEStoreClient*
[*]system/priv-app/ONEStoreService*
[*]system/priv-app/LGTDMB*
[*]system/priv-app/LG_PushAgent*
[*]system/priv-app/LGUDownloader*
[*]system/priv-app/oemsearch*
[/LIST]
Will install as soon as I can download it! Thanks for your work!
I let you know If I encounter any problems.
Thank you for your Work ! So Thema Fingerprint don't Work right?
How about mods Like the Dual speaker one ?
Again, thx you for your Work.
Nice job! If you fix the fingerprint sensor before LG releases Oreo for the US998 I'll give it a shot on mine. Take your time though, I'm sure LG won't release it for another 4-5 weeks ?
Got the system up and running
For now I can life without the fingerprintsensor (but still please fix it fast xD)
Flashed it via TWRP, System runs smooth and I can boot into TWRP without any problems.
The AI camera really improves the quality of the camera!
Small details like the boot splashscreen and name titels are still V300L21b not the V30 H930.
If you need any logs or when you need me to try something let me know :good:
Found the solution (thanks @Rashed97 <3 )
making a hotfix zip now, has to be flashed over v1... dont wanna upload 2.4GB just for 1 file change xD
SGCMarkus said:
Found the solution (thanks @Rashed97 <3 )
making a hotfix zip now, has to be flashed over v1... dont wanna upload 2.4GB just for 1 file change xD
Click to expand...
Click to collapse
Nice! Thank you!
Think you, seems perfect so far!
One thing before flashing, is this rom already rooted? With Magisk or SU?
Think you again?
Nice one. Thanks! Now i have reson to unlock bootloader
Downloading !! and also now is a reason to unlock bootloader ;D
(can one make check/know it's contatins Polish lang. ? (PL)
niko99 said:
Downloading !! and also now is a reason to unlock bootloader ;D
(can one make check/know it's contatins Polish lang. ? (PL)
Click to expand...
Click to collapse
There is PL
---------- Post added at 10:26 AM ---------- Previous post was at 10:16 AM ----------
bvannier said:
Think you, seems perfect so far!
One thing before flashing, is this rom already rooted? With Magisk or SU?
Think you again?
Click to expand...
Click to collapse
No, you have to flash root by yourself
bvannier said:
Think you, seems perfect so far!
One thing before flashing, is this rom already rooted? With Magisk or SU?
Think you again
Click to expand...
Click to collapse
Its just stock, so unrooted, Im using Magisk 16.2 myself and have no problems
Gonna include that in the FAQ
***EDIT****
OK its finally working BUT there is no POLISH / POLAND / PL lag. any idea how to add lang ?
niko99 said:
***EDIT****
OK its finally working BUT there is no POLISH / POLAND / PL lag. any idea how to add lang ?
Click to expand...
Click to collapse
Only way i have found (could be wrong though) how to add a new language to the whole system, is by manually decompiling all apps, and translating every string... and you can imagine, thats a damn lot of work (especially because i have no clue about polish xD).
And then to make it selectable in settings... Thats something i have no idea about, sorry :/
Can this be flashed over stock?
I've got TWRP and magisk already in place but running stock rom.
7.1.2 january scurity patch.
Thanks for the rom!
i think you gonna wipe: cache, dalvik cache, system and data before but I gonna be wrong. Maybe @SGCMarkus add to OP step by step procedure?
swayjd said:
Can this be flashed over stock?
I've got TWRP and magisk already in place but running stock rom.
7.1.2 january scurity patch.
Thanks for the rom!
Click to expand...
Click to collapse
I didnt try that, and i suppose i wouldnt recommend it, as its a system update, and not even to the same model build as you have currently (as this is based off of the korean V300L).
You can try it though, but make sure to make a backup of EVERYTHING you wanna keep, in case something goes wrong.
swayjd said:
Can this be flashed over stock?
I've got TWRP and magisk already in place but running stock rom.
7.1.2 january scurity patch.
Thanks for the rom!
Click to expand...
Click to collapse
Do a Clean flash - it is always good to avoid problems.
Also its grand update, not a little one.
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
Hi All -
Just wanted to make a thread here to link to the Magisk Module I created that bypasses the bootloop we get when we have CN hardware with the Global Rom. I think this will work for India and Russia hardware too. Enjoy.
https://forum.xda-developers.com/apps/magisk/module-xiaomi-global-rom-cn-hardware-t3899316
PWn3R said:
Hi All -
Just wanted to make a thread here to link to the Magisk Module I created that bypasses the bootloop we get when we have CN hardware with the Global Rom. I think this will work for India and Russia hardware too. Enjoy.
https://forum.xda-developers.com/apps/magisk/module-xiaomi-global-rom-cn-hardware-t3899316
Click to expand...
Click to collapse
Thanks for this! Have you tested this to make sure stock camera still works without any issue?
xterminater07 said:
Thanks for this! Have you tested this to make sure stock camera still works without any issue?
Click to expand...
Click to collapse
Mine never stopped working before, however, this works completely differently. This inserts a script into the boot process that happens before the device starts launching system services that changes the ro.boot.hwc and ro.boot.hwcountry to be "global". The other way I was doing it was to make the product props to a value that would make it skip the checks entirely. Unfortunately, changing that value removed the slider settings, broke the slider camera, and for some, stopped the stock camera from working. I have checked an all expected settings are in the menu, safetynet passes, the slider works, the stock camera works.
Great, all works, no problem with camera or slider settings.
PWn3R said:
Mine never stopped working before, however, this works completely differently. This inserts a script into the boot process that happens before the device starts launching system services that changes the ro.boot.hwc and ro.boot.hwcountry to be "global". The other way I was doing it was to make the product props to a value that would make it skip the checks entirely. Unfortunately, changing that value removed the slider settings, broke the slider camera, and for some, stopped the stock camera from working. I have checked an all expected settings are in the menu, safetynet passes, the slider works, the stock camera works.
Click to expand...
Click to collapse
Eggcellent!!! lol... so just flash with twrp and that's it?
Yes, flash Magisk, 18.0 and 18.1 don't work for me. Use 17.3 and then flash this and you should be golden.
i dont know who created this, but this was shared on a Mi Mix3 FB group from PH.
Magisk-v18.1_mix3专版
bluviper said:
i dont know who created this, but this was shared on a Mi Mix3 FB group from PH.
Magisk-v18.1_mix3专版
Click to expand...
Click to collapse
does this work on chinese device with chinese rom or xiaomi eu rom?
I have got it working on chinese device with xiaomi.eu rom.
xterminater07 said:
does this work on chinese device with chinese rom or xiaomi eu rom?
Click to expand...
Click to collapse
I can confirm that works, I already flashed
Inviato dal mio MIX 3 utilizzando Tapatalk
yes, its working on EU ROM coz im on Mi-Globe which is based on EU ROM.
bluviper said:
yes, its working on EU ROM coz im on Mi-Globe which is based on EU ROM.
Click to expand...
Click to collapse
Why would you use it on the EU/Mi-Globe?
Mackay53 said:
Why would you use it on the EU/Mi-Globe?
Click to expand...
Click to collapse
before, V18.0 wont work with mix3.
no matter how you install it. only 17.3 works
as of the moment, since the week before the Chinese New Year, there are no updates from mi-globe. until this weekend. so this is a good alternative to make v18 work with mix3.
bluviper said:
before, V18.0 wont work with mix3.
no matter how you install it. only 17.3 works
as of the moment, since the week before the Chinese New Year, there are no updates from mi-globe. until this weekend. so this is a good alternative to make v18 work with mix3.
Click to expand...
Click to collapse
What benefits do v18 make over v17.3?
Mackay53 said:
What benefits do v18 make over v17.3?
Click to expand...
Click to collapse
Other than a new magisk manager interface I don't notice any difference.
954wrecker said:
Other than a new magisk manager interface I don't notice any difference.
Click to expand...
Click to collapse
That's what I was thinking but people seem to really want to install it, I'm still on 17.1 as that's what comes with twrp.
I haven't tested 18.1 as posted above, but 17.3 is the latest working released version for global.
PWn3R said:
I haven't tested 18.1 as posted above, but 17.3 is the latest working released version for global.
Click to expand...
Click to collapse
Most people on telegram are now using 18.1 , apparently support for modules will end soon for 17.
The released 18.0 and 18.1 do not work on the mix 3. I have no idea if the one linked above does, but I also don't know what they modified which is why I was advising 17.3
Sent from my Mi MIX 3 using Tapatalk
PWn3R said:
The released 18.0 and 18.1 do not work on the mix 3. I have no idea if the one linked above does, but I also don't know what they modified which is why I was advising 17.3
Sent from my Mi MIX 3 using Tapatalk
Click to expand...
Click to collapse
its working. some of the others guys here installed it.
they said its working. i for one, installed, and its working.
based on the screen capture i posted. you can see a logo of xda, maybe they are a part of it somehow.
moreover, there are tons of bulleted changelogs for the 18.0 & 18.1
some of them may not be noticeable for a very large audience, but this "i guess" will make it future proof for the reason of rom updates and compatibility. since Android Q is in the works.
also, noticed these changes
Code:
v18.1
- [General] Support EMUI 9.0
- [General] Support Kirin 960 devices
- [General] Support down to Android 4.2
- [General] Major code base modernization under-the-hood
other changes are for MagiskHide, maybe to better hide other apps. because there are some few apps that still can detect rooted devices even if they are HIDDEN.
HUGE thanks to @giri45 for actually providing the fix!
What's this?
A Unity installer ensures that you can use this module with any kind of root solution (as long as it supports init.d)! If you have Magisk, flash the module through the Magisk Manager, but if you don't have Magisk, just flash the module through TWRP. When you want to uninstall the module, flash it again in Magisk Manager or TWRP.
As for the module itself, it provides a fix for LiveDisplay/Night Light on the Moto G5/G5S for anyone running an AOSP-based ROM running Android 9 or higher, and enables Camera2 API + EIS if you wish so.
Do NOT attempt to install this on other devices, or ROMs based on Android <9! Device and Android version checks have been applied to make sure this module will not install on incompatible devices. This module assumes that you are using the latest stock Oreo firmware (including bootloader, GPT and etc.)! Do not report issues if you are not on the latest firmware.
Tested ROMs:
Havoc OS 2.2
Pixel Experience 9.0
AOSPExtended 6.3
crDroid 5.0
Known issues:
Fix doesn't work on Nougat firmware. You must have fully flashed the stock ROM/flashed it via OTA, for this fix to work.
Downloads:
Download from Magisk Repo.
Flash via Magisk Manager or TWRP. Make sure you have a root solution which supports init.d!
Thanx for trying to fix this. Unfortunately it's not working on my xt1794 running AospExtented. First try flashing through twrp failed, the updaterscript didn't recognize my phone (correctly), then installing as magisk module, but no night light..
Ænimal said:
Thanx for trying to fix this. Unfortunately it's not working on my xt1794 running AospExtented. First try flashing through twrp failed, the updaterscript didn't recognize my phone (correctly), then installing as magisk module, but no night light..
Click to expand...
Click to collapse
That's really weird. Installs fine and works on PE, installs fine but doesn't work on ViperOS, and now doesn't work on AOSPExtended.
Could you try providing installation logs located in the Internal storage?
Have you also tried manually replacing the files? If that works, then it's not a problem with the ROM...
JarlPenguin said:
That's really weird. Installs fine and works on PE, installs fine but doesn't work on ViperOS, and now doesn't work on AOSPExtended.
Could you try providing installation logs located in the Internal storage?
Have you also tried manually replacing the files? If that works, then it's not a problem with the ROM...
Click to expand...
Click to collapse
Deleted
PE 9.0LOG is attached
@JarlPenguin You mentioned fix is working on AOSPExtended 6.3, is that for the g5, or is there a montana build? If so, please provide a link if possible, thanx
Ænimal said:
@JarlPenguin You mentioned fix is working on AOSPExtended 6.3, is that for the g5, or is there a montana build? If so, please provide a link if possible, thanx
Click to expand...
Click to collapse
It's an internal build. You can test it out here: https://t.me/montanadevelopment
JarlPenguin said:
It's an internal build. You can test it out here: https://t.me/montanadevelopment
Click to expand...
Click to collapse
I'm running this build now and tried the fix but to no avail, still (xt1794)
Ænimal said:
I'm running this build now and tried the fix but to no avail, still (xt1794)
Click to expand...
Click to collapse
Are you on the Oreo firmware? GPT and bootloader included. Did you do a screen repair before?
JarlPenguin said:
Are you on the Oreo firmware? GPT and bootloader included. Did you do a screen repair before?
Click to expand...
Click to collapse
Nougat firmware and Oreo baseband, screen is original. Do you think that partition table is the problem?
Ænimal said:
Nougat firmware and Oreo baseband. Do you think that partition table is the problem?
Click to expand...
Click to collapse
Okay, I think I have found the problem now. What have you not upgraded?
JarlPenguin said:
Okay, I think I have found the problem now. What have you not upgraded?
Click to expand...
Click to collapse
As I said, I upgraded the baseband, the rest is firmware from nougat. On another device I'm running lollipop firmware and no problems regarding night light on pie ROMs..
Edit: I see you updated op, will report back once I fully upgraded firmware (for now I want to be able to revert back to nougat). Thanx for your efforts
Ænimal said:
As I said, I upgraded the baseband, the rest is firmware from nougat. On another device I'm running lollipop firmware and no problems regarding night light on pie ROMs..
Edit: I see you updated op, will report back once I fully upgraded firmware (for now I want to be able to revert back to nougat). Thanx for your efforts
Click to expand...
Click to collapse
Thanks. I updated the OP a while ago, but I do want to figure out the root cause of the problem, whether it is the vendor image, bootloader, GPT, or something else.
JarlPenguin said:
Thanks. I updated the OP a while ago, but I do want to figure out the root cause of the problem, whether it is the vendor image, bootloader, GPT, or something else.
Click to expand...
Click to collapse
I'm planning on upgrading everything except bootloader and gpt.bin, then I'll try your fix again and report back:good:
Edit: OK, done. I did flash bootloader, did not erase userdata and did not flash stock recovery. Good news is: system feels alot snappier - not so good news is that fix is still not working for me..
For anyone with similar issue: use cf.lumen instead and don't forget to thank the dev
Ænimal said:
I'm planning on upgrading everything except bootloader and gpt.bin, then I'll try your fix again and report back:good:
Edit: OK, done. I did flash bootloader, did not erase userdata and did not flash stock recovery. Good news is: system feels alot snappier - not so good news is that fix is still not working for me..
For anyone with similar issue: use cf.lumen instead and don't forget to thank the dev
Click to expand...
Click to collapse
That's weird... One thing I know that is that this fix doesn't work on Nougat firmware.
Working flawlessly on crDroid 9.
Thank you devs!
I have installed the mod with magisk and not working on my device with Pixel Experience 9.0
Arn'oh said:
I have installed the mod with magisk and not working on my device with Pixel Experience 9.0
Click to expand...
Click to collapse
Hehe, same like me , if you didn't updated officially than this fix won't work on any PIE ROM
zahidm said:
Hehe, same like me , if you didn't updated officially than this fix won't work on any PIE ROM
Click to expand...
Click to collapse
I had updated to Oreo official beta test with fastboot commands
Arn'oh said:
I had updated to Oreo official beta test with fastboot commands
Click to expand...
Click to collapse
Did you flash everything? Try fully flashing Stock Oreo via Fastboot and then install TWRP, custom ROM and this fix.