No fingerprint option in Security options in settings! - Moto G5 Plus Questions & Answers

I was using Xtended Custom ROM (Oreo) with a rooted device and then i was just trying to unroot the phone and flashing Stock ROM but it didnt worked so i rolled back to Custom ROM and then my fingerprint sensors are not getting detected in any Oreo ROM.. please help!

If you really want to stay on an Oreo custom rom, you have to downgrade to stock nougat first. Easiest way to do that is use the latest nougat twrp flashable stock rom
https://forum.xda-developers.com/g5-plus/development/twrp-flashable-stock-builds-t3813351
Other option is to just go to a pie custom rom.
Edit - just remembered the is another thing you can flash that will just get back the fingerprint, but if you use NFC that won't be fixed. Maybe someone else has the link.

I got my fingerprint sensor back but lost VolTe now!
NZedPred said:
If you really want to stay on an Oreo custom rom, you have to downgrade to stock nougat first. Easiest way to do that is use the latest nougat twrp flashable stock rom
https://forum.xda-developers.com/g5-plus/development/twrp-flashable-stock-builds-t3813351
Other option is to just go to a pie custom rom.
Edit - just remembered the is another thing you can flash that will just get back the fingerprint, but if you use NFC that won't be fixed. Maybe someone else has the link.
Click to expand...
Click to collapse
I got my fingerprint sensor back by flashing "potter-twrp-flashable-NPNS25.137-92-14-a" image but lost Volte support! I am currently using PixelExperience Custom ROM! Oreo based! I am gonna try shifting to a new custom ROM to see if i can get Volte working! If any suggestions please let me know!

If u had nougat and the u flashed PE 9.0 then volte will have issues. PE moved to oreo base long time back. Its better u flash stock oreo first and then move to any Pie Rom. There are some guides around to get volte back might wanna look around. Did you not make a backup of the stock image?

RascalMonk said:
I got my fingerprint sensor back by flashing "potter-twrp-flashable-NPNS25.137-92-14-a" image but lost Volte support! I am currently using PixelExperience Custom ROM! Oreo based! I am gonna try shifting to a new custom ROM to see if i can get Volte working! If any suggestions please let me know!
Click to expand...
Click to collapse
Did you boot into stock nougat before flashing the custom Oreo rom? If not, it is probably necessary. (When you had -a at the end of that filename, I assume you mean aroma? If so, then that one applies a fix to your persist which is needed going back to stock nougat, so that's all good.)
If you did, then it may just be a case of needing to go onto stock Oreo then a pie custom rom. Some things about the stock nougat just don't work properly after being on Oreo...

NZedPred said:
Did you boot into stock nougat before flashing the custom Oreo rom? If not, it is probably necessary. (When you had -a at the end of that filename, I assume you mean aroma? If so, then that one applies a fix to your persist which is needed going back to stock nougat, so that's all good.)
If you did, then it may just be a case of needing to go onto stock Oreo then a pie custom rom. Some things about the stock nougat just don't work properly after being on Oreo...
Click to expand...
Click to collapse
I was originally trying to unroot the phone and getting into stock nougat so that i can get basic updates from moto itself and then i can get into stock oreo but it didnt happen as i wished! now i am stuck in custom oreo with no volte working and way too irritated! since im using volte support sim card i am not able to call anyone or get any incoming calls! please help me what should i do now? i have flashed that persist file with twrp but using custom oreo now! guide me please! need it most!

RascalMonk said:
I was originally trying to unroot the phone and getting into stock nougat so that i can get basic updates from moto itself and then i can get into stock oreo but it didnt happen as i wished! now i am stuck in custom oreo with no volte working and way too irritated! since im using volte support sim card i am not able to call anyone or get any incoming calls! please help me what should i do now? i have flashed that persist file with twrp but using custom oreo now! guide me please! need it most!
Click to expand...
Click to collapse
Ok, so you flashed some persist file? Was it my persist fix zip, or someone else's persist backup, in which case you're kinda screwed.

debdeep98 said:
If u had nougat and the u flashed PE 9.0 then volte will have issues. PE moved to oreo base long time back. Its better u flash stock oreo first and then move to any Pie Rom. There are some guides around to get volte back might wanna look around. Did you not make a backup of the stock image?
Click to expand...
Click to collapse
i am newbie in this so i havent made backup! big mistake!

Got back everything!
NZedPred said:
Ok, so you flashed some persist file? Was it my persist fix zip, or someone else's persist backup, in which case you're kinda screwed.
Click to expand...
Click to collapse
I flashed the "potter-twrp-flashable-NPNS25.137-92-14-aroma" file and got into stock nougat successfully but after i chose to install OTA updates which i got for my device it got stuck in TWRP only! can you help me out here please????

RascalMonk said:
I flashed the "potter-twrp-flashable-NPNS25.137-92-14-aroma" file and got into stock nougat successfully but after i chose to install OTA updates which i got for my device it got stuck in TWRP only! can you help me out here please????
Click to expand...
Click to collapse
Try clearing cache within twrp. You shouldn't take any OTAs from the twrp flashable. If it was the OTA for Oreo, then might be easier to do a wipe, as I can't remember where the OTA gets saved.
I'm assuming that your device is trying to go to recovery all the time as it knows the OTA is there to be installed.
Worst case, total clean flash and install again.

RascalMonk said:
I flashed the "potter-twrp-flashable-NPNS25.137-92-14-aroma" file and got into stock nougat successfully but after i chose to install OTA updates which i got for my device it got stuck in TWRP only! can you help me out here please????
Click to expand...
Click to collapse
Two basic rules:
- Make a backup. Every time before you flash anything. Every time.
- You only can apply and install OTA updates when on a signed and unmodified fastboot firmware.
Twrp flashable ROMs have a lot of advantages but they are not unmodified.
Agree with @NZedPred: Make a full wipe and install
a) a fastboot firmware if you need to take OTA updates, these are found here:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
b) a twrp flashable ROM if you won't take OTA updates, these are found here: https://forum.xda-developers.com/g5...flashable-stock-builds-coming-t3830482/page68

I have this same problem. I'm currently on stock Oreo and I'm not getting fingerprint option since I flashed PE 9.0. someone help.

Related

Upgrade from custom ROM to Android 7.0

Hi guys,
Not sure if this is the right place to post this but unless I am missing something, I have yet to find a thread or instructions on how to do this.
I am on Pure Nexus, but I posted here because I'm guessing the answer applies to virtually any custom ROM. What are the steps involved in upgrading from a custom 6.0 ROM to the newly released Android 7.0? Is there a way to do this while keeping root?
Thanks,
speedemonV12 said:
Hi guys,
Not sure if this is the right place to post this but unless I am missing something, I have yet to find a thread or instructions on how to do this.
I am on Pure Nexus, but I posted here because I'm guessing the answer applies to virtually any custom ROM. What are the steps involved in upgrading from a custom 6.0 ROM to the newly released Android 7.0? Is there a way to do this while keeping root?
Thanks,
Click to expand...
Click to collapse
There's roms you can flash, other than that just wait for the images to release and there will be alot options
So if it's a custom ROM based on 7.0 I can go ahead and flash using that specific ROM instructions?
I thought the official 7.0 came out yesterday, that's why I was wondering if I could update to the official and keep root and how to do that.
speedemonV12 said:
So if it's a custom ROM based on 7.0 I can go ahead and flash using that specific ROM instructions?
I thought the official 7.0 came out yesterday, that's why I was wondering if I could update to the official and keep root and how to do that.
Click to expand...
Click to collapse
I'd Mae a backup send it to PC and try tupac4us rom or digitalhighs . They have vendors built in the zip .
I was on Benzo rom and this is exactly what I did; I restored back to stock rom only leaving bootloader unlocked. I joined the Android beta and the N ota was ready to install. I then flashed the latest twrp. I made sure to do a full nandroid and physically backed up anything important to my laptop before I restored to stock. I noticed until I flashed ditialhighs N rom my twrp would not "stick" but no big deal I just flashed it and went into recovery. It seems Android Pay is working with digitialhighs rom, you just toggle off root, use it, toggle back. Good luck
Which guide did you use for restoring to stock while keeping the bootloader unlocked?
i was on pure nexus 6.1 i used this guide to revert everything back to stock then i subscribed to the developer program and got 7.0 update in seconds, section 14 is pretty much all you need
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

HELP regarding Upgrade to MM STOCK ROM OR CM 13.0 !!!

Hi guys, its been a few days since I joined here. [Read : I am a noob/newbie in Android related things, and I desperately need help.]
In July (maybe, I forgot), I rooted my ZE550KL, using exactly this method from the website of www-asus-zenfone-com. :cyclops:
Now that, my android seems aged, I wanna shift/upgrade to Marshmallow/Nougat, be it Stock or Custom ROM.
Few days earlier, I unlocked my Bootloader using the Unofficial Bootloader Unlocking Method, as found on this Forum.
I also installed TWRP Recovery, and I tried to flash CM-14.1 [7.1] Nougat-Nightly through TWRP, but, unfortunately, resulted in Status 7 Error. I tried to solve the problem by removing "asserts" section in Update-Binary text file, in the build. But, again, I seemingly worsened the problem; as I got Status 6 error thereby. So, I did factory reset, and I still retain root.
Now, today as I am going through the Official thread of CM 14.1 Nougat, I saw numerous users reporting Bugs of connection issues (something like Wifi to Mobile Data switch problem), which I would like to OBVIOUSLY AVOID, as I want a stable, bug-less build. So, I am thinking to go with the last snapshot build of CM 13.0 Marshmallow.
Here comes the my question : " SHOULD I FLASH CM 13.0 MM -- OR -- STOCK ROM OF MM -- OR -- RESURRECTION REMIX MM ROM?? "
In any of the case, please guide me through the process of doing so.
And, if I have to flash CM 13.0 MM, what would I do if I encounter Status Error 7 again ? :crying:
first you have to upgrade it to marshmallow using stock rom. Then you can flash cm13 or cm14.1
Devc100 said:
first you have to upgrade it to marshmallow using stock rom. Then you can flash cm13 or cm14.1
Click to expand...
Click to collapse
Please, like I said, guide me through how to do it. Thanks in advance, in case you help. :good:
Ph4nToM_Z3rO said:
Hi guys, its been a few days since I joined here. [Read : I am a noob/newbie in Android related things, and I desperately need help.]
In July (maybe, I forgot), I rooted my ZE550KL, using exactly this method from the website of www-asus-zenfone-com. :cyclops:
Now that, my android seems aged, I wanna shift/upgrade to Marshmallow/Nougat, be it Stock or Custom ROM.
Few days earlier, I unlocked my Bootloader using the Unofficial Bootloader Unlocking Method, as found on this Forum.
I also installed TWRP Recovery, and I tried to flash CM-14.1 [7.1] Nougat-Nightly through TWRP, but, unfortunately, resulted in Status 7 Error. I tried to solve the problem by removing "asserts" section in Update-Binary text file, in the build. But, again, I seemingly worsened the problem; as I got Status 6 error thereby. So, I did factory reset, and I still retain root.
Now, today as I am going through the Official thread of CM 14.1 Nougat, I saw numerous users reporting Bugs of connection issues (something like Wifi to Mobile Data switch problem), which I would like to OBVIOUSLY AVOID, as I want a stable, bug-less build. So, I am thinking to go with the last snapshot build of CM 13.0 Marshmallow.
Here comes the my question : " SHOULD I FLASH CM 13.0 MM -- OR -- STOCK ROM OF MM -- OR -- RESURRECTION REMIX MM ROM?? "
In any of the case, please guide me through the process of doing so.
And, if I have to flash CM 13.0 MM, what would I do if I encounter Status Error 7 again ? :crying:
Click to expand...
Click to collapse
While flashing CM13 if that error 7 includes "asus.verify trustzone failed..." Then its bcoz of need to update modem files (LP to MM)....
Easy way to overcome it is..... download MM modem ZIP from second post of OFFICIAL CM13 thread (120MB) and flash it using TWRP (If you are using twrp).... THEN you can flash cm13 hopefully without error 7....
If you are using stock recovery then Either u can flash twrp and use above method... OR... Download ASUS ZE550KL firmware zip file from ASUS site (1.6GB) .... Put it in SDCARD... Then boot to stock recovery and use "apply update from sdcard" option... select ZIP... Alongwith firmware Ur Modem files will also update to MM... and now u can flash twrp and then cm13...
sorry.. I know if i am lazy to post direct links...
Try it.. I will help if i can
aadi50 said:
While flashing CM13 if that error 7 includes "asus.verify trustzone failed..." Then its bcoz of need to update modem files (LP to MM)....
Easy way to overcome it is..... download MM modem ZIP from second post of OFFICIAL CM13 thread (120MB) and flash it using TWRP (If you are using twrp).... THEN you can flash cm13 hopefully without error 7....
If you are using stock recovery then Either u can flash twrp and use above method... OR... Download ASUS ZE550KL firmware zip file from ASUS site (1.6GB) .... Put it in SDCARD... Then boot to stock recovery and use "apply update from sdcard" option... select ZIP... Alongwith firmware Ur Modem files will also update to MM... and now u can flash twrp and then cm13...
sorry.. I know if i am lazy to post direct links...
Try it.. I will help if i can
Click to expand...
Click to collapse
Thanks, dude. One question, should I get CM 13.0 or Resurrection Remix ?
Ph4nToM_Z3rO said:
Thanks, dude. One question, should I get CM 13.0 or Resurrection Remix ?
Click to expand...
Click to collapse
We have both stable RR and CM13.
CM is simple and clean and less loaded.... RR is most feature rich Custom rom we have alongwith stability...
Rest depends on what type of user, u are... If u like trying differnt ROMs... Start with CM13...
If u just want to have a feature rich longtime setup, U can use RR directly without wasting time... It is based on CM, So it obviously have everything CM has.... :good:
Ph4nToM_Z3rO said:
Please, like I said, guide me through how to do it. Thanks in advance, in case you help. :good:
Click to expand...
Click to collapse
Latest Stock Marshmallow:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-21.40.1220.1877-user.zip
Stock RecoveryRestore it using TWRP)
https://drive.google.com/open?id=0B2BGto29cXq1NjYySjRES21yOTg
Last Lollipop Software:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-1.17.40.1531-user.zip
First Lollipop Software:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-1.11.40.299-user.zip
First Do A nandroid backup of your phone. So that if any thing goes wrong, U can recover it.
Then Download both the Stock MM and Recovery file named TWRP.zip.
Extract TWRP.zip.
Then take both the MM software and Xtracted TWRP folder in a memory card.
Then Open TWRP recovery in ur phone and restore the stock recovery.
Then Erase Every Thing including System.
Then Restart The recovery. Now you will see that the recovery has gone back to the stock recovery.
Now flash the stock marshmallow from your memory card.
Then flash TWRP from fastboot and thn u can flash any supported custom Android MM or Android N.
N.B. If it dosent work. Then you have to first install the last lollipop Zenfone 2 Laser(Z00LD) software then install the marshmallow.

FingerPrint Enrollment not working on any Custom Rom

The fingerprint was working fine on stock rom. Unlocked the bootloader and flashed twrp image. Somehow I formatted the internal storage erasing everything. After that, I flashed Pixel Experience custom rom and the fingerprint scanner isn't working. Getting "fingerprint enrollment issue". The enrollment happens only when I try pressing it very hard and I didn't face the issue on stock rom. I tried every custom rom available my bad. Somehow registered the edge of the finger and its working for now. What is the issue, I don't think it is hardware issue Any fixes for the same?
+1
ajeteja said:
The fingerprint was working fine on stock rom. Unlocked the bootloader and flashed twrp image. Somehow I formatted the internal storage erasing everything. After that, I flashed Pixel Experience custom rom and the fingerprint scanner isn't working. Getting "fingerprint enrollment issue". The enrollment happens only when I try pressing it very hard and I didn't face the issue on stock rom. I tried every custom rom available my bad. Somehow registered the edge of the finger and its working for now. What is the issue, I don't think it is hardware issue Any fixes for the same?
Click to expand...
Click to collapse
By any chance were you on the Oreo soak test when last on Stock rom? If so, the blobs wouldn't be compatible. Confirm whether or not that was the case, and if it is, then I'll point you in the right direction.
Yes I was on soak test. Pls help Moto g5s plus
---------- Post added at 10:47 AM ---------- Previous post was at 10:46 AM ----------
NZedPred said:
By any chance were you on the Oreo soak test when last on Stock rom? If so, the blobs wouldn't be compatible. Confirm whether or not that was the case, and if it is, then I'll point you in the right direction.
Click to expand...
Click to collapse
Yes I was on soak test. Pls help Moto g5s plus
@NZedPred Can you pls help? I am also facing the same issue.
#shubham Bane/- said:
Yes I was on soak test. Pls help Moto g5s plus
---------- Post added at 10:47 AM ---------- Previous post was at 10:46 AM ----------
Yes I was on soak test. Pls help Moto g5s plus
Click to expand...
Click to collapse
kiranbala003 said:
@NZedPred Can you pls help? I am also facing the same issue.
Click to expand...
Click to collapse
Taken from the Oreo thread:
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc. To ensure they run correctly, it is MANDATORY to install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
So flash the persist fix from the first link, and flash the latest Nougat stock rom from the second. Reboot and make sure all is working OK in stock. Then flash whichever custom rom you want.
NZedPred said:
Taken from the Oreo thread:
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc. To ensure they run correctly, it is MANDATORY to install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
So flash the persist fix from the first link, and flash the latest Nougat stock rom from the second. Reboot and make sure all is working OK in stock. Then flash whichever custom rom you want.
Click to expand...
Click to collapse
@NZedPred thanks man. It worked
kiranbala003 said:
@NZedPred thanks man. It worked
Click to expand...
Click to collapse
hi, i am also facing the same issue. fingerprint lock disappeared after i flash a AEX custom rom from stock oreo soak test in my moto g5 plus (potter).
could you please provide the setp by step procedure to fix my issue thanks a lot
ugander1989 said:
hi, i am also facing the same issue. fingerprint lock disappeared after i flash a AEX custom rom from stock oreo soak test in my moto g5 plus (potter).
could you please provide the setp by step procedure to fix my issue thanks a lot
Click to expand...
Click to collapse
Step by step instructions are in my post above... Do you have a more specific question?
Does this work with moto G5s plus [sanders]
Will the above method work with moto g5s plus sanders
sarath6622 said:
Will the above method work with moto g5s plus sanders
Click to expand...
Click to collapse
Yes, if you did the same thing, i.e. flashed stock Oreo and then went to an Oreo custom rom, then yes the same approach will work. I have a flashable build and persist fix for sanders here:
https://www.androidfilehost.com/?w=files&flid=280579
Clean flash/Dirty flash?
@NZedPred I am facing the same problem. I own the Indian Moto G5 Plus (retin)
Here's what I did -
1. I unlocked my bootloader
2. I updated to Oreo (soak test) using the OTA capture.
2. I somehow rooted my phone after flashing TWRP.
3. Just after I flashed TWRP i.e. before rooting, I took a complete backup including the persist and EFS partitions.
4. After rooting, I clean installed MSM-Xtended ROM (8.1.0)
5. Everything is fine, but the fingerprint feature doesn't work/appear anywhere. Even the gesture support is gone.
What do I need to do?
If I follow your steps mentioned above i.e. flashing the persist-fix first, flashing the Nougat ROM you provided and then flashing any custom ROM, how should I proceed?
I am really confused whether I should clean flash (Wipe Data, System, Cache) after every step or dirty flash everything.
Please guide me.
Before you go back to custom ROM from stock Oreo ROM you have to flash stock nouget ROM if not fingerprint , NFC will not work.
NZedPred said:
Taken from the Oreo thread:
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc. To ensure they run correctly, it is MANDATORY to install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
So flash the persist fix from the first link, and flash the latest Nougat stock rom from the second. Reboot and make sure all is working OK in stock. Then flash whichever custom rom you want.
Click to expand...
Click to collapse
I was also in the same problem of fingerprint not working. Tried your method i.e. flashed persist zip and nougat rom (after wiping dalvik, system ,data, cache) and now when I try to clean flash custom Oreo rom . Gapps is not getting flashed . Its detecting the rom as 7.1.2. any solution for this
navinsingh said:
I was also in the same problem of fingerprint not working. Tried your method i.e. flashed persist zip and nougat rom (after wiping dalvik, system ,data, cache) and now when I try to clean flash custom Oreo rom . Gapps is not getting flashed . Its detecting the rom as 7.1.2. any solution for this
Click to expand...
Click to collapse
@sinchan_nohara
navinsingh said:
I was also in the same problem of fingerprint not working. Tried your method i.e. flashed persist zip and nougat rom (after wiping dalvik, system ,data, cache) and now when I try to clean flash custom Oreo rom . Gapps is not getting flashed . Its detecting the rom as 7.1.2. any solution for this
Click to expand...
Click to collapse
U wrongly flashed firmware, try Oreo custom rom
NZedPred said:
Taken from the Oreo thread:
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc. To ensure they run correctly, it is MANDATORY to install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
So flash the persist fix from the first link, and flash the latest Nougat stock rom from the second. Reboot and make sure all is working OK in stock. Then flash whichever custom rom you want.
Click to expand...
Click to collapse
dhinesh_cool said:
U wrongly flashed firmware, try Oreo custom rom
Click to expand...
Click to collapse
can you please guide me to install a custom oreo rom. because when i try to flash custom oreo rom (franken rom i used) , the rom gets flashed but the gapps (arm64 mini 8.1.x) fails everytime and shows error code 20 (incompatible rom). but i had flashed both the rom and the gapps successfully before the fingerprint issue bcoz of which i had to flash the stock 7.0 with the persist fix. and one more thing the rom is getting flashed succesfully (as twrp shows me) but when i try to boot into system without the gapps installed( i.e. only with the rom) it gets stuck on the bootloader page so i think the rom itself is not getting flashed. please help......
navinsingh said:
can you please guide me to install a custom oreo rom. because when i try to flash custom oreo rom (franken rom i used) , the rom gets flashed but the gapps (arm64 mini 8.1.x) fails everytime and shows error code 20 (incompatible rom). but i had flashed both the rom and the gapps successfully before the fingerprint issue bcoz of which i had to flash the stock 7.0 with the persist fix. and one more thing the rom is getting flashed succesfully (as twrp shows me) but when i try to boot into system without the gapps installed( i.e. only with the rom) it gets stuck on the bootloader page so i think the rom itself is not getting flashed. please help......
Click to expand...
Click to collapse
ask in telegram grp

need help ( stock rom)

hey ! i want to flash fastboot rom , currently im on custom rom. please tell me what is the latest firmware for indian varrient & link also of firmware.
If you're on a custom rom, and that rom is an Oreo rom, you will need to apply the persist fix to make sure you don't have any problems when moving to stock (e.g. lost IMEI, no Volte, no 4G, etc). For the guide here:
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
If you know what you're doing, here's a link to NPNS25.137-92-14, the latest for the retin channel.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Edit: Also, do you really need the fastboot roms? Unless you're looking to lock your bootloader, maybe you'll be fine with the TWRP flashable stock roms - available for both Nougat and Oreo (soak test, not yet official).
NZedPred said:
If you're on a custom rom, and that rom is an Oreo rom, you will need to apply the persist fix to make sure you don't have any problems when moving to stock (e.g. lost IMEI, no Volte, no 4G, etc). For the guide here:
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
If you know what you're doing, here's a link to NPNS25.137-92-14, the latest for the retin channel.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Edit: Also, do you really need the fastboot roms? Unless you're looking to lock your bootloader, maybe you'll be fine with the TWRP flashable stock roms - available for both Nougat and Oreo (soak test, not yet official).
Click to expand...
Click to collapse
Thanks for your reply bro , one last ques is it worthy to move to proper stock again?? or flashable builds are better ?
zooreo said:
Thanks for your reply bro , one last ques is it worthy to move to proper stock again?? or flashable builds are better ?
Click to expand...
Click to collapse
Comes down to what you want to do with your phone. If you want to keep root access, then you may as well stick with the TWRP flashables, as the full stock firmware will not install OTAs if you are rooted. Quite often the TWRP flashable builds will be available sooner than a lot of people receive OTAs through official channels. That is, once one person receives the OTA and shares it with me, I build the next flashable zip normally within a couple of days (I'm the maintainer). The modifications are minimal - just disabling dm-verity and forced encryption (the latest Oreo flashables built on the Aroma installer make that optional).
If you want to lock the bootloader for any reason (e.g. in order to sell your phone, or you want to ensure the highest level of security) then you only really have one choice - full fastboot stock.
Anyway, you can have a read in the two threads for Nougat and Oreo:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
[Oreo][Stock][Rom] TWRP Flashable Stock Builds

Oreo ROMs that can be flashed over stock Oreo

Are there any custom Oreo based ROMs that can be flashed directly over stock Oreo without issues like missing fingerprint functionality?
Thanks.
Every Oreo based ROM can be flashed over stock ROM, however it will end-up with unprecedented errors, and possibilities of soft-brick/hard-brick can not be avoided.
However, if you are looking for a custom ROM closed to stock, try flashing LOS, for which you need the bootloadwe to be unlocked.
checksamir said:
Every Oreo based ROM can be flashed over stock ROM, however it will end-up with unprecedented errors, and possibilities of soft-brick/hard-brick can not be avoided.
However, if you are looking for a custom ROM closed to stock, try flashing LOS, for which you need the bootloadwe to be unlocked.
Click to expand...
Click to collapse
Thank you. I tried that one and it needs blobs from Nougat apparently. When flashing LOS 15.1 over stock oreo, the fingerprint sensor doesn't work.
badtlc said:
Thank you. I tried that one and it needs blobs from Nougat apparently. When flashing LOS 15.1 over stock oreo, the fingerprint sensor doesn't work.
Click to expand...
Click to collapse
Some ROMs (mostly pie) need Oreo as base but a lot of Oreo ROMs need Nougat because stock Oreo wasn't released that time, that's also the reason why many Oreo custom ROMs are a bit unstable. Ask the developer what base is needed to be on the safe side.
In your case I recommend flashing a twrp stock nougat ROM:
https://forum.xda-developers.com/g5-plus/development/twrp-flashable-stock-builds-t3813351
After that reflash your preferred Oreo ROM.
If you haven't done it yet make a backup of EFS and persist with the latest TWRP 3.2.3.1 to avoid losing your IMEI and/or 4g.
Read the OP of the above thread:
An important note for those who have flashed custom Oreo roms
It is a frequent issue regarding Oreo roms that the device's IMEI is set to 0 in certain conditions. It is possible that these roms (or something used with them) are tampering with the persist partition of the devices. When this occurs, if the EFS is erased, it is not reconstructed correctly.
Click to expand...
Click to collapse
Wolfcity said:
Some ROMs (mostly pie) need Oreo as base but a lot of Oreo ROMs need Nougat because stock Oreo wasn't released that time, that's also the reason why many Oreo custom ROMs are a bit unstable. Ask the developer what base is needed to be on the safe side.
In your case I recommend flashing a twrp stock nougat ROM:
https://forum.xda-developers.com/g5-plus/development/twrp-flashable-stock-builds-t3813351
After that reflash your preferred Oreo ROM.
If you haven't done it yet make a backup of EFS and persist with the latest TWRP 3.2.3.1 to avoid losing your IMEI and/or 4g.
Read the OP of the above thread:
Click to expand...
Click to collapse
I tried doing the backup in TWRP. Not sure I got it backed up right. I have the following files in my TWRP backup folder my external SDcard:
- efs1.emmc.win
-efs1.emmc.win.sha2
- efs2.emmc.win
- persist.ext4.win
- persist.ext4.win.sha2
- persist.info
- recovery.log
Does that look like the correct number and type of files to have for backup? Thanks.
badtlc said:
I tried doing the backup in TWRP. Not sure I got it backed up right. I have the following files in my TWRP backup folder my external SDcard:
- efs1.emmc.win
-efs1.emmc.win.sha2
- efs2.emmc.win
- persist.ext4.win
- persist.ext4.win.sha2
- persist.info
- recovery.log
Does that look like the correct number and type of files to have for backup? Thanks.
Click to expand...
Click to collapse
Looks good.

Categories

Resources