Database Users

Galaxy S4 i9500 - CM 12.1 Nightly (20160110) - GApps crashing constantly

So today I went from stock 5.0.1 to CM 12.1 Nightly (20160110) but gapps keeps crashing which makes my phone semi useless
First Things first
1. Flashed TWRP using Odin
2. Went into recovery and wiped Data and System
3. Installed CM 12.1
4. Installed GApps
5. Wiped Cache/Dalvik and rebooted
Phone boots up normally, And after unlocking the screen a stream of errors emerges, Not sure if i'm using the right gapps or not
Any help is much appreciated
~Chik

Chikyu Tenshi said:
So today I went from stock 5.0.1 to CM 12.1 Nightly (20160110) but gapps keeps crashing which makes my phone semi useless
First Things first
1. Flashed TWRP using Odin
2. Went into recovery and wiped Data and System
3. Installed CM 12.1
4. Installed GApps
5. Wiped Cache/Dalvik and rebooted
Phone boots up normally, And after unlocking the screen a stream of errors emerges, Not sure if i'm using the right gapps or not
Any help is much appreciated
~Chik
Click to expand...
Click to collapse
Did you by any chance use Opengapps? Opengapps is like a hit or miss. Some days they work and some days then don't.
Try these gapps:
http://download.dirtyunicorns.com/files/gapps/banks_gapps/
You need to perform a full wipe though.

Lennyz1988 said:
Did you by any chance use Opengapps? Opengapps is like a hit or miss. Some days they work and some days then don't.
You need to perform a full wipe though.
Click to expand...
Click to collapse
Yes I did try Opengapps which also didn't work
Edit: The gapps is 6.x.x while my phone is 5.1.1, That won't break my phone will it?
~Chik

You need 5.1 gapps then.

Chikyu Tenshi said:
Yes I did try Opengapps which also didn't work
Edit: The gapps is 6.x.x while my phone is 5.1.1, That won't break my phone will it?
~Chik
Click to expand...
Click to collapse
My bad. Here is also another gapps
http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368

Lennyz1988 said:
My bad. Here is also another gapps
Click to expand...
Click to collapse
Still :c I only flashed the base tho, Am I supposed to flash the add ons too?

I think you can try a complete boot before flashing Gapps. And try other builds of Opengapps like mini or micro(well or even smaller depending your "Google apps" usage)

CHIN3S3_N00B said:
I think you can try a complete boot before flashing Gapps. And try other builds of Opengapps like mini or micro(well or even smaller depending your "Google apps" usage)
Click to expand...
Click to collapse
Thanks for the reply, I'm downloading micro right now. Gonna fresh install CM 12.1 using TWRP then boot my phone fully before going back to recovery and flashing Gapps
Will edit my post within 30 mins with the result
Edit: No luck, And now for some reason my phone does not recognise my sim card

Could you try GearCM? Official CM for i9500 had lots of issues.
Sent from my GT-I9500

Chikyu Tenshi said:
Thanks for the reply, I'm downloading micro right now. Gonna fresh install CM 12.1 using TWRP then boot my phone fully before going back to recovery and flashing Gapps
Will edit my post within 30 mins with the result
Edit: No luck, And now for some reason my phone does not recognise my sim card
Click to expand...
Click to collapse
Strange... because the symptoms shows like a mismatched gapps to cm... btw are you using the lastest TWRP?
If Yes try other recoveries. I used to use Philz until I bricked mine and had to flash back to stock and now I'm using a modified TWRP to enable dual boot.
If No then try update it and give it another try?

CHIN3S3_N00B said:
Strange... because the symptoms shows like a mismatched gapps to cm... btw are you using the lastest TWRP?
If Yes try other recoveries. I used to use Philz until I bricked mine and had to flash back to stock and now I'm using a modified TWRP to enable dual boot.
If No then try update it and give it another try?
Click to expand...
Click to collapse
I recommend against doing this. The other recoveries are outdated and will give you problems. Stick with the latest TWRP.

Lennyz1988 said:
I recommend against doing this. The other recoveries are outdated and will give you problems. Stick with the latest TWRP.
Click to expand...
Click to collapse
I think that i didn't express myself very well. Yes it's advisable and strongly recommended to use lastest builds of any recovery available as stable build.
But once i had to use Philz to flash a MIUI ROM because TWRP 2.8.6.0 was unable to execute the installation script didn't know why and that's why i said about different recoveries, and oh.... I forgot to say that after successful install rollback to TWRP because it's pretty new , stable and more user friendly than others.(CMW and the rainbow Easter egg was fine but having to use vol and power keys..... NO THANKS!)

Not able to run 6.0 based ROMs

Hi all,
I try to run a 6.0 based ROM, but when I first boot the phone after an install the phone reboots after half a minute. It looks like it boots normally, but after entering language and other settings (or also when skipping all) the phone reboots and the process starts over again.
I tried to install factory ROM via ADB, this doesn't give any errors while installing.
The same happens when I try another ROM like CM 13.
Only stable ROM for me is CM12, all other ROMS give reboot.
Any suggestions? Am I installing the wrong ROMs? I have a XT1562, run Squid kernel and latest TWRP.

knielen said:
Hi all,
I try to run a 6.0 based ROM, but when I first boot the phone after an install the phone reboots after half a minute. It looks like it boots normally, but after entering language and other settings (or also when skipping all) the phone reboots and the process starts over again.
I tried to install factory ROM via ADB, this doesn't give any errors while installing.
The same happens when I try another ROM like CM 13.
Only stable ROM for me is CM12, all other ROMS give reboot.
Any suggestions? Am I installing the wrong ROMs? I have a XT1562, run Squid kernel and latest TWRP.
Click to expand...
Click to collapse
You tried tesla rom. Also first just flash the rom and boot. Once it successfully boots up, go ahead with gapps.

Thanks for your answer, it indeed is caused by the Gapps package. When I install a ROM without Gapps, everything works fine. Trying to find a compatible Gapps package now.

K.khiladi said:
You tried tesla rom. Also first just flash the rom and boot. Once it successfully boots up, go ahead with gapps.
Click to expand...
Click to collapse
knielen said:
Thanks for your answer, it indeed is caused by the Gapps package. When I install a ROM without Gapps, everything works fine. Trying to find a compatible Gapps package now.
Click to expand...
Click to collapse
As far as i remember, ever since MM, it's recommended to flash both the ROM and GAPPS together.

varounmirchi said:
As far as i remember, ever since MM, it's recommended to flash both the ROM and GAPPS together.
Click to expand...
Click to collapse
Only 6.0 rom I found that works is DU with Banks Gapps, and yes, had to install them at the same time.
This rom is a battery drain and has gps fix issues for me, not sure if I stay with this rom or go back to CM 12
Sent from my du_lux using XDA-Developers mobile app

varounmirchi said:
As far as i remember, ever since MM, it's recommended to flash both the ROM and GAPPS together.
Click to expand...
Click to collapse
Nope, there's no such requirement. I have just flashed the rom first cause sometimes the Gapps cause stability issues.
Automated reply by JARVIS

Stuck in bootloop trying to flash 7.1 custom rom

My phone is android 6.0 and I've been using "TruPureXMM 2.9" ever since it first came out. I have a February 1, 2016 android security patch level and my system version is 24.11.18 clark_retus.retus.en.US retus
I had an older version of twrp so I just updated it to the latest one before attempting this ofc...
I tried flashing the latest RR and AICP and both give me boot loops and I always get this one problem where it says
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
I'm not sure if this has anything to do with the bootloop though...
Going to recovery after seeing the bootloop I always get the "keep system read only?" prompt where i swipe to allow modification but i usually just restore back to my backup from there... i dont think allowing it and trying to boot again will get rid of the bootloop...
I followed the process of first doing a full wipe with twrp > flash rom > flash gapps > restart system
no idea what i'm doing wrong..

OppaiHeroStar said:
My phone is android 6.0 and I've been using "TruPureXMM 2.9" ever since it first came out. I have a February 1, 2016 android security patch level and my system version is 24.11.18 clark_retus.retus.en.US retus
...
I followed the process of first doing a full wipe with twrp > flash rom > flash gapps > restart system
no idea what i'm doing wrong..
Click to expand...
Click to collapse
1st - you need twrp 3.x+,
2nd - full wipe - format data, adv.wipe - all without micro sd.
3rd - flash rom, flash gapps(opengapps.org, ≤mini, arm64, 7.1)
Last Rr is for Nougat modem - you are on MM modem.
Flash RR 21.11.2017.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36

dzidexx said:
1st - you need twrp 3.x+,
2nd - full wipe - format data, adv.wipe - all without micro sd.
3rd - flash rom, flash gapps(opengapps.org, ≤mini, arm64, 7.1)
Last Rr is for Nougat modem - you are on MM modem.
Flash RR 21.11.2017.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36
Click to expand...
Click to collapse
The first 3 steps I've already done that since the beginning
Where can i get the nougat modem/is it possible to update to it? I guess that's the reason every single 7.1 custom rom I tried in the android development section gave me boot loops...
And could you link the 21.11.2017 version of RR? I'm looking at the download links for RR and I dont see one with that exact date
edit-just saw your edit

Custom roms for MM modem works better.

I fully wiped using TWRP, checked everything I possibly could except my micro SD card and I flashed RR-N-v5.8.5-20171121-clark-Final.zip then gapps arm64, 7.1 nano and it's still giving me boot loops. I'm using TWRP 3.2.1-0
im gonna try using gapps arm64 7.1 mini really quick since you said I should use that one and see if it boot loops... - Edit guess I was too optimistic thinking this would fix it

Bugs probably after flashing december RR.
Change twrp to 3.1.x, reboot twrp, change all partitions to ext4 - adv wipes - One by one - cache, system, data, reboot twrp.
Change back to f2fs - only cache & data, wipe all, flash what I wrote.

dzidexx said:
Bugs probably after flashing december RR.
Change twrp to 3.1.x, reboot twrp, change all partitions to ext4 - adv wipes - One by one - cache, system, data, reboot twrp.
Change back to f2fs - only cache & data, wipe all, flash what I wrote.
Click to expand...
Click to collapse
changed to 3.1.1-0 and did everything you said, still have boot loop...
when flashing this RR i still get this, not sure if it's a problem but thought I would just let you know
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"

OppaiHeroStar said:
changed to 3.1.1-0 and did everything you said, still have boot loop...
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
Click to expand...
Click to collapse
It doesn`t matter.
Try another custom - LOS f.e.
If bootloop still will be - you should flash full stock.
Last MM for RetUs

dzidexx said:
It doesn`t matter.
Try another custom - LOS f.e.
If bootloop still will be - you should flash full stock.
Last MM for RetUs
Click to expand...
Click to collapse
I tried crDroidAndroid-7.1.2-20171119-clark-v3.8.3.zip and it still boot loops :\ I also already tried LineageOS and AICP before we started talking
I went back to my backup and it put me in a bootloop which never happened before but changing cache back to ext4 instead of f2fs fixed it..

OppaiHeroStar said:
when flashing this RR i still get this, not sure if it's a problem but thought I would just let you know
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
Click to expand...
Click to collapse
A little late to chime in and this does not help with your current situation, but here's a little advice. I flash a lot of ROMs (how else am I going to test builds right?). This error happens all the time, BUT if you flash a ROM twice it should not show on the 2nd flash.
So flash order goes:
Wipe/Factory reset
Format data x3 (yes I format my data 3 times for every ROM)
Reboot
Wipe/Factory reset
ROM
ROM again
GAPPS
Wipe caches
Reboot
Do the Initial setup
Reboot before use
OPTIONAL Kernel (if its not already build in)
OPTIONAL Magisk (I never flash Magisk on a clean build but heck I'm expecting a NON boot most of the time anyways)

At this point I would flash the stock Nougat image via fastboot to get the device operational again... Then look at TWRP, root, or custom ROM.

acejavelin said:
At this point I would flash the stock Nougat image via fastboot to get the device operational again... Then look at TWRP, root, or custom ROM.
Click to expand...
Click to collapse
so should I just straight up flash the nougat image via fastboot from your thread here? https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
i dont need to go back to mm stock or something first? I don't really have much knowledge about this.

OppaiHeroStar said:
so should I just straight up flash the nougat image via fastboot from your thread here? https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
i dont need to go back to mm stock or something first? I don't really have much knowledge about this.
Click to expand...
Click to collapse
Correct... And verify everything is working properly before you flash TWRP, root, or take any OTA update.

acejavelin said:
Correct... And verify everything is working properly before you flash TWRP, root, or take any OTA update.
Click to expand...
Click to collapse
so i finished flashing that nougat firmware and looks like everything is working ok, does that mean I can try flashing custom roms after twrp now?

OppaiHeroStar said:
so i finished flashing that nougat firmware and looks like everything is working ok, does that mean I can try flashing custom roms after twrp now?
Click to expand...
Click to collapse
Boot TWRP (don't flash it) and make a full back, and I would recommend not talking any OTAs either.
Then knock yourself out... You can always get back to this state if things go badly.

acejavelin said:
Boot TWRP (don't flash it) and make a full back, and I would recommend not talking any OTAs either.
Then knock yourself out... You can always get back to this state if things go badly.
Click to expand...
Click to collapse
was finally able to flash a custom rom without bootloops!
thank you and everyone else here for the help I honestly really appreciate it

OppaiHeroStar said:
was finally able to flash a custom rom without bootloops!
thank you and everyone else here for the help I honestly really appreciate it
Click to expand...
Click to collapse
What custom did you flashed?

dzidexx said:
What custom did you flashed?
Click to expand...
Click to collapse
I tried out AICP, AOKP, and RR. All latest versions and they worked but for some reason my data doesn't work on any of those customs.
guess my happiness was short lol. Considering just staying stock now

OppaiHeroStar said:
I tried out AICP, AOKP, and RR. All latest versions and they worked but for some reason my data doesn't work on any of those customs.
guess my happiness was short lol. Considering just staying stock now
Click to expand...
Click to collapse
I'm not sure for others but RR - only 5.8.5-04.12 works with N modem.
Did you check/set access points properly?
All customs for N modem(I think) have problems with notification sound, so you can stay at stock.

dzidexx said:
I'm not sure for others but RR - only 5.8.5-04.12 works with N modem.
Did you check/set access points properly?
All customs for N modem(I think) have problems with notification sound, so you can stay at stock.
Click to expand...
Click to collapse
I'm using t-mobile and I've checked the access points, clicking on the one im using and hitting save doesn't fix it. Always getting a notification telling me to sign in to network. Not sure what else I can do. I'll give it a day since I had this kind of problem before when I switched sim cards and data didn't work until the next day
Edit - just went back to stock and my data doesn't work now either... just going to stay at RR now and hope my data fixes itself because my access point settings for tmobile should be correct since I looked it up on the official website..

Oreo 8.0 8.1 installing issues

Hi you there,
I start this thread because I´m having some issues installing 8.0 and 8.1 Oreo Roms, every of them have the same problems when I try to install them in my device (REDMI 3X). Actually, I have install and running Resurrection Remix Nougat + Gapps Micro, and it works fine.
When I try to install some Oreo Rom, I have these 2 possible options:
1 - I install rom + gapps (no matter which one, cause I tried each one): phone restarts and stucks at logo and after maybe 30 minutes I must restart it manually and reinstall a nougat rom. It never starts, and it is f...ng annoying.
2 - I install rom, afterwards, I restart and it works fine, but I have no gapps. The I boot into recovery and after gapps are installed I restart the phone, then gapps never work.
Please, I just get 2 times an oreo rom working, but now they never work, I don´t know whta to do. I also tried different recoveries, flashing them from PC, installing them from .img with TWRP, nothing seems to work. As I said: F...NG ANNOYING. I need heeeeeeeeeeeeeeeeelp
I think I am not the only one with this problem, if anyone can help I will appreciate that.
Thansk in advance.

First of all, this should be in the Q&A section. Secondly, I can help you. I'm sure that you downloaded the gapps from the cloudkenzo something, right? Yeah those gapps do not have any issues, instead they make an issue. After flashing your rom and then these gapps file, the system partition normally unmounts. But usually when you boot into the ROM, the partition should re-mount. These unofficial gapps causes some issues with that. A simple solution- Just mount system in twrp, now reboot to system and you should be fine. I faced the same issue and this is my solution.

alopez_666 said:
Hi you there,
I start this thread because I´m having some issues installing 8.0 and 8.1 Oreo Roms, every of them have the same problems when I try to install them in my device (REDMI 3X). Actually, I have install and running Resurrection Remix Nougat + Gapps Micro, and it works fine.
When I try to install some Oreo Rom, I have these 2 possible options:
1 - I install rom + gapps (no matter which one, cause I tried each one): phone restarts and stucks at logo and after maybe 30 minutes I must restart it manually and reinstall a nougat rom. It never starts, and it is f...ng annoying.
2 - I install rom, afterwards, I restart and it works fine, but I have no gapps. The I boot into recovery and after gapps are installed I restart the phone, then gapps never work.
Please, I just get 2 times an oreo rom working, but now they never work, I don´t know whta to do. I also tried different recoveries, flashing them from PC, installing them from .img with TWRP, nothing seems to work. As I said: F...NG ANNOYING. I need heeeeeeeeeeeeeeeeelp
I think I am not the only one with this problem, if anyone can help I will appreciate that.
Thansk in advance.
Click to expand...
Click to collapse
Make sure using the latest twrp.
If u already have the latest twrp then the problem is in gapps, use gapps for oreo 8.1, maybe there is posted in ur rom thread

F4nno said:
Make sure using the latest twrp.
If u already have the latest twrp then the problem is in gapps, use gapps for oreo 8.1, maybe there is posted in ur rom thread
Click to expand...
Click to collapse
I already tried, it did not work, I have installed last gapps 8.1, last twrp, last everything and it never works, it keeps stucking again and again.

same ****ty problem with my 3s 2gb .. doesnt matter which oreo 8.1 rom i flash.. tried almost 4 oreo 8.1 roms.. all couldnt boot.. and if by chance it boots then cant add google account..
yet to try that 'Mount' thing solution suggested by Williams

You ask in wrong place stupid!
Ask in Q&A section stupid!
This section jus for downloading rom and kernel stupid!

I face the same issue with a Redmi 3 S (global version) with 3 GB RAM. Nougat ROM's are fine but all Oreo ROM's which I tried (most recent builds of PixelExperience, crDroid, Atomic-OS) show these boot loops. This is all with the latest TWRP installed (also tried custom builds), cleaned properly my device and was using the linked Oreo GAPPS. I usually flash in one instance 1) ROM, 2) GAPPS and 3) Magisk.
The only time I had a working Oreo ROM was after several tries with PixelExperience where on my last try I booted into safe mode and it somehow worked after that.

AidANiem said:
You ask in wrong place stupid!
Ask in Q&A section stupid!
This section jus for downloading rom and kernel stupid!
Click to expand...
Click to collapse
go **** your mother, she likes it

william.johhn7! said:
First of all, this should be in the Q&A section. Secondly, I can help you. I'm sure that you downloaded the gapps from the cloudkenzo something, right? Yeah those gapps do not have any issues, instead they make an issue. After flashing your rom and then these gapps file, the system partition normally unmounts. But usually when you boot into the ROM, the partition should re-mount. These unofficial gapps causes some issues with that. A simple solution- Just mount system in twrp, now reboot to system and you should be fine. I faced the same issue and this is my solution.
Click to expand...
Click to collapse
Thanks, it worked for me:
1 - full wipe and format
2 - install rom
3 - install gapps
4 - mount system
5 - reboot system

I have tried many ROMs for my A2017U, but non of them works well

First, I unlocked bootloader and installed twrp with axon7toolkit.
Then I have tried following roms.
1. AospExtended-v5.4-axon7-20180421-0700:
no sound when calling, /data does not shown, crashes when voice call from wechat.
2. BootleggersROM-Oreo4axon7.2.1-Stable-Unshishufied-20180331:
no sound when calling, have not test other
3. dotOS-O-v2.1-axon7-UNOFFICIAL-20180404
(downloaded but not tested)
4. A2017(U)(N-B35)_AROMA_SL!M1_DF!NR_by_raystef66
always crashes before I can finish initial setup
5.lineage-14.1-20180425-nightly-axon7-signed
password needed to start android, but I do not know what is the pass word
6. A2017Uv1.1.0B35_StockSystem_by_DrakenFX
this is the only one which calling works, wechat voice call works.
Rooted with Magisk16.0.
Problems with original ROM still exist:
1. battery drain pretty fast,
2. show 31000 and roaming for verizon.
New problem after unlock bootloader,
bootloader unlocked warning when startup
new problem after root:
crashes when start es file explorer:
testing others

The last resurrection remix(official nougat) is solid and so is AOKP. I'm just wondering what kernel would be best for a nougat Lineage-based rom on B35

thanks for reply.
I will temporally stay with stock rom B35. The unlocked bootloader warning is removed now.
The only two issues with stock rom are battery drain, verizon signal label.
I may give resurrection remix a try later.
Amer532 said:
The last resurrection remix(official nougat) is solid and so is AOKP. I'm just wondering what kernel would be best for a nougat Lineage-based rom on B35
Click to expand...
Click to collapse

Are you installing the bootstack too? I have the same model and don't have any of those issues. I run encryption so I'm stuck on the 2/24 build of AOSP-eXtended, but the only bug I have is a slow initial GPS lock. Otherwise it runs solid.
Sounds like you didn't follow all the directions.

I am sure I followed instructions strictly.
I have also tried to flash each ROM start from specified Bootloader, Modem, Bootstack, then ROM in the post.
TPMJB said:
Are you installing the bootstack too? I have the same model and don't have any of those issues. I run encryption so I'm stuck on the 2/24 build of AOSP-eXtended, but the only bug I have is a slow initial GPS lock. Otherwise it runs solid.
Sounds like you didn't follow all the directions.
Click to expand...
Click to collapse

llaalways said:
thanks for reply.
I will temporally stay with stock rom B35. The unlocked bootloader warning is removed now.
The only two issues with stock rom are battery drain, verizon signal label.
I may give resurrection remix a try later.
Click to expand...
Click to collapse
i'm pretty sure you're doing things wrong:
-No sound on calls is fixed by toggling speakerphone on and off
-Password on boot is because your internal storage is encrypted, because you installed a ROM and forgot to flash Magisk or SuperSU before booting for the first time.
-Everything crashing on slim roms can be because you failed to wipe. Anyways simply wipe evetrything and try flashing it again, it'll probably be fixed.
-5 second screen is not a problem, it's a feature. There are ways to fix that anyways: Remove unlocked bootloader inscription by Raystef66 should work, and it is safe. And also there's NFound's zip on the Themes and Apps section, but it'a very risky (you might end up having to unbrick your phone).

I'm running LineageOS 15.1 Oreo based room currently and all seems well except there seems to be no working camera. Ive tried many and no seem to work or install correctly no matter how I flash. I tried to go back to stock 35 but got stuck at boot screen for an extremely long time so I was force to pick another Oreo room to go back to in order for me to get my phone to work. Do you guys know of a working camera I can install that you have personally tried with Oreo and links would be helpful. I tried a lot on xda so far to no avail. Thanks in advance. Or link me to what I need to get back to stock 35. Also, LineageOS 15.1 has ridiculous battery life. In a good way.

King Ice said:
I'm running LineageOS 15.1 Oreo based room currently and all seems well except there seems to be no working camera. Ive tried many and no seem to work or install correctly no matter how I flash. I tried to go back to stock 35 but got stuck at boot screen for an extremely long time so I was force to pick another Oreo room to go back to in order for me to get my phone to work. Do you guys know of a working camera I can install that you have personally tried with Oreo and links would be helpful. I tried a lot on xda so far to no avail. Thanks in advance. Or link me to what I need to get back to stock 35. Also, LineageOS 15.1 has ridiculous battery life. In a good way.
Click to expand...
Click to collapse
Footej? Gcam? ZTE stock cam? Have you also tried AEX? I'm curious as to how it performs.

Victor13f said:
Footej? Gcam? ZTE stock cam? Have you also tried AEX? I'm curious as to how it performs.
Click to expand...
Click to collapse
I tried GCam but the rear camera didn't work. It's weird but that was the consensus that a lot of people was having. I heard that the ZTE Stock 13 v2 camera works but I haven't been able to find a link to anyone that actually has it. Everyone that I've come across has had a link, but when you get there it's for b04, 05, o7 Oreo or something else. I've tried those also and it hasn't work on LineageOS. I might go back to Nougat 7.1.1 if I can find the proper way to do so.

OK, I have resolved the problem with Password on boot.
I have tried many times, every time after flashed twrp, then I boot into twrp recovery, then do following steps:
1. advance wipe cache/dalvik cache/data/system,
2. install bootloader, modem, warning_patch, rom,
3. advance wipe cache/dalvik cache/data
4. install Magisk
5. advance wipe cache/dalvik cache/data
6. install Gapps
7. advance wipe cache/dalvik cache/data
then reboot to system, and the password is always asked on boot.
I have found out that instead of "advance wipe cache/dalvik cache/data", do a "factory reset" in twrp recovery, then the problem solved.
So the step should be
1. advance wipe cache/dalvik cache/data/system,
2. install bootloader, modem, warning_patch, rom, Gapps
3. install Magisk ( wipe cache/dalvik cache/data if fail to install, then install again)
4. factory reset.
After factory reset, boot into system and works.
There is still no sound on call problem, but fixed by toggling speakerphone on and off as you suggested.
Thanks.
Choose an username... said:
i'm pretty sure you're doing things wrong:
-No sound on calls is fixed by toggling speakerphone on and off
-Password on boot is because your internal storage is encrypted, because you installed a ROM and forgot to flash Magisk or SuperSU before booting for the first time.
-Everything crashing on slim roms can be because you failed to wipe. Anyways simply wipe evetrything and try flashing it again, it'll probably be fixed.
-5 second screen is not a problem, it's a feature. There are ways to fix that anyways: Remove unlocked bootloader inscription by Raystef66 should work, and it is safe. And also there's NFound's zip on the Themes and Apps section, but it'a very risky (you might end up having to unbrick your phone).
Click to expand...
Click to collapse

I can confirm that WEEKLY Resurrection Remix Oreo ROM works perfectly. No bugs for me, not event the call one. Give that a try!

baconboy said:
I can confirm that WEEKLY Resurrection Remix Oreo ROM works perfectly. No bugs for me, not event the call one. Give that a try!
Click to expand...
Click to collapse
Download link?

Sure. I will try it later.
Just need stay with lineage 14.1 for couple of days to test it.
baconboy said:
I can confirm that WEEKLY Resurrection Remix Oreo ROM works perfectly. No bugs for me, not event the call one. Give that a try!
Click to expand...
Click to collapse

NFound has both RR-O-v6.0.0-20yymmdd-axon7-Weekly.zip, and RR-O-v6.0.0-20yymmdd-axon7-ENCRYPT-VERSION.zip on his androidfilehost page.
https://androidfilehost.com/?w=profile&uid=817550096634750733
Kranoner has RR-O-v6.0.0-20yymmdd-axon7-Unofficial.zip on his androidfilehost page.
https://androidfilehost.com/?w=profile&uid=457084094631641923
Victor13f said:
Download link?
Click to expand...
Click to collapse

llaalways said:
OK, I have resolved the problem with Password on boot.
I have tried many times, every time after flashed twrp, then I boot into twrp recovery, then do following steps:
1. advance wipe cache/dalvik cache/data/system,
2. install bootloader, modem, warning_patch, rom,
3. advance wipe cache/dalvik cache/data
4. install Magisk
5. advance wipe cache/dalvik cache/data
6. install Gapps
7. advance wipe cache/dalvik cache/data
then reboot to system, and the password is always asked on boot.
I have found out that instead of "advance wipe cache/dalvik cache/data", do a "factory reset" in twrp recovery, then the problem solved.
So the step should be
1. advance wipe cache/dalvik cache/data/system,
2. install bootloader, modem, warning_patch, rom, Gapps
3. install Magisk ( wipe cache/dalvik cache/data if fail to install, then install again)
4. factory reset.
After factory reset, boot into system and works.
There is still no sound on call problem, but fixed by toggling speakerphone on and off as you suggested.
Thanks.
Click to expand...
Click to collapse
That's still wrong. It works but it's unnecessary. You have to use the FORMAT DATA button instead of just advanced wipe data

llaalways said:
NFound has both RR-O-v6.0.0-20yymmdd-axon7-Weekly.zip, and RR-O-v6.0.0-20yymmdd-axon7-ENCRYPT-VERSION.zip on his androidfilehost page.
https://androidfilehost.com/?w=profile&uid=817550096634750733
Kranoner has RR-O-v6.0.0-20yymmdd-axon7-Unofficial.zip on his androidfilehost page.
https://androidfilehost.com/?w=profile&uid=457084094631641923
Click to expand...
Click to collapse
Cheers! Which one do you recommend? Kranoner or NFounds build?

I have not tested them yet.
Victor13f said:
Cheers! Which one do you recommend? Kranoner or NFounds build?
Click to expand...
Click to collapse

All Oreo 8.1 ROM have problem with dual SIM.
I have tried Lineage, RR, AEX, BootLeggers, dotOS.
llaalways said:
I have not tested them yet.
Click to expand...
Click to collapse

Im using AEX 8.1 with hell Kernel and it performs awesome. No buggs so far, only dual sim not working but its a know Problem.

llaalways said:
All Oreo 8.1 ROM have problem with dual SIM.
I have tried Lineage, RR, AEX, BootLeggers, dotOS.
Click to expand...
Click to collapse
Well maybe LOS 15 won't since they got the oreo files from ZTE. Which rom felt the smoothest to you from all the ones you tried?