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.
Related
Hey friends i am seeing green screen after flashing custom ROM and i am not able to boot into custom rom.
Phone model Samsung j500F 2015.
aytida4 said:
Hey friends i am seeing green screen after flashing custom ROM and i am not able to boot into custom rom.
Phone model Samsung j500F 2015.
Click to expand...
Click to collapse
It's because you are flashing MM rom (except cm13) and you are on Lollipop or vice versa.
#Henkate said:
It's because you are flashing MM rom (except cm13) and you are on Lollipop or vice versa.
Click to expand...
Click to collapse
No friend actually I m using marshmallomarshmallow stock
Rom and I'm installing ressurction Rom 6.0 but still it is showing green screen. Is it the problem of BOOTLOADER?
aytida4 said:
No friend actually I m using marshmallomarshmallow stock
Rom and I'm installing ressurction Rom 6.0 but still it is showing green screen. Is it the problem of BOOTLOADER?
Click to expand...
Click to collapse
I have the same problem …
aytida4 said:
No friend actually I m using marshmallomarshmallow stock
Rom and I'm installing ressurction Rom 6.0 but still it is showing green screen. Is it the problem of BOOTLOADER?
Click to expand...
Click to collapse
SiiXFX said:
I have the same problem …
Click to expand...
Click to collapse
You must be on Lollipop to flash RR 6.0.1, just like CM13.
#Henkate said:
You must be on Lollipop to flash RR 6.0.1, just like CM13.
Click to expand...
Click to collapse
Thanks friend I will try.
Same Green Screen
I have a same problem and i try the first 5.1.1 rom and after it i install the cyanogenmod 13 which i found in the rom article anybody can help me ? skype or somthing call service ?
Vityy said:
I have a same problem and i try the first 5.1.1 rom and after it i install the cyanogenmod 13 which i found in the rom article anybody can help me ? skype or somthing call service ?
Click to expand...
Click to collapse
Friend i had that problem then i installed stock 5.1.1 rom and
Then tried this and then it is working good. U can also
Try this.
aytida4 said:
Friend i had that problem then i installed stock 5.1.1 rom and
Then tried this and then it is working good. U can also
Try this.
Click to expand...
Click to collapse
I flashed the 5.1.1 rom but still i get the green screen/lines at the boot. I always get bootloops when i flash any zip. Plz help
aytida4 said:
Hey friends i am seeing green screen after flashing custom ROM and i am not able to boot into custom rom.
Phone model Samsung j500F 2015.
Click to expand...
Click to collapse
Possible problems,
- the rom is not for your device or variant
- The bootloader is for another version of Android
- Twrp was compiled with a different version of Android so are you going to get an error.
- Your bad luck exceeds an acceptable level ... ???
I have the same problem on my j500h too its turn to yellow color until the logo cant see because of that color i flashed custom kernel properly step by step 2 custom kernel i flashed they have already problem with that im running on 5.1.1 lollipop and my build number is LMY48B.J500HXXU1APA5
Keancarl said:
I have the same problem on my j500h too its turn to yellow color until the logo cant see because of that color i flashed custom kernel properly step by step 2 custom kernel i flashed they have already problem with that im running on 5.1.1 lollipop and my build number is LMY48B.J500HXXU1APA5
Click to expand...
Click to collapse
Which Custom Rom did you flash?
Keancarl said:
I have the same problem on my j500h too its turn to yellow color until the logo cant see because of that color i flashed custom kernel properly step by step 2 custom kernel i flashed they have already problem with that im running on 5.1.1 lollipop and my build number is LMY48B.J500HXXU1APA5
Click to expand...
Click to collapse
You get green screen when:
1) You flash MM ROMs (based on stock Touchwiz MM) over Lollipop and vice versa.
2) You flash MM/N ROMs (based on AOSP/CM such as LOS13, AOSIP, Mokee etc.) over Lollipop and vice versa.
3) I can't confirm this, but based on your comment, you get green screen when you flash a MM kernel over Lollipop and of course, vice versa too.
AndroiDTechi said:
Which Custom Rom did you flash?
Click to expand...
Click to collapse
not custom rom but kernel idk what the problem is so now i decided to have android backup in order to back again to my current system
---------- Post added at 06:46 AM ---------- Previous post was at 06:31 AM ----------
#Henkate said:
You get green screen when:
1) You flash MM ROMs (based on stock Touchwiz MM) over Lollipop and vice versa.
2) You flash MM/N ROMs (based on AOSP/CM such as LOS13, AOSIP, Mokee etc.) over Lollipop and vice versa.
3) I can't confirm this, but based on your comment, you get green screen when you flash a MM kernel over Lollipop and of course, vice versa too.
Click to expand...
Click to collapse
:good: i back to its current system now what i want is stock rom with customize and rooted system
aytida4 said:
Hey friends i am seeing green screen after flashing custom ROM and i am not able to boot into custom rom.
Phone model Samsung j500F 2015.
Click to expand...
Click to collapse
Flash 5.1.1 cynogenmod rom then install RR remix
Demicro said:
Possible problems,
- the rom is not for your device or variant
- The bootloader is for another version of Android
- Twrp was compiled with a different version of Android so are you going to get an error.
- Your bad luck exceeds an acceptable level ...
Click to expand...
Click to collapse
For those, who -as I did - don't really understand this (see the quote)...
I had the same issue when I wanted to install a custom Marshmallow ROM (6.0.1) over my stock Lollipop (5.1.1). The solution was to download and flash a new Bootloader and Modem with Odin. See tis:
https://forum.xda-developers.com/galaxy-j5/how-to/6-0-1-5-1-1-bootloader-modem-j500xx-t3566801
I just ran into this error while trying to install a custom ROM for my J500H.
My phone was running latest 6.0.1. I installed TWRP from This thread, then installed followed the instructions to install Resurrection Remix (7.1.2), but on first boot i got the green screen with the error (set warranty bit: kernel). Also tried Lineage 14.0 but doesn't work. I can still enter TWRP and download mode after getting this error.
This is my first time flashing a Samsung device. Could someone tell me what i did wrong?
https://forum.xda-developers.com/galaxy-j5/development/rom-resurrectionremix-v5-8-1-t3566035
iH8Ecchi said:
I just ran into this error while trying to install a custom ROM for my J500H.
My phone was running latest 6.0.1. I installed TWRP from This thread, then installed followed the instructions to install Resurrection Remix (7.1.2), but on first boot i got the green screen with the error (set warranty bit: kernel). Also tried Lineage 14.0 but doesn't work. I can still enter TWRP and download mode after getting this error.
This is my first time flashing a Samsung device. Could someone tell me what i did wrong?
Click to expand...
Click to collapse
Sorry, first time i didn't your post till the end.
First of all.
Restore firmware with "Samsung smart switch".
You can downgrade to 5.1.1 by this instruction.
1.Flash this firmware by Odin
https://drive.google.com/file/d/0B-pt1IG7T4hmVzhuMnRyeTBjTGM/view?usp=drivesdk
(Before flashing, wipe all storages(all except internal, external in advanced wipe. If you have stock recovery, you must do both wipes)
2. After first boot flash recovery from Vince
(for both bootloaders)
3. Before flashing RR5.8.4 wipe all storages too( all, except extrnl and intrlnl)
4. Flash RR and gapps.
5. Wipe data and cache.
wrongwriter3 said:
Sorry, first time i didn't your post till the end.
First of all.
Restore firmware with "Samsung smart switch".
You can downgrade to 5.1.1 by this instruction.
1.Flash this firmware by Odin
https://drive.google.com/file/d/0B-pt1IG7T4hmVzhuMnRyeTBjTGM/view?usp=drivesdk
(Before flashing, wipe all storages(all except internal, external in advanced wipe. If you have stock recovery, you must do both wipes)
2. After first boot flash recovery from Vince
(for both bootloaders)
3. Before flashing RR5.8.4 wipe all storages too( all, except extrnl and intrlnl)
4. Flash RR and gapps.
5. Wipe data and cache.
Click to expand...
Click to collapse
Did you mean i have to flash RR over 5.1.1? Last time i ran into this error i was flashing it over 6.0.1, and I did full wipes within TWRP.
iH8Ecchi said:
Did you mean i have to flash RR over 5.1.1? Last time i ran into this error i was flashing it over 6.0.1, and I did full wipes within TWRP.
Click to expand...
Click to collapse
Yes.
Because it work only with 5.1.1 bootloader.
Hi there,
just to give a feedback. DUALSIM is not working on both builds. LTE function fails. Made complete new flash, nothing helps...
Same applies to crDroid - build 20170802 - 7.1.2
I would kindly ask for help around here
Thanks,
Light of Magic
after one day....
Hi,
I don´t know why dualsim function stopped working... I tried 2 builds each - Lineageos, Ressurection OS, crDroid ... going back to stock ROM, everthing works fine. I even searched through the net to get a suitable pit file.
Only thing - I wanted to update like https://forum.xda-developers.com/galaxy-s5/development/rom-lineage-os-samsung-galaxy-s5-lte-t3534283
And I could not find TWRP 3.0.0 as recommended, so I use 3.1.0 - I could not install SkiesROM, since it was maybe to large....
For any help I would be greatful,
Light of Magic
LightofMagic said:
Hi,
I don´t know why dualsim function stopped working... I tried 2 builds each - Lineageos, Ressurection OS, crDroid ... going back to stock ROM, everthing works fine. I even searched through the net to get a suitable pit file.
Only thing - I wanted to update like https://forum.xda-developers.com/galaxy-s5/development/rom-lineage-os-samsung-galaxy-s5-lte-t3534283
And I could not find TWRP 3.0.0 as recommended, so I use 3.1.0 - I could not install SkiesROM, since it was maybe to large....
For any help I would be greatful,
Light of Magic
Click to expand...
Click to collapse
Here u get TWRP 3.0.0.0 for klte as recommended. Extract the zip before use. Use the .tar for Odin flash or the .img for flash through recovery. Tip: download twrp-app from Playstore. You'll find all downloadable content there.
I've read that going back from LOS / AOSP to SkiesROM is not possible without flashing a Stock Rom first. Make sure u have flashed the fitting bootloaders via Odin before u flash the Stock ROM. Suitable are the ROMS from ALEXNDR. They're prerooted and a good base to go further.
Good luck
still
I wounder, does anyone have the same issue? Using the builds in May I did not have this issue.
Thanks to ottili81 for TWRP 3.0.0.0 !!!
Greetings,
Light of Magic
Is it possible or is it with the recovery image im using
Asus Zenfone 2 laser ze550kl z00l is my phone model
I have tried many stockroms to install but only one get installed perfectly namely back2stock-1.17.40.1234.zip. Because of this i can't even install any other custom roms like i tried to install lineage rom but itstuck on bootloop
Any kind of replies and queries about my problem asked will be much help full
moddinandroid said:
Is it possible or is it with the recovery image im using
Asus Zenfone 2 laser ze550kl z00l is my phone model
I have tried many stockroms to install but only one get installed perfectly namely back2stock-1.17.40.1234.zip. Because of this i can't even install any other custom roms like i tried to install lineage rom but itstuck on bootloop
Any kind of replies and queries about my problem asked will be much help full
Click to expand...
Click to collapse
Install mm framware then install custom ROM...it will sure booted up
mg712702 said:
Install mm framware then install custom ROM...it will sure booted up
Click to expand...
Click to collapse
What im trying to tell is that my problem is not only installation in custom roms but i also cant install any other roms eiether from official site or some other site which means i cant install any roms accept the one the stock rom i mentioned above. And also i already tried to install MM firmware but it gives out error code 7 in twrp. I tried as i was said to install the previous version of lollipop before the update of MM came out but still i cant install them.
moddinandroid said:
What im trying to tell is that my problem is not only installation in custom roms but i also cant install any other roms eiether from official site or some other site which means i cant install any roms accept the one the stock rom i mentioned above. And also i already tried to install MM firmware but it gives out error code 7 in twrp. I tried as i was said to install the previous version of lollipop before the update of MM came out but still i cant install them.
Click to expand...
Click to collapse
Which Android u r using now
Lolipop or MM
is your bootloader locked on unlocked?
just go back to stock versions for now
if u r on lollipop, download the 'next version' from asus
if u r on marshmallow, download the next version from asus
use fastboot (bootloader) mode to flash if required
when all is stable and done,
download & flash twrp
flash lineage 13, then lineage 14
yograjfire18 said:
Which Android u r using now
Lolipop or MM
Click to expand...
Click to collapse
Iam using lollipop right now
pokipokipxorn said:
is your bootloader locked on unlocked?
just go back to stock versions for now
if u r on lollipop, download the 'next version' from asus
if u r on marshmallow, download the next version from asus
use fastboot (bootloader) mode to flash if required
when all is stable and done,
download & flash twrp
flash lineage 13, then lineage 14
Click to expand...
Click to collapse
Yes my bootoader is unlocked cuz i tried rooting my phone when MM update came out
I cant roll back to the original/factory rom cuz i can't install any rom including official asus ones
2. Ill be trying to using fastboot will post results soon
moddinandroid said:
Iam using lollipop right now
Click to expand...
Click to collapse
that's the reason u can install any custom rom, bcs they r all MM or N
so U hav to first upgrade to mm using stock rom
then u can flash any rom
moddinandroid said:
Iam using lollipop right now
Click to expand...
Click to collapse
https://basketbuild.com/filedl/devs?dev=LuK1337&dl=LuK1337/ZF2L-FW/Z00L-WW-21.40.1220.1615.zip
Download and flash then u r ready to go
Now u can install any rom, like RR MM, CM 13 many others too
Hit thanks if i helped
Yeah that right..or you can make backtostock.zip by your self,just download stock mm rom and copy the following requirement file to backtostock.zip and flash that on twrp..
Thnsk guys for all your replies
My problem i was not using latest twrp recovery
Again thank you so much for ur help
Hi guys I have rooted my YU yureka cm 11. Its been 2 days I am trying to flash twrp on my device using both twrp official app and twrp manager. I have tried 3.1,3.0,3.02 versions while flashing. After flashing it says successfull but when I tried to reboot into recovery the mobile stucks on YU logo I think gets bricked this is what happening every time
CM11?
Any reason to sticking with CM11?
It is a 32 bit ROM and TWRP you're trying to flash is 64 bit. It won't get flashed ever.
Better install COS12.1 or any other custom ROMs.
There is no any specific reason for sticking with cm11 I thought it is most stable.
So is there any way I can flash twrp?
Or do I have to upgrade to cm 12.1 and then try to flash?
Can you recommend me any rom with better stability for yureka?
First try to upgrade to COS12.1 and than flash TWRP.
There are lots of N custom ROMs available and is stable. You can find more about them here or at YU Forum.
minestrome said:
There is no any specific reason for sticking with cm11 I thought it is most stable.
So is there any way I can flash twrp?
Or do I have to upgrade to cm 12.1 and then try to flash?
Can you recommend me any rom with better stability for yureka?
Click to expand...
Click to collapse
Flash Cos12.1 via fastboot, as it will change ur architecture from 32bit to 64bit...
Then check bootloader status, and if locked, unlock it as well, flash TWRP and enjoy custom ROMs,
Nougat ROMs are much stable now
For any problem, feel free to ask,
Thank YOU
thanks
Thank you very much guys , your help is very very appreciated.
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