I explain my situation:
I was on fulmics 4.2 and everything ok.
Tried a flash oreo without format /data
Bootllop
Ok clean install
Still bottloop
Cleaned everything, installed fulmics + ota
Now all ok except the fingerprint, it is like it does not exist, no option in settings at all.
Does someone have a solution without flashing back a kdz?
Maybe a flashable fingerprint driver?
Same problem
siggey said:
I explain my situation:
I was on fulmics 4.2 and everything ok.
Tried a flash oreo without format /data
Bootllop
Ok clean install
Still bottloop
Cleaned everything, installed fulmics + ota
Now all ok except the fingerprint, it is like it does not exist, no option in settings at all.
Does someone have a solution without flashing back a kdz?
Maybe a flashable fingerprint driver?
Click to expand...
Click to collapse
Same problem with fingerprint with stock version after update.
I solved fkashing stock oreo zip after a full wipe + data.
siggey said:
I explain my situation:
I was on fulmics 4.2 and everything ok.
Tried a flash oreo without format /data
Bootllop
Ok clean install
Still bottloop
Cleaned everything, installed fulmics + ota
Now all ok except the fingerprint, it is like it does not exist, no option in settings at all.
Does someone have a solution without flashing back a kdz?
Maybe a flashable fingerprint driver?
Click to expand...
Click to collapse
with the oreo update there were also update files for the bootloader, you have to flash official nougat to recover the old version of the bootloader because the new bootloader is not compatible with nougat and created problems like the unrecognized fingerprint reader
Mindy07du44 said:
with the oreo update there were also update files for the bootloader, you have to flash official nougat to recover the old version of the bootloader because the new bootloader is not compatible with nougat and created problems like the unrecognized fingerprint reader
Click to expand...
Click to collapse
I have the same problem with lineage 15.1. Flashed Oreo zip to test and now my fingerprint is gone in Lineage. Do you mean flash Nougat kdz to recover old version of the bootloader? or just a nougat zip?
Flashing a Nougat Zip (Open EU)worked for me. No need to flash kdz.
schoeni11 said:
I have the same problem with lineage 15.1. Flashed Oreo zip to test and now my fingerprint is gone in Lineage. Do you mean flash Nougat kdz to recover old version of the bootloader? or just a nougat zip?
Flashing a Nougat Zip (Open EU)worked for me. No need to flash kdz.
Click to expand...
Click to collapse
yes the kdz or otherwise with the zip is possible but check if the files for the bootloader and in the zip
schoeni11 said:
I have the same problem with lineage 15.1. Flashed Oreo zip to test and now my fingerprint is gone in Lineage. Do you mean flash Nougat kdz to recover old version of the bootloader? or just a nougat zip?
Flashing a Nougat Zip (Open EU)worked for me. No need to flash kdz.
Click to expand...
Click to collapse
When you reinstalled lineage did you wipe anything?
Gobrel said:
When you reinstalled lineage did you wipe anything?
Click to expand...
Click to collapse
did a restore of my nandroid backup.
Please explain step by step
So last year i started learning a bit about roms as stuff like that so after searching i saw Fulmics Rom and i chose that one to flash on my device. On that day i was on Oreo. I did all the stuff (format data, wipe...) then flashed the Rom and it was ok But the fingerprint option was there sometimes and sometimes not... After a day or so it expired so i flashed again (after formatting etc) but no fingerprint. So i just gave up, i was happy that i didnt brick my phone so i just accepted it...But today it's kind of annoying i searched a lot and everyone talks about flashing stock Nougat and then the Rom or flash stock Oreo and then Nougat and then the Rom... Well i tried but with no success.
I hope someone can help me with that
Thank you
Related
I'm already try flash trough TWRP over leaked official nougat version.
Works fine just dalvik and cache wipe after flash.
this is international ver. (not like hydrogen Eng/Chinese only)
original post from official forum
https://forums.oneplus.net/threads/oxygenos-open-beta-1-n-for-oneplus-3t.482846/
If i were to flash over my stock OS, what do I need to delete (without losing pictures etc). I keep forgetting..
I have read that TWRP has some errors when flashing, not sure what this was.
vincedyne said:
If i were to flash over my stock OS, what do I need to delete (without losing pictures etc). I keep forgetting..
I have read that TWRP has some errors when flashing, not sure what this was.
Click to expand...
Click to collapse
Hi
You can try side-load, but you need backup for sure.
my device is root and bootloader is open and I have already Nougat beta ver. before there so my upgrade was quick and all files and settings remains.
hampik said:
Hi
You can try side-load, but you need backup for sure.
my device is root and bootloader is open and I have already Nougat beta ver. before there so my upgrade was quick and all files and settings remains.
Click to expand...
Click to collapse
Ahh. I'll look into this, thanks!
hampik said:
Hi
You can try side-load, but you need backup for sure.
my device is root and bootloader is open and I have already Nougat beta ver. before there so my upgrade was quick and all files and settings remains.
Click to expand...
Click to collapse
So you just flashed the zip in TWRP and SuperSU afterwards? Or did it take additional steps?
bmwbasti said:
So you just flashed the zip in TWRP and SuperSU aftwerwards? Or did it take additional steps?
Click to expand...
Click to collapse
No additional steps. Flash the zip, supersu and wipe cache and everything is working fine.
I'll give it a shot eventhough i'm still on 3.5.4 and not the leaked beta.
I'm guessing as this will have the original boot.img (kernel), as no custom Nougat kernels are yet built (have to wait on the source code) that it will once flashed Encrypt the phone again? Thus the need for the pin/password for twrp?
No point in flashing Open Beta; th official stable OTA is coming tonight too.
https://twitter.com/getpeid/status/815171834345885696
Deleted
So seems there are soon to be two channels beta and stable coming. Great stuff!
Are the sources for ROM and kernel up yet?
Can we side load this over the top of the leaked nougat ROM ?
Moderator Information,
Thread closed, we do not need multiple threads for this.
Hi everyone,
I have a little problem with fingerprint with these 2 roms.
Normally I could add 5 fingers but I can only 3 max. If I try to configure the last 2, all my fingerprints dont work at all.
Moreover I can't delete fingeprints. When I try, they come back.
That is an issue which not occur with 6.0 custom roms.
Someone know how to fx it?
Thanks.
I'd suggest flashing the stock nougat 93-11 or 93-14 firmware (e.g. from the guides section) to resolve your fingerprint issues. Once that's done, future installs of lineage and RR should have fingerprint support for more than 3 fingers.
Thanks for replying.
I have xt1642. Is there a stock firmware Nougat for this device? I didnt find it
Nicozyp said:
Thanks for replying.
I have xt1642. Is there a stock firmware Nougat for this device? I didnt find it
Click to expand...
Click to collapse
I've got an XT1642 (UK - retGB, EMEA baseband) and updated to Nougat 93-11 using the stock files on here okay (now running Lineage with 4 FPs set).
The ROM I used to upgrade was the one linked here: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-install-official-december-nougat-t3518262 This will bring you up to the official 93-11 update via installing from stock recovery - you need Marshmallow build 139-63/64 however.
However, you may like to try either of these guides as well: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
As long as you can successfully install a Nougat stock ROM onto your device, the updates should mean your fingerprint sensor works properly in the custom ROMs. Bear in mind that updating to Nougat may wipe your data and cause you to lose TWRP/root until you re-install them.
Last question: can I wipe system and internal storage before installing ressurection?
Nicozyp said:
Last question: can I wipe system and internal storage before installing ressurection?
Click to expand...
Click to collapse
Once you've installed Nougat (and I recommend installing TWRP too), if you wish to install Resurrection Remix, only wipe system, data, Dalvik and cache. Don't wipe internal storage, since that's where your ROM zip is stored!
Silesh's initial post on the RR version for Moto G4s has more information on this https://forum.xda-developers.com/moto-g4-plus/development/rom-resurrection-remix-n-5-8-0-t3507275
Unable to flash stock recovery => "image not signed or corrupt"
Nicozyp said:
Unable to flash stock recovery => "image not signed or corrupt"
Click to expand...
Click to collapse
The image is flashed. Boot into recovery and you'll realize.
Nicozyp said:
Unable to flash stock recovery => "image not signed or corrupt"
Click to expand...
Click to collapse
Which file are you flashing? Does it end in OKAY after that error?
EDIT - zeomal is too quick for me
Indeed it's ok.
For the moment I upgrade MM, then gonna flash stock Nougat.
So problem solved.
I've flashed RR and configured fingerprint ==> it works fine
Thanks for ur help and advices
fingerprint option is not displayed in my zuk z1
Hey I have installed official lineage-os on my zuk z1 handset but still I can't find fingerprint option in my zuk
What to do help me
I'm on AEX 4.6 and I'd like to know if there's a way to restore stock via TWRP? if so, plz give me the link to download the rom. Unfortunatly, my miflash is crashing and making EDL method not usable. (Sorry for the english)
Arthur Winchest said:
I'm on AEX 4.6 and I'd like to know if there's a way to restore stock via TWRP? if so, plz give me the link to download the rom. Unfortunatly, my miflash is crashing and making EDL method not usable. (Sorry for the english)
Click to expand...
Click to collapse
well, miflash is not the only one, you could also try EDL Tool from right here (ROMs, kernels, development thread).
But yeah, you can. I wonder why you are still in AEX 4.6, but I guess you still haven't got a vendor partition. If that's the case just download a flashable zip of the stock ROM that you want (would've been real handy if you told us what model you have) and flash it away
Arthur Winchest said:
I'm on AEX 4.6 and I'd like to know if there's a way to restore stock via TWRP? if so, plz give me the link to download the rom. Unfortunatly, my miflash is crashing and making EDL method not usable. (Sorry for the english)
Click to expand...
Click to collapse
Dont update to treble ,it will cause problems
Predatorhaze said:
Dont update to treble ,it will cause problems
Click to expand...
Click to collapse
because you think you have problems, i guess?
I wonder who said to update to treble though
Choose an username... said:
well, miflash is not the only one, you could also try EDL Tool from right here (ROMs, kernels, development thread).
But yeah, you can. I wonder why you are still in AEX 4.6, but I guess you still haven't got a vendor partition. If that's the case just download a flashable zip of the stock ROM that you want (would've been real handy if you told us what model you have) and flash it away
Click to expand...
Click to collapse
I've a A2017G, I'm sorry but I didn't get it the vendor part. And another question, will I have to wipe my internal too??
Arthur Winchest said:
I've a A2017G, I'm sorry but I didn't get it the vendor part. And another question, will I have to wipe my internal too??
Click to expand...
Click to collapse
I'm just saying that you are on an ancient ROM. What's that AEX version, Nougat?
Right now I'm on AEX 6.0 Pie. But yeah, i was just curious.
You will probably need to format your internal storage, but maybe you won't need it. Just do this: After installing the ROM (whatever you decide, EDL Tool or TWRP) install Magisk too, BEFORE BOOTING FOR THE FIRST TIME (If EDL Tool, simply flash the ROM, then tell it not to reboot, flash TWRP, enter TWRP, and flash Magisk; if directly from TWRP just flash magisk right away). This will prevent your internal storage from getting encrypted.
Remember to WIPE DATA AND CACHE BEFORE FLASHING
Anyhow if your phone asks you for a password that doesn't really exist when you try to boot, you'll have to format the internal storage
Hi,
I just flashed the latest stock update.
The problem is that I can't decryt my data in TWRP, and hence cant flash anything from internal storage.
Is there any TWRP build that supports encryption/decryption ?
A Taiwanese regularly compiles TWRP up to date with the security updates on Zentalk (TW). You can check this MEGA folder every month he uploads to. The latest one works with .339
In case you cant fix it, next time make sure that you flash the files in this order: rom, magisk, decrypt.zip
farhanshaikh671 said:
In case you cant fix it, next time make sure that you flash the files in this order: rom, magisk, decrypt.zip
Click to expand...
Click to collapse
Sometimes people actually want their data encrypted, so that's more like a dirty fix.
farhanshaikh671 said:
In case you cant fix it, next time make sure that you flash the files in this order: rom, magisk, decrypt.zip
Click to expand...
Click to collapse
What is the difference when applying in rom, magisk, decrypt compared to rom, decrypt, magisk?
I use the latter method always because that is recommended by this guide:
https://forum.xda-developers.com/as...to/rom-update-stock-firmware-keeping-t3808269
camlin said:
Hi,
I just flashed the latest stock update.
The problem is that I can't decryt my data in TWRP, and hence cant flash anything from internal storage.
Is there any TWRP build that supports encryption/decryption ?
Click to expand...
Click to collapse
No you have to factory reset
Device: ZB602KL 4gb
I was using the latest Liquid Remix 10.0.6 with the stock darkonah kernel for a wee after having just updated from LR 10.0.5 and Singh 2.7. When I noticed he released a stable update for his kernel to 2.8 I downloaded it and flashed it as normal. Upon booting into LR, the lockscreen no longer responded to my fingerprint. It wasn't even turning the screen on. After inputting my password, I noticed that my wifi wouldn't turn on. And later when I tried the stock gcam, it kept crashing. Cam2API Probe is completely blank.
Things I've done to try and fix this:
1. Rebooted multiple times.
2. Someone suggested wiping /system and /vendor only and dirty flashing the rom. Did that, dirty flashed LR, openGApps(wasn't sure I needed to, did it anyway), and Magisk 19.
3. Clean flashed stock 340, decrypt and magisk19.
4. Flashed fw_only-X00T-WW-16.2017.1902.037.zip. I had previously flashed fwpie050.zip(the one from opendesktop) when updating LR before all this happened.
5. Fully wiped phone including internal storage and flashed the latest HavocOS which I am on right now as I've given up and just need it to work as a phone for the meantime.
Camera seems to be working again on Havoc, though. Fingerprint is still missing from Security settings and WiFi will not turn on.
Any help would be appreciated. Thanks!
I also got bootloop by using magisk 19.0,use magisk 17.1 or 18.1.
How did you clean flash stock 340 ? If it was through TWRP then try fastboot ROM
Tianhe said:
How did you clean flash stock 340 ? If it was through TWRP then try fastboot ROM
Click to expand...
Click to collapse
Yes, through twrp. What are the adb commands to do it through fastboot? I used Avinash's modified stock340 btw.
I think the modem firmware is corrupted somehow. I cannot receive or make calls but can get 4g data connection and SMS. My wifi mac address sometimes is "Uknown" or 02:00:00:00:00:00.
defurious said:
Yes, through twrp. What are the adb commands to do it through fastboot? I used Avinash's modified stock340 btw.
I think the modem firmware is corrupted somehow. I cannot receive or make calls but can get 4g data connection and SMS. My wifi mac address sometimes is "Uknown" or 02:00:00:00:00:00.
Click to expand...
Click to collapse
Flash fastboot stock rom it will fix the issue.
https://forum.xda-developers.com/as...ow-to/guide-revert-to-stock-rom-lock-t3798420
Hit thanks if it helped
Flashing stock rom thru adb basically reverts your phone to factory state so everything should be fixed unless somehow your hardware is damaged
farhanshaikh671 said:
Flashing stock rom thru adb basically reverts your phone to factory state so everything should be fixed unless somehow your hardware is damaged
Click to expand...
Click to collapse
Yeah, i understand. I'm just a little confused because the steps in the linked post above are for 334. I don't know how to do it using 340. Should I just follow those steps then after relocking, manually update to 340, and then unlock bootloader again?
Is there any way to flash fastboot rom without relocking bootloader?
To me it seems that i'm having some problems with pie beta firmware. After flashing 339 and then LR 10.0.5 which is the last version before requiring pie beta firmware, everything is working normally again. But as soon as i try to update to 10.0.6 or latest Havoc with pie beta firmware, the wifi and fpsensor stop functioning. But the strange thing is, I was on LR 10.0.6 for a week before flashing Singh 2.8 kernel which then killed my hardware.
Now I'm wondering if I should just wait for official Pie release from Asus.
defurious said:
Yeah, i understand. I'm just a little confused because the steps in the linked post above are for 334. I don't know how to do it using 340. Should I just follow those steps then after relocking, manually update to 340, and then unlock bootloader again?
Is there any way to flash fastboot rom without relocking bootloader?
To me it seems that i'm having some problems with pie beta firmware. After flashing 339 and then LR 10.0.5 which is the last version before requiring pie beta firmware, everything is working normally again. But as soon as i try to update to 10.0.6 or latest Havoc with pie beta firmware, the wifi and fpsensor stop functioning. But the strange thing is, I was on LR 10.0.6 for a week before flashing Singh 2.8 kernel which then killed my hardware.
Now I'm wondering if I should just wait for official Pie release from Asus.
Click to expand...
Click to collapse
Just Flash Stock rom via fastboot to fix this issue. Dont bother about bootloader getting relocked.( U may unlock it ri8 after flashing)
And one more thing.
If u flash Decrypt.zip used for Stock Oreo roms on Stock Pie, you will loose wifi and fingerprint options.(I experimented this thoroughly)
So flash decrypt.zip for pie on Pie Stock(Beta or Stable).
Tested personally and worked fine.:good:
Hit thanks if it helped,
akhil850 said:
Just Flash Stock rom via fastboot to fix this issue. Dont bother about bootloader getting relocked.( U may unlock it ri8 after flashing)
And one more thing.
If u flash Decrypt.zip used for Stock Oreo roms on Stock Pie, you will loose wifi and fingerprint options.(I experimented this thoroughly)
So flash decrypt.zip for pie on Pie Stock(Beta or Stable).
Tested personally and worked fine.:good:
Hit thanks if it helped,
Click to expand...
Click to collapse
This must be the problem then because I didn't know there was a decrypt for pie beta and i usually do flash decrypt coz i have a phobia that my internal data will get encrypted with no password to recover. ?
Can you provide a link for pie beta decrypt please? I can't find it here in xda. Thanks
defurious said:
This must be the problem then because I didn't know there was a decrypt for pie beta and i usually do flash decrypt coz i have a phobia that my internal data will get encrypted with no password to recover. ?
Can you provide a link for pie beta decrypt please? I can't find it here in xda. Thanks
Click to expand...
Click to collapse
Here https://forum.xda-developers.com/as...w-to/decrypt-zip-asus-stock-pie-roms-t3923265
Hit thanks if i helped.