What's working:
Wi-Fi
Bluetooth
Mobile Network (Calling, Data, etc.)
Signal Strength
GPS
NFC
Audio (Stereo Speakers)
Camera
Fingerprint Sensor
HDMI
MTP
Call Recording
HWC
Encryption
SELinux Enforcing
OTA Updates
Bugs:
?
Notes:
If you are not on Q BL it will not boot.
I would suggest 3.2.3 TWRP or the included lineage recovery
For encryption to work make sure you are on 3.2.3 twrp and haven't formatted /data with any newer versions, issue described here.
Use a stock unmodified vendor and update whenever available, we are using our own fstab now for optional encryption and adoptable storage support so we don't need to touch the vendor.
If you go back to an official build after this with stock vendor, you will be force encrypted on first boot.
These builds are based on the official lineage device trees and kernel, but with more flexibility and my preferred configuration.
Lineage Recovery will be uploaded with each build and if you will only be running this rom i suggest to switch to it.
Instructions:
Make sure TWRP has been installed and is functional
Download the latest build and latest stock vendor.img that is available (optionally gapps and magisk if needed)
Reboot to recovery
Wipe data and cache (required if you switch from other ROMs)
Flash the vendor image
Flash the latest build (then gapps and magisk if needed)
Reboot
How to update builds?
OTA or manually like below
Do not wipe anything unless stated in the changelog
Flash only the rom.zip and it will automatically reinstall your gapps, magisk etc
use /system/addon.d if you would like to keep system mods after an update
Downloads:
Lineage-17.1: (mega) https://mega.nz/#F!0McClQKJ!ic8c0LEYF3zGSo_Ivv1nSw
Lineage-17.1: (github) https://github.com/synt4x93/OTA/releases
Google Apps: https://opengapps.org/
Telegram Channel:
@godlike9810
Paypal:
synt4x.93
XDA:DevDB Information
LineageOS 17.1, ROM for the Samsung Galaxy S9/+
Contributors
Synt4x.93, Erfanoabdi
Source Code: https://github.com/synt4x93/
ROM OS Version: Android 10
ROM Kernel: Linux 4.9.226
ROM Firmware Required: Q BL / Q Vendor
Version Information
Status: Stable
Created: 01-04-2020
Last Updated: 05-06-2020
temp
Great ROM really smooth but only one issue i have is when i try to record the screen with internal sound (gaming) it will mute the sound from the speaker and it's working fine Evox (sorry for my bad English
Hello everyone! Not sure how many people here already been trying this ROM from the Telegram group, but was wondering if anyone has the following issue. Google Chrome seems to become really laggy in the evening hours on my phone, but is fine during the day. Basically scrolling and animations within Chrome are really slow causing bad performance. Wanted to confirm if it's just me as Rob said the issue doesn't seem to happen with the Note 9 and see if anyone here has any suggestions? I am running DTB4 BL and vendor with TWRP 3.2.3.0.
so everything good other than Android Auto? Well done!
Great news! Thanks a lot for keeping our device alive and updated!
Can't wait to try this one out. I assume it's working fine as a daily driver?
geronimoge said:
Great news! Thanks a lot for keeping our device alive and updated!
Can't wait to try this one out. I assume it's working fine as a daily driver?
Click to expand...
Click to collapse
Yup, been using it for several weeks. No odd reboots and stuff, just very stable.
How can I check for the right BL?
What does it mean "Q BL"?
Thanks
EDIT:
Never mind, I found it! :good:
..ok, stupid question, but where can I get q bl?
Do I need to use odin to flash just bl from one of q roms or is there just q bl to download somewhere?
Great rom, thanks for this, I came from the LOS 16 and LOS 17.1 of the 09/01 and all good until now
Here is a link for download q bootloader
https://mega.nz/#F!oFJ1nK5Z!eWD2AU4CQxWSdA_kxxRkHA
vendor images and bootloader zip are taken from devbase rom by alexndr so big thank for his work
current vendor version
S9/S9+ : DTB5
N9 : DTB6
Hoooly ****, I tried to make dirty flash from LOS 16(with replacing bl and vendor, of course), with just cache and dalvik cache wipe, and everything just WORKS fine.
This is AMAZING!
So:
1. twrp - wipe dalvik and cache,
2. twrp - flash bl,
3. twrp - flash vendor, but vendor from OP(!),
4. twrp - flash ROM,
5. twrp - flash opengapps.
Damn, it saved me reinstalling 132 apps, and setting all accounts all over.
What's great - all settings are kept from previous OS.
Of course, I lost viperfx and all magisk-related plugs(list of plugins is still there, so all I needed to do was reinstalling plugins ), but, still, this is great.
Great, glad all went good for you
Thanks for working instructions and links!
Thanks a lot! :victory:
I guess it's to much to ask for those information from a developer...
Side note: there is a boot loader for DTB5 only, but the modified vendor for LOS is DTB4. It works, though.
I did update from the 09/01/2020, so far found two issues:
1. After installing White Wolfs Kernel, UI seems to crash after unlocking via pattern, returning me back to unlock pattern. Had to wipe and re-install (dirty install of LOS didn't solve the issue ).
2. AFWall doesn't work. Applying rules fails leaving the system without internet access.
First one is not that important, but I'd like a firewall on my device...
Anyway: Thanks for the work on the LOS.
HackAR
DeCo59 said:
Here is a link for download q bootloader
https://mega.nz/#F!oFJ1nK5Z!eWD2AU4CQxWSdA_kxxRkHA
vendor images and bootloader zip are taken from devbase rom by alexndr so big thank for his work
current vendor version
S9/S9+ : DTB5
N9 : DTB6
Click to expand...
Click to collapse
xo.en said:
1. twrp - wipe dalvik and cache,
2. twrp - flash bl,
3. twrp - flash vendor, but vendor from OP(!),
4. twrp - flash ROM,
5. twrp - flash opengapps.
Click to expand...
Click to collapse
Great work! ROM works great, even Google pay is working good!
I just installed your ROM. It is very nice that the keyboard is now bigger then the one of theolder version and my new bluetooth headset is finally working.
Unfortunately, I cannot get ctsProfile to pass.
Does anyone have ctsProfile passing?
Edit: nevermind, should have read the docs of MagiskHide Props, the last module did the config automatically...
All the best,
Daniel
Hack_AR said:
After installing White Wolfs Kernel, UI seems to crash after unlocking via pattern, returning me back to unlock pattern. Had to wipe and re-install (dirty install of LOS didn't solve the issue ).
Click to expand...
Click to collapse
Same here, can’t unlock after installing White Wolf kernel. Furthermore, the phone is in Emergency calls only mode, as if there is no SIM card.
How to “undo” or otherwise solve this?
Hack_AR said:
2. AFWall doesn't work. Applying rules fails leaving the system without internet access.
First one is not that important, but I'd like a firewall on my device...
Anyway: Thanks for the work on the LOS.
Click to expand...
Click to collapse
I have the same problem. I'm still on LOS 16 as a daily driver because of this (and because of its awesome battery live). I will keep testing though...
Also my thanks for the great work on LOS!
oldipp said:
Same here, can’t unlock after installing White Wolf kernel. Furthermore, the phone is in Emergency calls only mode, as if there is no SIM card.
How to “undo” or otherwise solve this?
Click to expand...
Click to collapse
I had the problem that the first boot after upgrade went without problems (or PIN prompt in my case) but after that, when entering the correct PIN, the screen got black and then locked again. If I entered the wrong PIN, the phone told me so.
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Good luck,
Daniel
Speedmatze said:
I'm still on LOS 16 as a daily driver because of this
Click to expand...
Click to collapse
I didn't have the problem with the old 09/01/2020 version, so you ca try it, or wait for the fix
---------- Post added at 12:35 PM ---------- Previous post was at 12:21 PM ----------
Weirdly enough, my system doesn't have this file. BUT, another try of White Wolfs kernel just worked. It seems this is an obsolete file, that some times is left behind confused and causes problems in the kernel.
Hofedan said:
I had the problem that the first boot after upgrade went without problems (or PIN prompt in my case) but after that, when entering the correct PIN, the screen got black and then locked again. If I entered the wrong PIN, the phone told me so.
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Good luck,
Daniel
Click to expand...
Click to collapse
Hofedan said:
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Click to expand...
Click to collapse
It was too late for me to remove that file, because I had encrypted /data, was no longer able to access it from within LOS, and I don’t know if TWRP can decrypt /data. If it happens to you, I would suggest to seize the opportunity while LOS still unlocks on the first boot to delete that locksettings file. In any case, having a backup is a must, because I am not sure this will actually work.
Related
Hello out there,
my problem is a bit annoying. Everything is fine if I use my OP3T with Oxygen (4.0.3) and TWRP (3.0.3-1). But I want to use LineageOS with TWRP and cant, because my TWRP isnt working after flashing lineage.
"Normal"-Setup:
- TWRP 3.0.3-1
- Oxygen 4.0.2 or 4.0.3 (doesn't matter)
- supersu 2.79
- Encrypted Device
"Lineage"-Setup:
- TWRP 3.0.3-1
- lineageOS (lineage-14.1-20170214-nightly-oneplus3-signed.zip OR lineage-14.1-20170208-nightly-oneplus3-signed.zip - tried both, doesnt matter)
- supersu 2.79
- openGApps for 7.1 nano
- Encrypted Device
My Problem is, that I can boot up lineage and use it, but if I reboot into my TWRP to flash something or make some Backups, it asks for my encryption-passphrase, it says it is okay and boots into the twrp main-windows. After that I can't touch anything (stuck in mainmenu) and after a few seconds it results into a black screen (plus white LED) and I am forced to reboot the device. After that reboot I have to reconfigure lineage (seems to loose data).
Does anyone have an idea how to fix this annoying "bug"?
Thank you very much!
Atomique
EDIT: I found that Thread after searching for a issue like that in the lineageOS official Thread - I will try this and report! - Thank you! https://forum.xda-developers.com/on.../recovery-official-twrp-oneplus-3-3t-t3543391
I had the exact same problem when I hab LineageOS installed! It would always lose all its data. After flashing and reflashing a hundred times, I ended up reverting my OP3T back to stock using a OnePlus forum guide (I'm a new user, so I can't post the link). I am now back to OOS 4.0.3 but can't even get SuperSU to work. Whenever I flash it (with or without the dm-verity fix) the phone is stuck booting forever.
I found the post you linked to aswell but haven't tried flashing LineageOS using the new TWRP. But I can tell that the new version doesn't help rooting OOS...
Did you have any luck flashing LineageOS by now?
Edit: With the newest Lineage Version I always get an error when trying to flash it. Do you have the same problem? The nightly from two weeks ago seems to work better.
Use latest TWRP 3.0.4.1
nitinvaid said:
Use latest TWRP 3.0.4.1
Click to expand...
Click to collapse
That's what I'm doing... Could the dm-verity be a problem? There are two versions, one with opt and one with force in the name.
Thank you for your replies! The link (TWRP 3.0.4-1) worked like a charme!
@Tafelbomber: I would recommend you to start from scratch. But please be warned: you will loose your data! Make a backup first!
1. Delete everything with fastboot -w
2. Flash the recovery noted in my first post with fastboot flash recovery <twrp-filename.img>
3. Optional: Restart into the TWRP and flash the OOS 4.0.3 to make sure that you have a clean OS installed befor flashing lineage
4. Flash lineage OS + additional ZIPs (like supersu, betterbatterystats, Gapps etc)
5. Clean Dalvik and Cache!
6. Reboot and have fun. --> Sometimes you get problems with the encryption chain (Red Error --> in my case the fastboot -w did it for me)
Good luck - I will close this thread - thanks again for your help!
Atomique
EDIT: I want to close this thread, but I don't know how.
The official Android Pie 9.0 update from SAMSUNG is months ahead. Thanks to @phhusson!:angel: We can now get a taste of The Sweetest Release of Android ever!
This is a GSI (Generic System Image) and will most Probably work on all Devices running 8.0 or above (your device must be fully Treblized )
Telegram Channel
Enjoy Android PIE!
Video- https://youtu.be/VfmzkIVSzu0
What Works-
-RIL(Calls,sms,lte)
-Bluetooth, WiFi
-Camera( Stock isn't that great) Use GCam)
-Fingerprint
-and pretty much everything
What Doesn't Work
-Iris Scanner(with high hopes that it'll work in future updates)
-Telephoto Lens( also may work in the Future)
Links and Instructions in the 2nd Post
Links and Instructions
LINKS-
Android Pie 9.0 Phh-GSI https://github.com/phhusson/treble_experimentations/releases/
Gapps
GCam By IDan with Working Dual Aperture!
Google Camera
ADDONS
BRH4 Vendor (flash this first if getting boot loop)
NOTE-U need to be on a Treble Supporter ROM like Stock, any vendor will work)
GSI strands for GENERIC SYSTEM IMAGE
Instructions -
1. Check your device architecture and download the GSI.img accordingly, also download the appropriate gapps for this device
2. Reboot to recovery and Wipe system,cache,dalvik,data(backup previously if you want)
3. Go to install section and find the GSI(choose to install image)
4. Flash the gsi to system partition
5. Now REBOOT to RECOVERY again.
6. Now flash the Gapps.zip normally
7. Reboot to system
8. Enjoy!
[FIXES]
1. If bluetooth doesn't work the try Clean flashing again with latest stock firmware and Vendor
2. If Black screen appears when trying to add Google account then select Chrome in Android Webview Implementation in Developers settings...
Even if that doesn't work then to to twrp(backup data if required) then wipe system the flash GSi,reboot again to recovery and then flash Gapps( micro is recommended) now reboot. Skip the Google setup wizard by not connecting to WiFi or LTE. Now choose sideload Chrome(install via apk) and choose in Webview Implementation)
3. If webview implementation thing isn't working:
Backup data via TWRP. Wipe everything except data, sd card and internal storage.(wipe system partition also) Now flash the GSI again,reboot to recovery, clear cache & dalvik now flash gapps and reboot. Skip the setup by not connecting to internet and then go to dev Settings and choose chrome in webview implementation
4. If gapps give an error: that's most probably because of it detecting 8.1 or 8.0 firmware. So after flashing the GSI, reboot to recovery again then flash Gapps
Addons-
2 .kl Files-
Place the two .kl files in /system/usr/keylayout
Overlays-PR1.zip
Flash for gestures get working
aosp-9.0_Pixel-theme.zip
Flash for Pixel Blue theme instead of Green
Digital Wellbeing App-
Download the Apk from the Addons folder,signup here- Digital Wellbeing Beta ,Install the apk and give it Usage Data Access Permission in App settings
Pixel launcher-
download the launcher apk from addons Folder, replace the quickstep.apk in /system/priv-app/quickstep with this one!
Thanks to @saxmydix for the zips
There is a known incompatibility with CSC PHN
What's the best way to correct the padding for our rounded screen?
For sure i have to root and install the twrp to flash this rom? Will **** the knox counter to flash this rom?
vuoshino said:
For sure i have to root and install the twrp to flash this rom? Will **** the knox counter to flash this rom?
Click to expand...
Click to collapse
Of course, it's a custom ROM
Just another OT sorry. But if I flash something when i will try to restore, the knox counter will be ****ed anyway? Is it right?
vuoshino said:
Just another OT sorry. But if I flash something when i will try to restore, the knox counter will be ****ed anyway? Is it right?
Click to expand...
Click to collapse
Yes, it's permanent
s3xxt0y said:
What's the best way to correct the padding for our rounded screen?
Click to expand...
Click to collapse
You should get correct rounded padding on second boot (you need to wait a minute after first boot)
Quick question, when you mean i have to be on a treble rom before that, does it have to be a Treble rom or a standard lineage would work?#
When I try to add a google account the screen just goes blank!
what's working and not working will be nice to see in the OP and gcam version if u can... this'll Clear all doubts of people
phhusson said:
You should get correct rounded padding on second boot (you need to wait a minute after first boot)
Click to expand...
Click to collapse
Awesome. Thanks mate, thanks for getting the GSI out so quickly too ?
Muntasir Mahmud Saif said:
what's working and not working will be nice to see in the OP and gcam version if u can... this'll Clear all doubts of people
Click to expand...
Click to collapse
I was unable to find anything about what's working and what isn't working?
Lags ... bixby button , home button unlock , google account attachment screen off , access point Not Work but the rom is so fast , so go back to stock
"I was unable to find anything about what's working and what isn't working?"
https://youtu.be/VfmzkIVSzu0
dokibull said:
"I was unable to find anything about what's working and what isn't working?"
https://youtu.be/VfmzkIVSzu0
Click to expand...
Click to collapse
Because it's a generic image
Bluetooth is broken
Which gapps did you guys flash?
OP has been Updated with "What work and what doesn't" and link to GCamera that I use!
MidnightDevil said:
Quick question, when you mean i have to be on a treble rom before that, does it have to be a Treble rom or a standard lineage would work?#
When I try to add a google account the screen just goes blank!
Click to expand...
Click to collapse
Just go to developers settings and in Webview Implementation select Chrome! Hope that helps!?
We already know this phone is arm64,
the GSI rom AOSP v112 has support for this phone.
But how is the rom behave? What works and doesn't?
How are other GSI flavours doing? Like RR, AEX, HAVOC,....
[NOTE: For those who are interested i'll change this post to some GSI guide cepheus,
as soon as i recieve my Mi 9. But until then i'll hope for some of your feedback]
See this: https://github.com/phhusson/treble_experimentations/wiki/Xiaomi-Mi-9
and these two: https://forum.xda-developers.com/showpost.php?p=79284072&postcount=46, https://forum.xda-developers.com/showpost.php?p=79295919&postcount=53
It shoudn't be needed to write a guide
a video guide would be interesting
I usually used twrp to flash the Gsi file but now I didn't understand what steps should be taken
tried Foloko, RR trebles and it's entertaining as STDs.. couldn't add Gapps for hours and never managed to using 2 very different TWRPs we've got, tons of tricks, or adding stock system/vendor.
I don't understand the assumption "Please don't use third-party custom rom (e.g. Xiaomi.eu roms) as the base rom. Some hacky roms have wrong (unofficial) fingerprint and GSI can't detect what device you are using. ", ok, what should be in the phone then?
After some attempts Phh treble from post 60 installed, greeting me with "There's an internal problem with your device. Contact your manufacturer for details.", some vendor nonsense. After reboot i cannot log in, as fingerprint overrides the letter i need to type the password. omg. So i have to reflash.
update: since Phh was ultra vanilla with literally 2 extra settings, tried RR, same greeting, no fp, and no swipe to apps there, i don't really beg for their modifications as i have Xposed Edge for this. Finally went back to Floko knowing how to fix gapps problem, it's got best navbar solution, although with tons of bugs (contradicting navbar user actions, non responsive gestures, nonresponsive buttons), no tap2wake, AOD sucks, fp sucks too, produces blinking screen.
Looks like trebles are unusable, time to go back to XIAOMI EU... so much for "don't need device specific ROMs".
doggydog2 said:
tried Foloko, RR trebles and it's entertaining as STDs.. couldn't add Gapps for hours and never managed to using 2 very different TWRPs we've got, tons of tricks, or adding stock system/vendor.
I don't understand the assumption "Please don't use third-party custom rom (e.g. Xiaomi.eu roms) as the base rom. Some hacky roms have wrong (unofficial) fingerprint and GSI can't detect what device you are using. ", ok, what should be in the phone then?
After some attempts Phh treble from post 60 installed, greeting me with "There's an internal problem with your device. Contact your manufacturer for details.", some vendor nonsense. After reboot i cannot log in, as fingerprint overrides the letter i need to type the password. omg. So i have to reflash.
Click to expand...
Click to collapse
You have to flash *official* MIUI rom (China or Global depend on your hardware, and it's better to flash developer version to get latest update).
To install GApps, you have to do Wipe -> Advanced wipe -> Select system -> Resize, then Mount -> mount system, then install GApps zip.
dear mod please close this one, there seems to be already a conversation about this
AndroPlus said:
You have to flash *official* MIUI rom (China or Global depend on your hardware, and it's better to flash developer version to get latest update).
To install GApps, you have to do Wipe -> Advanced wipe -> Select system -> Resize, then Mount -> mount system, then install GApps zip.
Click to expand...
Click to collapse
tried to do that, tried to install arm64 Gapps, I'd get an error saying my system is arm, so i install arm gapps, they do get "installed", but when i reboot, there is no gapps at all.
edit: arm64 gapps worked when used LR.Team/wzsx150 twrp.
AndroPlus said:
You have to flash *official* MIUI rom (China or Global depend on your hardware, and it's better to flash developer version to get latest update).
To install GApps, you have to do Wipe -> Advanced wipe -> Select system -> Resize, then Mount -> mount system, then install GApps zip.
Click to expand...
Click to collapse
which Global please? this is the link http://en.miui.com/download-361.html claiming to be Full Rom, but the zip is similar to EU version, just a patch.. just tried it, then flashed EU and magisk and getting "can't connect to camera". i was thinking i need to flash some bigger package (.tgz file), but there's none published and going throught the million childish looking forums on eu.miui.com, not sure.. would like TWRP way. perhaps format system?
doggydog2 said:
which Global please? this is the link http://en.miui.com/download-361.html claiming to be Full Rom, but the zip is similar to EU version, just a patch.. just tried it, then flashed EU and magisk and getting "can't connect to camera". i was thinking i need to flash some bigger package (.tgz file), but there's none published and going throught the million childish looking forums on eu.miui.com, not sure.. would like TWRP way. perhaps format system?
Click to expand...
Click to collapse
You can find fastboot image here:
https://en.miui.com/a-234.html
AndroPlus said:
You can find fastboot image here:
https://en.miui.com/a-234.html
Click to expand...
Click to collapse
thanks but both links redirect me to http://www.miui.com/ in chinese where i can browse to quasi-full roms again. strange.
btw i'm a fan of your kernel except it causes "can't connect to camera".. after many combinations of flashing i tried skipping the kernel (v01, or v02 or any kernel), and camera is back. however without Night mode this time...
update: found stable ROM at least https://c.mi.com/thread-1907373-1-0.html
update: somehow i trust this is the legit link to develop ROM http://bigota.d.miui.com/9.3.1/ceph....1_20190301.0000.00_9.0_global_cdb3885bac.tgz
AndroPlus said:
You can find fastboot image here:
https://en.miui.com/a-234.html
Click to expand...
Click to collapse
Hey,
Could you make your magisk patch to not require pressing FP scanner twice for FP to register?
Without the patch, works fine from first try, but with it, two presses at least are needed Everytime.
Thank you!
Hey,
So after a lot of observation and reading I think LOS 17.1 seems stable enough to be used for a daily driver.
Right now I am on the normal stock ROM, without any modifications, no TWRP, no root whatsoever.
However, I have unlocked the bootloader a few months ago, so that's done already.
Current state of the phone:
Code:
MIUI version: 11.0.1.0 (QFKMIXM) - Is this the global version?
Device model: Mi 9T Pro (128GB, 6GB RAM)
I want to install TWRP, I want to root the phone, I want to install all needed modules for a proper camera etc, I want to install LineageOS 17.1 (latest build) and lastly I want to install Immensity Kernel (latest build) because I have heard it works well with LOS and provides lots of battery improvements.
I did lots of tinkering with my phone a couple years back, but I haven't done so in a while, and neither have I done anything with this device, so to make sure I am not breaking anything I decided its the best to ask here.
What steps do I have to provide in which order? Can someone provide my a detailed explanation of all the needed steps?
Also, can I install MicroG on it, or do I have to use GApps?
My guess is, first TWRP and root, then ROM and then kernel?
Also, I have read about some issues with Magisk and Android 10, is that still a problem, or is that solved by now?
Anything else I need to look out for?
Cheers
KuroRyu said:
Hey,
So after a lot of observation and reading I think LOS 17.1 seems stable enough to be used for a daily driver.
Right now I am on the normal stock ROM, without any modifications, no TWRP, no root whatsoever.
However, I have unlocked the bootloader a few months ago, so that's done already.
Current state of the phone:
I want to install TWRP, I want to root the phone, I want to install all needed modules for a proper camera etc, I want to install LineageOS 17.1 (latest build) and lastly I want to install Immensity Kernel (latest build) because I have heard it works well with LOS and provides lots of battery improvements.
I did lots of tinkering with my phone a couple years back, but I haven't done so in a while, and neither have I done anything with this device, so to make sure I am not breaking anything I decided its the best to ask here.
What steps do I have to provide in which order? Can someone provide my a detailed explanation of all the needed steps?
Also, can I install MicroG on it, or do I have to use GApps?
My guess is, first TWRP and root, then ROM and then kernel?
Also, I have read about some issues with Magisk and Android 10, is that still a problem, or is that solved by now?
Anything else I need to look out for?
Cheers
Click to expand...
Click to collapse
Make sure you are in the latest version of MIUI first.
For TWRP flash the latest Mauronofrio TWRP, he has the official TWRP, but his unofficial, latest version is probably a better option at its a little bit more up to date.
Once you've flashed TWRP you will need to boot immediately in to TWRP without allowing the phone to boot into MIUI, otherwise the phone will detect that recovery had been modified and will restore stock recovery.
When you've booted into TWRP, format data (needs to be format and not only wipe), then wipe cache and dalvik.
Reboot into TWRP, to ensure that the newly formatted data partition is correctly mounted.
Now flash lineage and a GApps package. I've only used Open GApps Pico, but I believe microG should be OK. If you use Open GApps it is still in beta and packages larger than the micro package are likely to cause issues, so stick with micro, pico or nano. (For clarification, micro G is a GApps package, what you are really asking is do you need to use Open GApps or not)
The latest Magisk is fine now. It is recommended to boot into LOS first at least once before flashing Magisk. I can't remember the details but sometimes you may get issues if you flash Magisk after flashing a ROM, without booting to the ROM first. You may be fine if you don't boot the ROM first, but since I've forgotten the reasons and can no longer find it, I now boot the ROM before flashing Magisk, just to be safe.
From here, you should be OK to flash different kernels, personally I've never felt the need to, as I'm happy with the performance of things as they are. My battery life is similar to what it was on stock MIUI. If you want to try kernels other than Immensity, just double check first that it is for AOSP ROMs. There are some kernels that have been created that are only compatible with Stock MIUI.
For the camera, I believe the latest advice for ANX Cam is still version 158 along with the 48MP fix for Q ROMs. There are a few later versions, which are not appropriate for this phone. I don't believe there has been a later version for this phone.
Edit: just noticed your question in the quote.
You have the global version of the phone. AFAIK 11.0.1 is still the latest version of the global version of MIUI.
Robbo.5000 said:
Make sure you are in the latest version of MIUI first.
For TWRP flash the latest Mauronofrio TWRP, he has the official TWRP, but his unofficial, latest version is probably a better option at its a little bit more up to date.
Once you've flashed TWRP you will need to boot immediately in to TWRP without allowing the phone to boot into MIUI, otherwise the phone will detect that recovery had been modified and will restore stock recovery.
When you've booted into TWRP, format data (needs to be format and not only wipe), then wipe cache and dalvik.
Reboot into TWRP, to ensure that the newly formatted data partition is correctly mounted.
Now flash lineage and a GApps package. I've only used Open GApps Pico, but I believe microG should be OK. If you use Open GApps it is still in beta and packages larger than the micro package are likely to cause issues, so stick with micro, pico or nano. (For clarification, micro G is a GApps package, what you are really asking is do you need to use Open GApps or not)
The latest Magisk is fine now. It is recommended to boot into LOS first at least once before flashing Magisk. I can't remember the details but sometimes you may get issues if you flash Magisk after flashing a ROM, without booting to the ROM first. You may be fine if you don't boot the ROM first, but since I've forgotten the reasons and can no longer find it, I now boot the ROM before flashing Magisk, just to be safe.
From here, you should be OK to flash different kernels, personally I've never felt the need to, as I'm happy with the performance of things as they are. My battery life is similar to what it was on stock MIUI. If you want to try kernels other than Immensity, just double check first that it is for AOSP ROMs. There are some kernels that have been created that are only compatible with Stock MIUI.
For the camera, I believe the latest advice for ANX Cam is still version 158 along with the 48MP fix for Q ROMs. There are a few later versions, which are not appropriate for this phone. I don't believe there has been a later version for this phone.
Edit: just noticed your question in the quote.
You have the global version of the phone. AFAIK 11.0.1 is still the latest version of the global version of MIUI.
Click to expand...
Click to collapse
Do I also need the force encrypt file? Some people mention it needs to be flashed too?
How do I properly install twrp? I boot into fastboot mode, and then I can flash it, I assume?
In the thread it also states that one should first flash vbmeta?
EDIT: Ok, I flashed vbmeta and twrp, booted into twrp, formated data and wiped dalvik and cache.
Now should I flash LOS next and then gapps ..? Which GApp package is the right one for 17.1? It is not linked in the LOS thread?
I've read that some people had issues when flashing the wrong gapps package
EDIT2: Ok, so far I have persisted TWRP and installed magisk. I flashed LOS 17.1 (latest build) and booted into it. I did not flash gapps yet as I dont know which gapps package to use. Also I would prefer to use microG if possible, but I dont think its possible to install it easiely? If it is, please let me know.
Now, the issue is, for some reason after the clean install of LOS17.1 I still see google apps like google drive (remember, I did not flash gapps). This shouldn't be the case? I did format data and cleared dalvik and cache, so it is a bit weird that this happens...
Also I constantly get "android.process.media keeps stopping" .. I assume that is because some applications try to access google service, which are not correctly available? What did I do wrong?
So my questions are:
1) Is it possible to use microG (opensrc implementation of google services), rather than gapps? If so, how?
2) If I need to use GApps, which one to flash?
3) Why were google apps still present on my device after flashing and formatting data ..?
KuroRyu said:
Do I also need the force encrypt file? Some people mention it needs to be flashed too?
How do I properly install twrp? I boot into fastboot mode, and then I can flash it, I assume?
In the thread it also states that one should first flash vbmeta?
EDIT: Ok, I flashed vbmeta and twrp, booted into twrp, formated data and wiped dalvik and cache.
Now should I flash LOS next and then gapps ..? Which GApp package is the right one for 17.1? It is not linked in the LOS thread?
I've read that some people had issues when flashing the wrong gapps package
EDIT2: Ok, so far I have persisted TWRP and installed magisk. I flashed LOS 17.1 (latest build) and booted into it. I did not flash gapps yet as I dont know which gapps package to use. Also I would prefer to use microG if possible, but I dont think its possible to install it easiely? If it is, please let me know.
Now, the issue is, for some reason after the clean install of LOS17.1 I still see google apps like google drive (remember, I did not flash gapps). This shouldn't be the case? I did format data and cleared dalvik and cache, so it is a bit weird that this happens...
Also I constantly get "android.process.media keeps stopping" .. I assume that is because some applications try to access google service, which are not correctly available? What did I do wrong?
So my questions are:
1) Is it possible to use microG (opensrc implementation of google services), rather than gapps? If so, how?
2) If I need to use GApps, which one to flash?
3) Why were google apps still present on my device after flashing and formatting data ..?
Click to expand...
Click to collapse
There is no need to flash force encrypt files or vbmeta.
I have never used MicroG so couldn't give any answers about that, however Open GApps are open source too. For android 10 it is still in beta. The beta files can be found here https://sourceforge.net/projects/opengapps/files/arm64/beta/20191209/. Pico is the smallest package that gives Google Play, personally I recommend going with that, then installing any other Google stuff from the play store, should you want them.
No idea why you would be seeing Google apps. I can only suggest formatting data again in TWRP.
If that doesn't work I would start again. Fastboot flash the latest MIUI 11.0.1 global ROM, boot into it once, there is no need to go through the set-up. Then go through the steps given before.
This time don't flash vbmeta, it is not needed.
The fastboot ROM can be found here http://bigota.d.miui.com/V11.0.1.0....M_20191111.0000.00_10.0_global_11d3a1700a.tgz
Edit:
Having seen some of your other posts, I'll give you some more info.
vbmeta is mainly used to persist TWRP. However flashing Magisk will persist TWRP and flashing a custom ROM will persist TWRP. You would only need to flash vbmeta if you wanted to stay on MIUI and not use Magisk. (There are other uses for vbmeta, but you don't need them, so I'll not go into them)
Is widevine L1 available on the ROM? Is the FOD working well?
Hi guys, I'm here looking for any help
I'm having this weird behavior in any custom rom I flash.
A while after flashing some rom (some 2 or 3 cycles of battery, around 1 to 3 days) suddenly all apps start crashing, falling at that force close popup. I mean every app, when I try to launch some new app it goes to the force close immediately.
I can't take a screenshot because it fails, I can't take a screen record because it crashes.
So I have to reboot, and it boots normally, but already happened that some apps loose their cache/data, because they start from zero and I have to log in again.
Happening on any A13 build, I don't remember about A12.
Can that be a hardware issue? I doesn't happen on MIUI.
Tried PE+, LO, CrDroid, ArrowOS, CherishOS, Voltage, Spark... Well, I'm trying it all.
Tried changing recovery: Kewl TWRP, TWRP, OrangeFox
Tried leaving phone on LTE only.
Tried flash fastboot MIUI before other rom.
Flashing all of them like: wipes, install rom, format data.
Does anybody has any idea?
Thanks and sorry about my english!
Leonvrx said:
Hi guys, I'm here looking for any help
I'm having this weird behavior in any custom rom I flash.
A while after flashing some rom (some 2 or 3 cycles of battery, around 1 to 3 days) suddenly all apps start crashing, falling at that force close popup. I mean every app, when I try to launch some new app it goes to the force close immediately.
I can't take a screenshot because it fails, I can't take a screen record because it crashes.
So I have to reboot, and it boots normally, but already happened that some apps loose their cache/data, because they start from zero and I have to log in again.
Happening on any A13 build, I don't remember about A12.
Can that be a hardware issue? I doesn't happen on MIUI.
Tried PE+, LO, CrDroid, ArrowOS, CherishOS, Voltage, Spark... Well, I'm trying it all.
Tried changing recovery: Kewl TWRP, TWRP, OrangeFox
Tried leaving phone on LTE only.
Tried flash fastboot MIUI before other rom.
Flashing all of them like: wipes, install rom, format data.
Does anybody has any idea?
Thanks and sorry about my english!
Click to expand...
Click to collapse
Did you've formated DATA with yes and reboot recovery
Then flashed fw
and last the ROM?
I mean exactly like this?
Laptapper said:
Did you've formated DATA with yes and reboot recovery
Then flashed fw
and last the ROM?
I mean exactly like this?
Click to expand...
Click to collapse
No i've rebooted to the recovery, wiped, installed firmware, installed rom, formated data.
But would this order change anything even to roms that say that don't need any specific firmware?
Leonvrx said:
No i've rebooted to the recovery, wiped, installed firmware, installed rom, formated data.
But would this order change anything even to roms that say that don't need any specific firmware?
Click to expand...
Click to collapse
Wipe isn't enough, formating with yes is necessary.
Try exactly my procedure (fw isn't necessary for all roms / cherishos don't need, Los need)
Some ROMs installation instructions do not require an initial format of data before installation of the ROM itself, like EliteRom. Follow your ROM's installation instructions regarding required firmware. (MIUI)
Leonvrx said:
No i've rebooted to the recovery, wiped, installed firmware, installed rom, formated data.
But would this order change anything even to roms that say that don't need any specific firmware?
Click to expand...
Click to collapse
Sheist! said:
Some ROMs installation instructions do not require an initial format of data before installation of the ROM itself, like EliteRom. Follow your ROM's installation instructions regarding required firmware. (MIUI)
Click to expand...
Click to collapse
Also elite rom need format data if encrypted (normally data is encrypted!)
Leonvrx said:
No i've rebooted to the recovery, wiped, installed firmware, installed rom, formated data.
But would this order change anything even to roms that say that don't need any specific firmware?
Click to expand...
Click to collapse
If installing the EliteROM (for example), your formatting after installing the ROM is the correct procedure, per the declared instructions:
Installation Instructions:
- Install rom zip using TWRP/OFOX
- Format if you are encrypted, otherwise wipe data is enough
- Reboot
- Enjoy the smoothness+performance
Sheist! said:
If installing the EliteROM (for example), your formatting after installing the ROM is the correct procedure, per the declared instructions:
Installation Instructions:
- Install rom zip using TWRP/OFOX
- Format if you are encrypted, otherwise wipe data is enough
- Reboot
- Enjoy the smoothness+performance
Click to expand...
Click to collapse
@Leonvrx
according my experience it's not important if you format before ROM or after Rom installation but very important to restart recovery when you do it before ROM installation in encryption state.
If decrypted then only wiping data
Please feedback your trying and results.
Laptapper said:
@Leonvrx
according my experience it's not important if you format before ROM or after Rom installation but very important to restart recovery when you do it before ROM installation in encryption state.
If decrypted then only wiping data
Please feedback your trying and results.
Click to expand...
Click to collapse
I didn't know that; thank you for your help, guidance, and patience.
Tried your steps exactly this morning, so far so good, I'll update in the next days, for better or for worse.
@Laptapper
Yeah, same results, it crashed the same (using AlphaDroid atm).
I've rebooted it and it even started initial android setup again, after redoing it, i have all my apps like nothing happened, but my sound settings, fingerprint settings (and probably other too) reseted.
I've also already tried to remove the microSD expation slot, same results,
Tried Vanilla + NikGapps, Vanilla + BitGapps and Gapps builds.
I think it's just bad luck with this specific device :/
Leonvrx said:
@Laptapper
Yeah, same results, it crashed the same (using AlphaDroid atm).
I've rebooted it and it even started initial android setup again, after redoing it, i have all my apps like nothing happened, but my sound settings, fingerprint settings (and probably other too) reseted.
I've also already tried to remove the microSD expation slot, same results,
Tried Vanilla + NikGapps, Vanilla + BitGapps and Gapps builds.
I think it's just bad luck with this specific device :/
Click to expand...
Click to collapse
Which recovery?
Take this:
👍[SHARED] orange fox recovery with decryption for Android 12,13
Update post 9 with android 13 decryption support Here I'm sharing the nearly perfect recovery orange fox with implemented decryption for android 12 ( I've tested only pin protection) The main advantage comparing TWRP is the "beautiful" UI and...
forum.xda-developers.com
Try cherishos with exactly my procedure above. Fw isn't needed!
Laptapper said:
Which recovery?
Take this:
👍[SHARED] orange fox recovery with decryption for Android 12,13
Update post 9 with android 13 decryption support Here I'm sharing the nearly perfect recovery orange fox with implemented decryption for android 12 ( I've tested only pin protection) The main advantage comparing TWRP is the "beautiful" UI and...
forum.xda-developers.com
Try cherishos with exactly my procedure above. Fw isn't needed!
Click to expand...
Click to collapse
I think that it's exactly this version, but I will reflash to make sure and I'll try again
Leonvrx said:
I think that it's exactly this version, but I will reflash to make sure and I'll try again
Click to expand...
Click to collapse
If not working then try this:
In orange fox recovery
format data with manually typing yes
reboot recovery
install cherish gapps rom
format data/yes Again
Start system
Laptapper said:
If not working then try this:
In orange fox recovery
format data with manually typing yes
reboot recovery
install cherish gapps rom
format data/yes Again
Start system
Click to expand...
Click to collapse
Ok, I'll try if happens again. Sometimes it takes 2 or 3 days to happen.
But I have a problem in Cherish that on my bank app (C6 Bank Brazil) my facial recognition doesn't work. It stays on a black screen despite I had given camera permission.
Leonvrx said:
Ok, I'll try if happens again. Sometimes it takes 2 or 3 days to happen.
But I have a problem in Cherish that on my bank app (C6 Bank Brazil) my facial recognition doesn't work. It stays on a black screen despite I had given camera permission.
Click to expand...
Click to collapse
Playstore certified?
Rooted?
Cts matching?
Laptapper said:
Playstore certified?
Rooted?
Cts matching?
Click to expand...
Click to collapse
Non-rooted, CTS profile ok and certified.
It's a thing that just happen in this ROM.
Also this app is really annoying to hide root from, so I never root
Leonvrx said:
Non-rooted, CTS profile ok and certified.
It's a thing that just happen in this ROM.
Also this app is really annoying to hide root from, so I never root
Click to expand...
Click to collapse
Try kernelsu root
Then delete caches of playstore and Google play services.
Reboot
I've got non problems with banking and camera in cherish and kernelsu