Related
Hi,
I was stupid not to take a complete backup through TWRP, but oh well.
After reflashing EUI 5.8.019S after I flashed the unofficial December update of EUI 5.9.20S, I discovered that my SIM card wasn't detected and that WiFi wasn't operational. I tried flashing EUI 5.8.015S, wiping, reflashing, OTA updates, flashing the modem separately and a host of other things to no avail. Should I get the device repaired as I'm still under warranty, or can I use fastboot or TWRP to fix this? Currently, I am on EUI 5.8.015S, and waiting for the first build @codeworkx's LineageOS so that I can see if this problem persists. Anyway, if anyone has a TWRP backup that they can upload, I'd be really grateful.
Flash volte fix
From kanak sharma
Availabke at rim thread by me rom thread is tittled unofficial eui 29s step by step guide
Even if nai hua pm me personally will solve the issue
Shrivaas73 said:
Hi,
I was stupid not to take a complete backup through TWRP, but oh well.
After reflashing EUI 5.8.019S after I flashed the unofficial December update of EUI 5.9.20S, I discovered that my SIM card wasn't detected and that WiFi wasn't operational. I tried flashing EUI 5.8.015S, wiping, reflashing, OTA updates, flashing the modem separately and a host of other things to no avail. Should I get the device repaired as I'm still under warranty, or can I use fastboot or TWRP to fix this? Currently, I am on EUI 5.8.015S, and waiting for the first build @codeworkx's LineageOS so that I can see if this problem persists. Anyway, if anyone has a TWRP backup that they can upload, I'd be really grateful.
Click to expand...
Click to collapse
jhakjhuk1853 said:
Flash volte fix
From kanak sharma
Availabke at rim thread by me rom thread is tittled unofficial eui 29s step by step guide
Even if nai hua pm me personally will solve the issue
Click to expand...
Click to collapse
I did that too, doesn't work. It's the one by Kanak Sharma, right? Well, no harm trying it again.
I'll PM you after this.
Shrivaas73 said:
Hi,
I was stupid not to take a complete backup through TWRP, but oh well.
After reflashing EUI 5.8.019S after I flashed the unofficial December update of EUI 5.9.20S, I discovered that my SIM card wasn't detected and that WiFi wasn't operational. I tried flashing EUI 5.8.015S, wiping, reflashing, OTA updates, flashing the modem separately and a host of other things to no avail. Should I get the device repaired as I'm still under warranty, or can I use fastboot or TWRP to fix this? Currently, I am on EUI 5.8.015S, and waiting for the first build @codeworkx's LineageOS so that I can see if this problem persists. Anyway, if anyone has a TWRP backup that they can upload, I'd be really grateful.
Click to expand...
Click to collapse
You can do 1 thing. Restore the phone into stock and then root it with twrp provided by @codeworkxx's.
Maybe it can help.
Thanks
Wrt
HB xt
Fixed ?
I'm sorry I didn't respond until now. Yes, I've fixed it. I repeatedly wiped and reflashed with various TWRP recoveries and even fastboot. After I flashed MIUI, wiped it and used stock recovery to flash EUI 5.8.019S, both WiFi and RIL started working. It's working fine now on LineageOS
DISCLAIMER:
I am not an official maintainer or developer, I have made this thread so we can discuss the builds and possibly have some way of communicating with actual developers who are working on builds for our device.
I am also not responsible for anything that you might chose to do or not do to your personal device, nor am I responsible for anything that happens to it because of decisions you have made.
HOW TO INSTALL:
Install latest stock firmware
Flash TWRP
Wipe Data - System - Dalvik and Cache
Flash latest LineageOS & GApps
FAQ:
Are the official builds stable enough for daily use?
Yes.
Does the camera work?
Yes.
How is the picture quality?
As close to stock as it will ever get without the proprietary Sony algorithms that we will never get anyway. Personally I can't tell the difference between stock and this.
When will we get Oreo builds?
I doubt anyone knows, but constantly asking for it won't bring it faster.
WHAT'S NOT WORKING?
NOTE: Please do not report bugs you encounter after dirty flashing. Try doing a clean flash and recreating the issue first.
Issues with encryption.
Download & Changelog
Code Review
Hello, are you new developer/maintainer?
Possible to add stock feature for data ON on mms? Very convenient https://review.lineageos.org/#/c/165222/ thanks you!
n/A
Bluetooth is crashing when playing music. Seems to be a common bug with LineageOS and nearly any device.
Mastertryce said:
Bluetooth is crashing when playing music. Seems to be a common bug with LineageOS and nearly any device.
Click to expand...
Click to collapse
Another bugs? Is good for daily use?
Good to see,when a new Person support this phone.
Dear maintainer,
I'm using the latest build (lineage-14.1-20180318-nightly-suzuran-signed.zip). After phone encryption I can't decrypt the /data partition when using TWRP (3.2.1-0). Password is correct but it keeps printing:
Code:
Faild to decrypt data
Password failed, please try again!
This makes updating the device complicated. I'm using adb sideload to transfer updates to the phone when flashing with TWRP. Mounting external micro SD-card (/sdcard1 | Micro SD card) is also not possible. When you select in TWRP: "Mount -> Micro SD card" it's not possible to mount the external card.
Any ideas?
Problems
In total the LineageOS 14.1 works fine - I work with the lastest release lineage-14.1-20180318.
Problems:
1. TWRP can not decrypt the data partition.
2. With encrypted data partition, my mobile phone does not work under LineageOS.
3. All actions in the GUI of LineageOS to be subsequently executed under TWRP (like Factory Reset and LineageOS Update) show no reaction, i.e. do not do anything. LineageOS does nothing, TWRP is not started and nothing is executed. Except that the LineageOS Updater reports "error".
4. My hotspot under LineageOS has connection problems, but WLAN is working fine.
I think the first problem is a TWRP problem - the rest are LineageOS problems.
All problems remained unchanged without and with Factory Reset, as well as with LineageOS reinstallation (with full wipe Boot, Cache, Data and System partition) without and with Factory Reset.
My z5 on Stock ROM is very hot. Is official linageos
Cooler than stock rom? Some times I watch online video in Firefox z5 very hot and touch screen doesn't respond.
DXXXA said:
My z5 on Stock ROM is very hot. Is official linageos
Cooler than stock rom? Some times I watch online video in Firefox z5 very hot and touch screen doesn't respond.
Click to expand...
Click to collapse
I think you ask this question in the wrong thread.
This thread is for suzuran - that is a Sony Xperia Z5 Compact, not a Sony Xperia Z5.
rm43115 said:
1. TWRP can not decrypt the data partition.
Click to expand...
Click to collapse
Yes. I have the same problem and found this.
HTML:
Not working (for now):
- Decryption <- working on it when I have time
rm43115 said:
2. With encrypted data partition, my mobile phone does not work under LineageOS.
Click to expand...
Click to collapse
I'm using lineage-14.1-20180318-nightly-suzuran-signed.zip. Encryption is working and my phone also. What is your problem? Can you specify?
shellshocker said:
Yes. I have the same problem and found this.
I'm using lineage-14.1-20180318-nightly-suzuran-signed.zip. Encryption is working and my phone also. What is your problem? Can you specify?
Click to expand...
Click to collapse
The thread for the TWRP is well know - give him time - trax7 and TwrpBuilder will integrate encryption ... if possible.
The mobile phone gets no connection to the radio cell.
rm43115 said:
The mobile phone gets no connection to the radio cell.
Click to expand...
Click to collapse
That was also my problem. Just remove SIM-card protection/PIN under Settings -> Security. Reboot.
shellshocker said:
That was also my problem. Just remove SIM-card protection/PIN under Settings -> Security. Reboot.
Click to expand...
Click to collapse
Thanks - I will try again as soon as our TWRP is able to decrypt the data partition.
shellshocker said:
Just remove SIM-card protection/PIN under Settings -> Security. Reboot.
Click to expand...
Click to collapse
You can only use this rom with disabled sim-card protection? That's not good...
Berni-0815 said:
You can only use this rom with disabled sim-card protection? That's not good...
Click to expand...
Click to collapse
Well yes. After encrypting the phone I won't get a signal. Seems to be a bug. And another problem arises after phone encryption: The signal is not well. So the phone boosts the mobile connection which drains the battery faster.
shellshocker said:
Well yes. After encrypting the phone I won't get a signal. Seems to be a bug. And another problem arises after phone encryption: The signal is not well. So the phone boosts the mobile connection which drains the battery faster.
Click to expand...
Click to collapse
Have you tried encryption on Berni's unofficial Lineage build?
QWERTYsystems said:
Have you tried encryption on Berni's unofficial Lineage build?
Click to expand...
Click to collapse
No. I think this should work with the official build. I'm not going to flash a different ROM. I'm using this phone daily. So no time for experiments.
Berni-0815 said:
You can only use this rom with disabled sim-card protection? That's not good...
Click to expand...
Click to collapse
Well yes, this is a bug. But not a serious one. What can possibly happen when sim-card protection is disabled? When the phone is locked someone needs my 12 number digit to unlock the phone before he can make a call.
shellshocker said:
Well yes, this is a bug. But not a serious one. What can possibly happen when sim-card protection is disabled? When the phone is locked someone needs my 12 number digit to unlock the phone before he can make a call.
Click to expand...
Click to collapse
Or just put your SIM card in their phone.
Someone is testing LOS 16 on yours Shamu Phone? 15.1 Nightly is a stable build, is it 16 Nightly Build the same?
How should people know this? Lineage-16.0 is out since a few hours.
but since we have this https://github.com/LineageOS/charter/blob/master/device-support-requirements.md you can be shure of a certain quality
Any guidance on moving from 15.1 to 16.0? I assume a clean install is probably a good idea?
Thanks!
-C
First build isn't working properly for me. After flashing it gives me the "Decryption unsuccessful" message. Don't have encryption enabled, and my phone is formatted to ext4. Tried wiping multiple times in different ways. Had been running LOS 15.1 for months with no problems. Clean flash.
Update: Just to see, reinstalled LOS 15 and encrypted my device. Decryption still fails after flashing LOS 16 and trying to boot.
Quade321 said:
First build isn't working properly for me. After flashing it gives me the "Decryption unsuccessful" message. Don't have encryption enabled, and my phone is formatted to ext4. Tried wiping multiple times in different ways. Had been running LOS 15.1 for months with no problems. Clean flash.
Update: Just to see, reinstalled LOS 15 and encrypted my device. Decryption still fails after flashing LOS 16 and trying to boot.
Click to expand...
Click to collapse
I was thinking about flashing back to the last official google release (N6F27M), and then up to 16.0, but was going to wait to see if there was any official recommendation. Kind of a nuke the "site" from orbit approach - "it's the only way to be sure..."
-C
cdaly1970 said:
I was thinking about flashing back to the last official google release (N6F27M), and then up to 16.0, but was going to wait to see if there was any official recommendation. Kind of a nuke the "site" from orbit approach - "it's the only way to be sure..."
-C
Click to expand...
Click to collapse
Yeah, I was thinking about doing that, but just didn't feel like it, and can't imagine how it'd help. Probably just wait a week (probably more) or so for the builds to settle down. They're always pretty unstable at first anyway.
Quade321 said:
First build isn't working properly for me. After flashing it gives me the "Decryption unsuccessful" message. Don't have encryption enabled, and my phone is formatted to ext4. Tried wiping multiple times in different ways. Had been running LOS 15.1 for months with no problems. Clean flash.
Update: Just to see, reinstalled LOS 15 and encrypted my device. Decryption still fails after flashing LOS 16 and trying to boot.
Click to expand...
Click to collapse
Did you follow the instructions on the LOS site? I upgraded from LOS 15.1 to LOS 16 without issues. I wasn't encrypted on LOS 15.1 and still won't because right now that is a headache with TWRP being unable to decrypt.
https://lineageos.org/Changelog-22/
BootloopedMillennials said:
Did you follow the instructions on the LOS site? I upgraded from LOS 15.1 to LOS 16 without issues. I wasn't encrypted on LOS 15.1 and still won't because right now that is a headache with TWRP being unable to decrypt.
https://lineageos.org/Changelog-22/
Click to expand...
Click to collapse
I don't see anything that isn't normal in the instructions. Wipe, flash, done. And also don't know what you mean about TWRP being unable to decrypt. Newest TWRP (been for like 2 years) 3.2.3-0 works fine for me. That's interesting that it works for you though. No clue what's causing my problem.
Also when you say upgrade, do you mean you flashed 16 on top of 15.1? I did a clean flash, wiping everything.
The March 2 build is now booting for me. Noticed some changes to cryptfs in the logs, and sure enough. Now that it's booting, everything actually seems pretty stable.
I also got the "Decryption unsuccessful" on first boot of an upgrade from lineage 15.1
I was eventually able to boot, but had to do a bunch of random button pushing, and ended up nukeing the phone, but eventually got it to boot... But it has several other issues...
I did an "Advanced Wipe" in TWRP, and turned on every checkbox... Cleared every partition... Then did TWRP sideload of:
lineage-16.0-20190302-nightly-shamu-signed.zip
open_gapps-arm-9.0-nano-20190302.zip
Magisk-v18.1.zip
And it still asked for password on first boot... No way to put away the password entry keyboard BTW, preventing you from getting to the "Emergency Call" button... No 911 for you :'(
So I read somewhere that doing a "Format Data" under the TWRP wipe might help...
So I rebooted, did the above steps again, then tried "Format Data" before leaving TWRP... This failed to mount, and so no format... For some reason, I think on my phone I have TWRP on 2 partitions maybe? For some reason, rebooting from inside TWRP to "Recovery" (so yah, load recovery, then reboot directly to recovery) appeared to fix this unable to mount issue...
So now, I again wiped all paritions, sideloaded everything, got the "Format Data" to mount and work, then rebooted...
This booted and presented the initial setup (YAY!!) Went through that, and attempted to do a Google restore of the phone during setup... This looked like it worked, but NOTHING would download (Everything said it was trying to install, but nothing would...)
I am not super knowledgeable about this stuff, but one of my guess-timations of the issue was that it was a storage permission issue... Rebooted to TWRP again, and under Advanced I found something called "Fix Contents" that claimed it would attempt to repair the SELINUX model or something, which sounded permission issue related to me, so I tried that one...
And it booted, and things installed from Google Play (Double YAY!!)
I attempted to setup multiple users, and logging in a second user apparently seems to kill the Software Home Buttons for all users, and only rebooting brings them back for the primary user, and they disappear again when booting a secondary user... Other than this so far it is very fast, really quick, and looks like it has alot of potential as soon as they work out the kinks
P.S. Now I just wish they would un-discontinue Lineage support for the LG V20... Long live Removable Batteries paired with SDCard slot and IR-Blaster for the win!
Is there a way too root yet
I installed the "stock" version of Gapps that came with the pixel launcher. I can only use the Trebuchet launcher because the Pixel Launcher only crashes. Should I have installed a different Gapps version if it is unsupported? Or is this just a bug? Also, the Android Setup wizard keeps crashing when it is checking for an update at the beginning. It will not complete. Other than those issues, everything else seems to be working fine so far.
girkev said:
Is there a way too root yet
Click to expand...
Click to collapse
Yes. Magisk.
nhasian said:
I installed the "stock" version of Gapps that came with the pixel launcher. I can only use the Trebuchet launcher because the Pixel Launcher only crashes. Should I have installed a different Gapps version if it is unsupported? Or is this just a bug? Also, the Android Setup wizard keeps crashing when it is checking for an update at the beginning. It will not complete. Other than those issues, everything else seems to be working fine so far.
Click to expand...
Click to collapse
I am also seeing this problem, as are several others: https://forum.xda-developers.com/nexus-6/help/pixel-launcher-issue-lineage-16-nexus-6-t3906748
I am also facing the problem of the crash of pixel launcher. Does anybody know whether there is a recovery could decrypt the data of Android Pie?
1997cui said:
I am also facing the problem of the crash of pixel launcher. Does anybody know whether there is a recovery could decrypt the data of Android Pie?
Click to expand...
Click to collapse
Do you have a backup of your data? If you do, don't bother trying to decrypt it. Just wipe format your phone and start fresh.
wipe is not enough, must format encrypted partition
Just wanted to clarify that wiping is not sufficient to remove the encrypted partition. it must be formatted from the advanced wipe settings in TWRP.
David B. said:
Do you have a backup of your data? If you do, don't bother trying to decrypt it. Just wipe your phone and start fresh.
Click to expand...
Click to collapse
nhasian said:
Just wanted to clarify that wiping is not sufficient to remove the encrypted partition. it must be formatted from the advanced wipe settings in TWRP.
Click to expand...
Click to collapse
Yes. Sorry. I am aware of this, but used the incorrect terminology. Format was indeed what I had intended to say.
the 1st 16 release my camera did not work but it did on the 2nd nightly. i did today's [mar 6th] update and the camera does not work. info only.
dr1445 said:
the 1st 16 release my camera did not work but it did on the 2nd nightly. i did today's [mar 6th] update and the camera does not work. info only.
Click to expand...
Click to collapse
Usually, a reboot fixes the camera. It seems that on some boots it works and on some it doesn't.
https://forum.xda-developers.com/ne...geos-16-0-nexus-6-shamu-t3906045/post79053994
ok, i will give it a try.
Like for real
I really hope one day we have it for A6+/A6
Because I hate samsung stock fimmware .....
Same here, Because I Hate either.
If you have treble enabled device you can flash it with twrp.
Zirizard said:
If you have treble enabled device you can flash it with twrp.
Click to expand...
Click to collapse
There have been many attempts to flash a GSI (and A6/A6+ do support treble), but the bugs are a bit nasty (lockscreen issues, no voice, no sd card access, etc.)
Though, i just saw that (updated 13 days ago):
https://github.com/phhusson/treble_experimentations/wiki/Samsung-Galaxy-A6-Plus
It claims that most issues are now fixed, barring VoLTE & Fingerprint.
Has anyone tested that?
jcd000 said:
There have been many attempts to flash a GSI (and A6/A6+ do support treble), but the bugs are a bit nasty (lockscreen issues, no voice, no sd card access, etc.)
Though, i just saw that (updated 13 days ago):
https://github.com/phhusson/treble_experimentations/wiki/Samsung-Galaxy-A6-Plus
It claims that most issues are now fixed, barring VoLTE & Fingerprint.
Has anyone tested that?
Click to expand...
Click to collapse
When i had phh's gsi only bug was not working stock cam app and not working front cam. Now i have havoc 2.9 and i dont found any bugs. Lockscreen issue i get when i flash twrp and root my phone, maybe custom kernel fix it :/
Zirizard said:
When i had phh's gsi only bug was not working stock cam app and not working front cam. Now i have havoc 2.9 and i dont found any bugs. Lockscreen issue i get when i flash twrp and root my phone, maybe custom kernel fix it :/
Click to expand...
Click to collapse
Ah, interesting. I will try a variant soon-ish.
jcd000 said:
Ah, interesting. I will try a variant soon-ish.
Click to expand...
Click to collapse
Boot to twrp, click to wipe > advanced wipe. Select system, data, dalvik, cache, internal storage (when i wasn't wipe it, it doesn't start initial setup)
Then click install, find folder with rom, click it and check system image only. When you install it, reboot recovery. Now you can install open gapps (i use pico) and magisk latest version. After that you can reboot system. This works for A6
Zirizard said:
Boot to twrp, click to wipe > advanced wipe. Select system, data, dalvik, cache, internal storage (when i wasn't wipe it, it doesn't start initial setup)
Then click install, find folder with rom, click it and check system image only. When you install it, reboot recovery. Now you can install open gapps (i use pico) and magisk latest version. After that you can reboot system. This works for A6
Click to expand...
Click to collapse
Using A6+ (SM-605FN) here. I also need the dual sim feature as well.
Since i am still on oreo 8.1, i was planning to try the latest AOSP 8.1 & LOS 8.1 GSIs by phh (probably on Sunday)
I will report back here afterwards, specially if results are good.
jcd000 said:
Using A6+ (SM-605FN) here. I also need the dual sim feature as well.
Since i am still on oreo 8.1, i was planning to try the latest AOSP 8.1 & LOS 8.1 GSIs by phh (probably on Sunday)
I will report back here afterwards, specially if results are good.
Click to expand...
Click to collapse
Okay :good:
So.. results:
- phh LOS 8.1 GSI does not boot at all
- phh AOSP 8.1 (arm32-binder64) boots, but the second sim is not detected at all. Don't know how to fix.
- phh AOSP 10 does not boot.
- Havoc does not boot at all (didn't try the boot.img fix)
Back to my stock, rooted, debloated 8.1 i guess. I really hate the samsung & google bloatware / spyware apps. Here's to pinephone!
jcd000 said:
So.. results:
- phh LOS 8.1 GSI does not boot at all
- phh AOSP 8.1 (arm32-binder64) boots, but the second sim is not detected at all. Don't know how to fix.
- phh AOSP 10 does not boot.
- Havoc does not boot at all (didn't try the boot.img fix)
Back to my stock, rooted, debloated 8.1 i guess. I really hate the samsung & google bloatware / spyware apps. Here's to pinephone!
Click to expand...
Click to collapse
I don't have dual sim phone. Mobile data not working, but i fix it with replacing some files from stock. Stock rom is android 9 and havoc 2.9 is android 9 too. When i tried phh aosp android 10, can't boot. But when i tried android 9 it's works.
Btw mobile data is only bug i found. And i tried only these roms (all arm32-binder64 = A64):
- Resurrection remix (Android 9) = can't boot
- Phh's AOSP v201 (Android 10) = can't boot
- Phh's AOSP v119 (Android 9) = Some camera and sim issues
- Havoc 2.9 (Android 9) = No bug
J6 users had the problem with /system/bin/rw_system.sh
Deleting this would make some GSI that were stuck on bootanimation work.
So if you get stuck on bootanimation, delete that file and reboot and see if it works
ShaDisNX255 said:
J6 users had the problem with /system/bin/rw_system.sh
Deleting this would make some GSI that were stuck on bootanimation work.
So if you get stuck on bootanimation, delete that file and reboot and see if it works
Click to expand...
Click to collapse
I deleted it but aex and rr still can't boot.
Btw i tried Lineage 17
Zirizard said:
Btw i tried Lineage 17
Click to expand...
Click to collapse
A6/A6+? Is everything working?
jcd000 said:
- phh AOSP 8.1 (arm32-binder64) boots, but the second sim is not detected at all. Don't know how to fix.
Click to expand...
Click to collapse
Second sim can be toggled by setting persist.radio.multisim.config=dsds
MultiSIM Toggle does it. If there is still no voice over second sim try settings ro.multisim.set_audio_params=true
Zirizard said:
Btw i tried Lineage 17
Click to expand...
Click to collapse
Which Lineage you tried, can you provide me a link?
JasonS. said:
A6/A6+? Is everything working?
Click to expand...
Click to collapse
Yep, only stock camera app not working and gapps. If i flashed beta gapps 10, it wrote to me i have android 8.1 so i flashed 8.1 gapps and it wrote i have android 10. So i edited in install.sh sdk and then it wrote i dont have enought space, after resizing too. Idk how to fix that.
nebkas said:
Which Lineage you tried, can you provide me a link?
Click to expand...
Click to collapse
Treble, download: https://mega.nz/#!FpQ1gKyT!idDcQSgzm3zD0953v1m71UZy3MmoovsmV7Bz8IpXEc0
Fixed magisk: https://mega.nz/#!ZsBXBS5J!r1uknnmBWoh6OFd_z2rxIhKgHofNGml-Vh70m03nSvY
Just flash it like another gsi if you dont know, i put instructions here on previous page.
Zirizard said:
Yep, only stock camera app not working and gapps. If i flashed beta gapps 10, it wrote to me i have android 8.1 so i flashed 8.1 gapps and it wrote i have android 10. So i edited in install.sh sdk and then it wrote i dont have enought space, after resizing too. Idk how to fix that.
Treble, download: https://mega.nz/#!FpQ1gKyT!idDcQSgzm3zD0953v1m71UZy3MmoovsmV7Bz8IpXEc0
Fixed magisk: https://mega.nz/#!ZsBXBS5J!r1uknnmBWoh6OFd_z2rxIhKgHofNGml-Vh70m03nSvY
Just flash it like another gsi if you dont know, i put instructions here on previous page.
Click to expand...
Click to collapse
It would be nice if you post the offiial link and not reupload! Please respect the work from other members!
https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.0/
nebkas said:
It would be nice if you post the offiial link and not reupload! Please respect the work from other members!
https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.0/
Click to expand...
Click to collapse
I posted it because you can download bad file, yes this is unlikely to happen, sorry. And Im not posted ad link
** Standard Disclaimer: Unlocking your Bootloader will Void your Warranty. I take no responsibility for this or for any bricked devices. These thing should go without saying at this point, but there they are. If you are here, I assume you are familiar with LineageOS, TWRP, and moving from MIUI to AOSP-based ROMs**
I've built a clean version of LineageOS 17.1 for Mi 9 that includes Signature Spoofing, but no other modifications.
This will allow those who are interested to get full MicroG support without the need of using any sort of Patcher or Magisk/XPosed Module. YOu all may have used my previous LineageOS Clean,Stock ROM and this is just an updated build of that ROM + Signature Spoofing to make life easier for those who want MicroG.
I flashed this and followed the simple steps of installing F-Droid, adding the MicroG Repo, and Installing the necessary packages via F-Droid and confirmed MicroG Self-check passes all the tests (once you finish granting the necessary permissions for each).
I prefer this over the NanoDroid or other patching methods as a much cleaner way to use MicroG with LineageOS.
Proprietary Blobs/Device Tree are DRG-Developer's as referenced in their post: here
Kernel source is by DRG-Developer: here
Xiaomi Hardware package used is the primary LineageOS from their github here
My reason for this is that there does not seem to be an officially-supported build for our device on the LineageOS for MicroG project or a recent, unofficial build.
What Works:
Pretty much everything from what I can tell
Fingerprint Sensor it working like a champ so far.
DT2W/DT2S
NFC Seems to be working but I don't have a device to test against
Known Issues:
You tell me...
Download:
849.98 MB file on MEGA
mega.nz
Prerequisite:
Make sure you are running a current AOSP/MIUI ROM with the latest firmware flashed and TWRP Installed
Install:
From TWRP:
1) Wipe Date (standard wipe)
2) Format Date ---> 'yes'
3) push ROM zip to /sdcard/
4) Flash ROM zip
4b) - OPTIONAL - Flash Magisk Zip for Root
5) Reboot to system
If you want to to install MicroG, just follow the steps outlined here in the "Install" section to get F-Droid installed, add the MicroG Repo, and install the handful of apps needed. No need for any of the patching steps.
DRG-Developer's device trees were last updated on 2020-10-18 so expect this build to reflect that. So far everything seems to function very well.
Does it support GApps too or it's only for MicroG?
Edit:
I test it and It's working well with GApps
Thanks for your build.
Vogie said:
Does it support GApps too or it's only for MicroG?
Edit:
I test it and It's working well with GApps
Thanks for your build.
Click to expand...
Click to collapse
Thanks for testing! If you find any bugs, please post them here. I may not be able to troubleshoot everything but at least other users will be aware.
What changes between your older release of LineageOS 17.1? https://forum.xda-developers.com/t/...ineageos-17-1-clean-stock-2020-07-10.4041523/
ICanTrollU said:
What changes between your older release of LineageOS 17.1? https://forum.xda-developers.com/t/...ineageos-17-1-clean-stock-2020-07-10.4041523/
Click to expand...
Click to collapse
Later/updated device trees and built-in Signature Spoofing that you don't get with stock Lineage.
photonmedia said:
Thanks for testing! If you find any bugs, please post them here. I may not be able to troubleshoot everything but at least other users will be aware.
Click to expand...
Click to collapse
Sure,
I'm using this ROM for daily use since yesterday and seems like very stable since now and battery life is good.
I missed `Internet Band-with Speed indicator` and `three finger swipe screen shot gesture` that I think these features are not available in LineageOS.
Vogie said:
Sure,
I'm using this ROM for daily use since yesterday and seems like very stable since now and battery life is good.
I missed `Internet Band-with Speed indicator` and `three finger swipe screen shot gesture` that I think these features are not available in LineageOS.
Click to expand...
Click to collapse
Yes, I do not believe those are included in stock LineageOS.
photonmedia said:
Yes, I do not believe those are included in stock LineageOS.
Click to expand...
Click to collapse
I didn't find any issue that relate to ROM, it's quite stable
I just have a issue on ANXCamera self camera that force close the ANXCamera that I think is not related to ROM
photonmedia said:
...
What Works:
...
NFC Seems to be working but I don't have a device to test against
Click to expand...
Click to collapse
This morning I checked NFC by sending a picture from my MI 9 to my wife's Mi 9T (also equipped with LOS). The transfer was successfull!
Thank you very much for providing this clean (stock) ROM!
Hi,
I've just unlocked my device and flashed Mauronofrio's TWRP afer that, i've installed this rom. And everytime it seems to be bootlooping. Showing the MI logo and after that it turns off and goes back to the Mi logo again. I've tried flashing it a few times, wiping data / system ETC. At the moment I'm restoring it with flashtool to get it back working. But am I doing something wrong?
nico445 said:
Hi,
I've just unlocked my device and flashed Mauronofrio's TWRP afer that, i've installed this rom. And everytime it seems to be bootlooping. Showing the MI logo and after that it turns off and goes back to the Mi logo again. I've tried flashing it a few times, wiping data / system ETC. At the moment I'm restoring it with flashtool to get it back working. But am I doing something wrong?
Click to expand...
Click to collapse
Did you wipe data AND "Format" Data? When you Format data is asks you to confirm by typing "yes" in the TWRP Recovery. Try Wiping and Formatting data, then push the ROM to the phone and Flash.
Ah that was probably it. ADB Sideload wasn't co-operating so i've flashed the rom first and after that wiped + formatted the data. Thanks! I've just restored the phone but will try this later again.
nico445 said:
Ah that was probably it. ADB Sideload wasn't co-operating so i've flashed the rom first and after that wiped + formatted the data. Thanks! I've just restored the phone but will try this later again.
Click to expand...
Click to collapse
Also, be sure you are coming from an updated ROM running current firmware.
Thank for your build ;-)
Are NFC Payements working on it?
john_matrix said:
Thank for your build ;-)
Are NFC Payements working on it?
Click to expand...
Click to collapse
I have not tested payments. Another user confirmed that file transfer via NFC works. I do not use NFC for payments so cannot test.
Hi, does screen off fod work?
Your rom is really simple stock rom, but there is something that I can't make it work. Waze has been my pain, the map dont load and I cant make it run. Anyway you did a good job. You discovered how can we put updates in the rom?
theandroid02 said:
Hi, does screen off fod work?
Click to expand...
Click to collapse
No, you have to double-tap to wake or hit the power button to wake the screen before you can use the fingerprint scanner.
Vinicius7 said:
Your rom is really simple stock rom, but there is something that I can't make it work. Waze has been my pain, the map dont load and I cant make it run. Anyway you did a good job. You discovered how can we put updates in the rom?
Click to expand...
Click to collapse
After installing, did you Install F-Droid and enable the Magisk repositories to install the necessary Magisk Modules and Location Backends? Then in the MicroG settings ensure all the checkboxes are checked?
Thanks for making this ROM. Really appreciate it.
The only small issue I am noticing is that my finance apps (example: banking apps, stock trading apps) popup an alert saying that my device is rooted (even though it is not) and this could be a security risk. The apps do still function but its a bit annoying to see this alert every time I launch the app.
Is this because the ROM has been signed with public keys? This alert does not appear when I used the iode OS ROM for Mi 9 or when I use the official Lineage OS for MicroG ROM on my Mi 8.
dmahtani said:
Thanks for making this ROM. Really appreciate it.
The only small issue I am noticing is that my finance apps (example: banking apps, stock trading apps) popup an alert saying that my device is rooted (even though it is not) and this could be a security risk. The apps do still function but its a bit annoying to see this alert every time I launch the app.
Is this because the ROM has been signed with public keys? This alert does not appear when I used the iode OS ROM for Mi 9 or when I use the official Lineage OS for MicroG ROM on my Mi 8.
Click to expand...
Click to collapse
I'm not sure. It could be the Signature Spoofing aspect. I don't think iode has that and I know stock LIneage does not.
Do you have Magisk installed?