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.
idk if posted some same thread but my problem is my phone suddenly reboots.
screen went off, twice vibration, then went to samsung galaxy s5 logo.
current setup: android 6.0.1 running no limits rom. all stock
sometimes it reboots then it is stock on the bootloader. i need to remove the battery and turn it on manually. using bootloader and modem of the latest recommended bootloader from the no limits rom.
(it also random reboots on stock firmware using spain which i downloaded from sam mobile firmwares)
is this a hardware issue?
edit: what i did was i upgraded my stock rom from 5.0.1 russia to 6.0.1 spain, does this affect anything? should i stick with russia?
rusherrrx said:
idk if posted some same thread but my problem is my phone suddenly reboots.
screen went off, twice vibration, then went to samsung galaxy s5 logo.
current setup: android 6.0.1 running no limits rom. all stock
sometimes it reboots then it is stock on the bootloader. i need to remove the battery and turn it on manually. using bootloader and modem of the latest recommended bootloader from the no limits rom.
(it also random reboots on stock firmware using spain which i downloaded from sam mobile firmwares)
is this a hardware issue?
Click to expand...
Click to collapse
Since you mentioned Hardware, Check if all the cores are working
Arabix.Sword said:
Since you mentioned Hardware, Check if all the cores are working
Click to expand...
Click to collapse
cores are all working my guess is the battery that is somehow related right??????
rusherrrx said:
cores are all working my guess is the battery that is somehow related right??????
Click to expand...
Click to collapse
i don't think it has to do with the battery because as long as you have power cores will work,
Do your phone gets too hot then?
I know what's going on I think. Something modified your kernel or something in the ROM is unstable. I had one that did that same thing when I used the camera. You need a better ROM. I recommend ressurection remix 5.8.3 nougat 7.1.2. No reason to be on marshmallow. And get this kernel. It fixed the camera issue and improves battery life. It's a unified klte rom.
godkingofcanada said:
I know what's going on I think. Something modified your kernel or something in the ROM is unstable. I had one that did that same thing when I used the camera. You need a better ROM. I recommend ressurection remix 5.8.3 nougat 7.1.2. No reason to be on marshmallow. And get this kernel. It fixed the camera issue and improves battery life. It's a unified klte rom.
Click to expand...
Click to collapse
i am currently on 6.0.1 mm stock firmware. and still i experience this issues
That does not guarantee there's no bugs in your phone. Have you ever flashed a ROM or anything to your device?
godkingofcanada said:
That does not guarantee there's no bugs in your phone. Have you ever flashed a ROM or anything to your device?
Click to expand...
Click to collapse
oh okay. well as soon as i got the device it was on android 5, flashed twrp. then flashed no limits rom didnt work (cause all i thought i can boot it to mm but no) so wiped again installed xstolite rom rather, ticked reactivation locked. [i think this was the time it started]so i updraded it to 6.0.1 but i didnt know the account cos this phone is a used phone so i did was to downgrade it to 4.4 then bypass it and it worked (still experiencing issues tho). so upgraded again to stock 6.0.1 and here i am. (
edit: im on phoenix rom latest version also using recommended bootloader and everything works tho it still reboots randomly halp plz
rusherrrx said:
oh okay. well as soon as i got the device it was on android 5, flashed twrp. then flashed no limits rom didnt work (cause all i thought i can boot it to mm but no) so wiped again installed xstolite rom rather, ticked reactivation locked. [i think this was the time it started]so i updraded it to 6.0.1 but i didnt know the account cos this phone is a used phone so i did was to downgrade it to 4.4 then bypass it and it worked (still experiencing issues tho). so upgraded again to stock 6.0.1 and here i am. (
edit: im on phoenix rom latest version also using recommended bootloader and everything works tho it still reboots randomly halp plz
Click to expand...
Click to collapse
Upgrade to a nougat ROM. It uses the same bootloader of mm so you only need to flash a ROM. Get ressurection remix or lineage is 14.1. Nougat fixes a lot of bugs and security issues. And xtrestolite isn't the most stable ROM. I had it in my s4.
---------- Post added at 06:47 AM ---------- Previous post was at 06:45 AM ----------
And then if you use rr get the kernel I showed you and flash that too. Please note these Roms don't come with gapps. Google open gapps and it comes up. You want arm 7.0 or 7.1. Stock if you don't mind waiting a while for it to download. I get nano to save time as it still installs the framework and playstore. It saves space and if you want something it didn't install play store will have it anyway.
godkingofcanada said:
Upgrade to a nougat ROM. It uses the same bootloader of mm so you only need to flash a ROM. Get ressurection remix or lineage is 14.1. Nougat fixes a lot of bugs and security issues. And xtrestolite isn't the most stable ROM. I had it in my s4.
---------- Post added at 06:47 AM ---------- Previous post was at 06:45 AM ----------
And then if you use rr get the kernel I showed you and flash that too. Please note these Roms don't come with gapps. Google open gapps and it comes up. You want arm 7.0 or 7.1. Stock if you don't mind waiting a while for it to download. I get nano to save time as it still installs the framework and playstore. It saves space and if you want something it didn't install play store will have it anyway.
Click to expand...
Click to collapse
so you mean cyanogenmod?
Cyanogen mod is now lineage os team. Don't use cyanogen. Get lineage 14.1
If none of the software fixes work, it's your battery. Personal experiance from my S3 Mini and my S5. Don't rage over it going nuts (been there, done that) but just get a new battery.
koragg97 said:
If none of the software fixes work, it's your battery. Personal experiance from my S3 Mini and my S5. Don't rage over it going nuts (been there, done that) but just get a new battery.
Click to expand...
Click to collapse
i dont see any pops or physical damage to it.. anyway, but ill update you as soon as I buy a new one. thanks!
Device _a6000 1gb ram variant
By your good experience, I need suggestions for a good 32-bit ROM developed till now. Lag free running of phone, and battery backup are the main concerns.Plz suggest suitable kernel too. Replies are much appreciated. Thankyou.
Redemptioner_ said:
Device _a6000 1gb ram variant
By your good experience, I need suggestions for a good 32-bit ROM developed till now. Lag free running of phone, and battery backup are the main concerns.Plz suggest suitable kernel too. Replies are much appreciated. Thankyou.
Click to expand...
Click to collapse
Stock ROM with MoStock kernel is good. Try it.
However, if you want a little lightweight ROM, you might want to try @ED300's CyanogenMod 11.
You might also like ED300's CyanogenMod 12.1 as well. However, the latest updates, I find, are a little slow on my phone.
You can also flash MoStock on said CM11, but I haven't tried it, as you have to repackage some modules for WiFi & such.
I personally am on CM11 update 11 (with no special kernel) right now.
AsCi1 said:
Stock ROM with MoStock kernel is good. Try it.
However, if you want a little lightweight ROM, you might want to try @ED300's CyanogenMod 11.
You might also like ED300's CyanogenMod 12.1 as well. However, the latest updates, I find, are a little slow on my phone.
You can also flash MoStock on said CM11, but I haven't tried it, as you have to repackage some modules for WiFi & such.
I personally am on CM11 update 11 (with no special kernel) right now.
Click to expand...
Click to collapse
CyanogenMod 11 is a KitKat based ROM as far as I know and currently I am on RR 5.8.4 64-bit nougat ROM . Can you please tell does it require a specific procedure to flash from Android N to K or is it okay to flash normally like wipe > adv wipe > cache , dalvik , system / flash ROM , gapps , reboot.
Redemptioner_ said:
CyanogenMod 11 is a KitKat based ROM as far as I know and currently I am on RR 5.8.4 64-bit nougat ROM . Can you please tell does it require a specific procedure to flash from Android N to K or is it okay to flash normally like wipe > adv wipe > cache , dalvik , system / flash ROM , gapps , reboot.
Click to expand...
Click to collapse
Reverting to KitKat from Android 5.1+ (Lollipop, Marshmallow & Nougat) requires you to flash stock KitKat ROM.
Or you can try this firmware: https://forum.xda-developers.com/le...itkat-lolipop-firmware-base-switcher-t3249046
Though I haven't tested this myself, I believe it will work fine.
---------- Post added at 07:39 AM ---------- Previous post was at 07:04 AM ----------
Since you are on Nougat:
- Download KitKat firmware.
- Wipe dalvik, cache, data, system (don't wipe internal).
- Flash KitKat firmware & then flash the CM11 ROM over it.
If you choose to flash Stock KitKat ROM, do the normal flash:
- Wipe cache, data, system, dalvik & then flash Stock KitKat ROM.
Doing the latter (flashing KitKat ROM) will bring your device to the state of first, out-of-the-box, fresh boot.
What this means is that you'll have to start all over again (i.e flash recovery again).
go for official lineage by harsh
have been using it for one month or so , its flawless and works without lag
RR 7.1 May 9 build. try this. smooth for my lenovo 1gb.
Have you faced wifi problem in stock kk with mostock kernel? I can't turn on wifi , for turning on , device needs a reboot
AsCi1 said:
Stock ROM with MoStock kernel is good. Try it.
However, if you want a little lightweight ROM, you might want to try @ED300's CyanogenMod 11.
You might also like ED300's CyanogenMod 12.1 as well. However, the latest updates, I find, are a little slow on my phone.
You can also flash MoStock on said CM11, but I haven't tried it, as you have to repackage some modules for WiFi & such.
I personally am on CM11 update 11 (with no special kernel) right now.
Click to expand...
Click to collapse
Sumer_7 said:
Have you faced wifi problem in stock kk with mostock kernel? I can't turn on wifi , for turning on , device needs a reboot
Click to expand...
Click to collapse
Sorry, no such problem for me.
Try to flash ROM again.
Best of luck.
:good:
vishal_kaushal said:
go for official lineage by harsh
have been using it for one month or so , its flawless and works without lag
Click to expand...
Click to collapse
Can u plsss give the link for official lineage OS for a6000???
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
Hi guys,
Everything was working great with LineageOS 15.1 (Android 8.1), but they have discontinued the support for this version and switched to 16.0, and a FOTA update of Lineage from 15 to 16 isn't possible, so I had to download the zip manually, and flashed it using TWRP, around the end of April. Since then the Wi-Fi does not work.
I should explain what this "does not work" mean: I turn it on (either from the pull-down curtain, or from the Settings -> Network -> Wi-Fi menu), it pretends to switch on for 1-2 seconds, and then the switch turns off by itself, so it doesn't even have time to scan the available networks.
I have tried to burn a newer image again, around the beginning of May, but it didn't fix the Wi-Fi problem. I was googling a lot, but seems like nobody reports such a problem.
Any ideas how to fix it, other than going back to Android 8.1? Preferably I'd like to stay with LOS, but if I have no choice, I can consider moving to RR, or AOSP Extended or whatever.
Thanks!
I think its a boot.img problem. I have seen this error in stock too. The wifi/bluetooth used to turn off immediately after i turned them on and the error was because i flashed the wrong boot.img . If i were you i would clean flash the rom again
What do you mean by "wrong boot.img"? I don't flash any boot.img separately, I just flash the whole LineageOS rom (and then Gapps) from TWRP. Should I flash anything else? I don't think so...
Well, in my case at least the Bluetooth works properly (with both headphones and smart watch).
SOLVED!
Surprisingly, the problem seems to be solved now.
After flashing lineage-16.0-20190426 and later lineage-16.0-20190530 versions, where the Wi-Fi didn't work - today I have flashed lineage-16.0-20190704, and guess what? It is back now!
Thought it should be important to update the thread here.
xdauseril said:
Surprisingly, the problem seems to be solved now.
After flashing lineage-16.0-20190426 and later lineage-16.0-20190530 versions, where the Wi-Fi didn't work - today I have flashed lineage-16.0-20190704, and guess what? It is back now!
Thought it should be important to update the thread here.
Click to expand...
Click to collapse
It would be safer to update to stock pie first then flash custom pie roms..
Jt380p said:
It would be safer to update to stock pie first then flash custom pie roms..
Click to expand...
Click to collapse
You mean, even if I upgrade from Lineage 15.1 to 16 I need to flash the stock rom first? Why?
BTW I saw some reports on Wi-Fi problem while going back from custom to stock rom too, and there was some patch suggested to fix it.
xdauseril said:
You mean, even if I upgrade from Lineage 15.1 to 16 I need to flash the stock rom first? Why?
BTW I saw some reports on Wi-Fi problem while going back from custom to stock rom too, and there was some patch suggested to fix it.
Click to expand...
Click to collapse
Because its a prerequisite on Lineage 16, it depends on parts of stock Pie rom being installed.
The LO16 thread also listed a migration step if you didn't flash the stock Pie rom beforehand.
barrack1 said:
Because its a prerequisite on Lineage 16, it depends on parts of stock Pie rom being installed.
The LO16 thread also listed a migration step if you didn't flash the stock Pie rom beforehand.
Click to expand...
Click to collapse
Probably I have missed it.
Still can't find it neither on "install" nor "update" page:
https://wiki.lineageos.org/devices/tissot/install
https://wiki.lineageos.org/devices/tissot/update
xdauseril said:
Probably I have missed it.
Still can't find it neither on "install" nor "update" page:
https://wiki.lineageos.org/devices/tissot/install
https://wiki.lineageos.org/devices/tissot/update
Click to expand...
Click to collapse
Its on the xda thread, not on the lineageos website.
Xiaomi made some changes during the upgrade from Oreo->Pie and introduced ARB. Now you cannot downgrade back to Oreo easily. Just flashing back to Oreo(stock or custom rom) will cause the phone to bootloop. For the same reason your phone probably faced issues when you flashed (Pie) LO16 without the Pie firmware.
barrack1 said:
Its on the xda thread, not on the lineageos website.
Xiaomi made some changes during the upgrade from Oreo->Pie and introduced ARB. Now you cannot downgrade back to Oreo easily. Just flashing back to Oreo(stock or custom rom) will cause the phone to bootloop. For the same reason your phone probably faced issues when you flashed (Pie) LO16 without the Pie firmware.
Click to expand...
Click to collapse
Well, I did not try to downgrade from Pie to Oreo. All I tried to do was an upgrade from LOS 15.1 to LOS 16 (15.1 worked excellent). And I had no idea I needed to flash the stock rom in between, so I just flashed 16 over 15.1, without wiping the data partition (only wiped dalvik cache).
Can you please point me to the XDA thread you mention, where it says I had to flash the stock rom first?
Anyway, since everything works OK now (or, at least, I don't find any malfunctioning, probably except for the native camera app, so I use an external app), I don't think I should play around with it again, right?
xdauseril said:
Well, I did not try to downgrade from Pie to Oreo. All I tried to do was an upgrade from LOS 15.1 to LOS 16 (15.1 worked excellent). And I had no idea I needed to flash the stock rom in between, so I just flashed 16 over 15.1, without wiping the data partition (only wiped dalvik cache).
Can you please point me to the XDA thread you mention, where it says I had to flash the stock rom first?
Anyway, since everything works OK now (or, at least, I don't find any malfunctioning, probably except for the native camera app, so I use an external app), I don't think I should play around with it again, right?
Click to expand...
Click to collapse
Some parts of the firmware might not be overwritten by LOS/stock depending on the version. The original LO16 used Oreo firmware iirc. The thread is not hard to find, just look for it.