1.I have a rog phone 5 covert to tecentgame. When I move to version WW but then there is a fingerprint error (losing the system fingerprint authentication). Who can help me?
2.There is an opinion that restoring the system partition can fix the above situation, do not know if it is true or false?can anyone guide me on how to do the above?
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
It's a known issue. As of yet, it appears this is a drawback to the conversion.
I'm currently working on a solution to get fingerprint working after a conversion. I've located the error and a Magisk module should be able to fix it. I can't make any promises until that theory is fully tested, though.
Of course my Magisk install is broken and won't install from storage...
I need the system/vendor/etc/vendor_(something)_styles.xml
Started a thread for it, since those with a working reader are unlikely to be looking through this thread.
losing fingerprint sensor happend always or its random issue?
yaser86100 said:
losing fingerprint sensor happend always or its random issue?
Click to expand...
Click to collapse
It's basically part of the conversion until that is perfected.
twistedumbrella said:
It's basically part of the conversion until that is perfected.
Click to expand...
Click to collapse
maybe one day thats be perfect ?
yaser86100 said:
maybe one day thats be perfect ?
Click to expand...
Click to collapse
Probably. They got there on the 3, from what I've seen.
..................
twistedumbrella said:
It's basically part of the conversion until that is perfected.
Click to expand...
Click to collapse
Unlocking BL and converting WW, there is a chance of losing your fingerprints, but back up the persist partition before conversion, you don’t have to worry about losing your fingerprints. Once you lose your fingerprints, you only need to restore the persist partition and your fingerprints will be normal. But it can only correspond to this phone, and restore on other phones is not possible.
yaser86100 said:
losing fingerprint sensor happend always or its random issue?
Click to expand...
Click to collapse
The quote below was meant for you. No idea why I was tagged instead.
johnny886 said:
Unlocking BL and converting WW, there is a chance of losing your fingerprints, but back up the persist partition before conversion, you don’t have to worry about losing your fingerprints. Once you lose your fingerprints, you only need to restore the persist partition and your fingerprints will be normal. But it can only correspond to this phone, and restore on other phones is not possible.
Click to expand...
Click to collapse
twistedumbrella said:
I need the system/vendor/etc/vendor_(something)_styles.xml
Started a thread for it, since those with a working reader are unlikely to be looking through this thread.
Click to expand...
Click to collapse
what shoul i change?
i rooted my rog phone 5
i dont know what to do to being back my fingerprint
i havent backuped
shayantt98 said:
what shoul i change?
i rooted my rog phone 5
i dont know what to do to being back my fingerprint
i havent backuped
Click to expand...
Click to collapse
Follow one of the newer threads. The info here is extremely outdated.
Related
Hi,
can anyone enlighten me as to what is the most up to date software.
Is it the "fix" software distributed by Oneplus
https://forums.oneplus.net/threads/fix-stuck-at-boot-logo-boot-loop-random-reboot.160199/
Or s it the Cyanogenmod Factory fastboot images here
https://cyngn.com/products/oneplusone/
I have examined the contents and much of the content seems to be the same (img files have same name and size) but there are exceptions such as boot.img
What is the most up to date boot .img to use?
Any ideas?
I dont have any of the problems listed and my OPO is spot on, but I still want to know what the most up to date "stock" software is.
I have asked the same question to oneplus but have not yet received a response.
would like to know as well.
jeffrey1027 said:
would like to know as well.
Click to expand...
Click to collapse
Hopefully, if there is anything new in the OPlus fix it will be released as a new image by Cyanogenmod soon. That way we have a decent reference point.
They are essentially the same, the "Fix" has the ColorOS partitions included (Persist.img & Reserve4.img) which alleviates some problems which some has experienced. But the software is the exact same version. I can tell you that the "Fix" version is a VERY easy way of updating your phone, as its a series of only 3 files you have to run compared to quite a number of fastboot commands for the Cyan Factory images version. In the end though both are 38R.
S M G said:
They are essentially the same, the "Fix" has the ColorOS partitions included (Persist.img & Reserve4.img) which alleviates some problems which some has experienced. But the software is the exact same version. I can tell you that the "Fix" version is a VERY easy way of updating your phone, as its a series of only 3 files you have to run compared to quite a number of fastboot commands for the Cyan Factory images version. In the end though both are 38R.
Click to expand...
Click to collapse
Will the the 'fixes' remove unlock and root?
JeffDC said:
Will the the 'fixes' remove unlock and root?
Click to expand...
Click to collapse
YES, it will wipe your device entirely leading to loss of root and it re-locks your bootloader. If you are already on 38R i don't see any advantages for you to flash this "FIX"
Thanks for the info. Appreciated. Any more detail on what the reserve4 and persist IMG do, can they be flashed on top of an existing install (38r factory).
What is the supported boot.IMG?
JeffDC said:
Will the the 'fixes' remove unlock and root?
Click to expand...
Click to collapse
zaphodbeeb said:
Thanks for the info. Appreciated. Any more detail on what the reserve4 and persist IMG do, can they be flashed on top of an existing install (38r factory).
Click to expand...
Click to collapse
YES, they can be flashed on top of a currently installed 38R without any data lost etc. AFAIK both persist and reserve4 are ColorOS specific partitions which somehow become corrupted during CyanogenMod software updates. This leads to all kinds of issues e,g, Lost IMEI,Boot Loops,CM Lockscreen FC etc. Any by simply erasing them and re-flashing them fixes many of the above if not all.
Tested the new "fix"
Does not fix my wif issue where it turns orange after idling.
I was able to flash the rooted boot.img, but it seems to have caused a problem with the fingerprint sensor. It works a little after a fresh reboot, but then it stops working completely. Anyone have an idea as to why and maybe how I can fix it?
i have the same problem, you fix it?
Probably, incompatible Boot
Try flash stock Boot back and check Fingerprint
5[Strogino] said:
Probably, incompatible Boot
Try flash stock Boot back and check Fingerprint
Click to expand...
Click to collapse
yeah, but we dont have the stock boot, we have tha us version c567 and its not online yet
Same problem
Abumarf said:
I was able to flash the rooted boot.img, but it seems to have caused a problem with the fingerprint sensor. It works a little after a fresh reboot, but then it stops working completely. Anyone have an idea as to why and maybe how I can fix it?
Click to expand...
Click to collapse
Hi Abumarf and depooltrd,
I have the same symptoms. I've flashed boot.img from C432 (rooted now) to my C567. It was the only way to unbrick it.
What region is rooted boot.img you flashed from. Do you think it is a software problem, not a hardware one?
Also, could anyone who has rooted MHA-L29C567B138 confirm that the fingerprint sensor works fine?
night_wind said:
Hi Abumarf and depooltrd,
I have the same symptoms. I've flashed boot.img from C432 (rooted now) to my C567. It was the only way to unbrick it.
What region is rooted boot.img you flashed from. Do you think it is a software problem, not a hardware one?
Also, could anyone who has rooted MHA-L29C567B138 confirm that the fingerprint sensor works fine?
Click to expand...
Click to collapse
I'm not sure as to what region I flashed but I can guarantee you it's a software problem. After checking the System/Bin/ it was clear that the fingerprintID folder and a few others were missing. This is most likely what causes the Fingerprint sensor to no longer work. All we can do is wait for Huawei to release the complete C567 update so we can revert to complete stock.
Abumarf said:
I can guarantee you it's a software problem. After checking the System/Bin/ it was clear that the fingerprintID folder and a few others were missing.
Click to expand...
Click to collapse
That is promising. So did you notice these problems right after you had flashed the boot.img?
BTW, it could work for hours after a fresh restart for me. What about yours?
night_wind said:
That is promising. So did you notice these problems right after you had flashed the boot.img?
BTW, it could work for hours after a fresh restart for me. What about yours?
Click to expand...
Click to collapse
Yes, as soon as I flashed both boot images that I had. One with root and the other with stock. I asked around and a dev buddy of mine told me that the KangVIP root isn't always interchangeable with the non-KangVIP roms. It was the same case for the Mate 8. Mine works for a few minutes at most, but I did flash an unknown stock boot image though it did nothing. It's a pain to live without a fingerprint sensor
Abumarf said:
Yes, as soon as I flashed both boot images that I had. One with root and the other with stock. I asked around and a dev buddy of mine told me that the KangVIP root isn't always interchangeable with the non-KangVIP roms. It was the same case for the Mate 8. Mine works for a few minutes at most, but I did flash an unknown stock boot image though it did nothing. It's a pain to live without a fingerprint sensor
Click to expand...
Click to collapse
I've just ran into this same issue, you think someone could just upload the missing files?
posydon1 said:
I've just ran into this same issue, you think someone could just upload the missing files?
Click to expand...
Click to collapse
I don't think so but I think there may be some hope. Ajsmsg78 released a full root and encryption guide (https://forum.xda-developers.com/mate-9/development/root-root-mate-9-t3556590) which I'm going to try from the complete beginning later to see if it'll restore functionality.
Abumarf said:
I don't think so but I think there may be some hope. Ajsmsg78 released a full root and encryption guide (https://forum.xda-developers.com/mate-9/development/root-root-mate-9-t3556590) which I'm going to try from the complete beginning later to see if it'll restore functionality.
Click to expand...
Click to collapse
That's exactly how I ended up here lol. His method works great but some file are still missing.
posydon1 said:
That's exactly how I ended up here lol. His method works great but some file are still missing.
Click to expand...
Click to collapse
Then we may be stuck until Huawei releases the C567 update. It's pretty disappointing that we seem to be the only version without an update even after almost a month and a half from release. :crying:
Abumarf said:
Then we may be stuck until Huawei releases the C567 update. It's pretty disappointing that we seem to be the only version without an update even after almost a month and a half from release. :crying:
Click to expand...
Click to collapse
Hey Abumarf,
Looks like Huawei released the new MHA-L29C567B167 and also decrypted-boot-MHA-L29C567B138.img has appeared as well. Did you try to flash any of them? Did it fix the fingerprint sensor?
night_wind said:
Hey Abumarf,
Looks like Huawei released the new MHA-L29C567B167 and also decrypted-boot-MHA-L29C567B138.img has appeared as well. Did you try to flash any of them? Did it fix the fingerprint sensor?
Click to expand...
Click to collapse
No I haven't as of yet. I've been trying to download the C567B167 OTA through Firmware Finder but it wasn't working for me. I also haven't had much time to look into it. If you or anyone else do end up trying either of the solutions, please let me know.
Abumarf said:
No I haven't as of yet. I've been trying to download the C567B167 OTA through Firmware Finder but it wasn't working for me. I also haven't had much time to look into it. If you or anyone else do end up trying either of the solutions, please let me know.
Click to expand...
Click to collapse
I tried decrypted-boot-MHA-L29C567B138.img and it fixed the fingerprint sensor, but I didn't manage to restore data partitions and the ROM wasn't full. Finally, I updated through FunkyHuawei and everything works fine now.
night_wind said:
I tried decrypted-boot-MHA-L29C567B138.img and it fixed the fingerprint sensor, but I didn't manage to restore data partitions and the ROM wasn't full. Finally, I updated through FunkyHuawei and everything works fine now.
Click to expand...
Click to collapse
I also did just that but just fixed the problem with the Huawei apps and system update by changing a few file names. Works like a charm now. Will wait till Monday and attempt to flash the B167 update. But as of now, I'm fully root, decrypted, and enjoying life!
Applying now...
Xda need an update too lol
Are touch screen issues present on the latest October build when using TWRP? I know hyp and rpm were updated last month, just curious if that touch issues remains on this newer build in TWRP?
Does magisk work after this Update?
Sorry guys can't answer ur questions cause I'm on stock locked bootloader not planning on modifying my phone.
All i can say for now that the phone feel faster and scrolling is better.
Did you ever have bluetooth issues and if so, did the patch happen to address the issue?
Alexis96312 said:
Does magisk work after this Update?
Click to expand...
Click to collapse
Yes, no issues with Magisk. But, I came from a clean fastboot flash and redid twrp and Magisk.
Topdroid01 said:
Did you ever have bluetooth issues and if so, did the patch happen to address the issue?
Click to expand...
Click to collapse
I would lose connection to my car after a few minutes but other devices worked fine. With the October update I connected to my car no problem and it held for well over an hour a reconnected just fine after getting out and back in. So I would say yes, the patched helped my Bluetooth issues.
how do you apply the normal image through the other or through twrp or through what? Sorry
Enviado desde mi PH-1 mediante Tapatalk
Notch settings are back under developer settings
garywojdan81 said:
Notch settings are back under developer settings
Click to expand...
Click to collapse
How to use full screen with Youtube? I see no difference on different options.
mcdull said:
How to use full screen with Youtube? I see no difference on different options.
Click to expand...
Click to collapse
pinch zoom out
I don't know how this feature worked in Oreo because I bought the phone when Pie was released. But on Pie and Firefox I don't get any difference with the notch settings.
Edit: Same for Chrome.
Pinch to zoom
resaik said:
Pinch to zoom
Click to expand...
Click to collapse
Maybe I'm blind and just don't see it, but what shall happen? Notch area has same color than the app, that's all what I notice. I believed e. g. the box where to enter the URL will be "behind" the notch or similar?
Edit: Maps works as my expectation: additional screen where the map is shown.
mcdull said:
How to use full screen with Youtube? I see no difference on different options.
Click to expand...
Click to collapse
That's a separate thing with the YouTube app. Just expand the screen by stretching it with multitouch during video play.
I'm rooted with Magisk but keep saying "Stock Backup does not exist". How can I fix this??
Yup, "Use Notch" doesn't work like it did on Oreo, and now I cant go back to Oreo from Pie. I fastboot flash Orea and after booting to the setup screen touch is unresponsive. UGH..
elinca247 said:
Yup, "Use Notch" doesn't work like it did on Oreo, and now I cant go back to Oreo from Pie. I fastboot flash Orea and after booting to the setup screen touch is unresponsive. UGH..
Click to expand...
Click to collapse
You have to unlock critical partitions then reflash the fastboot files. The critical partitions house the touchscreen firmware.
Alexis96312 said:
I'm rooted with Magisk but keep saying "Stock Backup does not exist". How can I fix this??
Click to expand...
Click to collapse
just flash back to stock and reapply twrp and magisk. remember to use the twrp-sept.img as temp image.
Fastboot command
Ascertion said:
You have to unlock critical partitions then reflash the fastboot files. The critical partitions house the touchscreen firmware.
Click to expand...
Click to collapse
Can you please provide the fastboot command to unlock the critical partions?
disregard found command. thanks for the reply.
For the sake of discussion, y'all ever see Tassadar's Multirom making a comeback ever? It was the absolute coolest thing ever!
That said, the new way Android works most likely killed this off entirely. A/B partitions that share userdata, and encryption that locks you out of your phone unless the security patch at least matches. Kinda hate the new way Android works to be honest.
If you remove encryption and AVB/Verity shouldnt it still work?
virtyx said:
If you remove encryption and AVB/Verity shouldnt it still work?
Click to expand...
Click to collapse
See now you got me thinking... Since Multirom mounts the userdata as system and then isolates the userdata for secondaries, it should right? Although people who have removed encryption on these newer devices have said you can't even have a screen lock or fingerprint at all with encryption gone, that's a big trade off. Hmm...
H4X0R46 said:
See now you got me thinking... Since Multirom mounts the userdata as system and then isolates the userdata for secondaries, it should right? Although people who have removed encryption on these newer devices have said you can't even have a screen lock or fingerprint at all with encryption gone, that's a big trade off. Hmm...
Click to expand...
Click to collapse
Hello, so what do you think is a good thing or a bad thing?
Personally, I'm a little afraid about that
H4X0R46 said:
See now you got me thinking... Since Multirom mounts the userdata as system and then isolates the userdata for secondaries, it should right? Although people who have removed encryption on these newer devices have said you can't even have a screen lock or fingerprint at all with encryption gone, that's a big trade off. Hmm...
Click to expand...
Click to collapse
On my pixel 3, removing encryption wouldn't let me use a pin or finger print to unlock, so no gpay.
On my 7 pro I tested out removing encryption and everything still worked perfectly, even removed Verity/ AVB too, fingerprint and pin worked fine.
I think the reason it didn't work on my pixel 3 is the Titan chip - but I'm unsure.
virtyx said:
On my pixel 3, removing encryption wouldn't let me use a pin or finger print to unlock, so no gpay.
On my 7 pro I tested out removing encryption and everything still worked perfectly, even removed Verity/ AVB too, fingerprint and pin worked fine.
I think the reason it didn't work on my pixel 3 is the Titan chip - but I'm unsure.
Click to expand...
Click to collapse
So you were able to keep your screen lock? That's neat! [emoji848] How do you remove encryption on these newer devices? I remember it used to just be a flag in the boot image, but has that changed?
H4X0R46 said:
So you were able to keep your screen lock? That's neat! [emoji848] How do you remove encryption on these newer devices? I remember it used to just be a flag in the boot image, but has that changed?
Click to expand...
Click to collapse
Firstly, you need to have twrp
Format data
Then
Make sure vendor is mounted
You need to pull the vendor/etc/fstab file to your PC
Rename "fileencryption" to "encryptable"
Then push it back to the vendor/etc location
I also make it a habit to do this before flashing magisk when unencrypted
Echo "KEEPVERITY" = false>>/data/.magisk
Echo "KEEPFORCEENCRYPT" =false>>/data/.magisk
Install magisk
And it's done.
To keep unencrypted between updates, you need to do the fstab move again in twrp and flash magisk again before first boot.
I suspect the pixels Titan chip prevents us from using a screen lock when decrypted
Which is silly, but I understand the security behind it.
virtyx said:
Firstly, you need to have twrp
Format data
Then
Make sure vendor is mounted
You need to pull the vendor/etc/fstab file to your PC
Rename "fileencryption" to "encryptable"
Then push it back to the vendor/etc location
I also make it a habit to do this before flashing magisk when unencrypted
Echo "KEEPVERITY" = false>>/data/.magisk
Echo "KEEPFORCEENCRYPT" =false>>/data/.magisk
Install magisk
And it's done.
To keep unencrypted between updates, you need to do the fstab move again in twrp and flash magisk again before first boot.
I suspect the pixels Titan chip prevents us from using a screen lock when decrypted
Which is silly, but I understand the security behind it.
Click to expand...
Click to collapse
Shoot I might just do this! I've always hated having to match the security patch when flashing a rom, or getting locked out of my phone, this might actually be better since Incan try roms and scrap em easily if I don't like em like I used to do in the older days of Android. Thanks so much! Gonna screenshot these steps and give it a go when I have time. Worst case, I restore a backup or use the MSM Tool, so no biggie! [emoji4]
H4X0R46 said:
Shoot I might just do this! I've always hated having to match the security patch when flashing a rom, or getting locked out of my phone, this might actually be better since Incan try roms and scrap em easily if I don't like em like I used to do in the older days of Android. Thanks so much! Gonna screenshot these steps and give it a go when I have time. Worst case, I restore a backup or use the MSM Tool, so no biggie! [emoji4]
Click to expand...
Click to collapse
No worries! Shoot me a PM if you have trouble
There is a noverity zip lying around somewhere but I prefer to do the steps manually gives me piece of mind.
virtyx said:
No worries! Shoot me a PM if you have trouble
There is a noverity zip lying around somewhere but I prefer to do the steps manually gives me piece of mind.
Click to expand...
Click to collapse
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
This is the zip you mentioned right? Since the change is made in the vendor partition, flashing a stock boot image wouldn't set it back to forced right? Or wrong?
H4X0R46 said:
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
This is the zip you mentioned right? Since the change is made in the vendor partition, flashing a stock boot image wouldn't set it back to forced right? Or wrong?
Click to expand...
Click to collapse
Right, but full rom zip will revert it back
Would this possibly mean multirom would be possible?
i had changed motherboard everything work fine but fingerprint is not anyone can help ?
it's was work normally
batmon15 said:
i had changed motherboard everything work fine but fingerprint is not anyone can help ?
it's was work normal
Click to expand...
Click to collapse
batmon15 said:
i had changed motherboard everything work fine but fingerprint is not anyone can help ?
it's was work normally
Click to expand...
Click to collapse
It's called your persist partition. And probably should of backed it up before messing with device. They are device specific and don't think there is anything you can do now other than contact OnePlus .
mattie_49 said:
It's called your persist partition. And probably should of backed it up before messing with device. They are device specific and don't think there is anything you can do now other than contact OnePlus .
Click to expand...
Click to collapse
i still have old motherboard work fine only issue have with is locked network sim can you please help how to backup persist partition ?
batmon15 said:
i still have old motherboard work fine only issue have with is locked network sim can you please help how to backup persist partition ?
Click to expand...
Click to collapse
Partitions Backup & Restore - Apps on Google Play
Backup your important partitions to avoid any data or IMEI corruption
play.google.com
Store in the cloud.
mattie_49 said:
It's called your persist partition. And probably should of backed it up before messing with device. They are device specific and don't think there is anything you can do now other than contact OnePlus .
Click to expand...
Click to collapse
thank you for help i found it '' https://www.droidwin.com/take-a-backup-of-persist-partition-fix-fingerprint-not-working/ ''
mattie_49 said:
Partitions Backup & Restore - Apps on Google Play
Backup your important partitions to avoid any data or IMEI corruption
play.google.com
Store in the cloud.
Click to expand...
Click to collapse
need to unlocked bootloder or not ?
batmon15 said:
i had changed motherboard everything work fine but fingerprint is not anyone can help ?
it's was work normally
Click to expand...
Click to collapse
I saw from a few post ago from your's, that you used to have sim locked from T mobile. Did you manage to unlock it? How?
Fors4kenArg said:
I saw from a few post ago from your's, that you used to have sim locked from T mobile. Did you manage to unlock it? How?
Click to expand...
Click to collapse
yes i got unlocked motherboard and i changed it with locked one that's only one solution i have tried everything nothing worked for me