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.
Related
I have had some issues with my phone since unlocking with sunshine. See separate thread http://forum.xda-developers.com/droid-turbo/help/help-bricked-xt1254-unlocking-to-t3279581 for description. I have a theory about this now and would like some opinions from folks with more experience.
I used device encryption on my Turbo before the OTA update to Lollipop. After encrypting the phone I would be prompted to enter my PIN to decrypt the data partition before the phone would boot, and then I'd have to enter the PIN again after boot to unlock it. After the OTA I no longer had to enter my PIN when booting the phone, but I would still have to enter it after boot to unlock. After the OTA the phone still reported that it was encrypted in the system security settings even though it didn't need a PIN to decrypt at boot time. That makes sense from what little I know because encrypting the device re-writes the data partition, and the OTA didn't touch the data partition and could not un-encrypt it. I was baffled by this, but I didn't want to factory reset and wipe the data partition to let me re-encrypt the phone.
So after the OTA, the data partition of my phone was still encrypted, but magically the phone was able to decrypt data and boot without my PIN. I don't know why. But one clue is that after unlocking and installing TWRP I looked at TWRP log and saw a log message saying something about decrypting with default PIN. Anyway, I never wiped data, but my phone somehow manages to boot. Re-flashing system and recovery caused problems at first, but now it seems to be back to the way it was. I haven't flashed a new ROM yet, but I expect that when I do I'll have to wipe data and that will get everything back to normal.
My question is has anyone else experimented with device encryption and is this behavior expected?
Thanks.
Not having to enter a PIN with the factory image was a bug I initially discovered, and reported, during the *initial* Android L SOAK test. Needless to say, they never fixed the bug (plus one of the Stagefright CVEs) during the second SOAK rollout. I reported it then, too. They did nothing. That second SOAK was the straw that broke the camel's back, for me. I will never participate in another.
As far as this bug goes, what I would do, is an FDR, and re-encrypt your device to wipe the key store and start over.
Sent from my DROID Turbo via Tapatalk. Now with that cyanogenmod goodness.
I got notifications that the SU4TL-49 OTA was ready to install on my phone, and I had read that if you try to install it with anything but stock recovery that you get into a boot loop. I figured it was a matter of time before I ended up accidentally installing the OTA upgrade and so decided to wipe my phone and go back to stock, and I would use that opportunity to re-encrypt the phone. It took me a couple of tries before I discovered that factory reset isn't enough to remove the encryption, and that I had to reformat the data partition. This took a few hours of going back and forth between reverting to stock, upgrading, rooting, configuring and starting over before I finally got it right, but eventually the phone said that it wasn't encrypted and gave me the option to encrypt. What a pain. After setting up all my apps for the third or fourth time I thought I was done. Whenever I rebooted I was prompted for my PIN before android booted. I even had to enter my PIN to run TWRP.
At least that's the way it was for a few hours. Now when I reboot it just starts up android with no password again. All the effort to un-encrypt and re-encrypt seems to have been a waste. Oh well, at least I avoided getting into boot loop hell.
Hopefully this unencrypting without requiring password/PIN thing gets fixed when (if) they come out with M for the turbo.
This just keeps getting better and better. I decided to flash the Unofficial CM13 ROM this afternoon just for fun. I got it all set up when I found that the GPS receiver wasn't working. Searching the thread I found a link to a flash-able radio image to fix that, and when I rebooted to TWRP it prompted me for a password to decrypt the data partition! Unfortunately it didn't like my PIN no matter how many times I entered it. I don't know if there's something about entering a numerical PIN on the qwerty keyboard, but it had worked earlier in the day before it stopped prompting for passwords. After a bunch of tries and reboots I gave up and downloaded a fastboot flashable version of the same. I've spent most of the day screwing around with this phone already and I'm not going to reformat the data partition again today for sure! Maybe it just needs a good night's sleep.
Astrobrewer said:
This just keeps getting better and better. I decided to flash the Unofficial CM13 ROM this afternoon just for fun. I got it all set up when I found that the GPS receiver wasn't working. Searching the thread I found a link to a flash-able radio image to fix that, and when I rebooted to TWRP it prompted me for a password to decrypt the data partition! Unfortunately it didn't like my PIN no matter how many times I entered it. I don't know if there's something about entering a numerical PIN on the qwerty keyboard, but it had worked earlier in the day before it stopped prompting for passwords. After a bunch of tries and reboots I gave up and downloaded a fastboot flashable version of the same. I've spent most of the day screwing around with this phone already and I'm not going to reformat the data partition again today for sure! Maybe it just needs a good night's sleep.
Click to expand...
Click to collapse
Encryption is totally broken on CM13. The issue is that our version of TWRP cannot decrypt it. I contacted the maintainer of TWRP for our device about this issue and he said that he tried to fix the issue, but he failed.
Also, official CM13 has been out for a while now for the Turbo. No need to go with the unofficial version.
Thanks for the info @TheSt33v, but I'm not sure that it's totally broken.
The strange thing is that I was using TWRP 3.0.2 just fine after encrypting phone while on stock ROM, and it worked for a while even after flashing CM13. Then it just stopped liking my PIN. But CM13 takes my PIN and decrypts data just fine. So my phone is usable for now, and the problem of it decrypting without asking for a PIN is solved for now. I just went to cyanogenmod and see that there's a CM13 recovery. Based on your post I'm guessing that's what is broken, so no point in flashing that. Oh well, at least my phone is secure.
Astrobrewer said:
Thanks for the info @TheSt33v, but I'm not sure that it's totally broken.
The strange thing is that I was using TWRP 3.0.2 just fine after encrypting phone while on stock ROM, and it worked for a while even after flashing CM13. Then it just stopped liking my PIN. But CM13 takes my PIN and decrypts data just fine. So my phone is usable for now, and the problem of it decrypting without asking for a PIN is solved for now. I just went to cyanogenmod and see that there's a CM13 recovery. Based on your post I'm guessing that's what is broken, so no point in flashing that. Oh well, at least my phone is secure.
Click to expand...
Click to collapse
Just FYI, our TWRP maintainer has fixed decryption. You can get the latest version here: https://www.androidfilehost.com/?w=files&flid=39562 (version 3.0.2-0 mod 02 as of this writing). I still had trouble decrypting a partition that was previously formatted using the stock recovery menu, but once I formatted the data partition using this version of TWRP and re-encrypted, it decrypted fine.
TheSt33v said:
Just FYI, our TWRP maintainer has fixed decryption...
Click to expand...
Click to collapse
Yes they have fixed it! I found TWRP Mod 2 over the weekend and saw from the change log that decryption was fixed. I flashed it and it works great. No problems decrypting my previously encrypted data partition since I flashed mod 2. The funny thing about it is that basic TWRP 3.0.2 (no mod) worked well enough for long enough for me to flash CM13, and it even seemed to work for a little while after that. But then it decided that it didn't know how to decrypt my phone anymore and I was stuck until Mod 2. I can't explain why it worked for a while and then stopped, but I'm very happy that mod 2 fixed it.
Thanks for your help and support. Sometimes I feel like I'm the only user who encrypts his phone. There don't seem to be a lot of threads about encryption/decryption issues.
Astrobrewer said:
Yes they have fixed it! I found TWRP Mod 2 over the weekend and saw from the change log that decryption was fixed. I flashed it and it works great. No problems decrypting my previously encrypted data partition since I flashed mod 2. The funny thing about it is that basic TWRP 3.0.2 (no mod) worked well enough for long enough for me to flash CM13, and it even seemed to work for a little while after that. But then it decided that it didn't know how to decrypt my phone anymore and I was stuck until Mod 2. I can't explain why it worked for a while and then stopped, but I'm very happy that mod 2 fixed it.
Thanks for your help and support. Sometimes I feel like I'm the only user who encrypts his phone. There don't seem to be a lot of threads about encryption/decryption issues.
Click to expand...
Click to collapse
Most people don't seem to think it's worth the impact that it has on performance.
I was worried about the performance hit too before I tried it. But I don't notice any real difference in performance. Of there is a hit it's too small for me to tell.
Sent from my DROID Turbo using XDA-Developers mobile app
Astrobrewer said:
I was worried about the performance hit too before I tried it. But I don't notice any real difference in performance. Of there is a hit it's too small for me to tell.
Sent from my DROID Turbo using XDA-Developers mobile app
Click to expand...
Click to collapse
This is a very interesting thread. I would like to encrypt so I can setup my work exchange email as its a requirement. Just to clarify what is the order to do this in? Currently I am running RR 6.01 but have run CF's 1.3.6 ROM most of the time as its awesome.
Can I encrypt using RR or do I need to switch back to CFs ROM or to stock Lollipop after installing the upgraded TWRP in place of the standard version I am running now?
thanks for the help and information.
oldidaho said:
This is a very interesting thread. I would like to encrypt so I can setup my work exchange email as its a requirement. Just to clarify what is the order to do this in? Currently I am running RR 6.01 but have run CF's 1.3.6 ROM most of the time as its awesome.
Can I encrypt using RR or do I need to switch back to CFs ROM or to stock Lollipop after installing the upgraded TWRP in place of the standard version I am running now?
thanks for the help and information.
Click to expand...
Click to collapse
You can encrypt on RR. Just make sure you're running TWRP version 3.0.2-0 mod 2: https://www.androidfilehost.com/?w=files&flid=39562
If encryption fails, you'll need to format your data partition (aka do a factory reset) using this version of TWRP. Then it will work.
TheSt33v said:
You can encrypt on RR. Just make sure you're running TWRP version 3.0.2-0 mod 2: https://www.androidfilehost.com/?w=files&flid=39562
If encryption fails, you'll need to format your data partition (aka do a factory reset) using this version of TWRP. Then it will work.
Click to expand...
Click to collapse
thanks so much for the clarification! Being encrypted, how does that affect installing future updates or restores? Can I still flash ROMS and other ZIPS from TWRP the same as now?
oldidaho said:
thanks so much for the clarification! Being encrypted, how does that affect installing future updates or restores? Can I still flash ROMS and other ZIPS from TWRP the same as now?
Click to expand...
Click to collapse
The only difference is that you'll have to enter your password/pin every time you boot twrp. Don't try to use a pattern lock. Everything else will be the same.
TheSt33v said:
The only difference is that you'll have to enter your password/pin every time you boot twrp. Don't try to use a pattern lock. Everything else will be the same.
Click to expand...
Click to collapse
thank you for the help! I was able to encrypt my RR MM install without having to wipe the data partition. It now prompts me to put my PIN in when booting up and when going into the modded version of TWRP. It then is able to decrypt the partition in TWRP so as you said just like before. Only difference is a little longer boot up time. Performance seems the same to me.
oldidaho said:
thank you for the help! I was able to encrypt my RR MM install without having to wipe the data partition. It now prompts me to put my PIN in when booting up and when going into the modded version of TWRP. It then is able to decrypt the partition in TWRP so as you said just like before. Only difference is a little longer boot up time. Performance seems the same to me.
Click to expand...
Click to collapse
Guess I spoke too soon. phone was working fine for a day. Yesterday at work I'm looking at my phone as it reboots on its own (just sitting there). I then get cant decrypt partition message. Cant do anything and it wont boot up into the OS WO giving this error. In TWRP still cant do anything because it cant decript the partition. So I formatted the data partition and started over. I had saved a recent backup to my PC so I was able to get back to that. Now running CFs latest instead of RR. I need my phone, cant take a chance on this happening again as I was instantly dead in the water. Just wont encrypt.
oldidaho said:
This is a very interesting thread. I would like to encrypt so I can setup my work exchange email as its a requirement. Just to clarify what is the order to do this in? Currently I am running RR 6.01 but have run CF's 1.3.6 ROM most of the time as its awesome.
Can I encrypt using RR or do I need to switch back to CFs ROM or to stock Lollipop after installing the upgraded TWRP in place of the standard version I am running now?
thanks for the help and information.
Click to expand...
Click to collapse
oldidaho said:
thank you for the help! I was able to encrypt my RR MM install without having to wipe the data partition. It now prompts me to put my PIN in when booting up and when going into the modded version of TWRP. It then is able to decrypt the partition in TWRP so as you said just like before. Only difference is a little longer boot up time. Performance seems the same to me.
Click to expand...
Click to collapse
oldidaho said:
Guess I spoke too soon. phone was working fine for a day. Yesterday at work I'm looking at my phone as it reboots on its own (just sitting there). I then get cant decrypt partition message. Cant do anything and it wont boot up into the OS WO giving this error. In TWRP still cant do anything because it cant decript the partition. So I formatted the data partition and started over. I had saved a recent backup to my PC so I was able to get back to that. Now running CFs latest instead of RRI need my phone, cant take a chance on this happening again as I was instantly dead in the water. Just wont encrypt.
Click to expand...
Click to collapse
Well, just as you used CM13 Marshmallow and RR Marshmallow just fine without encryption, not sure why you went to CF Lollipop instead of RR just because encryption didn't work. It just seems you were implying it's CM13 or RR at fault when you used them just fine before, and even now on CF you are NOT using encryption.
But it's your phone, so you can run what you want.
I do commend you for having a recent backup on your PC.
ChazzMatt said:
Well, just as you used CM13 and RR just fine without encryption, not sure why you went to CF instead of RR just because encryption didn't work. But it's your phone.
Just not sure why you are implying it's CM13 or RR at fault when you used them just fine before, and even now on CF you are NOT using encryption.
I do commend you for having a recent backup on your PC.
Click to expand...
Click to collapse
I should have clarified, I dont think RR had anything to do with my issue. I actually really liked RR, it has some great features, great performance and good battery life too. I just missed the Moto features in the stock and CFs ROMs.
oldidaho said:
I should have clarified, I dont think RR had anything to do with my issue. I actually really liked RR, it has some great features, great performance and good battery life too. I just missed the Moto features in the stock and CFs ROMs.
Click to expand...
Click to collapse
Strange. I've been using RR M encrypted for several weeks now with no issues. Oh well. If you're happy with modified stock, that's all that matters. You can encrypt that too if you like. I'm a big fan of the Moto features as well, and RR M has basically all of them built in besides Voice (chop chop flashlight was removed for a while, but it has been added back). Although I've never understood what Voice offers that Google Now does not.
Mystery solved!
Astrobrewer said:
... At least that's the way it was for a few hours. Now when I reboot it just starts up android with no password again. All the effort to un-encrypt and re-encrypt seems to have been a waste. Oh well, at least I avoided getting into boot loop hell.
Hopefully this unencrypting without requiring password/PIN thing gets fixed when (if) they come out with M for the turbo.
Click to expand...
Click to collapse
I have been running the CM13 ROM for the past few months and it's been great, but now that Verizon came out with official Marshmallow I decided to go back to a stock-based ROM again because I've been missing VOLTE. So I flashed ComputerFreak274_MM. After flashing and rooting I was back in the stupid state of the phone saying that it was encrypted but booting without a PIN. It seemed unreal that Moto/Verizon would have left this bug in MM too. So I reformatted data, re-flashed and rooted the ROM and tried encrypting. Then I discovered that it won't encrypt if it's rooted. So back to wiping, re-formatting and flashing again, but this time I am able to successfully encrypt before rooting. Success! Now root and start setting up the phone. Now I have to enter my PIN before it will boot into the system or into TWRP. Yay! By now it's 1:00am and I have to be at work early, so I let it sit overnight while my apps download. In the morning I flash SuperSU and notice that I wasn't prompted for a password to decrypt when I booted into TWRP and I wasn't prompted for password when booting system after flashing SuperSU. WTF!!! More time wasted. It seemed that stock ROMs just don't like encryption. :crying:
Anyway, after stewing about it all day I randomly chanced into the solution. In the Security settings menu there's an option under Encryption called "Secure start-up" which only becomes available when phone is encrypted. The Secure start-up options says:
"You can further protect this device by requiring your PIN before it starts up. Until the device starts up, it can't receive calls, messages, or notifications, including alarms. This helps protect data on lost or stolen devices."​Secure start-up defaults to disabled for some reason, and when it's disabled the phone automatically decrypts itself when it boots without requiring PIN entry. So you can encrypt your phone and still be totally unprotected. What a dumb-ass default!
But when I enable Secure start-up then encryption works the way it should -- with phone prompting for PIN before booting. Maybe I just didn't notice it, but I didn't see anything when I encrypted the phone saying to enable Secure start-up to actually protect the phone. I'm guessing that this option was there in Lollipop too; but who knew???
Hi!
I recently bought a Mi Mix and want to flash it with Lineage OS.
I followed all relevant instructions - did unlock the bootloader and so on - but I am not able to install TWRP using ADB and fastboot.
The phone is connecting well in ADB - even the "fastboot flash recovery twrp.img" gets a positive response - all seems to work fine. But after rebooting, I am always confronted with the stock recovery - the flashing so seems not to work out of some reason - TWRP gets removed during the reboot process.
I also tried to first flash and then use the "fastboot boot twrp.img" command. This command starts TWRP, but only in a frozen state - TWRP then starts in a way that you are not able to interact with the interface. Also here - after rebooting the stock recovery is there again. Can someone give me a hint, how to solve this problem?
I am running ADB on a Linux Computer (Debian 9) - dont think, that this might cause issues, but maybe....
The phone runs the MIUI-Version "MIUI Global 9.1 Stable"
It would be great, if someone here could help me out. I am somehow stuck and dont know how to proceed..
Thanks for taking the time!
Best
You can find two compatible versions of TWRP here.
Thanks Gavin!
Just out of curiosity - can you explain me, why the official TWRP Versions are not working and the ones you did post are good?
Best
Heiko
H0707 said:
Thanks Gavin!
Just out of curiosity - can you explain me, why the official TWRP Versions are not working and the ones you did post are good?
Best
Heiko
Click to expand...
Click to collapse
Touch has never worked on the official versions to my knowledge. Even the latest 3.2.1.0 build still has broken touch. It is still usable if you use a USB adapter/mouse, but not via touch.
Dear Gavin! Your TWRP file worked great.
But I have no another issue that seems to be common with the Mi Mix - the media sound is not working anymore. Notification and phone works fine but music and video is gone. I just was reading that you should update the firmware. Are the other files added in the link you did send by chance the relevant firmware files?
Best
H0707 said:
Dear Gavin! Your TWRP file worked great.
But I have no another issue that seems to be common with the Mi Mix - the media sound is not working anymore. Notification and phone works fine but music and video is gone. I just was reading that you should update the firmware. Are the other files added in the link you did send by chance the relevant firmware files?
Best
Click to expand...
Click to collapse
Use 8.1.4 and wipe caches
https://redirect.viglink.com/?forma...://mega.nz/#F!zlJBQJhJ!BJuv0brw0doTafuLTXJATw
Thanks - do I have to wipe cache and dalvik in TWRP before installing?
H0707 said:
Thanks - do I have to wipe cache and dalvik in TWRP before installing?
Click to expand...
Click to collapse
After
I use thishttps://androidfilehost.com/?fid=673368273298927160 TWRP Modified by MrRaines (Highly recommended) and this how to show install twrp on mi mix
gavin19 said:
You can find two compatible versions of TWRP here.
Click to expand...
Click to collapse
I was looking for that as well! Thanks for sharing. I can confirm that this TWRP version works well with the Mi Mix.
Thanks guys - the device works fine now. You saved my day!
There is one thing left. I still cannot initiate TWRP manually - have to use ADB for this. Once TWRP is started, I cannot reach the devices harddisk anymore from my computer. Thats no issue now, but might cause issues in the future. Any idea how to solve this?
Best
H0707 said:
Thanks guys - the device works fine now. You saved my day!
There is one thing left. I still cannot initiate TWRP manually - have to use ADB for this. Once TWRP is started, I cannot reach the devices harddisk anymore from my computer. Thats no issue now, but might cause issues in the future. Any idea how to solve this?
Best
Click to expand...
Click to collapse
Are you encrypted, or maybe you missed a stage when installing,
H0707 said:
Thanks guys - the device works fine now. You saved my day!
There is one thing left. I still cannot initiate TWRP manually - have to use ADB for this. Once TWRP is started, I cannot reach the devices harddisk anymore from my computer. Thats no issue now, but might cause issues in the future. Any idea how to solve this?
Best
Click to expand...
Click to collapse
No. It happened with my device as well. You cannot mount your internal storage on your PC. I've tried many different versions of TWRP and none have allowed access. I'm not quite sure why ... I had other devices in the past and it always worked. On the Mi mix however, it does not. So just turn on your phone and transfer what you need to or adb sideload it.
james1089 said:
Are you encrypted, or maybe you missed a stage when installing,
Click to expand...
Click to collapse
No. I don't believe that he did James. Does it work for you? because it never worked for me either. I've tried all the different versions of TWRP and it didn't do a thing. Also I have no passwords or encryption. I'm sure of this. Maybe I'm also doing something wrong and that's why I can't Mount my internal storage while in TWRP recovery?
I don't use the official TWRP because for some reason the official versions of TWRP offered for the Mi Mix are broken. The touchscreen never works and I don't have an external controller or anything else to make it work other than the phones screen. So I've used the custom versions that have been fixed and re-released on XDA.
malimt said:
No. It happened with my device as well. You cannot mount your internal storage on your PC. I've tried many different versions of TWRP and none have allowed access. I'm not quite sure why ... I had other devices in the past and it always worked. On the Mi mix however, it does not. So just turn on your phone and transfer what you need to or adb sideload it.
No. I don't believe that he did James. Does it work for you? because it never worked for me either. I've tried all the different versions of TWRP and it didn't do a thing. Also I have no passwords or encryption. I'm sure of this. Maybe I'm also doing something wrong and that's why I can't Mount my internal storage while in TWRP recovery?
I don't use the official TWRP because for some reason the official versions of TWRP offered for the Mi Mix are broken. The touchscreen never works and I don't have an external controller or anything else to make it work other than the phones screen. So I've used the custom versions that have been fixed and re-released on XDA.
Click to expand...
Click to collapse
Well its strange cause there are thousands using it for over a year now. Maybe you have always been encrypted. Which ROM are you using, I mean you haven't still got the vendor fake ROM, any updates?
james1089 said:
Well its strange cause there are thousands using it for over a year now. Maybe you have always been encrypted. Which ROM are you using, I mean you haven't still got the vendor fake ROM, any updates?
Click to expand...
Click to collapse
That's very odd. I'm not quite sure what to tell you. I know for a fact though that my device is not encrypted. I'm currently running RR without any password/pattern. Before installing RR I was on stock OS and still no password/pattern. I live alone and so I don't feel the need to use a password on my phone. So ever since I've purchased this phone I've never had a password on it.
No updates as far as I'm aware on the RR.
Does it Mount for you? If so, what TWRP are you using on your device?
malimt said:
That's very odd. I'm not quite sure what to tell you. I know for a fact though that my device is not encrypted. I'm currently running RR without any password/pattern. Before installing RR I was on stock OS and still no password/pattern. I live alone and so I don't feel the need to use a password on my phone. So ever since I've purchased this phone I've never had a password on it.
No updates as far as I'm aware on the RR.
Does it Mount for you? If so, what TWRP are you using on your device?
Click to expand...
Click to collapse
I've used the same 1 from the beginning, smarty, I just followed the guide in the guide section how to remove vendor ROM. I use Linux it works fine. Everyone thought they had official ROM in the beginning only to find out it was vendor ROM. What about using mtp to send files, maybe that's what I did, can't even remember.
james1089 said:
I've used the same 1 from the beginning, smarty, I just followed the guide in the guide section how to remove vendor ROM. I use Linux it works fine. Everyone thought they had official ROM in the beginning only to find out it was vendor ROM. What about using mtp to send files, maybe that's what I did, can't even remember.
Click to expand...
Click to collapse
Wow. Well you're lucky tbh. I can't seem to figure out why mine doesn't connect. I'm not sure what the difference is between the vendor (ROM) and the "stock" (ROM) - I know I was using the global stable (ROM) that's what my phone first came with and it was running 6.0 MM.
Yes, I have tried to use MTP while in TWRP and it doesn't do anything. My computer does detect something but doesn't show the phone to be connected or anything. I have even tried to mount it in the options but nothing. I know I have all drivers installed and does not make a difference. I'm running Windows 10 not Linux.
malimt said:
Wow. Well you're lucky tbh. I can't seem to figure out why mine doesn't connect. I'm not sure what the difference is between the vendor (ROM) and the "stock" (ROM) - I know I was using the global stable (ROM) that's what my phone first came with and it was running 6.0 MM.
Yes, I have tried to use MTP while in TWRP and it doesn't do anything. My computer does detect something but doesn't show the phone to be connected or anything. I have even tried to mount it in the options but nothing. I know I have all drivers installed and does not make a difference. I'm running Windows 10 not Linux.
Click to expand...
Click to collapse
So does it show up when phone is booted?
james1089 said:
So does it show up when phone is booted?
Click to expand...
Click to collapse
Yes, when it is booted it shows up perfectly, after I switch from "charging to file transfer (MTP)" in the status bar.
malimt said:
Yes, when it is booted it shows up perfectly, after I switch from "charging to file transfer (MTP)" in the status bar.
Click to expand...
Click to collapse
I'm going to try when I get home, it's been do long since I tried something like that, have you ticked and then unticked mount in read only. Then reboot to recovery again.
I've got the stock Oreo for H870 now in a state where it doesn't crashs the whole time and most things are working. Fingerprint reader won't recognize your Finger, and USB Debugging isn't working, any other things are working although. The rom is now suited for being a daily driver (Fixed WiFi 3/05/18)
If you could get some logs, that would be extre helpful, so we (EvilHowl, J0sh1x and me) can turn this rom flawless.
Here the rom to download: https://androidfilehost.com/?fid=890278863836283338
How to Install:
Its like any other rom:
Format Data (With the option where you have to type yes)
Wipe System
Wipe Cache
Wipe Dalvik Cache
Flash the Zip File (Oreo_r8.zip)
At the First boot:
- To change language you tap on the first bar
- Setup with Internet, everytime I setupped without Internet connection it caused me a bootloop (In this case Format Data, and reboot to system)
- Don't try to turn on WiFi, this should be fixed in the Rom, but it can cause bootloops if you turn it on
- Don't Download the Bloat apps, they will mostly be in korean
- Some texts can still be korean, just reboot your device
Extra Notes:
The Google Playstore will need some time to search, but it works normally.
If you keep rebooting into TWRP you need to completly power off your Phone (Hold Volume Down and Power button) and get into TWRP with the button combo, and then reboot to system
If you keep having Issues, come to our Telegram Group for better support: https://t.me/joinchat/DpmOZERW3-oD8x9l3jXGxA
It's better to install Gapps the Pico variant so you have a normal loading Playstore (take arm64 8.0.0)
For MTP to work, you must have atleast opened the File Manager once
You can turn Data on/off in the Settings, not in the Quick Settings
The bars on Data aren't accurate
Credits:
@J0SH1X <--- General Help
@EvilHowl <--- General Help
@Rashed97 <--- Built the Kernel
@autoprime <--- provided the kdz
@SGCMarkus <--- Guided me
Great work to all the developers! Will try it out in the weekend.
Thanks
Do I need TWRP installed in order to install it ?
If so can you leave me a link with a good tutorial where i can install it for my 870 because i really want to test this version?
BTW, great work.
Thanks,
David
david196 said:
Do I need TWRP installed in order to install it ?
If so can you leave me a link with a good tutorial where i can install it for my 870 because i really want to test this version?
BTW, great work.
Thanks,
David
Click to expand...
Click to collapse
https://www.google.de/amp/s/forum.x...fficial-lg-g6-bootloader-unlock-t3614719/amp/
[UPDATE] I just fixed WiFi, new build incoming
Thanks... Download in progress!!!
Fingerprint reader is must have as daily driver. Altho good job, keep it up
Thanks for all the effort.
Do you know if Magisk can be installed?
So finger print is not working?
Brugos27 said:
So finger print is not working?
Click to expand...
Click to collapse
No it doesn't work at the moment.
Thx mate View attachment 4492485
Sent from my LGM-G600L using Tapatalk
Is anybody in the process of porting this over to the us997 or would that be too different of a base OS for that to even be possible?
ScottThijs said:
Thanks for all the effort.
Do you know if Magisk can be installed?
Click to expand...
Click to collapse
Yes, it can be installed normally
BigBrad75 said:
Is anybody in the process of porting this over to the us997 or would that be too different of a base OS for that to even be possible?
Click to expand...
Click to collapse
I can port it tomorrow to US997 (maybe even H872)
AquaSize said:
I can port it tomorrow to US997 (maybe even H872)
Click to expand...
Click to collapse
Dude I would totally hit the thumbs up 100x on that post if it would let me.... That's great news, and I cant even begin to express how thankful I am, and I know others surely will be as well! Thank u
How can i have the data mobile toggle? I have the "roaming" toggle..no data mobile
Okay so I installed it yesterday, (on my H870) the ROM works very fluid, had no fc, overal performance great. Daily driver worthy.
Only issue I got was that the rom said my sd card was corrupted and should format it. Any one else got this problem?
Anyway, big thanks to the devs who make it possible to get it working on the H870, keep up the great work ??
mksail said:
How can i have the data mobile toggle? I have the "roaming" toggle..no data mobile
Click to expand...
Click to collapse
You can't deactivate the data on the Quick Settings, just in the normal Settings
ScottThijs said:
Okay so I installed it yesterday, (on my H870) the ROM works very fluid, had no fc, overal performance great. Daily driver worthy.
Only issue I got was that the rom said my sd card was corrupted and should format it. Any one else got this problem?
Anyway, big thanks to the devs who make it possible to get it working on the H870, keep up the great work
Click to expand...
Click to collapse
This happens quite often, actually its not corrupted, you can still access it
AquaSize said:
This happens quite often, actually its not corrupted, you can still access it
Click to expand...
Click to collapse
How can I acces it? It won't show up in the file manager.
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.
** 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?