[Huawei][TREBLE] Disable fingerprint navigation gestures in treble roms - Treble-Enabled Device Development A/AB ROMS

Navigation gestures on rear fingerprint of huawei devices in treble roms can be disable by replacing fingerprint.kl provided below or you can customise actions performed by your fingerprint by editing this file
Instructions: Use any Root file manager and replace fingerprint.kl (with attached fingerprint.kl) inside /system/phh/huawei/
Buy me a coffee

Thank you! Your post also showed me how these gestures actually have to be set up and now I've been playing around with the file a bit. My problem is, I'd really like to add Google Assistant, split screen and all that kind of stuff as a home button gesture.
Do you or anyone maybe know what the names for those actions in this file are? I already tried "ASSISTANT" and "84" but didn't work...

_lucx_ said:
Thank you! Your post also showed me how these gestures actually have to be set up and now I've been playing around with the file a bit. My problem is, I'd really like to add Google Assistant, split screen and all that kind of stuff as a home button gesture.
Do you or anyone maybe know what the names for those actions in this file are? I already tried "ASSISTANT" and "84" but didn't work...
Click to expand...
Click to collapse
Try generic.kl in which many action's codename mentioned,use those names to assign in fingerprint.kl
VOICE_ASSIST is the command shortcut for google assistant,try it in fingerprint.kl

arshilhonor6x said:
Try generic.kl in which many action's codename mentioned,use those names to assign in fingerprint.kl
VOICE_ASSIST is the command shortcut for google assistant,try it in fingerprint.kl
Click to expand...
Click to collapse
How can I get generic.kl?

_lucx_ said:
How can I get generic.kl?
Click to expand...
Click to collapse
To locate the file, go to /system/usr/keylayout/ and there should be a file called "Generic.kl"

arshilhonor6x said:
To locate the file, go to /system/usr/keylayout/ and there should be a file called "Generic.kl"
Click to expand...
Click to collapse
Thanks! I've succesfully done my perfect setup now. ^^

_lucx_ said:
Thanks! I've succesfully done my perfect setup now. ^^
Click to expand...
Click to collapse
Welcome

It does not work for me in Huawei P Smart

Thank you,it works really well on my Huawei mate 9
Now we don't have to deal with that annoying fingerprint navigation.

iNFeRNuSDaRK said:
It does not work for me in Huawei P Smart
Click to expand...
Click to collapse
U tried on treble roms

osk4rin said:
Thank you,it works really well on my Huawei mate 9
Now we don't have to deal with that annoying fingerprint navigation.
Click to expand...
Click to collapse
Yes,really annoying and I don't saw anyone even complaining about it,then I searched system files and found this solution.

Thanks for this fix

If only I could get my fingerprint scanner to actually work. The gestures work but unlocking doesn't. It won't let me save any fingerprints on my Mate 9.

tommiy995 said:
If only I could get my fingerprint scanner to actually work. The gestures work but unlocking doesn't. It won't let me save any fingerprints on my Mate 9.
Click to expand...
Click to collapse
Try a different rom

After this fix fingerprint working is slowly:victory:

tommiy995 said:
If only I could get my fingerprint scanner to actually work. The gestures work but unlocking doesn't. It won't let me save any fingerprints on my Mate 9.
Click to expand...
Click to collapse
Do a factory reset using stock recovery

phhusson said:
Do a factory reset using stock recovery
Click to expand...
Click to collapse
can I do that by flashing stock image, ram_disk, kernel, and recovery?

luckydeveloper said:
After this fix fingerprint working is slowly:victory:
Click to expand...
Click to collapse
No its fast but looks slow because it disables fingerprint wakeup,which wakes up screen with any finger touch

tommiy995 said:
can I do that by flashing stock image, ram_disk, kernel, and recovery?
Click to expand...
Click to collapse
No,flash stock recovery and wipe data,cache from there,u need to flash recovery_ramdisk

arshilhonor6x said:
No,flash stock recovery and wipe data,cache from there,u need to flash recovery_ramdisk
Click to expand...
Click to collapse
So just to be 100% sure so I don't mess it up:
Go to fastboot,
Code:
fastboot flash recovery_ramdisk stockrecovery.img
(which I can get through Huawei Extractor of my update file).
Then do
Code:
fastboot wipe data
fastboot reboot
Download the OS through eRecovery
Then go back through, unlock bootloader, twrp, flash PHH AOSP and I should be good to go?

Related

record call app

hi
i'm looking for working app for honor 7 for record calls, do you know about one without root?
thanks
Boldbeast call recoeder availabe on play store .auto record doesnt work you have to use it in manual mode see support page for honor 7 on their site
and there is something that works with auto record?
thank you
I7210I said:
and there is something that works with auto record?
thank you
Click to expand...
Click to collapse
As per my knowledge none for that you have to root then you can use huwaei s stock call rec. App but boldbeast is also good it records both way with good clarity
I7210I said:
and there is something that works with auto record?
thank you
Click to expand...
Click to collapse
Yes there is, but require you to change to Chinese Stock ROM ver PLK-TL00C01B388
I am currently using it now. Previously I was on Malaysia Stock Rom PLK-L01C636B371 then decided to flash over to chinese stock.
Amazingly this rom has the ability to have the automated call recorder and other nice build in function, such as Eye Comfort, App Twin etc.
Yes, Stock rom + no root = works. :highfive:
fiezwan said:
Yes there is, but require you to change to Chinese Stock ROM ver PLK-TL00C01B388
I am currently using it now. Previously I was on Malaysia Stock Rom PLK-L01C636B371 then decided to flash over to chinese stock.
Amazingly this rom has the ability to have the automated call recorder and other nice build in function, such as Eye Comfort, App Twin etc.
Yes, Stock rom + no root = works. :highfive:
Click to expand...
Click to collapse
do you have link for that please?
and also i will try the boldbeast too
I7210I said:
do you have link for that please?
and also i will try the boldbeast too
Click to expand...
Click to collapse
I use Huawei Firmware Finder to download the ROM (See attachment)
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
Then flash it like this step:
https://forum.xda-developers.com/honor-7/help/to-destroyed-ur-h7-noob-friendly-t3554793
* I used boldbeast before. yes, that one is the best and suitable to use. but can't do auto record, so end up i use this chinese rom
Good Luck! :highfive:
so it leaves only one option
fiezwan said:
I use Huawei Firmware Finder to download the ROM (See attachment)
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
Then flash it like this step:
https://forum.xda-developers.com/honor-7/help/to-destroyed-ur-h7-noob-friendly-t3554793
* I used boldbeast before. yes, that one is the best and suitable to use. but can't do auto record, so end up i use this chinese rom
Good Luck! :highfive:
Click to expand...
Click to collapse
where is the exact model i need to download rom for according to these pictures?
thank you
I7210I said:
where is the exact model i need to download rom for according to these pictures?
thank you
Click to expand...
Click to collapse
You need to click at "Common base" tab
Then find the model
Then click at the filelist to download the zip file
See attachment for reference
Hope this would help :highfive:
thank you,
what about the Huawai Update Extractor?need to download too?
also at the list it written 3.13GB and actually it's 1.6GB is it right?
I7210I said:
thank you,
what about the Huawai Update Extractor?need to download too?
also at the list it written 3.13GB and actually it's 1.6GB is it right?
Click to expand...
Click to collapse
I do not know why it contains bigger than usual, but for me, bigger files should be better.
Why would you wanted a 390 when there is 396 with latest security patch?
Anyway, I think you would want to have a look at my complete user-manual for changing the rom. (see attachment)
:highfive:
Hope this would help!
fiezwan said:
I do not know why it contains bigger than usual, but for me, bigger files should be better.
Why would you wanted a 390 when there is 396 with latest security patch?
Anyway, I think you would want to have a look at my complete user-manual for changing the rom. (see attachment)
:highfive:
Hope this would help!
Click to expand...
Click to collapse
the 390 i have now, which exact version do i need to search for??
also the extractor stuck at the cust file..is it OK!?
also attached how the unbrick folder looks now, it's ok?
and as i read at the other thread, there is instructions:
Type the following into the CMD window previously opend:
1- fastboot devices (should list up ur H7)
2- fastboot flash boot boot.img (flashes the Honor7 boot.img to the H7)
3- fastboot flash system system.img (flashes the system wich maybe corrupted)
4- fastboot flash recovery recovery.img (flashes the stock recovery and removes trwp)
5- fastboot reboot
is these is instead of the multi tool?it's easyer
I7210I said:
the 390 i have now, which exact version do i need to search for??
also the extractor stuck at the cust file..is it OK!?
also attached how the unbrick folder looks now, it's ok?
and as i read at the other thread, there is instructions:
Type the following into the CMD window previously opend:
1- fastboot devices (should list up ur H7)
2- fastboot flash boot boot.img (flashes the Honor7 boot.img to the H7)
3- fastboot flash system system.img (flashes the system wich maybe corrupted)
4- fastboot flash recovery recovery.img (flashes the stock recovery and removes trwp)
5- fastboot reboot
is these is instead of the multi tool?it's easyer
Click to expand...
Click to collapse
erm, if the extractor stuck as cust file, you can always re-extract it 1 more time. if it still fails, maybe the zip file is corrupted and you need to re-download again. otherwise, just choose different Stock zip file.
the other thread that you saw - asking you to type in those command in fastboot is also a correct way.
only the function of the multi-tool = you do not need to type in any commands. it will help you to do it. its the same thing.
both way will work. your choice.
have you not try it yet?
fiezwan said:
erm, if the extractor stuck as cust file, you can always re-extract it 1 more time. if it still fails, maybe the zip file is corrupted and you need to re-download again. otherwise, just choose different Stock zip file.
the other thread that you saw - asking you to type in those command in fastboot is also a correct way.
only the function of the multi-tool = you do not need to type in any commands. it will help you to do it. its the same thing.
both way will work. your choice.
have you not try it yet?
Click to expand...
Click to collapse
Did it before on Nexus , not on honor.
About the version , what exactly version do I need?
The 396 is the same as I have and not the Chinese one..
Thank you
Sent from my Nexus 6P using Tapatalk
I7210I said:
Did it before on Nexus , not on honor.
About the version , what exactly version do I need?
The 396 is the same as I have and not the Chinese one..
Thank you
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
If you need the automated call recorder build in - you need PLK-TL00C01B388 stock rom
and flash it either via multitool step by step like i provide before, or use fastboot command.
After using the method, your phone will change to chinese stock rom.
fiezwan said:
If you need the automated call recorder build in - you need PLK-TL00C01B388 stock rom
and flash it either via multitool step by step like i provide before, or use fastboot command.
After using the method, your phone will change to chinese stock rom.
Click to expand...
Click to collapse
thank you,
one last clearence, same languages in all the rom's correct?
and does the google apps will be the same after install these rom?
also the problem with the extraction of the cust persist even after few times of extracting maybe i need jsut to root and use call recorder by skvalex?
I7210I said:
thank you,
one last clearence, same languages in all the rom's correct?
and does the google apps will be the same after install these rom?
also the problem with the extraction of the cust persist even after few times of extracting maybe i need jsut to root and use call recorder by skvalex?
Click to expand...
Click to collapse
Language: You can choose English while setting the phone up
Google apps will not be there - due to their policy. However, there is always a work around. You need to download and install Google Play service + Google Contact in order to make it sync.
Please refer the line below for installing Google Play:
https://forum.xda-developers.com/showpost.php?p=57280942&postcount=4
one of the users at the device needs hebrew, is it available there?
thank you
I just replace my stock Europe ROM in Honor 7 with PLK-TL00C01B388. I don't have any problem so far. I don´t even lost my settings or data.
Is it here way how I can remove stock Huawei app like Browser, HiStudy, Phone Finder or HiWallet? Another question is about Yellow pages in Contact, how I can remove this?

How to remove boot security pattern permanently?

Hi,
sorry up front if this is a redunant question but I've locked my phone with FP and pin/pattern on MIUI. After switching to LOS the boot pattern is still active. Wiping /data with TWRP didn't help. How can I remove/delete it permenantly? Any hints/links? I couldn't find anything useful using the search though .
saski4711 said:
Hi,
sorry up front if this is a redunant question but I've locked my phone with FP and pin/pattern on MIUI. After switching to LOS the boot pattern is still active. Wiping /data with TWRP didn't help. How can I remove/delete it permenantly? Any hints/links? I couldn't find anything useful using the search though .
Click to expand...
Click to collapse
Theres a zip to remove lockscreen passwords, after you redo ur pattern and whatever, enter fingerprint and you need to reenable smart lock in trusted agents, because it won't show otherwise.
This is also the same thing just manually
Patch rom
Via
Orangfox or pitchblack recivery during flashing
Mooatreides said:
Theres a zip to remove lockscreen passwords, after you redo ur pattern and whatever, enter fingerprint and you need to reenable smart lock in trusted agents, because it won't show otherwise.
This is also the same thing just manually
Click to expand...
Click to collapse
could you pinpoint me to that zip please?
saif hussain said:
Patch rom
Via
Orangfox or pitchblack recivery during flashing
Click to expand...
Click to collapse
So orange fox recovery can actually erase the pattern? can I do this via hotboot since I use TWRP?
saski4711 said:
could you pinpoint me to that zip please?
Click to expand...
Click to collapse
Follow the video its easy and does the same, i tried uploading it and it dint work
Ok guys I managed to do this with TWRP by formatting/wiping everything. Was going to install another custom ROM anyway so I didn't mind the data loss.
Anyway thx for your help! :highfive:
saski4711 said:
So orange fox recovery can actually erase the pattern? can I do this via hotboot since I use TWRP?
Click to expand...
Click to collapse
Switch to orange fox
Its a easy wau

SMS failure after root with Magisk

Hello,
maybe someone would be able to help or explain. Running on 9.1.0.215 (but tried with 9.1.0.210 as well), after I try to root with Magisk (=flash patched recovery_ramdisk), my SMS stop working. I've tried more applications (default 'Messaging', Google 'Messages', also Facebook 'Messenger') but no chance, phone is not able to receive or create any SMS messages. However, everything else is working fine.
I'm pretty sure that it's caused by this activity, because when I flash back original RECOVERY_RAMDIS.img, SMS are back again.
Any ideas what could be wrong? I really like to use Magisk, but unfortunately, it's no go without SMS.
Thanks!
1. Flash stock recovery_ramdisk. (If you already flash magisk patched ramdisk). Stock recovery is needed to factory reset.
2. back up your data.
3. reboot to recovery. Perform factory reset
4. Power off device. Hold volume down, plug usb to boot to bootloader.
5. flash magisk patched recovery ramdisk
6. Reboot by holding power + volume up button.
7. Done
buchman said:
1. Flash stock recovery_ramdisk. (If you already flash magisk patched ramdisk). Stock recovery is needed to factory reset.
2. back up your data.
3. reboot to recovery. Perform factory reset
4. Power off device. Hold volume down, plug usb to boot to bootloader.
5. flash magisk patched recovery ramdisk
6. Reboot by holding power + volume up button.
7. Done
Click to expand...
Click to collapse
Thanks for hint!
Doing factory reset isn't exactly one's wish, but if there is no other choice I will definitely give it a try. Speaking of backup/restore of apps - can you please give me a hint, what could be the most comfortable way of doing that? I do not care about data - that is easy to backup/restore - but is there any simple way how to avoid manual re-installation of all apps after restore?
Thanks again!
burton_mb said:
I'm pretty sure that it's caused by this activity, because when I flash back original RECOVERY_RAMDIS.img, SMS are back again.
Click to expand...
Click to collapse
Hi, just to confirm that I had exactly the same problem. To solve it, I had to reinstall the original recovery ramdisk.
burton_mb said:
Thanks for hint!
Doing factory reset isn't exactly one's wish, but if there is no other choice I will definitely give it a try. Speaking of backup/restore of apps - can you please give me a hint, what could be the most comfortable way of doing that? I do not care about data - that is easy to backup/restore - but is there any simple way how to avoid manual re-installation of all apps after restore?
Thanks again!
Click to expand...
Click to collapse
When you go through the setup it should suggest it if you've backed up to drive. Otherwise use titanium backup. It saves the apks and works with root
pierangelof said:
Hi, just to confirm that I had exactly the same problem. To solve it, I had to reinstall the original recovery ramdisk.
Click to expand...
Click to collapse
But reinstall original recovery ramdisk means no root, right?
Did you succeed with rooting afterwards, e. g. with factory reset like suggested above?
burton_mb said:
But reinstall original recovery ramdisk means no root, right?
Click to expand...
Click to collapse
Yes, this was the price to pay to get the SMS working again
burton_mb said:
Did you succeed with rooting afterwards, e. g. with factory reset like suggested above?
Click to expand...
Click to collapse
I haven't tried it, sorry.
I ran into this problem on my honor 9 and in addition to a not working sms-app,the dialer app was broken aswell.
I did find this thread https://forum.xda-developers.com/mate-10/how-to/fix-messages-dialer-9-1-root-required-t3955964 and this fixed both issues.
adb shell
su
rm /data/user/0/com.android.providers.telephony/databases/*
rm /data/user/0/com.android.providers.contacts/databases/*
Go back to phone and wipe data of Phone and Messages
Go back to command prompt and:
reboot recovery​
Sheepy777 said:
I ran into this problem on my honor 9 and in addition to a not working sms-app,the dialer app was broken aswell.
I did find this thread https://forum.xda-developers.com/mate-10/how-to/fix-messages-dialer-9-1-root-required-t3955964 and this fixed both issues.
adb shell
su
rm /data/user/0/com.android.providers.telephony/databases/*
rm /data/user/0/com.android.providers.contacts/databases/*
Go back to phone and wipe data of Phone and Messages
Go back to command prompt and:
reboot recovery​
Click to expand...
Click to collapse
Thank you very much! This helped even without factory reset! :good::good::good:
burton_mb said:
Thank you very much! This helped even without factory reset! :good::good::good:
Click to expand...
Click to collapse
Glad I could help I tried a factory reset and rooted afterwards, but as soon as magisk was flashed, sms stopped working and tons of "access denied" or so errors started to show up in the log.
Hello, is it still possible to root the phone? I want to get rid of all the huawei apps and I need adaway.
timenewroman said:
Hello, is it still possible to root the phone? I want to get rid of all the huawei apps and I need adaway.
Click to expand...
Click to collapse
If your bootloader is unlocked, yes it's still possible
Sheepy777 said:
If your bootloader is unlocked, yes it's still possible
Click to expand...
Click to collapse
And any chances of unlocking the bootloader with Android 9?
Enviado desde mi STF-L09 mediante Tapatalk
xaametz said:
And any chances of unlocking the bootloader with Android 9?
Enviado desde mi STF-L09 mediante Tapatalk
Click to expand...
Click to collapse
I unlocked my bootloader last year, when you could get the unlock code from their website. Unlocking your bootloader on Pie with one of those codes should still work.
I don't know, if other unlocking method like dc-unlocker or funkyhuawei will work. Sry
Sheepy777 said:
I ran into this problem on my honor 9 and in addition to a not working sms-app,the dialer app was broken aswell.
I did find this thread https://forum.xda-developers.com/mate-10/how-to/fix-messages-dialer-9-1-root-required-t3955964 and this fixed both issues.
adb shell​su​rm /data/user/0/com.android.providers.telephony/databases/*​rm /data/user/0/com.android.providers.contacts/databases/*​​Go back to phone and wipe data of Phone and Messages​Go back to command prompt and:​reboot recovery​
Click to expand...
Click to collapse
Thank youuuuuu this worked perfectly for me. I had to change the directory name from user to user_de, but once I did that, it was perfect And I didn't even lose my text messages
Oh no This solution worked, but after doing it, I no longer have access to 4G/LTE on my phone. Did this happen to anyone else? Is there a fix for this?

[ROM][GSI] AOSP 10 - Discussion

Hi, I have been testing this on this device, and finally I was able to make AOSP 10 (GSI) run on our device.
Our device needs overlay to fix this issues. I will try to work into that
How to flash
WARNING: Your device must have unlocked bootloader
1. Download the latest TWRP Recovery: https://forum.xda-developers.com/mi...overy-unofficial-twrp-xiaomi-mi-note-t4015805
2. Download the latest AOSP 10 GSI (ab with gapps): https://github.com/phhusson/treble_experimentations/releases/
3. Download vbmeta.img: https://github.com/TadiT7/xiaomi_ce...9.3.1-release-keys/firmware-update/vbmeta.img
4. Disable vbmeta partition by flashing vbeta.img
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5. Flash TWRP
Code:
fastboot flash recovery <twrp_file_name.img>
6. Boot TWRP, make wipe (Format Data only!)
7. Flash the AOSP system.img file to System partition
NOTE: Trying to flash system.img using fastboot causes bootloop.
Aditionally here you can flash GAPPS and Magisk
- Flash GAPPS: https://opengapps.org/
- Flash Magisk: https://github.com/topjohnwu/Magisk/releases
10. Reboot system & enjoy!
Bugs
- Fingerprint
- Auto-brightness
- NFC
-Weird notification audio: can be fixed flashing this -> https://github.com/hmuny99/GsiSystemAudioFix/raw/master/fixaudiogsi.zip
-Video recording: can be fixed by flashing this -> https://forum.xda-developers.com/attachment.php?attachmentid=4374464&d=1514638461
-Flashing Magisk causes bootloop
- GCAM Camera starts to lag when the device has been on for a long time
Since we have a complete kernel sources/device tree, we can have this as a daily diver :good:
For now, I'd need the framework-res.apk from Stock rom, if someone could provide it, that would be really helpful
iFlashed said:
For now, I'd need the framework-res.apk from Stock rom, if someone could provide it, that would be really helpful
Click to expand...
Click to collapse
I saw this on another topic.
https://forum.xda-developers.com/showpost.php?p=81824837&postcount=50
Hi, what do you think, this flashing method will work with phhussons GSI too?
https://github.com/phhusson/treble_experimentations/releases
---------- Post added at 08:00 AM ---------- Previous post was at 07:43 AM ----------
If you need it still, I can copy it now, if you tell me the full path of this file.
technoboi1 said:
Hi, what do you think, this flashing method will work with phhussons GSI too?
https://github.com/phhusson/treble_experimentations/releases
---------- Post added at 08:00 AM ---------- Previous post was at 07:43 AM ----------
If you need it still, I can copy it now, if you tell me the full path of this file.
Click to expand...
Click to collapse
Same steps, Boots up, I recommend the system-quack-arm64-ab-gapps from your link, as it includes Gapps.
However, With that both I couldn't flash Magisk or I would get a bootloop. With LoS It would also not install gapps. But would boot just fine without Gapps or Magisk.
Currently Phhussons is working with Gapps. LOS Is not, atleast for me, but neither is working with Magisk 20.4.
thank for your reply, it has same bugs like LOS?
deathhall said:
Same steps, Boots up, I recommend the system-quack-arm64-ab-gapps from your link, as it includes Gapps.
However, With that both I couldn't flash Magisk or I would get a bootloop. With LoS It would also not install gapps. But would boot just fine without Gapps or Magisk.
Currently Phhussons is working with Gapps. LOS Is not, atleast for me, but neither is working with Magisk 20.4.
Click to expand...
Click to collapse
technoboi1 said:
thank for your reply, it has same bugs like LOS?
Click to expand...
Click to collapse
Yup, Same bugs
Sent from my Mi Note 10 using Tapatalk
I remember when Android P GSI comes, we have distorted audio bugs, maybe its same bug again.
Deleting folder vendor/lib64/soundfx fixed bug in Android P.
Bugs
- Fingerprint
- Auto-brightness
- NFC
-Weird notification audio
I have been working on an overlay, but seems like I couldn't fix any bug.
Fingerprint works, but for any reason the Google API/Fingerprint config app is not recognizing it, but I can see in logcat that sensor recognizes when I use the fingerprint with any problem, so maybe problem from the GSI?
For the rest of the bugs, nothing for now
Is there an improvement?
UtkuAblak said:
Is there an improvement?
Click to expand...
Click to collapse
I'm trying to contact with phhusson. Audio can be fixed flashing a .zip
This rom use stock camera or? And what about current photo quality?
Good work and thank you guys!
Hudinited said:
This rom use stock camera or? And what about current photo quality?
Good work and thank you guys!
Click to expand...
Click to collapse
I recommend using a Gcam in order to get better quality, for example: https://www.celsoazevedo.com/files/android/google-camera/dev-urnyx05/ (tell me if you find something better!)
how did you fix the fingerprint?
iSonik said:
how did you fix the fingerprint?
Click to expand...
Click to collapse
It's not fixed yet, What I just said is that 'works' in terms that if you touch the fingerprint it will be recognized in logcat, but nothing will happend on the fingerprint setup app. Currently I'm talking with phhusson about this and thinks that this could be a GSI related issue because he told me he will make a test image
technoboi1 said:
Hi, what do you think, this flashing method will work with phhussons GSI too?
https://github.com/phhusson/treble_experimentations/releases
---------- Post added at 08:00 AM ---------- Previous post was at 07:43 AM ----------
If you need it still, I can copy it now, if you tell me the full path of this file.
Click to expand...
Click to collapse
iFlashed said:
It's not fixed yet, What I just said is that 'works' in terms that if you touch the fingerprint it will be recognized in logcat, but nothing will happend on the fingerprint setup app. Currently I'm talking with phhusson about this and thinks that this could be a GSI related issue because he told me he will make a test image
Click to expand...
Click to collapse
My fingerprint is recognized in logcat as well as the button lighting up, but it doesn't work even in stock rom funny enough.
deathhall said:
My fingerprint is recognized in logcat as well as the button lighting up, but it doesn't work even in stock rom funny enough.
Click to expand...
Click to collapse
What do you mean when you say It doesn't work in stock rom funny enough?
iFlashed said:
What do you mean when you say It doesn't work in stock rom funny enough?
Click to expand...
Click to collapse
When I flashed this GSI for Lineage 17 when the other thread first started, even after Miflashing back to Global Stock my fingerprint doesn't work anymore, If i use the testing options, it'll activate the fingerprint and register me using my finger on it, but wont activate fingerprint settings as a password, it goes to the input screen then kicks back out immediately
deathhall said:
When I flashed this GSI for Lineage 17 when the other thread first started, even after Miflashing back to Global Stock my fingerprint doesn't work anymore, If i use the testing options, it'll activate the fingerprint and register me using my finger on it, but wont activate fingerprint settings as a password, it goes to the input screen then kicks back out immediately
Click to expand...
Click to collapse
This could be something related to unlocked bootloader? u tried to relock the bootloader?
iFlashed said:
This could be something related to unlocked bootloader? u tried to relock the bootloader?
Click to expand...
Click to collapse
Are you asking if i did, or i should? Also, I don't wanna hijack the thread, maybe chat in PM or Discord or whatever you prefer?

Question Magisk

Hi friends. Bought my one on *site name*. China version. How to install Magisk root? I tried to boot patched boot.img... didn't help
have you unlock your phone?
AmbazidA said:
have you unlock your phone?
Click to expand...
Click to collapse
Yea
Rezinochka said:
Yea
Click to expand...
Click to collapse
okay, was the flashing of patch boot image not successful? or what error did you find?
AmbazidA said:
okay, was the flashing of patch boot image not successful? or what error did you find?
Click to expand...
Click to collapse
In adb it wrote "OKAY". But in magisk root haven't installed.
may be you can try this; launch magisk app already installed in the phone and select direct install(recommended), wait for the process to complete and reboot. it might help
If for some reason it’s not already installed, install it.
AmbazidA said:
may be you can try this; launch magisk app already installed in the phone and select direct install(recommended), wait for the process to complete and reboot. it might help
Click to expand...
Click to collapse
Sorry, didn't understand wdym
Sirs. With your permission, we will continue tomorrow morning. I am forced to leave you for an indefinite period for the time being.
Ok. Good morning "Vietnam"
AmbazidA said:
may be you can try this; launch magisk app already installed in the phone and select direct install(recommended), wait for the process to complete and reboot. it might help
Click to expand...
Click to collapse
I didn't understand wdym
Is the magisk app currently on your device?
If so, enter it, and clcik on the install button. Then click on”direct install”
Arealhooman said:
Is the magisk app currently on your device?
Click to expand...
Click to collapse
Yes
Arealhooman said:
If so, enter it, and clcik on the install button. Then click on”direct install”
Click to expand...
Click to collapse
I patched boot.img earlier
this video will walk you through rooting the Redmi Note 12
-
Enddo said:
this video will walk you through rooting the Redmi Note 12
-
Click to expand...
Click to collapse
Thx, i will try
Enddo said:
this video will walk you through rooting the Redmi Note 12
-
Click to expand...
Click to collapse
i tried with different versions of rom and magisk. So it doesnt work. And in video he flash patched file to the boot_a. I can flash it only to boot_b
Rezinochka said:
i tried with different versions of rom and magisk. So it doesnt work. And in video he flash patched file to the boot_a. I can flash it only to boot_b
Click to expand...
Click to collapse
it will flash to whatever your current partition is set to. some will be set to the _a partition and others will be set to the _b partition. it all depends on how many OTA updates you have installed (or if you've manually switched partitions for some reason)
the video does work, my Redmi Note 12 is rooted right now
IDK if it will work or not. But at least you could try. Someone suggested to patch init_boot.img on the Redmi note 12 4g forum.
Actual Post

Categories

Resources