Database Info

Help Camera app not working...

Application of the camera does not work
Yesterday I installed the update of miui 10 V10.2.1.0.OEKMIXM of xiaomi EU after the installation everything correct, but the app of the camera stopped working and I can not make it come back up, install the global version and nothing , the same error, make the wipe cache, data, system all except the misc folder because it throws an error now I'm trying to download the ROM by xioamitool, I read a similar error in this forum but in mi8 and I managed to solve the problem installed a previous ROM but I do not know if miui 10 allows me to return to 9. if someone can help me to download a stable global ROM of miui 9 I would appreciate it.

icemanzor said:
Application of the camera does not work
Yesterday I installed the update of miui 10 V10.2.1.0.OEKMIXM of xiaomi EU after the installation everything correct, but the app of the camera stopped working and I can not make it come back up, install the global version and nothing , the same error, make the wipe cache, data, system all except the misc folder because it throws an error now I'm trying to download the ROM by xioamitool, I read a similar error in this forum but in mi8 and I managed to solve the problem installed a previous ROM but I do not know if miui 10 allows me to return to 9. if someone can help me to download a stable global ROM of miui 9 I would appreciate it.
Click to expand...
Click to collapse
From flash in this file in TWRP > select persist partition > restart the mobile
> https://we.tl/t-uCinDRXFgX

Thank you very much I work, I repair the camera and compass app, total thanks. :fingers-crossed::victory:

douglassillva said:
From flash in this file in TWRP > select persist partition > restart the mobile
> hxxps://we.tl/t-uCinDRXFgX
Click to expand...
Click to collapse
Hi, can you re-send the file? I have the same problem and the link expired already. Thanks!

solmich said:
Hi, can you re-send the file? I have the same problem and the link expired already. Thanks!
Click to expand...
Click to collapse
I also have the same problem.
Tried many roms and standard miui to no avail. Tired the camera2api apks and nada. Camera just not working any more after upgrading to pie...
Any ideas?

cyr1s said:
I also have the same problem.
Tried many roms and standard miui to no avail. Tired the camera2api apks and nada. Camera just not working any more after upgrading to pie...
Any ideas?
Click to expand...
Click to collapse
I've found a solution. So, I download standard miui firmware, 10.3.x in my case (Pie version), and then extract the content. In one of folders, you'll find vendor.img, copy this file to your /sdcard phone. Go to the TWRP terminal and execute this command: dd if=/sdcard/vendor.img of=/dev/block/mmcblk0pYY
YY is the vendor partition number, you can find it using mount command and carefully see which one is. Reboot and all is well. If your TWRP has an option to flash the vendor partition, it would be easier. Mine has no such option.
Read somewhere involving modifying xml file and using miflash, also emergency download mode (since vendor partition is readonly in fastboot), but I've failed to flash and the dd method above is succeeded. YMMV and good luck.
**update: it's persist not vendor, so change accordingly (vendor.img -> persist.img, also the mmcblk)

thanks
solmich said:
I've found a solution. So, I download standard miui firmware, 10.3.x in my case (Pie version), and then extract the content. In one of folders, you'll find vendor.img, copy this file to your /sdcard phone. Go to the TWRP terminal and execute this command: dd if=/sdcard/vendor.img of=/dev/block/mmcblk0pYY
YY is the vendor partition number, you can find it using mount command and carefully see which one is. Reboot and all is well. If your TWRP has an option to flash the vendor partition, it would be easier. Mine has no such option.
Read somewhere involving modifying xml file and using miflash, also emergency download mode (since vendor partition is readonly in fastboot), but I've failed to flash and the dd method above is succeeded. YMMV and good luck.
**update: it's persist not vendor, so change accordingly (vendor.img -> persist.img, also the mmcblk)
Click to expand...
Click to collapse
i had the same problem, and your solution works, i probed it on a redmi note 6 pro, but i flashed persist.img from INSTALL->persist i chose install image and then persist.img, i had probed install other firmwares but this was the only thing that works...Thanks you saved my phone :good:

solmich said:
I've found a solution. So, I download standard miui firmware, 10.3.x in my case (Pie version), and then extract the content. In one of folders, you'll find vendor.img, copy this file to your /sdcard phone. Go to the TWRP terminal and execute this command: dd if=/sdcard/vendor.img of=/dev/block/mmcblk0pYY
YY is the vendor partition number, you can find it using mount command and carefully see which one is. Reboot and all is well. If your TWRP has an option to flash the vendor partition, it would be easier. Mine has no such option.
Read somewhere involving modifying xml file and using miflash, also emergency download mode (since vendor partition is readonly in fastboot), but I've failed to flash and the dd method above is succeeded. YMMV and good luck.
**update: it's persist not vendor, so change accordingly (vendor.img -> persist.img, also the mmcblk)
Click to expand...
Click to collapse
Thx u save my camera too, i have to ask, ur compass works fine too?

solmich said:
Hi, can you re-send the file? I have the same problem and the link expired already. Thanks!
Click to expand...
Click to collapse
Can send it to me as well my camera just Dont want to connect its writing i want to try you way

Redmi Go Aosp 9

Follow the instructions
Files required to be download:
Aosp 9:here
build.prop: here
Flash GSI with TWRP use this fix sd card not read in twrp here
reboot to twrp by pressing power + volume up
Perform a factory reset within TWRP. format data
Download and extract system-arm-aonly-gapps-su.img.xz and you will get system-arm-aonly-gapps-su.img
Transfer the system-arm-aonly-gapps-su.img from your PC to your device’s internal storage where TWRP can access it.
Tap on “Install
Change the type from “zip” to “image.
Find and select the system-arm-aonly-gapps-su.img you downloaded.
Choose to flash to the system partition
no need to flash modified vendor
Once that is done, reboot your device.
Fix : performance copy the build.prop to system/
Bugs: google certification (fix here) after registration clear the google apps data (framewrork/services)
XDA:DevDB Information
Aosp 9 Redmi Go, ROM for all devices (see above for details)
Contributors
samsungics1200, phhusson
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Based On: Aosp 9
Version Information
Status: Testing
Current Beta Version: April 16 2019
Created 2019-04-17
Last Updated 2019-06-11

is there any bug?

Fix : performance copy the build.prop : here copy to system/
Click to expand...
Click to collapse
File needs permission to access - is there another link?

Thanks - the file is available for download now.
I have installed the ROM and it works well but do you know if it is possible to disable the forced device encryption?

Also, my SIM2 is not recognised. Any ideas?

Auto booting to fastboot after installing... (installed to redmi go, it is unlocked, followed instruction, tried minimum 3-4 times, tried several variants of 9.0 Pie GSI etc.)
If You installed 9.0 by the instruction above and it successfully started, it means there is some hardware difference between different region redmi go devices. Mine is Global version.
Stock 8.1 GO is installing and starting normally from TWRP. Problem occurs only with the rom from this thread.
I want to switch to 9.0 beacuse stock 8.1 GO have push notification issue. Believe me, I tried everything to fix it, but unsuccessfully...
Waiting for Your help.

Instructions
NOTE: Do not flash the vendor file from the OP, that causes bootloops on my device.
This is what I did - now happily running AOSP 9:
- Restore stock firmware (http://en.miui.com/download-365.html)
- Reboot then perform system update to get latest release
- Reboot to bootloader (fastboot mode)
- Download the GSI image from the OP
- fastboot flash system system-test-20190415-arm-a.img
- Boot to TWRP recovery
- Mount system partition
- Replace /system/build.prop with one from OP
- Reboot
Additionally, if you want to disable encryption:
- Format data partition (You will loose all of your data!)
- Download vendor image file from OP
- Extract default.prop and fstab.qcom
- Mount vendor partition
- Replace extracted files to phone

Update
Hello to my Russian friends who are following this thread from http://4pda.ru/forum/index.php?showtopic=939092&view=findpost&p=84933744
I have attached the files that need to be replaced to this post

hello guys. i have tried both procedures. it gets stuck on "android" logo (booting i guess).
shall i use vendor? shall not use vendor?
"
- Restore stock firmware (http://en.miui.com/download-365.html)
....
- Replace /system/build.prop with one from OP
- Reboot"
now it should boot?
i tried stopping here, and no luck. i tried doing those "additionally.." steps, same lack of luck.

You only need to touch vendor if you want to disable forced encryption.
These instructions worked when I posted them on 4pda:
- Unlock bootloader - there are instructions elsewhere
- Download: http://treble.phh.me/system-test-20190415-arm-a.img (system.img)
- Download TWRP from other thread (trwp.img)
- Download files.zip from my previous post and extract build.prop
- Power off the phone
- Press volume down and power buttons to go to fastboot bootloader
- Connect your phone to your computer via usb cable
- Type in terminal: fastboot flash system system.img
- Wait for process to finish
- Type in terminal: fastboot boot twrp.img
- Phone will reboot to TRWP recovery mode
- Select "Mount" then "System"
- Type in terminal: adb push build.prop /system/
- Type in terminal: adb shell chmod 600 /system/build.prop
- Reboot phone

If you need GApps, grab the latest pico from https://github.com/opengapps/arm/releases - ie https://github.com/opengapps/arm/releases/download/20190507/open_gapps-arm-9.0-pico-20190507.zip - and install from TWRP.

in locks every time in the "Encryption unsuccessful ... RESET PHONE"

/vendor issue
What process did you use? Did you touch the /vendor partition? Does formatting /data from TWRP help?
Restore stock formware (all partitions from fastboot) then follow steps here: post 10

Camera issue
Only issue I spotted on this ROM for now is - Camera quality became worse. Is it a driver or just app level issue?

This is a Project Treble device which means that the drivers remain untouched in the /vendor partition and the new GSI uses them, unlike older ROMs which contained their own drivers. Which version of firmware did you have before installing the GSI? On 4pda it was observed that camera2 api apps was the issue but I have not seen any such problem.

Just updated to the May 2019 build (v113) and all is good - just had to resize the image to fit the partition. I shall keep updating monthly as long as phh keeps making them.

The ROM from the original post is no longer available. If anyone is interested then I can make an updated GSI available.

Note: FM radio is missing

Kyuunex said:
Note: FM radio is missing
Click to expand...
Click to collapse
Indeed, but the developer is on it, follow progress here: Include FM Radio app

I can't find a gsi that will fit my system partition
need the smallest GSI possible for an obscure mt6580 device
EDIT: would love to try the outdated image that's no longer available ANYWHERE

Lenovo z5 - Install Gcam on stock rom

Not test on custom rom (because i am on stock rom 10.5.254 now).
Please find below steps to use gcam on any Zui rom:
- Root your device with magisk and patched boot
- install root browser and find build.prop in system folder (b4 editing, copy the file to another place and rename to build.prop.bak, then copy back to folder system. Your device will be safe with that new file)
- Open build.prop and copy this code to the bottom:
persist.vendor.camera.HAL3.enabled=1
Persist.vendor.camera.eis.enabled=1
- Reboot the phone
- Install this gcam: https://mega.nz/#!GrRlVSRa!MQjLBbqRKoMhxZjhLfE3pt4hhFDeRKO_dx65ziUtF9Q
Cheers!
P/s: On Zui 10 ported, no need to edit build.prop.

@vosathanh Kindly attach / upload / PM patched boot ZUI 10.5.254 file. Thanks in advance.
After flashing the patched boot file, Should I flash twrp and flash the magisk zip file? magisk zip file is standard i think, i have downloaded in mobile via magisk manager app.

Patched boot here: https://mega.nz/#!amh1kIzB!GChdAWSdNJmSmrgp01Ji9x4U4_riRz9_PLe6tY0vgqw
Install magisk apk 7.1.1 first. Reboot to bootloader and: fastboot flash boot patched_boot.img
Reboot. Done

vosathanh said:
Patched boot here: https://mega.nz/#!amh1kIzB!GChdAWSdNJmSmrgp01Ji9x4U4_riRz9_PLe6tY0vgqw
Install magisk apk 7.1.1 first. Reboot to bootloader and: fastboot flash boot patched_boot.img
Reboot. Done
Click to expand...
Click to collapse
All done camera installed but heavy green tint in front camera, is there any fix?

I don't know. For me no problems.

@vosathanh: I just use Lenovo Z5, it now on ZUI 10.5.254 ST, can you help me how to root and install twrp please.
Tks!

vosathanh said:
I don't know. For me no problems.
Click to expand...
Click to collapse
Which is the last Zui version on the top of oreo?

umarbest said:
Which is the last Zui version on the top of oreo?
Click to expand...
Click to collapse
It's 4.0.474. my gcam run very good. Really love gcam.

Any way to encrypt /data/data and /sdcard on Xiaomi EU ROM?

Hello,
Xiaomi EU ROM is running decrypted, that's a security breach...
Is there a way to use Xiaomi EU ROM, based on Miui 10, in a encrypted phone?
Thanks

I tried but no success. The only method to enable encryption is miflash official rom. For me it works perfectly in Los. Apparently xiaomi Eu removed encryption from vendor.

And there is no way to add the files to the vendor partition?

I am using the EU ROM for months encrypted (FBE).
It's a little complicated to get there (and to stay), but it can be done.
1. You need to come from an encrypted MIUI Rom
2. Enter TWRP, enter your decryption code.
Important note: NEVER format in TWRP, otherwise you'll have to start from MIUI again (which means flashing with MiFlash).
4. Dirty flash EU Rom. Do NOT reboot.
5. After flashing the ROM, go to the main menu in TWRP and mount the Vendor partition.
6. Install the attached Zip file with TWRP (copy to phone before starting the whole procedure steps)
7. Reboot
As I said I followed this procedure for the last months, running EU and still encrypted.
You have to do ALL the steps 2-7) again EVERYTIME you flash a new EU Rom.

Hello,
Thanks for the answer. I will try it, but...
1) After flash this, I can wipe device (not format) from TWRP?
2) Is also /sdcard encrypted or only /data/data?
3) I can't install Global MIUI from TWRP if I will return to Global?
4) I assume that I can install Magisk after 6 and before 7
Thanks
hoehm72 said:
I am using the EU ROM for months encrypted (FBE).
It's a little complicated to get there (and to stay), but it can be done.
1. You need to come from an encrypted MIUI Rom
2. Enter TWRP, enter your decryption code.
Important note: NEVER format in TWRP, otherwise you'll have to start from MIUI again (which means flashing with MiFlash).
4. Dirty flash EU Rom. Do NOT reboot.
5. After flashing the ROM, go to the main menu in TWRP and mount the Vendor partition.
6. Install the attached Zip file with TWRP (copy to phone before starting the whole procedure steps)
7. Reboot
As I said I followed this procedure for the last months, running EU and still encrypted.
You have to do ALL the steps 2-7) again EVERYTIME you flash a new EU Rom.
Click to expand...
Click to collapse

I reply my questions:
After flash EU ROM and the ZIP that @hoehm72 in the previous posts, the EU ROM is working fine.
You can wipe the device from TWRP and also return to Global version (you need to backup your /cust partition before flash EU for first time and restore /cust before flash Global ROM).
Also, /sdcard and /data/data remains encrypted in EU, like in Global.
Thanks mate!
EDIT: If you forgot to flash the zip file after flash EU ROM the phone will enter in a bootloop. No problem, you only need to enter TWRP then:
* mount vendor
* edit /vendor/etc/fstab.qcomm
then update "encryptable" by "fileencryption" then reboot...

Thank you, it worked for me too!

Hello how can I know if my rom is encrypted ?

If your device is rooted...
enter TWRP and, when TWRP asks for password click on cancel button.
Next, click on advanced -> file manager then navigate to /sdcard
If when you are on /sdcard (and also on /data/data) the file manager displays correctly the filenames you aren't encrypted and any can access to the files if has access to your device.
Bradco said:
Hello how can I know if my rom is encrypted ?
Click to expand...
Click to collapse

Bradco said:
Hello how can I know if my rom is encrypted ?
Click to expand...
Click to collapse
You can find it in settings-passwords&security- data privacy(or data security, I don't know in english) -encryption

The most secure mode to check it is to check over twrp, like I've explained.
Some roms, like eu, says encrypted but really aren't
Seosam said:
You can find it in settings-passwords&security- data privacy(or data security, I don't know in english) -encryption
Click to expand...
Click to collapse

This is what i posted some thime ago in xiaomi.eu forum.
I downloaded miui_MIMIX2SGlobal_V10.3.2.0.PDGMIXM_7e27e6e0d5_9.0.zip and xiaomi.eu_multi_MIMix2S_V10.3.1.0.PDGCNXM_v10-9.zip
than i extracted these folder and three files from global rom:
firmware-update
vendor.transfer.list
vendor.new.dat.br
vendor.patch.dat
than i deleted those three files and folder from xiaomi.eu rom
than i repacked xiaomi.eu rom with three vendor files from global rom (i used winrar, just drag and drop )
than i installed .zip on my phone
I managed to encrypt the latest (9.7.11) version too. You need to use vendor files from china beta (9.7.11). If you use older files your wifi wont work.

A less painful solution is to extract missing files from china rom
The file lists that should be added/replaced from china miui rom (about 3 MB, tested on Mi6 10.4.2.0, eu/cn):
Ps., some of below files are not necessary, but I am not sure which one did the trick.
/system/vendor/etc/gps.conf
/system/vendor/etc/mixer_paths_overlay_dynamic.xml
/system/vendor/etc/init/hw/init.qcom.rc
/system/vendor/etc/izat.conf
/system/vendor/etc/wifi/WCNSS_qcom_cfg.ini
/system/vendor/etc/fstab.qcom
/system/vendor/app/TrustZoneAccessService/TrustZoneAccessService.apk
/system/vendor/app/TrustZoneAccessService/oat/arm64/TrustZoneAccessService.odex
/system/vendor/app/TrustZoneAccessService/oat/arm64/TrustZoneAccessService.vdex
/system/vendor/app/ConnectionSecurityService/oat/arm64/ConnectionSecurityService.odex
/system/vendor/app/ConnectionSecurityService/oat/arm64/ConnectionSecurityService.vdex
/system/vendor/app/PowerOffAlarm/oat/arm64/PowerOffAlarm.vdex
/system/vendor/app/PowerOffAlarm/oat/arm64/PowerOffAlarm.odex
/system/vendor/app/PowerOffAlarm/PowerOffAlarm.apk
/system/vendor/app/SSGTelemetryService/oat/arm64/SSGTelemetryService.odex
/system/vendor/app/SSGTelemetryService/oat/arm64/SSGTelemetryService.vdex
/system/vendor/app/TimeService/oat/arm64/TimeService.odex
/system/vendor/app/TimeService/oat/arm64/TimeService.vdex
/system/vendor/app/TimeService/TimeService.apk
/system/vendor/lib/mediadrm/libdrmclearkeyplugin.so
/system/vendor/lib/mediadrm/libwvdrmengine.so
/system/vendor/lib/libmmcamera_imx386_semco.so
Obviously, in android 9 based miui 10, xiaomi.eu has removed encryption files from vendor, not just modified "fstab.qcomm".
On Mi6 10.4.2.0, I successfully encrypted /sdcard/ with above files.

In fact, you only need to replace fstab.qcomm at vendor/etc from the one included at eu miui from the one at stock rom.
This file as a size if 2KB
watert said:
Sorry, but I will add the file lists that should be added/replaced from china miui rom in hours later (about 3 MB).
Click to expand...
Click to collapse

Modification of "vendor/etc/fstab.qcomm" worked on android 8 based xiaomi.eu's miui, but not for android 9 based xiaomi.eu's miui -- at least for MI6.
If you only modify fstab.qcomm, but do not copy files which actually did the encryption job, encryption is fake (although it showed encrypted on "setting"). Check this by : goto twrp, click 'cancel' when it asks for gesture, then you would find you can still access files on /sdcard/ (without encryption).
bartito said:
In fact, you only need to replace fstab.qcomm at vendor/etc from the one included at eu miui from the one at stock rom.
This file as a size if 2KB
Click to expand...
Click to collapse

I have only modified fstab file and my device is encrypted (see screenshot).
The only that you need to do it not to do a format data under twrp after install EU ROM.
This is due the phone encryption will be done in global ROM. EU is not capable to do it even with the modified fstab, 9nly that can do is to manage a previously encrypted partition.
watert said:
Modification of "vendor/etc/fstab.qcomm" worked on android 8 based xiaomi.eu's miui, but not for android 9 based xiaomi.eu's miui.
If you only modify fstab.qcomm, but do not copy files which actually did the encryption job, encryption is fake (although it showed encrypted on "setting"). Check this by : goto twrp, click 'cancel' when it asks for gesture, then you would find you can still access files on /sdcard/ (without encryption).
Click to expand...
Click to collapse

Yes, that is one way. but I'd like to format/wipe everything in twrp before flashing.
If data partition was formated, I think ~3 MB files from china rom are necessary for encryption.
bartito said:
I have only modified fstab file and my device is encrypted (see screenshot).
The only that you need to do it not to do a format data under twrp after install EU ROM.
This is due the phone encryption will be done in global ROM. EU is not capable to do it even with the modified fstab, 9nly that can do is to manage a previously encrypted partition.
Click to expand...
Click to collapse

Please, post the files when possible. I will check. Thanks
watert said:
Yes, that is one way. but I'd like to format/wipe everything in twrp before flashing.
If data partition was formated, I think ~3 MB files from china rom are necessary for encryption.
Click to expand...
Click to collapse

hoehm72 said:
I am using the EU ROM for months encrypted (FBE).
It's a little complicated to get there (and to stay), but it can be done.
1. You need to come from an encrypted MIUI Rom
2. Enter TWRP, enter your decryption code.
Important note: NEVER format in TWRP, otherwise you'll have to start from MIUI again (which means flashing with MiFlash).
4. Dirty flash EU Rom. Do NOT reboot.
5. After flashing the ROM, go to the main menu in TWRP and mount the Vendor partition.
6. Install the attached Zip file with TWRP (copy to phone before starting the whole procedure steps)
7. Reboot
As I said I followed this procedure for the last months, running EU and still encrypted.
You have to do ALL the steps 2-7) again EVERYTIME you flash a new EU Rom.
Click to expand...
Click to collapse
For me this works with actual miui eu.
I checked it in TWRP too.
But maybe you need these 3MB when you do a clean start, without official miui first.

Seosam said:
For me this works with actual miui eu.
I checked it in TWRP too.
But maybe you need these 3MB when you do a clean start, without official miui first.
Click to expand...
Click to collapse
absolutely agree

Magisk/Twrp for GSI (Won't work on stock)

I have a Twrp backup with the boot img patched with Magisk/Twrp boot to recovery boots GSI with magisk boot to recovery hold volume up while rebooting to recovery will boot twrp for this boot img to work u have to be on the vendor of the boot img which is also in the backup so the phone won't bootloop this vendor is modified to work with GSIs pass the magisk environmental setup and notch fix so swiping down is like swiping down on stock.... to implement notch fix go to developer settings hide display cut and choose the first hide option and your notch will be fixed...
Thanks @Spaceminer for the twrp for without this none would of been possible
please note twrp will only boot with a android 9 vendor and your GSI will only boot with magisk and twrrp with the vendor in the backup cause it matches the boot img, GSIs only boot when the vendor and boot img match
the boot img & vendor img in the backup is from Channel/Retail (PPY29. 105-160-4)
Instructions
If on android 9 stock
1. Boot to bootloader
2. fastboot - w
3. fastboot GSI of your choice
4. fastboot boot twrp.img
5. format data
6. Place the twrp folder you downloaded from the zip into your devices internal storage which will be available after u format data
7.Resize system
8.Flash gapps zip if gapps is needed
9.wipe dalvick
10. go to twrp restore boot and vendor
11. reboot to recovery and phone will boot after boot is complete install magisk manager it will do the environmental setup phone will reboot and u will have magisk.... ( if u want the best experience with magisk on this device I recommend that you use havoc cause with the lineage GSI magisk doesn't play nice but with havoc its stable also when making a backup it's boot, system image, vendor image, data if u chose system instead your backup will bootloop your device upon restoration)
Download (twrp img is in twrp folder remove it and place it in ADB folder)
https://mega.nz/file/7t03DLhL#jjS9vgrJMlDS-_-hsApyx4uJ6L8wXCN8HtjSqJrg2ds
if u wanted to do this manually to install the latest canary or stable version magisk need to patch twrp to the recovery flash phh root boot up install magisk manager give it root permissions with phh superuser from apk mirror now with elevated permissions the option patch directly will be avaliable cause u got root (it's the recommended option ?) chose recovery and leave the other 2 unchecked patch the img and reboot to recovery the phone will reboot os with magisk and u hold up while booting recovery will boot twrp after that backup that boot img in twrrp for future installation of the GSI of your choosing....

Hello,
Already figured it out.
Is there any way to flash a Android 10 ROM (treble) without loosing magisk ?
thanks for your help!

xcode22 said:
Hello,
Already figured it out.
Is there any way to flash a Android 10 ROM (treble) without loosing magisk ?
thanks for your help!
Click to expand...
Click to collapse
Everytime u flash a GSI just use the vendor and boot from the twrp folder and your android 10 GSI Will have magisk and twrp no need for data disabler zip cause my backup already has the vendor and boot patches enabled for decryption so twrp will be accessible via boot to recovery
([emoji88]Havoc GSI[emoji88])

Also have edxposed for Android 10 since the one in the repo won't work cause it needs a custom magisk with merged patches for xposed to work on android 10 this version has the patches in the edxposed so having to use a custom magisk won't be an issue cause as ya know obtaining magisk and twrrp in this device was unknown into this OP was made
([emoji88]Havoc GSI[emoji88])

Thanks so much for the instructions, only way i could install on G7 play.
The only thing is I always have to boot in recovery mode to start the system.
If I boot normal it starts again. Any way to solve this ?
I think somehow I flashed my ROM to the recovery partition ?
thank you!!

xcode22 said:
Thanks so much for the instructions, only way i could install on G7 play.
The only thing is I always have to boot in recovery mode to start the system.
If I boot normal it starts again. Any way to solve this ?
I think somehow I flashed my ROM to the recovery partition ?
thank you!!
Click to expand...
Click to collapse
Your on a GSI go in your system settings and activate advance boot and when u have to reboot just put reboot to recovery and you don't have to worry about manually rebooting to recovery everytime u have to reboot also no way u installed the rom to the recovery partion our device doesn't have a recovery partion the recovery lives within the boot img
([emoji88]Havoc GSI[emoji88])]

thanks, not sure if I can do this with my Treble gsi (phhusson).
The other thing is that some things got messed up after instalation for example I cannot put in a passcode for the phone.
Is there no other way to install magisk on the G7 play ?
Maybe this has to do with the vendor and boot beeing different model than mine wich is XT 1952-2 (latin american model)
thanks

xcode22 said:
thanks, not sure if I can do this with my Treble gsi (phhusson).
The other thing is that some things got messed up after instalation for example I cannot put in a passcode for the phone.
Is there no other way to install magisk on the G7 play ?
Maybe this has to do with the vendor and boot beeing different model than mine wich is XT 1952-2 (latin american model)
thanks
Click to expand...
Click to collapse
The reason the lockscreen doesn't work is cause the device is decrypted which is essential for the device to be able to reboot to twrp my vendor has the decryption patches for the full functionality of twrp however if u don't care about twrp and just want magisk just patch a fresh version of your boot img in magisk manager with the patch a file option and fastboot that boot img to your device install fresh GSI with your vendor so it will boot encrypted since your vendor doesn't have the decryption zip patches in the vendor... However with this method to have full functionality with magisk u will have to remove from vendor/bin/init mimi hab if this file isn't removed your magisk won't pass the environmental setup... U be given root privileges with magisk before u have to do the environmental setup so u can remove that file...
([emoji88]Havoc GSI[emoji88])

PoochyX said:
The reason the lockscreen doesn't work is cause the device is decrypted which is essential for the device to be able to reboot to twrp my vendor has the decryption patches for the full functionality of twrp however if u don't care about twrp and just want magisk just patch a fresh version of your boot img in magisk manager with the patch a file option and fastboot that boot img to your device install fresh GSI with your vendor so it will boot encrypted since your vendor doesn't have the decryption zip patches in the vendor... However with this method to have full functionality with magisk u will have to remove from vendor/bin/init mimi hab if this file isn't removed your magisk won't pass the environmental setup... U be given root privileges with magisk before u have to do the environmental setup so u can remove that file...
([emoji88]Havoc GSI[emoji88])
Click to expand...
Click to collapse
Yes I understand, sounds logic. I tried to follow your guide but it didn't work.
I did the following:
1. Followed your first instructions with restore vendor and boot in the end to have magisk twrp (Now on Android 10).
2. patched the boot.img (stock one Android 9) with magisk and pulled via adb on computer
3. fastboot flash boot boot.img (patched)
4. Fastboot flash system gsi.img (android 10)
After that I get a bootloop if I go via normal boot and recovery doesn?t boot either.
In the end I tried to flash the stock vendor.img but everything stayed the same.
Not sure how to remove the file in the /vendor/bin, with twrp ?

xcode22 said:
Yes I understand, sounds logic. I tried to follow your guide but it didn't work.
I did the following:
1. Followed your first instructions with restore vendor and boot in the end to have magisk twrp (Now on Android 10).
2. patched the boot.img (stock one Android 9) with magisk and pulled via adb on computer
3. fastboot flash boot boot.img (patched)
4. Fastboot flash system gsi.img (android 10)
After that I get a bootloop if I go via normal boot and recovery doesn?t boot either.
In the end I tried to flash the stock vendor.img but everything stayed the same.
Not sure how to remove the file in the /vendor/bin, with twrp ?
Click to expand...
Click to collapse
PoochyX on telegram dm me I walk you threw it
([emoji88]Havoc GSI[emoji88])

xcode22 said:
Yes I understand, sounds logic. I tried to follow your guide but it didn't work.
I did the following:
1. Followed your first instructions with restore vendor and boot in the end to have magisk twrp (Now on Android 10).
2. patched the boot.img (stock one Android 9) with magisk and pulled via adb on computer
3. fastboot flash boot boot.img (patched)
4. Fastboot flash system gsi.img (android 10)
After that I get a bootloop if I go via normal boot and recovery doesn?t boot either.
In the end I tried to flash the stock vendor.img but everything stayed the same.
Not sure how to remove the file in the /vendor/bin, with twrp ?
Click to expand...
Click to collapse
The easiest way I know of is from the stock OS using termux and root.
Code:
su
setenforce 0
mkdir /mnt/x && chmod 0755 /mnt/x
mount -o loop /dev/block/by-name/vendor_a /mnt/x
Now navigate to /mnt/x and everything from vendor will be in there. Find the file and delete it with a root explorer. Then unmount the partition and the changes will be permanent. Doing it this way gets around FEC, which is what prevents you from changing anything in vendor.
Code:
umount /mnt/x
If you need to work on the other vendor partition just change out vendor_a with vendor_b

Any recommendation about what GSI to choice for XT1952-6 variant?

mickem said:
Any recommendation about what GSI to choice for XT1952-6 variant?
Click to expand...
Click to collapse
Chaos GSI Bluetooth works without disabling audio effects (so u can use viper with bluetooth headset) it's clean stock with minimum stuff added to it and works with gravitybox then you got havoc that has the majority of stuff gravity has off the rip so it's not as minimum so more memory usage is needed and Bluetooth only works with the phh disable audio effects work around also magisk works good on both of these lineage is good also if you don't care about magisk working cause with our device magisk has issues on lineage don't know if it was fixed on a recent bulid however if lineage is your preference there is a phh root for it so u can be functional
([emoji88]Havoc GSI[emoji88])

My device is xt1952-4. I downloaded the latest firmware (PPYS29-105-160-4-8), and installed it to both slots. I am currently using Resurection Remix Pie. Is your patched boot.img and vendor compatible with the newer firmware or will I get a downgrade error?