Database Info

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.

[Guide] Magisk manager installation on Mi CC 9

If you install twrp recovery then it is very easy to install magisk manager.
just go on your twrp recovery mode
Select advanced and select install root.
Reboot your Phone .
See magisk manager install successfully.
Any help about mi cc9 magisk manager just coment here. I will be ready for replay just like you want.
.
Or Download this file and install through twrp recovery.
Latest stable magisk manager zip [flash file]
https://drive.google.com/file/d/1j6EWKPt1ZNzW7QgtILkgW5xphCzzcKNH/view?usp=drivesdk
Magisk manager apk
https://drive.google.com/file/d/1Hzvi5f2bZcUPyzWx-ETfqZanQjLCJHGq/view?usp=drivesdk

Lijlp0/02plppp000p7 lu6pppp?0lpl
Ul u?????//6000

I've installed magisk without twrp, just follow guide online. No need specific software because 7zip can extract boot.img easily from update file. After that install magisk manager app on phone, select install - patch own boot file, copy modified file to pc again, reboot into bootloader, flash modified boot.img and reboot.

eidrag said:
I've installed magisk without twrp, just follow guide online. No need specific software because 7zip can extract boot.img easily from update file. After that install magisk manager app on phone, select install - patch own boot file, copy modified file to pc again, reboot into bootloader, flash modified boot.img and reboot.
Click to expand...
Click to collapse
I need unlock BL to flash the modded boot.img?

RazrBR said:
I need unlock BL to flash the modded boot.img?
Click to expand...
Click to collapse
Yes, first unlock BL to be able to enter fastboot mode. Apply to unlock bootloader with Mi account, please follow guide on how to unlock the bootloader.

eidrag said:
I've installed magisk without twrp, just follow guide online. No need specific software because 7zip can extract boot.img easily from update file. After that install magisk manager app on phone, select install - patch own boot file, copy modified file to pc again, reboot into bootloader, flash modified boot.img and reboot.
Click to expand...
Click to collapse
Hi. Did you do these passages also on MIUI 12? Because I installed Magisk app, but it showed Ramdisk: no, and now I don't know if I should install it in recovery partition or not

there's twrp and orangefox that can be used for cc9 meitu/vela. Unlock bootloader, enable adb, flash custom recovery by fastboot. After that use custom recovery to install magisk. I'm sorry I don't use cc9 anymore since last weekend because miui12 notification and permission is too aggressive, have to restart app everytime so that can get contact info.

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?

[Magisk][Recovery] Fully install/Upgrade Magisk through recovery mode ?

Hello,
I have a problem with my FP3. When I flash the Magisk zip with TWRP or when I flash the patched boot image through Fastboot mode, Magisk is not completely installed. I need to boot et click on the "Magisk app" with a standard icon to install it and to access Magisk Manager. Without this, Magisk is not really installed since "su" or magisk executable are not in /sbin.
I need a way to manually install/upgrade Magisk through recovery (TWRP) to obtain the su. In my context, I have constraints preventing the installation through GUI.
Have you already done this before ?

Question: Keeping root from OOS 11 to C.11 (OOS 12)

Hey everyone! Finally got the update for C.11 on my phone, but looking around it looks like the way to keep root from OOS 11 to OOS 12 has changed a bit, compared to the standard updates and keeping root. So right now, I'm on 11.0.12.12.KB05AA and have the update KB2005_11.C.16 and if I want to keep root I need to do the following:
B.2.1 Local Install​This is using:
OOS 11: System Update>Gear icon (local install)
OOS 12: MyApplication2 app (source: https://oxygenos.oneplus.net/English_20220225101104.apk; see https://forums.oneplus.com/threads/oxygenos-12-for-the-oneplus-8t.1555060/)
If you have TWRP installed then reboot recovery, restore the stock OOS recovery (you would/should have taken a copy of it when you installed TWRP as mentioned in A.2.1), and reboot system. Without doing this, an incremental OTA will fail when it checks for the stock recovery.
Move the update zip to /sdcard (NOT a subdirectory of /sdcard)
Magisk>Uninstall Magisk>Restore images - this restores the stock boot image whilst keeping Magisk
Install the update using the appropriate local installer for your version of OOS and DO NOT reboot
Restore root to the current slot using Magisk>Magisk Install>"Direct Install (Recommended)". This is so you keep root in case the update somehow fails and you're returned to the current system.
Root the updated boot image using Magisk>Magisk Install>"Install to inactive slot" and reboot
To re-install TWRP, follow the process in A.2.1
Is that all I have to do to keep root when going from OOS 11 to OOS 12? I've seen other methods where people need to use payload dumper to extract the boot img and patch it, then flash it. I can do that, it's just a pain in the neck is all.