Database Develop

I can't install Magisk v14

after reformatting my device and flashing stock rom through twrp, i went and download the zip file with magisk manager latest version and then i fully unroot my device with full unroot of supersu. after i rebooted to twrp, i installed magisk v14 zip and this is what it tells me after i flashed it.
Installing '/sdcard/Magisk-v14.0.zip...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
************************
* Magisk v14.0 Installer
************************
- Mounting /system, /vendor, /cache, /data
- Device platform: arm
- Constructing environment
! Unable to detect boot image
- Unmounting partitions
E: Error executing updater binary in zip ' /sdcard/Magisk-v14.0.zip'
Error flashing zip ' /sdcard/Magisk-v14.0.zip'
Updating partition details...
...done
i have few questions.
1. unable to detect boot image. what do you mean by that? where can i get this boot image?
2. what's that updater binary in the zip file?
what can i do to be able to use magisk? thank you in advance
my device is oppo neo 7 android 5.1

The boot image is a part of your device's software. It's what Magisk modifies to do it's thing. If the installer can't recognise it, there's not much you can do... Except providing logs, that is.
The update binary is a part of the installer. It's the script that modifies the boot image to install Magisk on your device.
When you have these kind of errors, save the recovery log after flashing the zip (Advanced -> Copy Log) and post that (attach it or use Pastebin or similar, don't copy it directly to the post). It's so much easier to troubleshoot with proper logs.
First thing you can try is to use the latest beta and see if that works.

Didgeridoohan said:
The boot image is a part of your device's software. It's what Magisk modifies to do it's thing. If the installer can't recognise it, there's not much you can do... Except providing logs, that is.
The update binary is a part of the installer. It's the script that modifies the boot image to install Magisk on your device.
When you have these kind of errors, save the recovery log after flashing the zip (Advanced -> Copy Log) and post that (attach it or use Pastebin or similar, don't copy it directly to the post). It's so much easier to troubleshoot with proper logs.
First thing you can try is to use the latest beta and see if that works.
Click to expand...
Click to collapse
i got the log, how do i upload it here? im only using android browser.
so itried to install magisk v14 and it didnt detect bootimg but v14.5 did detect but still failed to install.

rajoholic said:
i got the log, how do i upload it here? im only using android browser.
so itried to install magisk v14 and it didnt detect bootimg but v14.5 did detect but still failed to install.
Click to expand...
Click to collapse
I guess you can't attach a file, being so new... You can upload it somewhere and provide the link or use Pastebin and provide the link/id for it.

Didgeridoohan said:
I guess you can't attach a file, being so new... You can upload it somewhere and provide the link or use Pastebin and provide the link/id for it.
Click to expand...
Click to collapse
https://dropmb.com/download/aca1616df3f0d913cb70d1f88176d9d4.html
here it is. thanks for the help

I m also facing same problem
rajoholic said:
after reformatting my device and flashing stock rom through twrp, i went and download the zip file with magisk manager latest version and then i fully unroot my device with full unroot of supersu. after i rebooted to twrp, i installed magisk v14 zip and this is what it tells me after i flashed it.
Installing '/sdcard/Magisk-v14.0.zip...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
************************
* Magisk v14.0 Installer
************************
- Mounting /system, /vendor, /cache, /data
- Device platform: arm
- Constructing environment
! Unable to detect boot image
- Unmounting partitions
E: Error executing updater binary in zip ' /sdcard/Magisk-v14.0.zip'
Error flashing zip ' /sdcard/Magisk-v14.0.zip'
Updating partition details...
...done
i have few questions.
1. unable to detect boot image. what do you mean by that? where can i get this boot image?
2. what's that updater binary in the zip file?
what can i do to be able to use magisk? thank you in advance
my device is Micromax canvas nitro a310 current android version is cyanogen mode 13
Click to expand...
Click to collapse

rajoholic said:
https://dropmb.com/download/aca1616df3f0d913cb70d1f88176d9d4.html
here it is. thanks for the help
Click to expand...
Click to collapse
That was a bit of a shady file sharing site. Anyway...
Your installed TWRP is pretty old. That might have something to do about it. Update TWRP, or you could try letting the Magisk Manager patch the boot image and then flash the patched image with TWRP. Installation instructions in the release thread.

Didgeridoohan said:
That was a bit of a shady file sharing site. Anyway...
Your installed TWRP is pretty old. That might have something to do about it. Update TWRP, or you could try letting the Magisk Manager patch the boot image and then flash the patched image with TWRP. Installation instructions in the release thread.
Click to expand...
Click to collapse
sorry bout that. i just search the google free and temporary storage online. haha! thank you for the help. I'll try what u just said

Didgeridoohan said:
That was a bit of a shady file sharing site. Anyway...
Your installed TWRP is pretty old. That might have something to do about it. Update TWRP, or you could try letting the Magisk Manager patch the boot image and then flash the patched image with TWRP. Installation instructions in the release thread.
Click to expand...
Click to collapse
how do i flash the patched boot.img with twrp? i cant find it in my sd card. it's not showing up. i already got the patched boot img

rajoholic said:
how do i flash the patched boot.img with twrp? i cant find it in my sd card. it's not showing up. i already got the patched boot img
Click to expand...
Click to collapse
Hm.... It might be that your TWRP is to old, but it should be the same procedure as when flashing a zip file except you switch to image flashing by pressing the "Image" button after going to the "Install" screen.
If that doesn't work, use fastboot (or whatever is available for your device).
Code:
fastboot flash boot patched_boot.img

Didgeridoohan said:
Hm.... It might be that your TWRP is to old, but it should be the same procedure as when flashing a zip file except you switch to image flashing by pressing the "Image" button after going to the "Install" screen.
If that doesn't work, use fastboot (or whatever is available for your device).
Code:
fastboot flash boot patched_boot.img
Click to expand...
Click to collapse
So I did what u told me and flashed the boot.img succesfully. Now after flashing that, I flashed v14 and still error in executing update binary. Same with 14.5. But this time after I saw that, I rebooted my device and found magisk manager on my phone. It says v14 installed. Is it installed already?

rajoholic said:
So I did what u told me and flashed the boot.img succesfully. Now after flashing that, I flashed v14 and still error in executing update binary. Same with 14.5. But this time after I saw that, I rebooted my device and found magisk manager on my phone. It says v14 installed. Is it installed already?
Click to expand...
Click to collapse
Yes, if you flash the patched boot image you don't have to do anything else. The Magisk Manager has already taken care of everything.
If you want v14.5 beta, you should now be able to change the update channel (in Manager settings) to beta and update. Just as a FYI, you could have done this already when patching the boot image.
Sounds like it's working now, or? Can you install modules?

Didgeridoohan said:
Yes, if you flash the patched boot image you don't have to do anything else. The Magisk Manager has already taken care of everything.
If you want v14.5 beta, you should now be able to change the update channel (in Manager settings) to beta and update. Just as a FYI, you could have done this already when patching the boot image.
Sounds like it's working now, or? Can you install modules?
Click to expand...
Click to collapse
I installed an app and gave it root permission. It looks like it's working. However the module part, I'm still unsure. When I try to add modules, the screen took me in storage. Looks like it requires me to import something? Where can I download modules?

rajoholic said:
I installed an app and gave it root permission. It looks like it's working. However the module part, I'm still unsure. When I try to add modules, the screen took me in storage. Looks like it requires me to import something? Where can I download modules?
Click to expand...
Click to collapse
First of all, don't even mention that piece of piracy software on xda. It's used to steal from developers and is not allowed here.
In the "Modules" part you can manually install modules that you've previously downloaded. If you want to install directly from the Magisk repo, you (unsurprisingly ) go to the "Downloads" section of the Manager. If you can't see "Downloads", make sure the Manager has internet access.

Didgeridoohan said:
First of all, don't even mention that piece of piracy software on xda. It's used to steal from developers and is not allowed here.
In the "Modules" part you can manually install modules that you've previously downloaded. If you want to install directly from the Magisk repo, you (unsurprisingly ) go to the "Downloads" section of the Manager. If you can't see "Downloads", make sure the Manager has internet access.
Click to expand...
Click to collapse
Sorry I didn't know. What I had in mind is that I'll give u all the details without leaving none so u know what I do and be able to help fast. Anyway, again I'm sorry. I didn't mean it.
I tried to dl greenify4magisk and I successfully download and install it. Rebooting the device now

rajoholic said:
Sorry I didn't know. What I had in mind is that I'll give u all the details without leaving none so u know what I do and be able to help fast. Anyway, again I'm sorry. I didn't mean it.
I tried to dl greenify4magisk and I successfully download and install it. Rebooting the device now
Click to expand...
Click to collapse
Sir, did you manage to install? when i tried to install log is failed.

Need help on trying to install Magisk Root V16 onto my BLU Advance 5.2

Like the title says. I'm trying to install Magisk Root V16 and I read through everything. Still I don't get it. I even search on youtube and it doesn't say exactly what to do only to say read the entire post on xdadevelopers then download a few things on the phone and still nothing.

All the instructions you need are in the release thread.
Before you do anything you need to unlock the bootloader, so if you haven't already, start there. Keep in mind it'll most likely wipe your device, so make sure to have a backup.
Option 1:
Download the Magisk zip and flash it through a custom recovery, like TWRP. Done.
Option 2:
If you don't have a custom recovery, place a copy of your stock boot image on your internal storage, install the Magisk Manager (from the release thread), choose the option to install be patching the boot image (in the Manager), and finally flash the patched boot image (you'll find it in the MagiskManager folder on your internal storage) with fastboot or whatever is applicable to your device. Done.
If nothing works, make sure to provide as much detail as possible. Here's some useful reading about common issues and what logs to provide, etc:
https://www.didgeridoohan.com/magisk/Magisk
If you need help with the basics (bootloader unlock, custom recovery, etc), do a search here on XDA. You can usually find some good info that way:
https://forum.xda-developers.com/search?query=BLU advance 5.2

Magisk cannot actually patch a boot image? [Galaxy S8/SM-G955F, Android 7.0]

Hello all,
Hope this isn't a needless duplicate, but I've done a fair amount of searching and I can't find that this question has been answered anywhere.
If I understand correctly, it should be possible to use a 100% stock phone to produce a patched boot.img which can then be flashed to that same phone? From the instructions in topjohnwu's main thread about Magisk, I'm lead to believe Magisk can "bootstrap" itself in this way:
1) Install Magisk Manager and copy a stock boot.img extracted from the OTA
2) Use the "Install" menu item to produce a patched_boot.img, which can then be lifted off the phone and used (with ODIN) to flash the phone.
I never get to item 2.
My MagiskManager says "Magisk is not installed" which is obviously true, however, the instructions seem to say one can proceed from there, and yet I can't see how. I've created an /sdcard/magisk folder and an /sdcard/MagiskManager folder and stuck a(n unpatched) boot.img file in either of them; as well, I've just stuck one in /sdcard/ for good measure (the "root" of user-accessible storage) And yet no go.
Am I misunderstanding something? Is the patching of the boot image supposed to be happening somewhere else than on the (stock) phone? Poking around, I see that topjohnwu's "Magisk" git tree includes something called "magiskboot", but that doesn't seem to be part of the Magisk Manager package.
TL;DR: From what topjohnwu writes, it's supposed to be possible to install Magisk WITHOUT having a custom recovery installed, but I cannot find a way to actually do it with the provided tools and instructions.

You need internet access to download the Magisk zip to patch the image. No internet - no install button...

Ouch. Thanks for the help, Didgeridoohan, that's the answer right there. I like to get my phones set up "just right", which includes getting root and then backup up and freezing various things (for example using Titanium Backup), before ever allowing the phone to go online for the first time and triggering connections and synchronisations and registrations of the tonnes and tonnes of shovelware crap that seems to come in with the tide on any modern smartphone these days.
Thanks for the explanation. I guess I can get it taken care of with SuperSU, freeze the things I don't like and then get my download happening in Magisk Manager. Then when I'm ready with my patched boot.img, I can re-flash the stock ROM.
Wouldn't be a terrible feature to be able to just set up the files MagiskManager expects to find so that this all could work in an offline configuration, though!

Tangib1e said:
Ouch. Thanks for the help, Didgeridoohan, that's the answer right there. I like to get my phones set up "just right", which includes getting root and then backup up and freezing various things (for example using Titanium Backup), before ever allowing the phone to go online for the first time and triggering connections and synchronisations and registrations of the tonnes and tonnes of shovelware crap that seems to come in with the tide on any modern smartphone these days.
Thanks for the explanation. I guess I can get it taken care of with SuperSU, freeze the things I don't like and then get my download happening in Magisk Manager. Then when I'm ready with my patched boot.img, I can re-flash the stock ROM.
Wouldn't be a terrible feature to be able to just set up the files MagiskManager expects to find so that this all could work in an offline configuration, though!
Click to expand...
Click to collapse
If you have another device, you can use that one to patch the boot.img. just put magisk manager and the stock boot.img on that one and patch it. Then move it to your PC for flashing in Odin. Make sure that, in the patched boot format settings in magisk manager, you select .tar for the format of the patched image.

Didgeridoohan said:
You need internet access to download the Magisk zip to patch the image. No internet - no install button...
Click to expand...
Click to collapse
The app should really display a message if the phone is offline

TWRP WITH WORKING touch screen

Update for new year.
1-1-2020 Uploaded a version of twrp for Bold-N1 with working touchscreen.
thanks to the help of @vineethrp in This Post
Original thread hidden, since twrp build is fixed.
This initial version of TWRP, still has major issue. A second issue with the recovery is the screen will not turn on for about 30 seconds after boot. A time that lines up with the screen sleep timer. The touchscreen is not working. This has been a kernel issue on other devices that I am aware of.
The kernel source for th BOLD-N1 is released, and I have been reading through it. To no avail. I can't find the section that is checking for recovery mode.
For the time being, I have confirmed this version is working with the adb command line operations.
Partial list of functions found Here https://twrp.me/faq/openrecoveryscript.html
I have used the "install" and "sideload" operations.
In most cases (mods etc) sideload should be ok to try.
For the mod I was interested in (DM-Verity-No-Forceencrypt). The install does not support being done in sideload.
Because in the install script used, it checks the zip file name. Based on the file name it enables/disables options of the script.
Sideload changes the *.zip name, so more steps were necessary.
In the following steps, the device /data partition will be formatted. This will erase all your stored data, and more importantly,
it will remove the encryption.
The following steps require you to have already unlocked bootloader.
And,
As a reminder, whenever you modify your phone, you should NEVER relock the bootloader
INSTALL the attached TWRP img. Use Fastboot to install it.
Code:
fastboot flash recovery **insert-file-path-&name-here**
fastboot oem reboot-recovery
STEPS USED TO FLASH Disable_Dm-Verity_ForceEncrypt
Download zip file from developers XDA page HERE
Code:
adb shell twrp wipe data
adb shell reboot recovery
adb push Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip /sdcard/Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip
adb shell twrp install /sdcard/Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip
STEPS USED TO SIDELOAD MAGISK
Download from Developers GitHub repo HERE
I had trouble with the newest V20. Stay on tested version V19.2, unless you can troubleshoot problems on your own.
Code:
adb shell twrp sideload
adb sideload C:\Users\(your user name HERE)\Downloads\Magisk-v19.2.zip
Device tree used
https://github.com/mrmazakblu/Bold-N1_minimum_device
Kernel source
https://github.com/mrmazakblu/Bold-N1-Kernel.git
Released twrp folder on android file host HERE
Stock recovery image HERE
.

Call for help
@vampirefo ,you had fixed touchscreen issue in recovery on other devices. You also helped me to do the same too. If you find some time , could you try point me in some direction.

mrmazak said:
@vampirefo ,you had fixed touchscreen issue in recovery on other devices. You also helped me to do the same too. If you find some time , could you try point me in some direction.
Click to expand...
Click to collapse
No luck with decrypting here
Tried to backup stock recovery with no luck. Do u have a copy ?

greeneyez15o said:
No luck with decrypting here
Tried to backup stock recovery with no luck. Do u have a copy ?
Click to expand...
Click to collapse
How did you try to backup stock recovery?
Yes do have stock images loaded on filehost as well. I will add a link in the OP.
Let's try and figure out why you had trouble decrypt.
Start by flashing that twtp image to recovery. Boot I to the twrp then follow the steps I listed

mrmazak said:
How did you try to backup stock recovery?
Yes do have stock images loaded on filehost as well. I will add a link in the OP.
Let's try and figure out why you had trouble decrypt.
Start by flashing that twtp image to recovery. Boot I to the twrp then follow the steps I listed
Click to expand...
Click to collapse
Not sure, but now Im bootlooping to twrp :/

greeneyez15o said:
Not sure, but now Im bootlooping to twrp :/
Click to expand...
Click to collapse
do you know if your phone had received the ota update. there was an update made on
Wednesday, 16-Oct-19 03:27:28 UTC not sure when it was released, though.
it is possible, but unconfirmed that this update may have made this bootloop happen. because others have said that the update made them loose there root. Unknown about the unlock status

I am still trying to fix this twrp, as it is still only one I have seen.
I also have a different phone(umidigi F1) with same soc, mt6771.
A Dev made twrp for that device that even works decrypt. @PeterCxy.
I have forked his build tree. And am trying to copy his success. Unfortunately even though devices have same soc, the encryption method is different enough that the files used to make decrypt work on F1 are not present on N1.
A made a full firmware dump of the N1 at
https://github.com/mrmazakblu/blu_n0030ww_dump

working on porting , then building old Carliv touch recovery. since it can be used with the volume rocker as well as touch.
So far i have it ooting and adb works. Of course with device encrypted , the internal storage is not accessed. but once i get the fsab and vold correctly mapped, it will be ok.
am not posting the port till sdcard is fixed, and can be built from source.

sounds great man i just oem unlocked the bold n1 how do i go far as rooting wise without the custom recovery. using magisk or do i gotta wait until the carliv recovery is available

dxpeboiiii said:
sounds great man i just oem unlocked the bold n1 how do i go far as rooting wise without the custom recovery. using magisk or do i gotta wait until the carliv recovery is available
Click to expand...
Click to collapse
Well it's up to you. In this thread I have detailed how I used ADB with twrp to flash first decrypt install package, then magisk. Or you can patch boot.img with magisk manager then flash back to phone with fastboot or sp-flash tool.
Or if you are going to use gsi AOSP, you don't need any of these options.

Any word on the touch twrp. Im rooted with magisk but need viper4android and cant seem to flash properly without twrp... I tryed all kinds of ways

dxpeboiiii said:
Any word on the touch twrp. Im rooted with magisk but need viper4android and cant seem to flash properly without twrp... I tryed all kinds of ways
Click to expand...
Click to collapse
Did you try either of the 2 ways I explained how to use adb to install zips?
1- adb sideload
2- adb twrp install. Xzxsome-zip-name
But I thought viper4android has not worked on devices higher than marshmallow

I gotten it to work on my galaxy tab a on Oreo and my galaxy s7 and different varieties of devices. And yes i tryed the command from abd in twrp to install zip.. no success yet. BUT i have a otg from a samsung devices. And am able to use twrp within the mouse and keyboard. So tryna see what my options are as far as installin zips

dxpeboiiii said:
I gotten it to work on my galaxy tab a on Oreo and my galaxy s7 and different varieties of devices. And yes i tryed the command from abd in twrp to install zip.. no success yet. BUT i have a otg from a samsung devices. And am able to use twrp within the mouse and keyboard. So tryna see what my options are as far as installin zips
Click to expand...
Click to collapse
That's good, lets us know how the otg mouse works out. I did not have one to try it.

I got viper4android workin .. i downloaded a module called "Magisk SELInux permissive Script" this basically gave me the option to be permissive thats need for viper to work. And busybox but im pretty sure thats already installed from magisk but if not just install busybox. Should be good to go for audio mods?? bout to try dolby now.. let you kno how it goes

Basically i have the device unencrypted and under magisk settings you wanna uncheck "magisk hide" you will fail safety thing but me personally idc. But anyway follow the above comment along with wat i just said you should have no issues installin viper and dolby. I also recommend a otg for custom recovery. Just easier in my opinion. I basically got device setup how i want and backed it up thru twrp. But any question feel free to ask. More then welcome to help anybody .

deleted.

dml0211 said:
deleted.
Click to expand...
Click to collapse
I think you posted in wrong stop. I see you deleted before I got reply. Oh well.
But if you need to know which type of gsi to use on your device. The best bet is to use this app, from play store.
https://play.google.com/store/apps/details?id=tk.hack5.treblecheck

mrmazak said:
@vampirefo ,you had fixed touchscreen issue in recovery on other devices. You also helped me to do the same too. If you find some time , could you try point me in some direction.
Click to expand...
Click to collapse
I got to fix the touch issue. After a bit of debugging I figured out that kernel is not able to find the firmware file for goodix:
Code:
[ 0.935177] (4)[222:goodix-parse_cf]goodix_i2c 0-005d: Direct firmware load for goodix_cfg_group.bin failed with error -2
[ 0.935177] (5)[1:swapper/0]BOOTPROF: 935.177078:probe: probe=i2c_device_probe drv=goodix_i2c(ffffff80097f7b08) 77.446154ms
[ 0.935191] (5)[1:swapper/0]i2c i2c-0: Failed to register i2c client cap_touch at 0x5d (-16)
[ 0.935191] (4)[222:goodix-parse_cf]goodix_i2c 0-005d: Falling back to user helper
[ 0.935204] (5)[1:swapper/0]i2c i2c-0: of_i2c: Failure registering /[email protected]/[email protected]
...
...
[ 2.422885] (7)[222:goodix-parse_cf]goodix_i2c 0-005d: Direct firmware load for goodix_cfg_group.bin failed with error -2
[ 2.422892] (7)[222:goodix-parse_cf]goodix_i2c 0-005d: Falling back to user helper
[ 2.423524] (4)[321:ueventd]ueventd: firmware: loading 'goodix_cfg_group.bin' for '/devices/platform/11007000.i2c/i2c-0/0-005d/firmware/goodix_cfg_group.bin'
[ 2.423633] (4)[321:ueventd]ueventd: firmware: could not find firmware for goodix_cfg_group.bin
[ 2.423664] (4)[321:ueventd]ueventd: loading /devices/platform/11007000.i2c/i2c-0/0-005d/firmware/goodix_cfg_group.bin took 0ms
[ 2.423695] (7)[222:goodix-parse_cf][GTP-ERR][goodix_read_cfg_bin:493] Cfg_bin image [goodix_cfg_group.bin] not available,error:-11, try_times:2
I digged in deeper an figured out that the firmware files are in /vendor/firmware folder and and I extracted it out and put it in
Code:
recovery/root/etc/firmware
and touch works as a result.
Code:
adb pull /vendor/firmware/goodix_cfg_group.bin
BTW, I have not yet figured out the reason for delayed screen on. I am debugging that and will let you know if I get some leads. I am also not able to get the decrypt working as of now.
Please let me know if you need any more details about how to get the touch working.

vineethrp said:
I got to fix the touch issue. After a bit of debugging I figured out that kernel is not able to find the firmware file for goodix:
Code:
[ 0.935177] (4)[222:goodix-parse_cf]goodix_i2c 0-005d: Direct firmware load for goodix_cfg_group.bin failed with error -2
[ 0.935177] (5)[1:swapper/0]BOOTPROF: 935.177078:probe: probe=i2c_device_probe drv=goodix_i2c(ffffff80097f7b08) 77.446154ms
[ 0.935191] (5)[1:swapper/0]i2c i2c-0: Failed to register i2c client cap_touch at 0x5d (-16)
[ 0.935191] (4)[222:goodix-parse_cf]goodix_i2c 0-005d: Falling back to user helper
[ 0.935204] (5)[1:swapper/0]i2c i2c-0: of_i2c: Failure registering /[email protected]/[email protected]
...
...
[ 2.422885] (7)[222:goodix-parse_cf]goodix_i2c 0-005d: Direct firmware load for goodix_cfg_group.bin failed with error -2
[ 2.422892] (7)[222:goodix-parse_cf]goodix_i2c 0-005d: Falling back to user helper
[ 2.423524] (4)[321:ueventd]ueventd: firmware: loading 'goodix_cfg_group.bin' for '/devices/platform/11007000.i2c/i2c-0/0-005d/firmware/goodix_cfg_group.bin'
[ 2.423633] (4)[321:ueventd]ueventd: firmware: could not find firmware for goodix_cfg_group.bin
[ 2.423664] (4)[321:ueventd]ueventd: loading /devices/platform/11007000.i2c/i2c-0/0-005d/firmware/goodix_cfg_group.bin took 0ms
[ 2.423695] (7)[222:goodix-parse_cf][GTP-ERR][goodix_read_cfg_bin:493] Cfg_bin image [goodix_cfg_group.bin] not available,error:-11, try_times:2
I digged in deeper an figured out that the firmware files are in /vendor/firmware folder and and I extracted it out and put it in
Code:
recovery/root/etc/firmware
and touch works as a result.
Code:
adb pull /vendor/firmware/goodix_cfg_group.bin
BTW, I have not yet figured out the reason for delayed screen on. I am debugging that and will let you know if I get some leads. I am also not able to get the decrypt working as of now.
Please let me know if you need any more details about how to get the touch working.
Click to expand...
Click to collapse
Thank you. I added the firmware to the recovery ramdisk and repacked. Just like you said. Now I have touch working. THis may have re-sparked my interest. I have more to work with now. Thanks.
Perhaps twrp is not properly mounting the /vendor and this is why we need to add that bin file to recovery/root. May also be same issue making the screen on time lag. Either way this seems like a big step forward.
I am working on adding the goodix firmware to the device tree I am building with, so will not need to do repacking. I have added the test build with working touch to the file host folder linked in OP

Is there a guide on updating to the newest firmware and Magisk

Fairly newbie user here. I'm looking for a guide that lists how to upgrade the P5 to a new firmware and keep Magisk and all of that. I've looked at the thread below and it is good for getting started up in the beginning, but I'm not following how it works for a new firmware.
[Tutorial] Unlock Bootloader, get root and valid Safetynet
04/09/21 v2 Just install this Module via magisk manager: https://forum.xda-developers.com/attachments/hardwareoff_1-1-zip.5058405/ which is mentioned by this thread...
forum.xda-developers.com
Like how do I flash the new February firmware onto my phone?
Do I then copy the boot.img to the P5 and patch it with Magisk?
Then do I copy the patched boot.img back to my PC and flash it back onto the P5?
Are there are new step or process for unlocking SafetyNet?
I'm just very confused and would appreciate something simple and basic to follow, please.
Thanks!

1. Download the rom, extract it and copy boot.img to phone, patch with magisk then copy the patched file to computer
2. Disable all magisk modules and reboot
3. Remove -w from flash-all.bat, copy all the files in the ROM to where the adb files are located, reboot to bootloader and run flash-all.bat
4. Reboot to bootloader and flash the patched boot image
5. Reboot and enable magisk modules
6. Reboot

UPDATING Pixel 5 Factory Image & Re-Rooting
Why This Thread? I have seen several questions on the process for updating a rooted Pixel 5, since the existing guides only explain the unlock and initial rooting, I thought I'd throw together a quick HOW TO on UPDATING and Re-Rooting for...
forum.xda-developers.com

You can bypass safetynet perfectly with hiddencore module for xposed.
HiddenCore Module | Xposed Module Repository
repo.xposed.info

Xposed is dead since Android 10 and higher, so forget about the post of VD171. Sorry if I#m wrong with that, but never heard of working xposed on Pixels (with newest firmware).
cescman said:
1. Download the rom, extract it and copy boot.img to phone, patch with magisk then copy the patched file to computer
2. Disable all magisk modules and reboot
3. Remove -w from flash-all.bat, copy all the files in the ROM to where the adb files are located, reboot to bootloader and run flash-all.bat
4. Reboot to bootloader and flash the patched boot image
5. Reboot and enable magisk modules
6. Reboot
Click to expand...
Click to collapse
This will work definitely fine. Don't mess with uninstalling Magisk as whole application, just disable the modules. Otherwise it will cause bootloops.
I also wonder, why I can not first patch the boot.img and insert the patched version back in the .zip archive and only have to flash then once with flash-all? So no rebooting and flashing of the boot.img would be needed? Does someone tried this? I was to tired because of slow internet and have had to reflash the january boot.img to quit my bootloops.
It would only timesaving and you may don't need to disable the magisk modules. that is my hope of doing this. Otherwise just follow cesmans posting.

hanni2301 said:
Xposed is dead since Android 10 and higher, so forget about the post of VD171. Sorry if I#m wrong with that, but never heard of working xposed on Pixels (with newest firmware).
This will work definitely fine. Don't mess with uninstalling Magisk as whole application, just disable the modules. Otherwise it will cause bootloops.
I also wonder, why I can not first patch the boot.img and insert the patched version back in the .zip archive and only have to flash then once with flash-all? So no rebooting and flashing of the boot.img would be needed? Does someone tried this? I was to tired because of slow internet and have had to reflash the january boot.img to quit my bootloops.
It would only timesaving and you may don't need to disable the magisk modules. that is my hope of doing this. Otherwise just follow cesmans posting.
Click to expand...
Click to collapse
Xposed and Xposed modules are working perfectly on ANDROID 10.
So forget about post of hanni2301, lol

hanni2301 said:
I also wonder, why I can not first patch the boot.img and insert the patched version back in the .zip archive and only have to flash then once with flash-all? So no rebooting and flashing of the boot.img would be needed? Does someone tried this? I was to tired because of slow internet and have had to reflash the january boot.img to quit my bootloops.
It would only timesaving and you may don't need to disable the magisk modules. that is my hope of doing this. Otherwise just follow cesmans posting.
Click to expand...
Click to collapse
I have tried few years ago, in some previous version of android, instead of running flash-all.bat, I flash each image individually, (fastboot flash bootloader..., fastboot flash boot..., fastboot flash recovery.... etc. ). If I took the shortcut of not flashing the original boot image first and then the patched one, but flash the patched boot directly, then the phone run into a bootloop.

cescman said:
1. Download the rom, extract it and copy boot.img to phone, patch with magisk then copy the patched file to computer
2. Disable all magisk modules and reboot
3. Remove -w from flash-all.bat, copy all the files in the ROM to where the adb files are located, reboot to bootloader and run flash-all.bat
4. Reboot to bootloader and flash the patched boot image
5. Reboot and enable magisk modules
6. Reboot
Click to expand...
Click to collapse
1. Can I just do all of the file movement through Windows Explorer?
3. What command do I run? Like do I have to run ADB something before I run flash-all.bat?
4. What is the command for that? Is it ADB flash boot.img?
Sorry, I don't know and understand a lot of the commands and how you get it to work with the phone.

Ewto16 said:
1. Can I just do all of the file movement through Windows Explorer?
3. What command do I run? Like do I have to run ADB something before I run flash-all.bat?
4. What is the command for that? Is it ADB flash boot.img?
Sorry, I don't know and understand a lot of the commands and how you get it to work with the phone.
Click to expand...
Click to collapse
My friend, you can find a huge a mount of videos about it in youtube.
Adb is NOT for flashing.
Taken care or you can damage your device.
You need to READ and learn first, before to try anything.
If you try to search it, certainly you will find it.

VD171 said:
My friend, you can find a huge a mount of videos about it in youtube.
Adb is NOT for flashing.
Taken care or you can damage your device.
You need to READ and learn first, before to try anything.
If you try to search it, certainly you will find it.
Click to expand...
Click to collapse
Thanks, I appreciate the advice. I was able to follow the initial tutorial on how to setup my phone the first time, but it is well written out step by step. The other guides I've seen for upgrading just sort of breeze through the steps, assuming you know what you are doing.
My phone actually updated to the February release today, which broke my Magisk and lost me my Props configurations. I just want to get those things back.

Ewto16 said:
Thanks, I appreciate the advice. I was able to follow the initial tutorial on how to setup my phone the first time, but it is well written out step by step. The other guides I've seen for upgrading just sort of breeze through the steps, assuming you know what you are doing.
My phone actually updated to the February release today, which broke my Magisk and lost me my Props configurations. I just want to get those things back.
Click to expand...
Click to collapse
Next time, don't flash the factory image. Sideload the OTA.zip instead. That way you won't lose any of that.
Sideload the OTA, flash the patched boot.img (the boot.img you need to get from the factory image though), and you won't lose Magisk, your modules, or your root settings.
I used to do the same. Edit out the -w flag from the flash-all and re- setup my phone. Sideloading the OTA is easier and quicker in the end.

Ewto16 said:
1. Can I just do all of the file movement through Windows Explorer?
3. What command do I run? Like do I have to run ADB something before I run flash-all.bat?
4. What is the command for that? Is it ADB flash boot.img?
Sorry, I don't know and understand a lot of the commands and how you get it to work with the phone.
Click to expand...
Click to collapse
1. Yes
3. Edit the flash-all.bat file with any editor, e.g. notepad in windows, you will see -w near the end of the file, remove it, then save and run the file. You must make sure the -w is removed, otherwise all the data will be wiped
4. To boot into bootloader: adb reboot bootloader
To flash the patched boot image: fastboot flash boot magisk_ patched.img (the file name changes every time, just use the one you have when you patch the boot image)

It's easier to replace the "-w" with "--skip-reboot" (first one is double dashes). The phone won't reboot when the image flashing is complete so you can immediately re-flash the patched boot img.
This youtube video is great to follow and has clear step by step guide.

Thanks for the help and tips everyone. I really appreciate it! I was able to get my phone updated and re-rooted.
The only issue I'm having now is that I can't use GPay for contactless payments. When I go to try and use GPay, i get a slashed out line through the contactless payment symbol. It doesn't let me do anything with it from there.
I am on the Feb update, with Magisk installed, and the Universal SafetyNet Fix 2.0.0 module installed. I also have the MagiskHide Props Config module loaded. I pass the SafetyNet Check, but I can't do contactless payments.
I have Magisk hidden from GPay as well.
Any thoughts?

Ewto16 said:
Thanks for the help and tips everyone. I really appreciate it! I was able to get my phone updated and re-rooted.
The only issue I'm having now is that I can't use GPay for contactless payments. When I go to try and use GPay, i get a slashed out line through the contactless payment symbol. It doesn't let me do anything with it from there.
I am on the Feb update, with Magisk installed, and the Universal SafetyNet Fix 2.0.0 module installed. I also have the MagiskHide Props Config module loaded. I pass the SafetyNet Check, but I can't do contactless payments.
I have Magisk hidden from GPay as well.
Any thoughts?
Click to expand...
Click to collapse
Have you actually tried to use your phone at a pay terminal?
My device also passes safetynet but has contactless crossed out. However, it still works at payment terminals.

swangjang said:
Have you actually tried to use your phone at a pay terminal?
My device also passes safetynet but has contactless crossed out. However, it still works at payment terminals.
Click to expand...
Click to collapse
I have not attempted to use it yet. I just assumed that it wouldn't work since it was crossed out. I will have to give it a try.

Ewto16 said:
I have not attempted to use it yet. I just assumed that it wouldn't work since it was crossed out. I will have to give it a try.
Click to expand...
Click to collapse
On my device, I uninstalled the Google pay app and used the built-in "cards and passes" that shows up when you long press the power button.

swangjang said:
On my device, I uninstalled the Google pay app and used the built-in "cards and passes" that shows up when you long press the power button.
Click to expand...
Click to collapse
Interesting....I thought those were one and the same. Thanks for the tip. I'll give that a try.
I'd still like to get GPay working again though.

VD171 said:
Xposed and Xposed modules are working perfectly on ANDROID 10.
So forget about post of hanni2301, lol
Click to expand...
Click to collapse
And the Pixel 5 is on ANDROID 11.
So forget about post of VD171, lol^2

hanni2301 said:
And the Pixel 5 is on ANDROID 11.
So forget about post of VD171, lol^2
Click to expand...
Click to collapse
Grow up, my friend.
Anything can changes from device to device.