[GUIDE][FLASHABLE][ZIP] How to fix fingerprint error on Oreo custom roms - Moto G5S Guides, News, & Discussion

This tutorial is for people who can not use fingerprints on oreo custom roms and for people who do not have a computer and want to use this function.
Installation:
Download the zip file and flash it in recovery.
Download:https://androidfilehost.com/?fid=1395089523397943846
[19/04/2019] UPDATE: Not working, i will fix it soon.
This file is for oreo custom rom, if you want a zip for pie roms, i already made one, go check it! https://forum.xda-developers.com/moto-g5s/how-to/guide-how-to-fix-fingerprint-error-pie-t3897399.

Related

Flash Stock ROM

Can I use TWRP flash stock ROM ?
Thanks
No you can't. It'll brick your phone. But there's a custom TWRP maybe called ZSL or something else which can flash stock ROM and bypass the security option.
rhrokib said:
No you can't. It'll brick your phone. But there's a custom TWRP maybe called ZSL or something else which can flash stock ROM and bypass the security option.
Click to expand...
Click to collapse
The recovery is zcx to be correct. I'd like to say that i already updated miui rom with twrp, all i did was downloading recovery rom from miui site and use the updater app included in miui rom. The only downside is i lost twrp and root but flash them after upgrade and everything was back to normal!!

New to device and the whole firmware thing

OK, long story short. Came for the nexus 6 and nexus 6p to oneplus 3t. The 6p had to flash vendor.IMG after every new ROM flash. But what is this whole firmware thing in this device? I have tried to find answers before asking but, what should I DO and NOT DO to have a brick? Like, wanting to go from a nougat ROM to an Oreo ROM, but not sure how. And then if I wanted to go from a n/o ROM to a beta, not sure how...then if I wanted to downgrade from an o or beta ROM.......please help
Treat the OP3T pretty much the same as you would the Nexus 6. The only difference is, like you've discovered, that OnePlus provides firmware files rather than factory images.
The installation instructions for the different firmwares (stable and beta) are found in the first few posts of the respective threads:
https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
https://forum.xda-developers.com/oneplus-3t/how-to/coming-update-oos-based-7-1-t3564240
It's pretty much the same as flashing vendor image. OnePlus just simply offers Firmware images which flash the Modem and the Firmware.
If you're gonna be on OxygenOS and Custom OxygenOS ROMs then you wont need to worry about flashing the firmware. Some of the Custom ROMs such as Paranoid Android and PureFusionOS also flash the recommended firmware automatically.
However, others don't and require you to flash a particular fimware image manually. Usually the Firmware to be used would be mentioned on the ROM thread itself.
Once you've Unlocked the bootloader and flashed a custom recovery, The most common process for flashing ROMs which do not have an included firmwares goes as follows:
1. Reboot To Recovery
2. Wipe Cache & Dalvik Cache, System and Data Partitions
3. Flash Firmware
4. Flash ROM Zip
5. Flash GAPPS
6. Flash Magisk/SuperSU (Optional).
7. Reboot
And that's it.
That is the standard procedure for most of the ROMs, but, I'd advice reading the OP Instructions properly first in case theres anything different.
PS. For moving to Oreo from Nougat, follow the same, but be warned, If your current ROM is encrypted and the new one isn't you'll be locked out of your device until you flash the old ROM back OR wipe userdata with fastboot, which wipes the Internal Storage.
PPS. For moving from a Custom ROM to Oxygen OS, best way to go would be to flash the official recovery again and sideload the official ROM zip via ADB (In some cases, encryption still might cause the same issue as above)
Mizart said:
It's pretty much the same as flashing vendor image. OnePlus just simply offers Firmware images which flash the Modem and the Firmware.
If you're gonna be on OxygenOS and Custom OxygenOS ROMs then you wont need to worry about flashing the firmware. Some of the Custom ROMs such as Paranoid Android and PureFusionOS also flash the recommended firmware automatically.
However, others don't and require you to flash a particular fimware image manually. Usually the Firmware to be used would be mentioned on the ROM thread itself.
Once you've Unlocked the bootloader and flashed a custom recovery, The most common process for flashing ROMs which do not have an included firmwares goes as follows:
1. Reboot To Recovery
2. Wipe Cache & Dalvik Cache, System and Data Partitions
3. Flash Firmware
4. Flash ROM Zip
5. Flash GAPPS
6. Flash Magisk/SuperSU (Optional).
7. Reboot
And that's it.
That is the standard procedure for most of the ROMs, but, I'd advice reading the OP Instructions properly first in case theres anything different.
PS. For moving to Oreo from Nougat, follow the same, but be warned, If your current ROM is encrypted and the new one isn't you'll be locked out of your device until you flash the old ROM back OR wipe userdata with fastboot, which wipes the Internal Storage.
PPS. For moving from a Custom ROM to Oxygen OS, best way to go would be to flash the official recovery again and sideload the official ROM zip via ADB (In some cases, encryption still might cause the same issue as above)
Click to expand...
Click to collapse
That was very informative, thank you!!! Just one more question tho. What would happen if I didn't flash the correct firmware? Like, there is a RR ROM with custom sultan or something that looks like it needs a beta firmware, I'm not in beta firmware, so would I have any issues?
jamescable said:
That was very informative, thank you!!! Just one more question tho. What would happen if I didn't flash the correct firmware? Like, there is a RR ROM with custom sultan or something that looks like it needs a beta firmware, I'm not in beta firmware, so would I have any issues?
Click to expand...
Click to collapse
I'm not entirely sure but in most cases the ROM would simply refuse to flash. Like for RR, if you don't flash a correct firmware then the flashing returns an "Error 7" and the installation stops. But even if it does flash through, it would either not connect to a network or get stuck in a bootloop, but nothing too serious which you can't rectify.

treble support or gsi flashing method

Hy everyone, need gsi flashing matheod and files for our dipper. Didn't find any telegram channel or link for these files. Thanks
Why would the Mi 8 be special? The instructions are exactly the same, copy over the system.img, flash it via TWRP.
Kaleem_qadir said:
Hy everyone, need gsi flashing matheod and files for our dipper. Didn't find any telegram channel or link for these files. Thanks
Click to expand...
Click to collapse
Seriously, GSI roms are good when you own a device that has no roms, or development has completely stopped.
There is truly no reason to use a GSI rom on the Mi8 and they can often be unstable. For example, sometimes you can do something so simple such as use substratum, or flash a Magisk update and it will crash your whole installation. recovery will often not work and you have to start over.
If you must try it, basically flash any stable rom and make a TWRP backup.
Unpack the GSI rom within your TWRP backup folder, then use TWRP restore to restore system files from the Twrp folder that you just unpacked the rom into.
Reboot to recovery, now reboot to system and wait up to 10 minutes. most of the time this is all that is needed.
Again, I absolutely do not recommend GSI's on the Mi8 because why would you need to? Also the Mi8 is a type A device, only use type A roms.
Just want to try Irfan gsi's like OOS.

Is it possible to flash stock ROM with TWRP?

I have the LOS ROM installed and while I love it, I love wifi calling even more.
TWRP is installed. Is it possible to flash the stock ROM with TWRP?
I searched....
I don't see why not. Then again I haven't used twrp is years.
I was able to flash a rom based of the stock rom, very easy

[solved]How to install stock ROM + custom kernel and Magisk?

Hello everyone,
I currently use the stock ROM + WirusMOD Nethunter modified Kernel and Magisk on my SM-G781B/DS.
I installed it quite a while ago using TWRP. I'm still on Android 11 and I'd like to upgrade my system. OTA doesn't work, and I decided to just wipe and completly re-install the stock rom. The Magisk installation guide recommends patching the AP of the ROM over flashing via custom recovery. A custom recovery prohibits OTA upgrades as far as I know, so I would prefer to just keep the stock recovery.
So this is what I planned:
1. modify freshly downloaded stock ROM with Magisk
2. *somehow* install kernel in stock ROM if possible?
3. flash via ODIN
4. finish Magisk setup
I couldn't find that much information and I'm fairly new to rooting in general. So here are the questions I have:
1. Is it possible to flash a custom Kernel without custom recovery, if it is, how?
3. Will OTA updates be accessible with the custom Kernel?
4. Is there another way or did I miss something obvious?
Thanks for any feedback in advance.
you definitely can't flash an AP archive with a custom recovery.
a custom kernel is designed to be flashed by a custom recovery unless it's a single IMG file inside the zip for it.
there's a sizeable chunk of us who manually flash updates, redo twrp, flash a magisk patched boot.img with twrp (once it's been extracted from the AP archive (using a PC app that supports .LZ4 compression)) and then flash a custom kernel finally... every month!
using something like Swift Backup to save apps n data, messages etc helps cut down the misery a bit.
3mel said:
you definitely can't flash an AP archive with a custom recovery.
a custom kernel is designed to be flashed by a custom recovery unless it's a single IMG file inside the zip for it.
there's a sizeable chunk of us who manually flash updates, redo twrp, flash a magisk patched boot.img with twrp (once it's been extracted from the AP archive (using a PC app that supports .LZ4 compression)) and then flash a custom kernel finally... every month!
using something like Swift Backup to save apps n data, messages etc helps cut down the misery a bit.
Click to expand...
Click to collapse
thank you so much! I guess Ill do it that way. Maybe some day there will be an easier way.
Gurkinator said:
thank you so much! I guess Ill do it that way. Maybe some day there will be an easier way.
Click to expand...
Click to collapse
the trend seems to be that it's not getting easier sadly.

Categories

Resources