Disabling Pixel Spoofing completely on crDroid lavender source code - Xiaomi Redmi Note 7 Questions & Answers

Hello everyone, hope you're having a great day.
Recently I've installed OrangeFox Recovery as well as crDroid 9.5 on my RN7/lavender, all working fine, but by default I saw that the Pixel Spoofing feature is enabled by default.
Later on, I found as well that disabling it made my device be detected as a Pixel 5, rather than a RN7.
This is very annoying as I'm currently on the situation that I can't revert the Pixel Spoofing changes without rooting with Magisk or doing any other internal changes (e.g editing build.prop).
So, it comes up to my question regarding how can I delete completely Pixel Spoofing from the source code of crDroid lavender (https://github.com/crdroidandroid/android_device_xiaomi_lavender).
I've seen as well that the Pixel Spoofing feature is located on another crDroid repository that contains the "base" I guess for all devices (https://github.com/crdroidandroid/android_frameworks_base) (https://github.com/crdroidandroid/a...id/internal/util/crdroid/PixelPropsUtils.java).
I couldn't get any help on Telegram (Nexus Kernel), so if someone could help me figure out how to remove this feature and build the ROM, I'd appreciate it.
Thank you

Related

[mido] Unofficial Resurrection Remix ROMs discussion (eg, LineageOS eXtended etc)

This is not my Rom - this is just a Forum for discussion on XDA - the main forum is the 4pda.ru site
LineageOS 15.1 eXtended
4pda.ru - Original Rom Thread - https://4pda.ru/forum/index.php?showtopic=809215&view=findpost&p=72074026
Rom download
Source Forge - 1/4/2019 - last build
https://sourceforge.net/projects/lineageos-extended/
Latest Personal Build from Alexey71
https://drive.google.com/drive/mobile/folders/1EQCRrAVSPkzGQk1pVjDe67KaY12caGJ4
Change Log -
Find the current change log in the folder where you download the rom
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS eXtended is a free, community built, aftermarket firmware distribution of Android 8 (oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS eXtended is based on LineageOS and the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS eXtended does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS eXtended is available in the LineageOS eXtended Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Source Code:
https://github.com/LineageOS-eXtended
https://github.com/Alexey71
What's working :
Boots
RIL (Calls, SMS, Data)
Fingerprint
IR Blaster
Wi-Fi
Bluetooth
Camera
Camcorder (Supports up to 60fps via GCAM in bright light)
Video Playback
Audio
Sensors
Flash
LED
GPS
Volte
ViLte
Known issues:
You Tell me
FAQ: (Google Translation of Russian Forum FAQ)
Answers to questions or FAQ:
* The first time the firmware is installed, crashes the setting.
Delete the SetupWizard in GAPPS
* There is no "for program" option on LOS in the superuser settings, there is only "ADB". How do I enable root for programs?
Route of access is not present, it is necessary to flash Magisk treble or LineageOS extension https://download.lineageos.org/extras
Instructions :
Download the latest Rom build - Source Forge - https://sourceforge.net/projects/lineageos-extended/ - and GApps - https://opengapps.org/
Reboot to recovery
Flash the latest build and GApps
Reboot
Downloads :
Recovery & Magisk
Twrp 3.2.3.1 - treble version -
https://dl.twrp.me/mido/twrp-3.2.3-1-mido.img.html
Orange Fox r9.0 (twrp 3.2.3.1) -
https://forum.xda-developers.com/re.../recovery-orangefox-recovery-project-t3775933
Official https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 Magisk 19.0
Extra Camera's
MIUI Camera (For Slow Motion Video Capture)
Google Camera Builds
5.1 - made for. Redmi note 4x
https://androidfilehost.com/?fid=1322778262904015883 by k3lt
5.2 —Gcam by bulkin043
https://www.dropbox.com/s/w4x3ozscox5lidq/GoogleCamera.apk?dl=0
6.2 - Gcam by Bulkin043 (has night sight, time-lapse)
https://mega.nz/#!vPQFxYia!wh8AmGhr...n2VQJnw7VKVovduklp_ZkRH1ktJ/view?usp=drivesdk
Check out - https://www.celsoazevedo.com/files/android/google-camera/ for more Gcam builds
Credits :
Alexey711 - Rom Compiler / Developer
Alexey711 - Profile on 4pda.ru
Xda Id: Alexey71
Contributors
alexey71
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: Miui 9 8.5.x or later
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: Development Stopped
Stable Release Date: 2019-04-26
Created 2018-05-22
Last Updated 2019-04-27
We need a space to admiring this perfect ROM, thanks OP for opening the discussion thread ^_^
Magisk Module - to change some defaults - values listed below. Just allows me to turn off Noise Cancellation for Video recording, use fluencepro instead of regular fluence Noise Cancellation and enable EIS by default.
Verified that the getprop command from a ADB shell returns the new values. Looks like the Module is working
Build.prop additions
Code:
Code:
# Add EIS and disable noise cancelation
persist.camera.eis.enable=1
#use fluencepro instead of fluence
ro.vendor.audio.sdk.fluencetype=fluencepro
#turn off noise cancellation for audio recordings
persist.vendor.audio.fluence.voicerec=false
Google Translate of Russian Change Log - (old) https://pastebin.com/raw/zEH3kdjK
Current Log -
https://drive.google.com/drive/mobile/folders/1ylzMJ3VVcFTsbx7iY8NU6l1z2zQ22bpu
Great great rom. Although had a problem with the high temp/signal los bug. Flashed the module from other thread and hope its fixed now. Keep u posted.
Jaco90 said:
Great great rom. Although had a problem with the high temp/signal los bug. Flashed the module from other thread and hope its fixed now. Keep u posted.
Click to expand...
Click to collapse
Which module / recovery zip file has this patch? I haven't seen the bug yet, but i haven't tried heavy gaming on the device, mainly just casual short games
p3dboard said:
Which module / recovery zip file has this patch? I haven't seen the bug yet, but i haven't tried heavy gaming on the device, mainly just casual short games
Click to expand...
Click to collapse
Its in this thread: https://forum.xda-developers.com/showthread.php?p=76334866#post76334866
Backups - Btw, if anyone wants to get SMS Backup, Call History Backup etc, going on Oreo, and you have Root Access (Magisk Root as an example), then you can get it going by opening up a Terminal Window (get Terminal App from Google play).
Then from the terminal run
Code:
su
bmgr run
bmgr backupnow --all
Once its completed, do a reboot, and you'll notice that in your Backup Status, your SMS's, Call Logs, Device Settings etc are now backed up. They should now backup once every 2 Days to your Google Drive, for use if you need to restore your device.
Last time I tried an Oreo Rom, it wasn't backing up, and at that time, I didn't know how to fix it. So I went back to MIUI for a while, so I had the auto backup (yeah I could have used an application for SMS backup, but I wanted the OS to do it )
Jaco90 said:
Its in this thread: https://forum.xda-developers.com/showthread.php?p=76334866#post76334866
Click to expand...
Click to collapse
I just checked out the zip, the file sizes look identical to the ones already in Alexey711's rom. If you look at the change log, he already mentions adding thermal fixes
p3dboard said:
I just checked out the zip, the file sizes look identical to the ones already in Alexey711's rom. If you look at the change log, he already mentions adding thermal fixes
Click to expand...
Click to collapse
Yup, I noticed. Had the same heating bug again today. When driving in the car, the phone gets heated and i loose all signal.
i tried this ROM but cannot find the option to disable quick-setting in secure lockscreen and faceunlock option is absent in smart lock despite using nano gapps.
Skynet:) said:
i tried this ROM but cannot find the option to disable quick-setting in secure lockscreen and faceunlock option is absent in smart lock despite using nano gapps.
Click to expand...
Click to collapse
According to this post, someone fixed the face unlock issue by flashing gapps a second time.
https://www.google.com.au/amp/s/amp.reddit.com/r/LineageOS/comments/5q1awf/no_face_unlock/
I also don't have the option, i will give it a test and let you know.
As for the quick settings, don't know. Is that normally available in LineageOS 15.1? As this is just LineageOS with some extras.
Edit:
Reflashing Gapps enabled face unlock in secure unlock, so for some reason it's not registered properly the first time. So that fix works for me. I am using Micro Gapps package
p3dboard said:
According to this post, someone fixed the face unlock issue by flashing gapps a second time.
https://www.google.com.au/amp/s/amp.reddit.com/r/LineageOS/comments/5q1awf/no_face_unlock/
I also don't have the option, i will give it a test and let you know.
As for the quick settings, don't know. Is that normally available in LineageOS 15.1? As this is just LineageOS with some extras.
Edit:
Reflashing Gapps enabled face unlock in secure unlock, so for some reason it's not registered properly the first time. So that fix works for me. I am using Micro Gapps package
Click to expand...
Click to collapse
Yes reflashing brought back the face unlock but the other option seems to be not there .
p3dboard said:
According to this post, someone fixed the face unlock issue by flashing gapps a second time.
https://www.google.com.au/amp/s/amp.reddit.com/r/LineageOS/comments/5q1awf/no_face_unlock/
I also don't have the option, i will give it a test and let you know.
As for the quick settings, don't know. Is that normally available in LineageOS 15.1? As this is just LineageOS with some extras.
Edit:
Reflashing Gapps enabled face unlock in secure unlock, so for some reason it's not registered properly the first time. So that fix works for me. I am using Micro Gapps package
Click to expand...
Click to collapse
I reflashed gapps but no face unlock working. It doesn't unlock the phone. There is some hidden option?
djgigi94 said:
I reflashed gapps but no face unlock working. It doesn't unlock the phone. There is some hidden option?
Click to expand...
Click to collapse
Yes, after you add your face, you need to go into the screen lock settings and enable the Face Auto unlock feature
hi,
in previous thread I said that autonomy was good, but ultimately it is worse than miui or others 8.1 rom...
May 2018 Security patch build is out
Do we need to flash gapps everytime even on dirty updates?
cimdrap said:
Do we need to flash gapps everytime even on dirty updates?
Click to expand...
Click to collapse
Nope,only flash if you did wipe before updates
If you want to get more Miui level battery performance, you can turn on extreme power savings under battery which restricts background processes and performance.
Miui applies a heavy restriction on background processes

[REQUEST] Patched Vendor Image for GSI Roms

I've noticed that the same issues in all GSIs:
- Broken hotspot
- Notification LED stuck on
- Auto-flash broken
- Broken WiFi (won't matter with custom Kernel with QCACL3)
It's obvious that what we need a custom build vendor. The Mi A1 has the same thing built from 8.1 vendor, which supports all Pie GSIs. Now, I'll be honest, I have little to no knowledge on Android ROM development. I excel in native development in C/C++ in the Android Kernel and the Android userspace. I'll be willing to work with someone to produce a new vendor for the device with patches to allow GSIs to function properly. Contact me on telegram @tytydraco.
Edit: this is the Mi A1 patched vendor: https://github.com/tissot-dev/proprietary_vendor_xiaomi

[GUIDES][LIST][05.03.19] Boot Pie GSIs and Fix Issues [Brightness+Bt+VOLTE]

Hi everyone, I make this thread because even with all others threads in this forum, we still get the same questions all the day. How boot this gsi ?
So here it is, I'll try to keep it up-to-date. I don't have time to try every gsi out there, you can help me if you have other informations
​
OFFICIALS GSIs
PHH-Treble by Phhusson [08.01.2019] BRIGHTNESS FIXED
Use the normal way to install Gsi (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
Resurrection Remix
by Mracar [20.01.2019] Do not try 14th Feb build - Random Reboots
With Oreo Vendor (Thanks to Nikita)
https://forum.xda-developers.com/mi-max-3/how-to/guide-how-to-boot-rr-7-0-mi-max-3-t3892166
From Pie Vendor (Thanks to Lecterr)
I am on Xiaomi.eu 9.1.24 and this TWRP: https://www.androidfilehost.com/?fid...63190603912779
wipe only system, cache, dalvik-cache
flash RR-image
Reboot to system - it boots about a few minutes and reboots to recovery
Reboot to system - it boots into system...thats it!
AOSP Extendedby EnesSatim [19.12.2018]
Can't make boot latest versions (since December)
Older use the normal way to install Gsi (Thanks to Opasha)
VIPER OS by peaktogoo [31.01.2019]
Use the normal way to install Gsi (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
Bug : Vendor error message on boot
ARROW OS
by ArrowOs Team [15.01.2019]
Use the normal way to install Gsi (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
PIXEL DUST by amarbajpai [28.12.2018]
Latest [28.12.19]
With Oreo Vendor (Thanks to Nikita)
https://forum.xda-developers.com/mi-max-3/how-to/guide-how-to-boot-rr-7-0-mi-max-3-t3892166
Older builds
Use the normal way to install Gsi (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
Bootleggers by Dil3mm4
Not booted yet
AOSDP by EchelonTeam
Use the normal way to install Gsi (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
Descendant OS
by Dil3mm4
Use the normal way to install Gsi (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
AOSIP by AOSIP team [24.02.19]
Very Stable (Recommend Pie stable vendor 10.2.1)
Use the normal way to install Gsi (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
UNOFFICIALS GSIs
AOSP Extended unofficial
by Nfound (4pda) [13.01.2019] [15.02.19]
Oreo Vendor (Thanks to Nikita)
https://forum.xda-developers.com/mi-max-3/how-to/guide-how-to-boot-rr-7-0-mi-max-3-t3892166
Pixel Experience Unofficial
by EnesSatim [12.01.2019]
Pie Vendor (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
Xenon HD unofficial
by Nfound (4pda) [28.01.2019]
Pie Vendor (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
Bugs : 28.01.19 can't edit qs tiles
Nitrogen OS Unofficial by Nfound (4pda) [25.01.2019]
Pie Vendor (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
LiquidRemix Unofficial by king1990
Pie Vendor (Thanks to Opasha)
https://forum.xda-developers.com/sh...er button wait 5 min and retry untill it boot
AICP Mordiford Pie by Technical Pie builds here [01.12.2018]
Pie Vendor (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
DirtyUnicorns Unofficial by Peaktogoo [09.01.2019]
Pie Vendor (Thanks to Opasha) / Vendor error on boot.
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
GZOSP Unofficial by Nfound (4PDA) [01.02.2019]
Pie Vendor (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
MSM Xtended
By Nfound (4PDA) [02.02.2019]
Oreo Vendor (Thanks to Nikita)
https://forum.xda-developers.com/mi-max-3/how-to/guide-how-to-boot-rr-7-0-mi-max-3-t3892166
Don't forget to flash Dialer fix after system.img
Bug : No sound over headphones, sound goes to speakers.
SuperiorOS by Nfound [14.02.19]
Oreo Vendor (Thanks to Nikita)
https://forum.xda-developers.com/mi-max-3/how-to/guide-how-to-boot-rr-7-0-mi-max-3-t3892166
Bug : No sound over headphones, sound goes to speakers.
BAIKAL OS
By Nfound [MEDIUM]
Oreo Vendor (Thanks to Nikita)
https://forum.xda-developers.com/mi-max-3/how-to/guide-how-to-boot-rr-7-0-mi-max-3-t3892166
CrDroid By Peaktogoo [OPTIONS]
RR method Oreo Vendor (Thanks to Nikita) (you can try without Post gsi)
https://forum.xda-developers.com/mi-max-3/how-to/guide-how-to-boot-rr-7-0-mi-max-3-t3892166
OmniRom
by King1990
Pir Vendor (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
Havoc OS by Nfound
Issue : No headphone sound
Pie Vendor (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
Bootleggers by Nfound
Vendor : Oreo
Oreo Vendor (Thanks to Nikita)
https://forum.xda-developers.com/mi-max-3/how-to/guide-how-to-boot-rr-7-0-mi-max-3-t3892166
ION by Nfound
Pie Vendor (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
Bliss OS by Nfound
Oreo Vendor (Thanks to Nikita) = long boot without Post or use it but no LED
https://forum.xda-developers.com/mi-max-3/how-to/guide-how-to-boot-rr-7-0-mi-max-3-t3892166
Pie Vendor (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
Dot OS by Nfound
Pie Vendor (Thanks to Opasha)
https://forum.xda-developers.com/showpost.php?p=78061016&postcount=191
Aquarios by Nfound
Oreo Vendor (Thanks to Nikita) = long boot without Post or use it but no LED
https://forum.xda-developers.com/mi-max-3/how-to/guide-how-to-boot-rr-7-0-mi-max-3-t3892166
Syberia OS, LEAN OS, BEAST OS and FRED OS don't boot.
05.03.19 : DU from Nfound not booting too (crash on PIN)
BRIGHTNESS | BLUETOOTH | SOUND | VOLTE | LTE SMS | ETC .. FIXES
A HUGE THANKS to theses people https://forum.xda-developers.com/mi-max-3/how-to/treble-experience-t3856333
PHH Fixes + VOLTE Fix by @MrColdbird
- Brightness
- Bt (Phh way, maybe not working on every gsi, if not, flash Bt fix or replace vendor files)
- Flickering Sound (clean libs)
- Camera API
- VOLTE Fix
- SMS sending fix on 4G
Go here > https://forum.xda-developers.com/showpost.php?p=79039299&postcount=43
All-In-One fix by @lkmnArief
- Bt (Replace Files Vendor)
- Brightness (by Fingerprint)
- Camera API
View attachment MiMax3_Bt_Britghness_gsi_fixes_v1.1.zip
PHH Fixes thanks to @btvbtv
https://forum.xda-developers.com/mi-max-3/how-to/guide-android-9-pie-aosp-phh-treble-rom-t3862708
V110
View attachment phh-treble-pie-fixes-v110.zip
BRIGHTNESS
Install a terminal app
Into it
Type "su" and enter then allow root
? (if you don't have go flash magisk)
Type "setprop persist.sys.qcom-brightness 4095" press enter
BLUETOOTH
NEW* Flashable ZIP with TWRP
thanks to Telegram user @lkmnArief
Download FixGsiBTSound.zip View attachment FixGsiBTSound.zip
_____________________
Old Manual Way
Download file "Vendor-Etc-2018-11-09" Here or attached file
?Need ROOT explorer (if you don't have root go flash magisk)
??Unzip the file
??Copy or Cut and Paste every files in Root directory /vendor/ect some files go on /ect some on /ect/audio. Replace files if already existing. Then set every files to 0644 permission (Rw R -R) and reboot.
? If this technique don't work (can't copy on root directory of missing files after reboot) you'll need to do this changes through TWRP in file manager move every files one by one and one by one set chmod to 0644 for EVERY files. This technique can't fail.
A HUGE THANKS TO :highfive:
Devs mentionned for making Gsi for us
People mentionned for their guides or tips or workarounds or everything else
@Nikitel and Adnan for testing and helping me on Telegram Channel
History of Editions :
02.02.19 : Added AICP Mordiford, Dirty Unicorns Unofficial
08.02.19 : LEAN, BEAST and FRED OS don't boot.
13.02.19 : Added MSM Xtended, New BT flashable fix, Way to boot latest PixelDust, Corrections, Added a picture
15.02.19 : AEX unoff updated [Ok], RR updated [RandomReboots], Added SuperiorOS [HP issue]
17.02.19 : Added Baikal OS, Crdroid and Descendant Os.
19.02.19 : Added OmniRom thanks to @Lecterr + Phh Fixes V110 thanks to @btvbtv
25.02.19 : Added AOSIP (very good gsi) and Bootleggers, New Visual tab
05.03.19 : Added Ion, Dotos, Du, Auqarios, Bliss, and Two new all-in-one fixes for Gsis !
Won't update often the thread because of my exams soon...
Great guide! Thanks Skyllery
Nikitel said:
Great guide! Thanks Skyllery
Click to expand...
Click to collapse
Just forget AICP Mordiford, will add it later. Thx
Sent from my MI MAX 3 using XDA Labs
Very good. Thanks your work helping noobies[emoji1787]
Enviado desde mi MI MAX 3 mediante Tapatalk
Tks very much
Hi,
Thanks for this... But how is this a guide to boot a GSI image ?
Unless I've missed something, it's only a list of GSI ROM with a comment if they boot or not
As far as I am concerned, I tried to install Resurrection Remix following the "How to install RR on mi Max 3".
I sticked to the guide step by step...
In the end, it did not boot and got stuck on RR bootanim...
So my experience : being able to boot a mi Max 3 with a GSI ROM is like the lottery : sometimes you win, but more often you loose
My conclusion ? Treble is a nice idea. Support from manufacturers is terrible...
My question : why are manufacturers so eager to protect their own **** ? What does Xiaomi have to loose if a customer uninstalls MIUI ? Same goes for Huawei. Especially for HUAWEI. They got such a nice feature called eRecovery. In case your device doesn't reboot because you did something wrong, you can always reboot into "eRecovery" and download the latest version of eMUI from there... Evey manufacturer should do that and allow to unlock the bootloader and install a GSI ROM...
I've tested all (all the same) listed here. Most have problems when the device restarts (at least in my case). Any version of October and November work well with either the Oreo or Pie vendor. The only one that worked well now being released in January is NitrogenOS. By the way I used this rom to boot the Havoc released in January and it worked. But by successive installations, in the TWRP appears the message that the system partition needs cleaning. Overall, the idea of GSI is fantastic, but there are so many devices that hardly a rom of these will work perfectly. There will always be a bug here, another bug and nothing working as it needs to. I even cleaned the system partition, but it gave brick and I had to reinstall the miui by fastboot. What we needed was a proper rom for the Mi Max 3, but I find it difficult. I have tried a lot to use some GSI because this miui is more disappointing than the Huawei emui.
NexusPenguin said:
Hi,
Thanks for this... But how is this a guide to boot a GSI image ?
Unless I've missed something, it's only a list of GSI ROM with a comment if they boot or not
As far as I am concerned, I tried to install Resurrection Remix following the "How to install RR on mi Max 3".
I sticked to the guide step by step...
In the end, it did not boot and got stuck on RR bootanim...
So my experience : being able to boot a mi Max 3 with a GSI ROM is like the lottery : sometimes you win, but more often you loose
My conclusion ? Treble is a nice idea. Support from manufacturers is terrible...
My question : why are manufacturers so eager to protect their own **** ? What does Xiaomi have to loose if a customer uninstalls MIUI ? Same goes for Huawei. Especially for HUAWEI. They got such a nice feature called eRecovery. In case your device doesn't reboot because you did something wrong, you can always reboot into "eRecovery" and download the latest version of eMUI from there... Evey manufacturer should do that and allow to unlock the bootloader and install a GSI ROM...
Click to expand...
Click to collapse
1. Under each rom you've the way we get it to boot. It's not a guide but each rom use one way or most to boot. So that's why I get them all together here. And we can update this list when gsi testers on mi max 3 tell me if they boot or not.
2. If you missed to boot RR, consider to change your recovery to Nigel TWRP as we using it. Because with Oreo vendor's way on stable eu 10.2.1. I flash it everytime without problem and already did it 6 or 7 times.
3. We don't have choice to use Gsi until, Nigel make a booting LOS, but pie kernel sources are not out for our phone, we need to wait Miui Pie stable on my opinion.
Germano1980 said:
I've tested all (all the same) listed here. Most have problems when the device restarts (at least in my case). Any version of October and November work well with either the Oreo or Pie vendor. The only one that worked well now being released in January is NitrogenOS. By the way I used this rom to boot the Havoc released in January and it worked. But by successive installations, in the TWRP appears the message that the system partition needs cleaning. Overall, the idea of GSI is fantastic, but there are so many devices that hardly a rom of these will work perfectly. There will always be a bug here, another bug and nothing working as it needs to. I even cleaned the system partition, but it gave brick and I had to reinstall the miui by fastboot. What we needed was a proper rom for the Mi Max 3, but I find it difficult. I have tried a lot to use some GSI because this miui is more disappointing than the Huawei emui.
Click to expand...
Click to collapse
What kind of problems ? Something changed between Oct/November and December/January, don't know why. But with nigel recovery we boot them (listed here). Only LiquidRemix is a bit tricky. But others boot fine.
You tell you boot Havoc latest build with NitrogenOs installed ? Can you explain the way ?
I always wipe everything, flash eu, factory reset and reboot into recovery to continue the installation maybe that's why I never faced this problem in system partition.
Gsi is a solution not THE solution. But at least we've got correct battery life and fixes for bluetooth and brightness. The more annoying.
What twrp are you using ?
Most stable are full stocks, like PE, AOSDP. I use AICP, RR or AEX on my side with a way better SOT on RR. Nitrogen is a good one too.
Regards
question is. do you get much better battery life on these roms compare to EU?
Skyllery said:
1
What kind of problems ? Something changed between Oct/November and December/January, don't know why. But with nigel recovery we boot them (listed here). Only LiquidRemix is a bit tricky. But others boot fine.
You tell you boot Havoc latest build with NitrogenOs installed ? Can you explain the way ?
I always wipe everything, flash eu, factory reset and reboot into recovery to continue the installation maybe that's why I never faced this problem in system partition.
Gsi is a solution not THE solution. But at least we've got correct battery life and fixes for bluetooth and brightness. The more annoying.
What twrp are you using ?
Most stable are full stocks, like PE, AOSDP. I use AICP, RR or AEX on my side with a way better SOT on RR. Nitrogen is a good one too.
Regards
Click to expand...
Click to collapse
At all times I have fc messages on almost everything (system, systemUI and downloaded apps). I always make the installations clean and I always faithfully follow every step to install and I always have these problems. As for Havoc, I installed over nitrogenOS without cleaning anything, and it worked, but it all started to fail continuously. But before that, the Havoc released in January was bootloop. The liquid remix started normally, but when I needed to reboot, it came into bootloop, as well as all roms of December and January. The only ROM that worked well and I was able to reboot the device was nitrogenOS, but when I tried to edit the build.prop in the vendor, when I rebooted the device, the screen did not turn on. And I'm using nijel's TWRP to install the roms. As I said before, there are so many different gadgets that it is impossible for a single rom to work well for everyone.
pakudaboy said:
question is. do you get much better battery life on these roms compare to EU?
Click to expand...
Click to collapse
about the same for me when I used havoc
Germano1980 said:
At all times I have fc messages on almost everything (system, systemUI and downloaded apps). I always make the installations clean and I always faithfully follow every step to install and I always have these problems. As for Havoc, I installed over nitrogenOS without cleaning anything, and it worked, but it all started to fail continuously. But before that, the Havoc released in January was bootloop. The liquid remix started normally, but when I needed to reboot, it came into bootloop, as well as all roms of December and January. The only ROM that worked well and I was able to reboot the device was nitrogenOS, but when I tried to edit the build.prop in the vendor, when I rebooted the device, the screen did not turn on. And I'm using nijel's TWRP to install the roms. As I said before, there are so many different gadgets that it is impossible for a single rom to work well for everyone.
Click to expand...
Click to collapse
What you saying is strange, never facing these issues (system crash or ui or any downloaded app). I think you miss something (wipe data ?) or you don't use eu vendor as base. With bittgapps or opengapps no problem with eu and nigel for any of them. Except Liquid Remix which go easily into bootloop.
Havoc over Nitrogen is interressting, I'll see after my exams. Or if @Nikitel want to try ?
What did you changed in build.prop ?
Btw I'm agree with your last sentence, and we're not many to test them, hard to say what need or don't need to be done. As I'm not a dev, just go forward, blind.
Here's how I install almost every builds. Wipes (cache, dalvik, data, system, sometimes internal) install eu 10.2.1 or 9.1.24 depends, directly reboot into recovery, factory reset, flash mtp fix if needed, system.img and reboot. Sometimes install magisk too before reboot if I use pie gsi over oreo vendor.
Regards
Skyllery said:
Hi everyone, I make this thread because even with all others threads in this forum, we still get the same questions all the day. How boot this gsi ?
So here it is, I'll try to keep it up-to-date. I don't have time to try every gsi out there, you can help me if you have other informations​
Click to expand...
Click to collapse
Thanks Skyllery! If you (or other GSI users) could answer this it would be much appreciated, there are so many options that it's become confusing. I've flashed Nijel's TWRP and Xiaomi.eu 10.2.1 today so I'm ready to choose a GSI and have a play around. I don't really care about having a lot of added features and customizations, I just want everything to work. So my question:
Can any of the GSI's currently be made 'complete' and free of bugs with patches and workarounds? As in every feature working correctly including bluetooth audio streaming, brightness control, etc? Which is the best GSI to install from that point of view?
Many thanks
chongo_au said:
Thanks Skyllery! If you (or other GSI users) could answer this it would be much appreciated, there are so many options that it's become confusing. I've flashed Nijel's TWRP and Xiaomi.eu 10.2.1 today so I'm ready to choose a GSI and have a play around. I don't really care about having a lot of added features and customizations, I just want everything to work. So my question:
Can any of the GSI's currently be made 'complete' and free of bugs with patches and workarounds? As in every feature working correctly including bluetooth audio streaming, brightness control, etc? Which is the best GSI to install from that point of view?
Many thanks
Click to expand...
Click to collapse
As you are on 10.2.1 eu try RR. Except AEX, other need to run a pie vendor. Everything working if you apply correctly patches.
If you want stock google experience, flash 9.1.24 eu and try Pixel Experience or Phh-Treble
Regards
Sent from my MI MAX 3 using XDA Labs
Skyllery said:
As you are on 10.2.1 eu try RR. Except AEX, other need to run a pie vendor. Everything working if you apply correctly patches.
If you want stock google experience, flash 9.1.24 eu and try Pixel Experience or Phh-Treble
Regards
Sent from my MI MAX 3 using XDA Labs
Click to expand...
Click to collapse
Everything went fine until I tried to flash the RR system.img. I followed the steps exactly. I chose Install Image, had System Image selected for where to flash, and chose the image file. It starts to install then says:
Error opening: '/external_sd/system-190120-arm64-aonly-vanilla-nosu.img' (I/O error)
Any idea where I might be going wrong? I might try to download the RR image again
thanks for this guide sir.
chongo_au said:
Everything went fine until I tried to flash the RR system.img. I followed the steps exactly. I chose Install Image, had System Image selected for where to flash, and chose the image file. It starts to install then says:
Error opening: '/external_sd/system-190120-arm64-aonly-vanilla-nosu.img' (I/O error)
Any idea where I might be going wrong? I might try to download the RR image again
Click to expand...
Click to collapse
Sorry, was in exams last days, you fix your problem ? seems to be a image problem yes.
gunzgunz said:
thanks for this guide sir.
Click to expand...
Click to collapse
You're welcome, will update it soon
- beast
- lean
- Fred os
Regards
Sent from my MI MAX 3 using XDA Labs
Skyllery said:
Sorry, was in exams last days, you fix your problem ? seems to be a image problem yes
Click to expand...
Click to collapse
I did, after re-downloading the image I was able to flash RR. Thanks!
im experiencing a bug that i think is not necessarily related to the gsi in question but i dont know anyway. ive installed descendant 2.0 following the rr method and it works impressingly well, but each time i reboot, it boots into nijels twrp and it asks for a password for data decryption. to solve it, ive found that if i reboot via fastboot, i doesnt happen, but this needs a computer so its not very helpful. any idea?
btw awesome work, pretty big from u to help us beginner users this much. thank you very much.

MagiskFixes (Fixing Magisk with Magisk)

Welcome to the MagiskFixes XDA thread!
This module applies a few patches to help Magisk work on GSIs, and maybe a few other devices (targeting Motorola oem at the moment, but more will be added as I get feedback). Obviously it's neither perfect nor universal yet.
Currently targets Motorola and Google devices running either phh or Erfan GSIs, but and Motorola devices running stock.
If you have a fix for a specific device, let me know here! I'll be happy to add it in
As usual, I'm not responsible for any bricking of devices, or things caused by that. No cats were harmed in the making of this module
Currently implemented fixes
- Added a few missing libs for GSIs
- Nuked a Motorola specific boot script (this may depend on how early the module mounts. May need reevaluated on execution)
- Add key layout for phh gsi on Google devices
V1. 2+ uses MMT-ex, and earlier versions used Unity
Thanks to @topjohnwu for Magisk and @Zackptg5 for the template
XDA:DevDB Information
MagiskFixes, Tool/Utility for all devices (see above for details)
Contributors
linuxandria
Source Code: https://github.com/Magisk-Modules-Repo/mgskfixes
Version Information
Status: Stable
Current Stable Version: 1.2.2
Stable Release Date: 2020-03-01
Created 2019-10-03
Last Updated 2020-03-17
Does it work with Moto x4 on PE?(Android 10)
Can you add fingerprint support for gsi on realme 3 pro (rmx1851)
What does should it fix on Motos?
I've two Moto Z2 Force with stock Pie on board and they seems to work fine with Magisk and EdXposed too...
What does should be addressed. on Motos by this module?!?
I'm interested and I can help with testing if needed...
Compatable with Metro PCS Moto e5 Play XT 1921-3 stock rom, rooted with Magisk?
If you're not going to respond to any questions or post about updates, etc then what's the actual point in this thread @linuxandria ?
Listy2021 said:
If you're not going to respond to any questions or post about updates, etc then what's the actual point in this thread @linuxandria ?
Click to expand...
Click to collapse
I've said it before in my other threafs I am significantly more active on telegram than XDA
Thejayyadav said:
Can you add fingerprint support for gsi on realme 3 pro (rmx1851)
Click to expand...
Click to collapse
Not unless I know what's needed
V1. 2.2 released!
Changelog:
- Rework fixes for generic and Motorola
- Add fixes for Google devices (only supports phh GSIs for now)
Wow greate idea
What exactly is fixed with this module the description is very vague if anyone could enlighten me it would greatly be appreciated
Sent from my Phh-Treble vanilla using Tapatalk
@linuxandria might you help out with sepolicy? kindly head over to my post
https://forum.xda-developers.com/t/edxposed-framework-not-recognizing-riru.4334587/post-86405127

MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0

Universal SafetyNet Fix
Magisk module​
Magisk module to work around Google's SafetyNet attestation.
This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS profile attestation, which requires a valid combination of device and model names, build fingerprints, and security patch levels.
If you still have trouble passing SafetyNet with this module, use MagiskHide Props Config to spoof a certified device profile. This is a common issue on old devices, custom ROMs, and stock ROMs without GMS certification (e.g. Chinese ROMs).
Android versions up to 13 Beta 3 are supported, including OEM skins such as Samsung One UI and MIUI.
How does it work?
The way this workaround works is relatively low-level. An in-depth explanation, as well as source code and ROM changes, can be found on GitHub.
Ideally, this workaround should be incorporated in custom ROMs instead of injecting code with a Magisk module. See the ProtonAOSP website for more information.
Downloads
Downloads and changelogs can be found on GitHub. The topmost release is the latest.
Latest release
v2.4.0
Spoiler: Changelog
Highlights
Play Integrity bypass without breaking device checks or causing other issues
Disabled use of hardware attestation on Pixel 7 and newer (@anirudhgupta109)
Other changes
Updated instructions for newer Android and Magisk versions
Better debugging for future development
This version only supports Zygisk (Magisk 24 and newer).
It's taken a while to find a way to bypass Play Integrity that doesn't require spoofing the build fingerprint permanently, but I wanted to make sure this module doesn't cause any unnecessary breakage. Just like the original goal of Universal SafetyNet Fix, this minimizes adverse effects by spoofing dynamically at runtime only when necessary. Enjoy!
If you found this helpful, please consider supporting development with a recurring donation for rewards such as early access to updates, exclusive behind-the-scenes development news, and priority support.
Alternatively, you can also buy me a coffee. All support is appreciated
Source code
Note 8 pro Android 9 and Android 10 not working
Tested succesfully on Pixel 4a 5G, but Google Pay says "Your phone doesn't meet security requirements" even though PayPal can be set up.
Magisk Hide is activated.
Magisk says SafetyNet passes but Google Pay still doesnt
Dydnlee said:
Note 8 pro Android 9 and Android 10 not working
Click to expand...
Click to collapse
Please test it again with this version: https://github.com/kdrag0n/safetynet-fix/archive/e82c3d0674e6452938e49bc6ee6848aa2a603c27.zip
[QUOTE = "kdrag0n, gönderi: 84286879, üye: 7291478"]
Lütfen bu sürümle tekrar test edin : https://github.com/kdrag0n/safetynet-fix/archive/e82c3d0674e6452938e49bc6ee6848aa2a603c27.zip
[/ALINTI]
İnstall failed
Thank you a lot, Universal SafetyNet Fix v1.1.0 working excellent on Xiaomi Mi 9T, Xiaomi.eu 21.1.6, MIUI 12.5 / Android 11 Beta
Device certified but not using Google Pay
Safety net fix 1.0.2 worked for miui Eu 12.0.3.0 Android 10 for Poco F1.
Only that the ocbc bank Singapore app still able to detect the root and became unusable.
But I know that this doesn't relate to safetynet fix here because the issue already existed before the CTS false.
tylerdurden said:
Tested succesfully on Pixel 4a 5G, but Google Pay says "Your phone doesn't meet security requirements" even though PayPal can be set up.
Magisk Hide is activated.
Click to expand...
Click to collapse
Clear app data from Google pay aswell as Google play services.
Tested on Samsung S9:
- 1.0.2 worked in MM, but Root Checker said 'cannot access GPS'.
- 1.1.0 fails ctsProfile in MM, but Root Checker now can access GPS, also returns ctsProfile fail.
Massive thanks for this. Version 1.1.0 confirmed working on my device:
- Pixel 3, stock room
- Magisk 21.2, magisk manager 8.0.5
- Magisk hide enabled and magisk manager renamed
All banking apps and google pay work correctly, including contactless payments.
working on poco f2 pro,android 11,rom one os thanks
Tested on Huawei Mediapad M5 with EMUI 9.1.0 and Magisk 20.4:
- 1.1.0 fails ctsProfile in MM, basic integrity is ok
Working OK on Mi Note 10 Lite, Android 10 and ROM xiaomi.eu
Thanks
I tried this on my Samsung Galaxy A6 (official samsung firmware patched with magisk) - and even version 1.1.0 causes bootloop when using zip inside Magisk Manager - Android 10
Good morning. Working on Redmi Note 9 Pro xiaomi.eu 12.0.1 Android 10. No MagiskHide Props Config needed: basicIntegrity passed, ctsProfile passed, evalType BASIC.
Thank you so much
MI10 Global with V12.2.8 xiaomi.eu , used V 1.0.2 works
Thank you!
Works on pixel 3a, last A10 patch, using magisk hide props config to force basic attestation. Was already using mhpc so not sure if it works without it. Fixed my CTS issue though, so thanks!
@kdrag0n Thank you so much for this awesome masterpiece!
I find it a bit interesting, that I experience a problem which nobody else seems to have reported so far. I'm using a Galaxy S10 (Exynos, G973F), rooted with latest canary Magisk, no EdXposed or whatsoever...
If I enable this module, no bootloop, basic attestation, CTS passes. "Yes", so I thought...
The problem now... My bank app tries to access the keystore and crashes. This does not happen without having this module enabled... I have attached a fully logcat and hope that you have some insights...
EDIT1: re-attached file, didn't work on the first go.
EDIT2: oh... search for "easybank" or "keystore"
EDIT3: Android 11, One UI 3
POCO F1 user here. After flashing the module the phone stucks on the Google logo at boot.
The MHPC module didn't solve the problem either.
ROM: Pixel Experience 11 Beta (20201223)/Encrypted

Categories

Resources