Database Users

Help needed, bootloop. spyware?

Hi guys I have a problem, I am using miui7 developer ROM and my phone has been compromised twice, I have had my bank account hacked(long story but calls where diverted and bank log in details changed) and 4 days ago someone tried to log on to my banking app remotely 5 times and so it was locked down, bank has confirmed it was my phone and my WiFi provider that was used and I know it wasn't me, so I have tried to flash 2 ROMs using all the correct methods and it always results in the same, a boot loop, I am wondering if partitions have been messed with, or if there is something hidden on the file system causing this, what I would like to do is wipe everything, I don't mean just system data cache etc I have tried all that unsuccessfully, I mean fully wipe and reset all the partitions memory emc chip and totally start fresh, can anyone help please, I really need to sort it out I know my phone is compromised because of things that have happened. Any solutions please. Anyone experienced malware in miui7 ROMs? Your help is really appreciated.
Rich

Phone? BL locked/unlocked? Root?

krcovsky said:
Phone? BL locked/unlocked? Root?
Click to expand...
Click to collapse
Redmi note 4g single sim doir, bootloader not sure never unlocked so presume locked, rooted and unrooted tried both methods, flashed plenty of ROMs in the past without trouble.

Sorry but i cant really help since i do not own the device. It would probably be best to try to find a solution on miui forum, directly ask a member of a Dior device team. And don't know if you flashed through recovery or fastboot mode - try both mehtods, also developer/stable rom. I think flashing through fastboot also acts as a full factory reset. There must be a tutorial for unbricking or resolving bootloops. Also try some custom cm/aosp based roms to see if the phone will boot. And since miui is chinese, you can presume that there is some data leaking, but i don't think that it contains malware - it would be too much even for xiaomi (unless you "picked up" some shady script/trojan/whatever along the way).

Zenfone 5 LTE (T00P) Erroneous Behaviour

Hey guys,
Long time user of XDA here, but first time poster in this forum. I would like to request help for my mother's Asus Zenfone 5 LTE (model number T00P), which has recently began to function in a way to makes it unsuitable as a daily driver. The phone is slightly over 2 years old, running stock 4.4.2, build number KOT49H.WW_Phone-11.4.6.94-20141218044000274_201406050026. I am unsure about the circumstances in which the following behaviour started.
Half the time when it boots, it immediately shows a lot of core apps FC-ing, like com.android.phone and com.android.systemui, along with another one buried, which is the KeyGuardTestActivity FC. Other times, it boots normally, but some apps do not work properly: the Phone app fails to launch as Contacts FC, Settings FC when trying to access the All tab under Applications, the file manager FC. With SIM card inserted, mobile connectivity is also a hit and miss. Holding the power button causes the phone to do a soft reboot, rather than bring up the power menu. I cannot gain ADB authorisation as SystemUI also FCs when trying to come up with the RSA authorisation message. Much of these issues render the phone pretty much unusable.
Up till this point, the phone has remained unrooted and untouched, XDA-wise, and can boot in recovery and CSC modes. However, there was a system update that was found in the stock updater, but could not be installed due to Status 7 (framework-res.apk has unexpected contents). After that failed update, there was no change to the phone, and the updater no longer works.
I have since rooted the phone with Kingroot, but freezing the keyguard produces more issues. I am at a loss at this juncture, as I am trying my best to save the phone short of a data wipe. I am very sure a data wipe would solve the issues, but many backup apps simply FC, as I would also like to backup data to shift to a new phone.
Are there any ways to help? Thanks in advance for any answers.

Never heard an XDA member let their devices remaining​ stock after 2 years. The best choice for you is flash another rom, Stable android 5.1 to 7.1
No need to root to unlock bootloader and flash TWRP. More details you can research around here.
If you don't want loss data, use adb command to copy it to your lap or pc. Or here: http://www.droidviews.com/push-pull-files-android-using-adb-commands/

Redaki said:
Never heard an XDA member let their devices remaining​ stock after 2 years. The best choice for you is flash another rom, Stable android 5.1 to 7.1
No need to root to unlock bootloader and flash TWRP. More details you can research around here.
If you don't want loss data, use adb command to copy it to your lap or pc. Or here: http://www.droidviews.com/push-pull-files-android-using-adb-commands/
Click to expand...
Click to collapse
I don't think there are custom rom available for zenfone 5 LTE model .So that gives no choice but to stay on stock rom.
---------- Post added at 07:12 AM ---------- Previous post was at 07:10 AM ----------
NightRaven49 said:
Hey guys,
Long time user of XDA here, but first time poster in this forum. I would like to request help for my mother's Asus Zenfone 5 LTE (model number T00P), which has recently began to function in a way to makes it unsuitable as a daily driver. The phone is slightly over 2 years old, running stock 4.4.2, build number KOT49H.WW_Phone-11.4.6.94-20141218044000274_201406050026. I am unsure about the circumstances in which the following behaviour started.
Half the time when it boots, it immediately shows a lot of core apps FC-ing, like com.android.phone and com.android.systemui, along with another one buried, which is the KeyGuardTestActivity FC. Other times, it boots normally, but some apps do not work properly: the Phone app fails to launch as Contacts FC, Settings FC when trying to access the All tab under Applications, the file manager FC. With SIM card inserted, mobile connectivity is also a hit and miss. Holding the power button causes the phone to do a soft reboot, rather than bring up the power menu. I cannot gain ADB authorisation as SystemUI also FCs when trying to come up with the RSA authorisation message. Much of these issues render the phone pretty much unusable.
Up till this point, the phone has remained unrooted and untouched, XDA-wise, and can boot in recovery and CSC modes. However, there was a system update that was found in the stock updater, but could not be installed due to Status 7 (framework-res.apk has unexpected contents). After that failed update, there was no change to the phone, and the updater no longer works.
I have since rooted the phone with Kingroot, but freezing the keyguard produces more issues. I am at a loss at this juncture, as I am trying my best to save the phone short of a data wipe. I am very sure a data wipe would solve the issues, but many backup apps simply FC, as I would also like to backup data to shift to a new phone.
Are there any ways to help? Thanks in advance for any answers.
Click to expand...
Click to collapse
Well i don't have LTE model ... But i would suggest you to upgrade to latest android version provided by Asus for your model and see if the problem persisit ....

Redaki said:
If you don't want loss data, use adb command to copy it to your lap or pc. Or here: http://www.droidviews.com/push-pull-files-android-using-adb-commands/
Click to expand...
Click to collapse
Like I said in the OP, I cannot authenticate ADB as SystemUI crashes upon generating the notification for verification.
Boomshiva said:
Well i don't have LTE model ... But i would suggest you to upgrade to latest android version provided by Asus for your model and see if the problem persisit ....
Click to expand...
Click to collapse
Again, in the OP, I've mentioned the Updater does not work.
Are there any other solutions?

Redaki said:
Never heard an XDA member let their devices remaining​ stock after 2 years. The best choice for you is flash another rom, Stable android 5.1 to 7.1
No need to root to unlock bootloader and flash TWRP. More details you can research around here.
If you don't want loss data, use adb command to copy it to your lap or pc. Or here: http://www.droidviews.com/push-pull-files-android-using-adb-commands/
Click to expand...
Click to collapse
Yes, but there is no custom rom for zenfone 5 lte. maybe neither custom recovery or root.

Sorry i didn't read your post carefully. Did you try to unlock bootloader ? I think it will be the same as the Intel model. Try fastboot and then fastboot OEM unlock, or flash some ifwi file like Intel model.
Then if bootloader is unlocked, flash TWRP and u will have ADB.

[XIAOMI REDMI NOTE 3 PRO] Guide to Unlocking,common MiFlash and MIUnlock solutions.

Hello folks, this is my first ever post on XDA forums and I want to share how i bricked my Kenzo and the errors that i came across before unofficially unlocking my device. And also the solutions .
So firstly, some info
1. Kenzo doesnt have a recovery from the start.
2. As I read, Kenzo requires you to be on developer version of rom for unlocking bootloader the official way.
3. Xiaomi Servers are really bad, so say you want to unlock your device and you got your permission granted then its not clear when xiaomi will update that into their servers. I kept getting the 86012 error which as per forums is due to Xiaomi not updating the device info in their servers.
4. The unofficial way is much faster and imo better as it doesnt require you to wait like 10 days or so to get your permission granted with the only demerit that it would go away the moment you install a new MIUI rom. But you can reunlock it using the same method so no worries.
Oh and btw, do the disable driver signature enforcement for your windows before doing anything . https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Also, make sure your battery is >80% . Ik its quite common to do this but in my case my battery was 50% and after flashing multiple times it was 0% and i got the red led so i thought i was booting into edl mode but after putting it to charge i realized that it was the low battery indication .
Now , guides and fixes.
1. So to unlock the device officially you need to headover to the site mentioned in your miui, and to get to that firstly enable developer options then go to developer options>mi unlock state and in the bottom is the link and follow the steps. I suggest waiting 24 hrs after getting the permission granted (which usually takes 5 mins) and then trying to add acc using the button in mi unlock state.
2. If you get the 86012 error, you are in the same boat as most of the people so the only way to officially unlock the device now is to wait 2-30 days.
3. If you get the couldnt connect to network error, download the developer version of your rom and follow instructions to install it. And then try.
4. Now, if you got your permission granted and the add acc thing worked then Congrats . Now if you download the Miunlock app and get the "Account doesnt exist" or "Network Error" error then switch the internet connection, in my case ,if i used vodafone mobile data hotspot then i got the error but with airtel no error. And after getting this Miunlock completed successfully your bootloader is unlocked.
5. Now the unofficial way, simple thing . Follow this https://forum.xda-developers.com/redmi-note-3/how-to/guide-rn3-pro-se-t3565172 .
6. There are 2 types of edl mode on kenzo, first is when you get 900E in device manager, second is when you get 9008 in device manager on your pc. For any flash to work, you need to get 9008 .
7. Now most likely you might run into "Object instance " error or something like that or even "max buffer size 250k" using Miflash app to install a fastboot rom on kenzo. The fix is to firstly install the 2014 version of miflash app and then after running it on your pc and finding your device using it install latest version and run that. The preferred location to install the app is in C:\ instead of C:\Program Files. Also I used the 2016 version downloaded from a website rather than the latest official one .
8. Your device may get bricked and might only boot to edl mode and the 900E mode at that. To get into 9008 mode, either use edl cable or do the test point method .
9. For custom roms you dont need a modified boot.img which I was unable to retrieve for myself anyway. You can create them too.
Thats all i can gather for now, I will add more issues if i discover more and I hope that I get help from the mods and admins on the forums regarding putting reserved messages and all so that everyone who has a fix and reports here can benefit everyone else
I didnt include much links cause there are quite a few of these guides and I only wanted this to be a support thread and not a full guide .

[GUIDE] FIX for sensors and camera lag (Accelerometer, Gyroscope, Proximity, Light)

Ok, so a couple months ago, my phone sensors died and after a long time of procrastinating, I decided to try to fix it, I've managed to do it and I'm sharing the fix with you guys, as I didn't found any fix online.
So first, why this happens?
It's because of the phone's persist, that can be corrupted, this can happen if you flash roms, or even with updates, like it was in my case.
How to fix it?
Ok, so first you will need a few things.
Adb and Fastboot
persist.img file (and a couple more files for the flash to work, but I will place a link here)
Xiaomi Miflash (this version will install the drivers, but if don't, uninstall and boot Windows with Driver Signature Enforcement disabled and install it again)
Download All here - it's already modded to flash persist only. It will not wipe your data.
After installing Xiaomi Miflash, you will need to boot the phone in edl mode. You can do this even with you bootloader locked and it will work. To do this, first boot in Fastboot mode (Vol down + Power), plug the USB cable on phone and computer, then open cmd on the folder of fastboot and use the command:
fastboot oem edl
After that, your phone's screen will turn off and the led will keep blinking red.
Now, open Xiaomi Miflash.
Click on Select
Select the folder that you downloaded earlier.
Click refresh, your phone should appear on the list, if don't, reinstall drivers.
Now click flash.
The flashing is quick, and now your phone is fixed.
Any doubts, free feel to ask!
Tested on Redmi Note 4 Global Snapdragon Version
Known errors:
cannot receive hello packet,MiFlash is trying to reset status! - You will need to reflash stock ROM.

thanks a ton
you made my day

ayazuddinkhan said:
thanks a ton
you made my day
Click to expand...
Click to collapse
You're welcome. please let me know if it works for you.

worked, everything is fixed

Hello sir im facing same problem on Redmi 4x 32gb and can u use this fix file on my Redmi 4x thank you

Thank you so much buddy.
it fixed my problem.
Great guide ?.

How can I port it to the Mi A1, actually the phone doesn't even boot if there's something wrong with the persist.img. Really need your help.

Can i use for mtk version?
My phone camera laggy, video play laggy, and acceloremeter not working... @FalconMaster

Please help me! I did the flash, it worked correctly! but now you're saying that you have your account and my device is locked! 170 ****** mi account number. there it is reporting that it is linked to your account. please contact me at PM, and help me.

This method is not working for redmi 4x
Please give me persist.img file for redmi 4x for locked device. I tried your given method but it's not working in my device it show file and device does not match
..
sorry for my bad English

Different phones
For everyone with different phones, you need to get to Mi website, download the fastboot ROM for your phone and flash the persist only. This can be done by removing all lines from the xml file, except the one that flashes the persist. After that, flash it normally as in this guide.

Redmi note 5a prime
Hi, is this working on note 5a prime?, When I bought it the only problem is when I use camera, causing some lag, need to open and close again. Also when video recording.

Hello. For the first time I write on this forum and I want first of all to thank all of you for sharing your work and knowledge.
I would like to know if I can follow this procedure having already installed the pixel experience rom and the mido 8.2.1 firmware.
Thanks in advance and forgive my bad english.

Aaa
Please help me. I cant boot into edl wih Mi Note 3.

Aa
I cant boot into EDL. So, can i flash it with fastboot. Please help me. Im using mi note 3

Man, I don't really know how that worked for you. Your script erases persist and flashes rpm.mbn to persist, that file isn't even present images folder.

then open cmd on the folder of fastboot...... which folder do u mean ?
i used "C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\fastboot.exe" it detects the device but the phone's screen doesn't turn off and the led isn't blinking red, it stay at the LOGO FASTBOOT ....
i tried to flash it with XiaoMiFlash.. it detects the phone but it errors out...
i have Redmi Note 4 Global Snapdragon Version

Does this method work on custom roms?
Im on Los 15.1 and my gps doesnt work. Will this fix it?

fixed my problem on redmi note 4x
Thank you so much FalconMaster.
it fixed my problem on redmi note 4x (mido).
Thank Thank you very much.
Great guide :good:

So I read everything. Will this method work for my MI 9 global version ? After unlocking the bootloader, I flashed de Android Q beta from the official web page, using MiFlash(I think that's the correct name). So I didn't like the Beta one and downloaded the global stable version, flashed with MiFlash. Everything was perfect, but my Accelerometer and Gyroscope won't work. What do you suggest? Thanks a lot!

Comprehensive guide and resources for migrating to a custom ROM from stock OREO?

Okay, so I've been trying to get some answers regarding custom ROMs for the past few days but I haven't even got one...and it seems I'm not the only one looking for them. So...lay it in this thread maybe we can start something up.
I am on stock OREO B04, phone's software has never been tampered with anything, TWRP, BL unlock and so on.
This is the premise of the thread, not only for me but for other users who find themselves in the same situation.
Oreo seems to be a bit of a hassle right now for migrating to custom ROMs, and this is not helped by the fact guides in the A7 section are all over the place as well, some may be outdated and there's no clear "Don't use this on x.x version" warning.
I am not even going to attempt to unlock the BL until I clear answer on wether it's possible or not. So let's start with this:
-Is it possible to unlock the BL on OREO?
-If not, what stock official ROM should we install in order to successfuly attempt to unlock the bl?
-Which guide or method is the best for doing so? I've found 2, one from 2016 on MM ROMs and one provided by TurkDevs that seems to work on some Nougat ROMs.
Then comes the recovery section:
-What TWRP should we install on a freshly unlocked device, the official releases, or the Nfound custom ones?
-Also, what are the prerequisites for installing TWRP...I hear that fastboot commands are gone since Nougat and that some flashing methods don't work, then I hear somehow you can do it by bringing back fastboot. How? There's only replies saying "type that command in fastboot" but nobody says if they had it or reinstalled it somehow.
Then comes the ROMs section:
-All custom ROMs seem to require a vendor partition as most if not all of them are Treble based. How do we get that to work?
- I am aware of the fact that the ROM threads have a prerequisites section, but none of them redirect you to a guide on how to get those prerequisites working. I understand that it's not the dev's responsability, I am not bashing anyone here, but a little bit of info cleaning and structuring should be in order in this section.
What I want for me and others in my situation is a clear answer on how to proceed, not a "flash this flash that". There's no secret that the A7 still has life in it especially with the new PIE ROMs.
I've recently seen a reply in one of the threads, encouraging the dev of one of this ROMs to not be disappointed by the seemingly low interest in PIE ROMs. I don't think there's a low interest in them, I think there are users that don't want to risk a bricked phone because of outdated guides and unlcear steps.
There's a lot of confusion going around here so I hope this thread will become a source of updated info on what's possible and what not. Thanks in advance!

Hi, I'm not the best person to help you with this since i've unlocked my Axon 7 a long time ago and I can't remember everything but I will try to help you based on my experience and on what I can remember.
Let's go
Starting with the bootloader, I unlocked mine on stock Nougat B09 using EDL Tool (Oreo wasn't even out when I unlocked my bootloader so I don't know if you can do it while running Oreo but just to be safe you should downgrade to Nougat)
It should be quite easy to unlock the bootloader, here's a simple step by step (please anyone correct me if I'm wrong)
- Download the EDL tool from the link above
- Downgrade your phone to Nougat (Using the updater on the phone itself or an EDL Package with EDL Tool or MiFlash - you can find the stock ROMs on @raystef66 's Download Center
- Once running Stock Nougat, turn on USB Debugging and Allow OEM Unlocking on Developer Settings
- Plug the phone to your computer and open EDL Tool (that should reboot the phone into EDL mode automatically)
- Navigate through the EDL Tool using the number keys on the keyboard, and it should be easy to find the Unlock Bootloader option. Unlock it and you should be done.
Once again that's the way I did it, I don't know if this is the easiest one available. You have more methods available like this one
Now onto the recovery situation, I think each developer recommends a specific TWRP version for their ROM's, like for example
@raystef66 likes NFound's TWRP 3.2.1-8 as you can see on his ROM's posts (check the first line in the installation guide)
@OrdenKrieger likes the official TWRP as you can see on Lineage OS 16.0 post
Generally, official TWRP should work just fine with any ROM.
On a recently unlocked Nougat Stock ROM, I recommend maybe an older version of TWRP, like 3.2.1 for example and you can flash it also using EDL Tool.
But when moving to Pie I recommend you use the latest TWRP version or the version that the ROM developer recommends. You probably know this but you can update your TWRP version by flashing it over the current version you have.
Now about the ROM's, the new ones have a Vendor partition so you have to create it when you're coming from Stock (because our Axon 7 doesn't support Project Treble) and to do that you can use @Oki 's PARTY Tool and after that you can flash the ROM normally, using the proper Bootstack and Modem files.
You could also try GSI's but I can't help you with that because I never tried them.
And this should be all.
I tried to keep it simple for now but i can help you further
I'm not the best person to guide you but at least I tried Feel free to ask me something and good luck!

@joaocandeias Well, dang it worked. Everything you described:
-going back to Nougat
-unlocking the bootloader with the EDL tool
-flashing TWRP-
creating the Vendor partition, and installing the new ROMs.
There were a few hiccups on the road, mostly driver related from my previous attempt, but nothing severe or something that would cause the device to brick.
I just installed @raystef66 's ResRemix ROM and it works fine. I'll start testing more of them in daily use and see which suits my needs best.
Thanks for the assistance!

TorqueSsS said:
@joaocandeias Well, dang it worked. Everything you described:
-going back to Nougat
-unlocking the bootloader with the EDL tool
-flashing TWRP-
creating the Vendor partition, and installing the new ROMs.
There were a few hiccups on the road, mostly driver related from my previous attempt, but nothing severe or something that would cause the device to brick.
I just installed @raystef66 's ResRemix ROM and it works fine. I'll start testing more of them in daily use and see which suits my needs best.
Thanks for the assistance!
Click to expand...
Click to collapse
I'm glad I could help
Since you're not the only person with questions on how to migrate from stock to custom, I'm thinking about writing a full post so more people can see it.
Btw what method did you use to downgrade to nougat?

@joaocandeias Sorry for the delayed response, I've got a really f'd up sleeping schedule these days. I'll write the exact steps I've done.
1. So, I first downloaded the B09 Nougat full stock ROM from the download center and tried to downgrade using the normal software updater in the phone (OTA window, local option).
It didn't work at first, I received a compatibility error, saying that the update is for "ailsa_ii" devices, while the device is not(or to be more exact, my device was " " ), which I found odd.
But, I thought that maybe I need the linked versions(like the last Nougat ROM before Oreo) so I downloaded the B10 Nougat ROM, and used the same procedure.
2. I set up the phone as a dud(skip everything, no Google account), turned USB debugging and OEM unlocking on, installed the original ZTE drivers straight from the phone and rebooted it into EDL to proceed with unlocking the BL.
At this point, I had the QUSB_BULK driver stick from my previous use of Zadig, so one quick "uninstall device software" and relpuging the phone go me the Qualcom 9008 driver in order.
3. I started the EDL tool, navigated through it and started the BL unlock procedure.
Once the phone rebooted I was greeted by the password screen.
One factory reset later and repeating the procedure greeted me with the "Bootloader unlocked" message. Sucess!
4.Now for TWRP, Vendor and ROM, got all the files onto the SD card, I flashedTWRP 3.2.1-8 NFound, then, from TWRP, I used the party tool, then flashed the UBv2(at which point it reverted TWRP to 3.2.3, flashed the 3.2.1-8 again with EDL ), modem, ROM, GApps, rebooted, set it up, then flashed Magisk...and everything seems fine.
The only issue I have now seems to be the camera, both stock app and GCam.
Open camera works , has the correct photo and video res, 60FPS doesn't work and the flash seems a bit laggy, but for me it's ok.
The DAC however is there, alive and kicking, Neutron detected the Hi-Res codec at launch and switched to it. It sounds the same as stock OREO to me so it is great, as this was my greatest fear when migrating to PIE. The DAC-AMP combo is like 60% of the reason I bought this phone in the first place.

TorqueSsS said:
@joaocandeias Sorry for the delayed response, I've got a really f'd up sleeping schedule these days. I'll write the exact steps I've done.
1. So, I first downloaded the B09 Nougat full stock ROM from the download center and tried to downgrade using the normal software updater in the phone (OTA window, local option).
It didn't work at first, I received a compatibility error, saying that the update is for "ailsa_ii" devices, while the device is not(or to be more exact, my device was " " ), which I found odd.
But, I thought that maybe I need the linked versions(like the last Nougat ROM before Oreo) so I downloaded the B10 Nougat ROM, and used the same procedure.
2. I set up the phone as a dud(skip everything, no Google account), turned USB debugging and OEM unlocking on, installed the original ZTE drivers straight from the phone and rebooted it into EDL to proceed with unlocking the BL.
At this point, I had the QUSB_BULK driver stick from my previous use of Zadig, so one quick "uninstall device software" and relpuging the phone go me the Qualcom 9008 driver in order.
3. I started the EDL tool, navigated through it and started the BL unlock procedure.
Once the phone rebooted I was greeted by the password screen.
One factory reset later and repeating the procedure greeted me with the "Bootloader unlocked" message. Sucess!
4.Now for TWRP, Vendor and ROM, got all the files onto the SD card, I flashedTWRP 3.2.1-8 NFound, then, from TWRP, I used the party tool, then flashed the UBv2(at which point it reverted TWRP to 3.2.3, flashed the 3.2.1-8 again with EDL ), modem, ROM, GApps, rebooted, set it up, then flashed Magisk...and everything seems fine.
The only issue I have now seems to be the camera, both stock app and GCam.
Open camera works , has the correct photo and video res, 60FPS doesn't work and the flash seems a bit laggy, but for me it's ok.
The DAC however is there, alive and kicking, Neutron detected the Hi-Res codec at launch and switched to it. It sounds the same as stock OREO to me so it is great, as this was my greatest fear when migrating to PIE. The DAC-AMP combo is like 60% of the reason I bought this phone in the first place.
Click to expand...
Click to collapse
Thanks! That will help me a lot to write a full guide. You'll be credited, don't worry
And yeah, when you migrate to custom roms you'll have to sacrifice camera quality and functionality and also a bit of speakers sound quality (all dolby atmos ports I tried are quite buggy and don't work well ; i only use atmos with the speakers). Headphones sound quality is great though.
If you don't use camera that much (not my case) and you're okay with the speakers sound quality then custom roms are probably the best option out there.

@joaocandeias
I was fully aware of the camera issues I might encounter, this has been the case with my old Mediatek devices when going to custom as well, same camera issues, but at least...it works here. Yeah, I lost some functionality, but to me it's a good trade-off. It can still take snaps and film properly so it's enough for me.
I am kind of going to miss Dolby on speakers (never liked it on headphones though), as it did a really good job for podcast style videos on YT, but it still sounds way better than a lot of phones without it so it's fine. I just need to crank the volume up a little more than usual.

I've heard that treble Pie Roms require a oreo bootloader, is this true? I am still confused how to install on my A2017G. In which order would I install bootloader and vendor partition?